transportation modeler 9.0.0.0 getting started guide

Getting Started Guide JDA® Transportation Modeler

Release 9.0.0.0

Legal notice Rights to the content of this document

Copyright © 1995-2015 JDA Software Group, Inc. All rights reserved.

Printed in the United States of America.

Reproduction of this document or any portion of it, in any form, without the express written consent of JDA Software Group, Inc. ("JDA") is prohibited.

These materials are protected by the Copyright Act of 1976, as amended, as an unpublished work and the foregoing notice and legend shall not be deemed to constitute publication or an intent to publish thereunder. These materials are proprietary and confidential information of JDA and may be disclosed and used only as authorized in a signed, written agreement controlling such disclosure or use.

The fact that a particular name or logo does not appear on this notice does not constitute a waiver of any intellectual property rights that JDA has established in any of its products, feature or service names, or logos.

Modifications to the contents of this document

JDA reserves the right, at any time and without notice, to change these materials or any of the functions, features, and specifications of any of the software described herein. JDA shall have no warranty obligation with respect to these materials of the software described herein, except as provided in the JDA software license agreement with an authorized licensee.

Rights to the functionality of this document

Described functionality may not be available as part of a customer's maintenance agreement or the JDA Investment Protection Program. New features and products are subject to license fees. JDA warranty and support obligations apply only to the documentation as delivered by JDA, and are void if the documentation is modified or supplemented by anyone other than JDA. This document embodies JDA valuable trade secrets, is confidential to JDA, and must be kept in confidence and returned upon the expiration or termination of your JDA license agreement. You are not permitted to copy, extract, distribute, transfer, or share the contents of this document with anyone except authorized individuals within your organization.

Technical documentation

NOTICE: This design or technical documentation is supplied as a courtesy only and does not form part of the "Documentation" as defined in your JDA license agreement. This design or technical documentation is supplied in the English language only and is supplied "as is" and without warranties. JDA, at its discretion, may choose to offer this document in additional languages, but is under no obligation to do so. JDA undertakes no obligation to update this design or technical documentation.

Patents

This product may be protected by one or more United States and foreign patents. Please see the JDA Patents website (http://jda.com/JDAPatents).

http://jda.com/JDAPatents

Provide feedback on this document JDA values your opinion and strives to ensure that the documentation you receive is clear, concise, and provides the appropriate information required for you to use each JDA application efficiently.

If you would like to provide feedback on this document, you can submit your questions or suggestions to the JDA Documentation Management team (mailto:[email protected]) and they will be forwarded to the appropriate development teams for review and consideration in a future release.

mailto:[email protected]

Table of Contents

Chapter 1. Introduction ................................................................................................... 1 Use Transportation Modeler ......................................................................................... 1

Transportation Modeler process ........................................................................... 2 Analyze data using Transportation Modeler ........................................................... 2 Start Transportation Modeler .............................................................................. 3 Exit Transportation Modeler ................................................................................ 3

Modeling exercise overview ......................................................................................... 3 Related documentation ............................................................................................... 4 Get additional help from JDA ....................................................................................... 5

Chapter 2. Graphical user interface ................................................................................. 7 Ribbon ..................................................................................................................... 7

File menu ........................................................................................................ 7 Home tab ........................................................................................................ 8 View tab ........................................................................................................ 10 Map tab ......................................................................................................... 12

Quick access toolbar ................................................................................................ 13 Keyboard shortcuts ......................................................................................... 13 Customize keyboard shortcuts .......................................................................... 14

Shortcut menus ....................................................................................................... 15 Control center ......................................................................................................... 15

Customize the Favorites section ........................................................................ 15 Customize the control center sections ................................................................ 16 Dock or undock the control center ..................................................................... 16 Manage data through the Control Center ............................................................ 16

Status bar .............................................................................................................. 17 Editable and non-editable fields ................................................................................. 17 Menu buttons .......................................................................................................... 18

Chapter 3. Truckload modeling exercise ........................................................................ 19 Model description ..................................................................................................... 19

Shipments ..................................................................................................... 19 Rates ............................................................................................................ 20 Analysis overview ........................................................................................... 20

Chapter 4. Create the TL rates with the Access Rating Tool spreadsheet ....................... 22 Rating tool overview ................................................................................................ 22 Create required tariffs .............................................................................................. 22

Create a TL Tariff ............................................................................................ 22 Create the remaining lanes ............................................................................... 25 Create the charge for stops .............................................................................. 27

Convert the data to a rating database ......................................................................... 28 Convert the excel data to a rating database ........................................................ 28

Set the base currency .............................................................................................. 28 Specify the base currency ................................................................................ 28

Acceptable field values ............................................................................................. 29 View the acceptable field values in the Access database ........................................ 29

Chapter 5. Create locations and shipments .................................................................... 33 Understand Transportation Modeler data ..................................................................... 33

Scenarios ....................................................................................................... 33 Entities .......................................................................................................... 33 Create locations .............................................................................................. 34 Modify location records .................................................................................... 34

Create shipments .................................................................................................... 38 Create the Shipment records ............................................................................ 38

Modify shipment records ........................................................................................... 38 Set the display order ....................................................................................... 38 Add shipment data .......................................................................................... 39

Save scenario ......................................................................................................... 39

Chapter 6. Set solver options ......................................................................................... 40 Access values in the Solver Options dialog box ............................................................. 40

Edit Solver options .......................................................................................... 40 Required values for Solver settings .................................................................... 40 Save solver options ......................................................................................... 44 Load solver options ......................................................................................... 45

Chapter 7. Baseline parameter and strategy file ............................................................ 46 The Baseline parameters .......................................................................................... 46

Use the Parameter File Editor to edit the Parameters File ...................................... 46 Required values for the Parameter file ................................................................ 47

Baseline Strategy file ............................................................................................... 48 Study the Baseline Strategy file ........................................................................ 48

Edit a strategy file ................................................................................................... 50 Open a strategy file for editing .......................................................................... 50 Use the Line Editor and Required Parameters ...................................................... 51

Chapter 8. Solve and analyze the baseline scenario ...................................................... 53 Solve the scenario ................................................................................................... 53

Validate the scenario ....................................................................................... 53 Optimize your scenario .................................................................................... 53

Analyze the results .................................................................................................. 54 View data in maps ................................................................................................... 54 Map view ................................................................................................................ 55

Define map zones ........................................................................................... 55 Create a map view .......................................................................................... 55 Set map view display properties ........................................................................ 56 Save a map view ............................................................................................ 57 Open an existing map view ............................................................................... 57 Set map view options ...................................................................................... 58 Location and hub options ................................................................................. 58

Chapter 9. Tuning parameters and strategies ................................................................ 60 Tuning analysis ....................................................................................................... 60 Solve and Analyze ................................................................................................... 61

Chapter 10. Tuning and solving multi-pick/multi-drop scenario .................................... 63 Tuning to support multi-picks .................................................................................... 63 Solve and analyze for multi-picks ............................................................................... 63 Final strategy tuning ................................................................................................ 64

Save the scenario ........................................................................................... 64

Chapter 11. LTL modeling exercise ................................................................................ 65 LTL software requirements ........................................................................................ 65 Model description ..................................................................................................... 65

Shipments ..................................................................................................... 65 Rates ............................................................................................................ 65 Analysis Overview ........................................................................................... 66

Chapter 12. Create LTL shipments ................................................................................. 67 Open an existing scenario ......................................................................................... 67 Create additional locations ........................................................................................ 67

Create the new location records ........................................................................ 67 Modify the new location records ................................................................................. 67

Add the location data ....................................................................................... 67 Use data utilities to populate Lat/Lon and postal code information .......................... 68

Create LTL shipments ............................................................................................... 68 Create the LTL Shipment records ....................................................................... 69

Modify the LTL shipment records ................................................................................ 69 Add the LTL shipment data ............................................................................... 69

Save the scenario .................................................................................................... 69

Chapter 13. Create the LTL rates ................................................................................... 70 Create required tariffs .............................................................................................. 70

Update the TL tariffs ........................................................................................ 70 Creating an LTL Tariff ...................................................................................... 70

Chapter 14. Solve the LTL scenario ................................................................................ 74 Tune to support LTL Shipments.................................................................................. 74

Rating Engine changes ..................................................................................... 74 Solve and analyze for LTL ......................................................................................... 74

Chapter 15. Hub modeling exercise ............................................................................... 76 Model description ..................................................................................................... 76

Hub .............................................................................................................. 76 Rates ............................................................................................................ 76 Analysis overview ........................................................................................... 76

Chapter 16. Create the hub ............................................................................................ 78 Open an existing scenario ......................................................................................... 78

Open the existing scenario ............................................................................... 78 Create the hub ........................................................................................................ 78

Create the new hub record ............................................................................... 78 Modify the new hub records ...................................................................................... 78

Add the hub data ............................................................................................ 78 Use data utilities to populate Lat/Lon information ......................................................... 79

Load data utility tables .................................................................................... 79 Set the lat/lon ................................................................................................ 79

Save the scenario .................................................................................................... 79 Save the scenario ........................................................................................... 79

Chapter 17. Create the hub rates ................................................................................... 80 Create the hub record .............................................................................................. 80

Create the hub ............................................................................................... 80 Create required rates ............................................................................................... 82

Create the TL Rates for the Hub ........................................................................ 82 Create the remaining lanes ............................................................................... 85

Chapter 18. Solve the hub scenario ............................................................................... 87 Tuning to support hubs ............................................................................................. 87

Initial strategy file changes for hubs .................................................................. 87 Split the remaining shipments ........................................................................... 88

Improve the hub model ............................................................................................ 88 Create an initial unconsolidated plan .................................................................. 88 Create the hub assignment plan ........................................................................ 88 Create the original consolidation plans ............................................................... 89 Use the stack to merge plans ............................................................................ 89 Analyze the results .......................................................................................... 91 Assess increase in the cross dock charge ............................................................ 92

Chapter 19. Continuous move modeling exercise .......................................................... 93 Model description ..................................................................................................... 93

Shipments ..................................................................................................... 93 Rates ............................................................................................................ 93 Analysis overview ........................................................................................... 93

Chapter 20. Create backhaul shipments ........................................................................ 95 Open an existing scenario ......................................................................................... 95

Open the existing scenario ............................................................................... 95 Create the backhaul shipments .................................................................................. 95

Create the backhaul shipment records ................................................................ 95 Modify the backhaul shipment records ........................................................................ 95

Add the backhaul shipment data ....................................................................... 95 Save the scenario .................................................................................................... 96

Save the scenario ........................................................................................... 96

Chapter 21. Create the continuous move rates .............................................................. 97 Create required tariffs .............................................................................................. 97

Create the tariff .............................................................................................. 97 Create the remaining Lanes ............................................................................ 100 Update the cross dock charge ......................................................................... 101

Chapter 22. Solve the continuous move scenario ........................................................ 103 Tuning to support continuous moves ........................................................................ 103

Initial strategy file Changes for continuous moves ............................................. 103 Solve the model and save the optimization log .................................................. 103

Improve the continuous move model ........................................................................ 104 Examine the hub assignment .......................................................................... 104 Solve the model and save the optimization log .................................................. 104

Filter to exclude new shipments ............................................................................... 104 Solve the model and save the optimization log .................................................. 105

BONUS: Tuning the use of FilterState ....................................................................... 105

Chapter 23. Equipment domicile modeling exercise ..................................................... 107 Model description ................................................................................................... 107

Scenario Data ............................................................................................... 107 Rates .......................................................................................................... 107 Analysis Overview ......................................................................................... 107

Chapter 24. Create domicile ........................................................................................ 109 Open an existing scenario ....................................................................................... 109

Open the existing scenario, do the following ..................................................... 109 Create the domicile and exclude shipments ............................................................... 109

Create the new Carrier record ......................................................................... 109 Create the new Equipment Type record ............................................................ 109 Create the new Domicile record ....................................................................... 110 Exclude shipments not required ...................................................................... 110

Save the scenario .................................................................................................. 110

Chapter 25. Create the rates for the domicile exercise ................................................ 111 Create the dedicated carrier rates ............................................................................ 111

Create the rates for the dedicated carrier ......................................................... 111

Chapter 26. Solve the domicile scenario ...................................................................... 115 Initial strategy file for domiciles ............................................................................... 115

Solve the model and save the optimization log .................................................. 115 Create and test alternate domiciles .......................................................................... 116

Create the alternate Fort Wayne domicile ......................................................... 116 Solve with both domiciles ............................................................................... 117 Create the alternate Louisville domicile ............................................................ 117

Introduce the common carrier to the scenario ............................................................ 119 Create the lanes from the origins to destinations ............................................... 119 Create the lanes to and from the Fort Wayne hub .............................................. 121 Create the stop charge .................................................................................. 122 Create the hub ............................................................................................. 123 Include only the Pittsburgh domicile ................................................................ 124 Solve the model with the Pittsburgh domicile and save the optimization log ........... 124 Improve the Solution ..................................................................................... 125

Chapter 27. Carrier equipment availability modeling exercise ..................................... 127 Model description ................................................................................................... 127

Scenario data ............................................................................................... 127 Parameter values .......................................................................................... 127 Rates .......................................................................................................... 127 Constraints .................................................................................................. 127 Analysis overview ......................................................................................... 128

Chapter 28. Create the carrier equipment availability scenario ................................... 129 Open an existing scenario ....................................................................................... 129

Open the existing scenario ............................................................................. 129 Update the shipment IDs ........................................................................................ 129

Update the Shipment IDs ............................................................................... 129 Edit Optimizer Parameters file ......................................................................... 129

Set the domiciles ................................................................................................... 130 Exclude all but the Pittsburgh domicile ............................................................. 130

Save the Scenario .................................................................................................. 130

Save the scenario ......................................................................................... 130

Chapter 29. Update the rates for the CEA exercise ...................................................... 131 Update the dedicated carrier rates ........................................................................... 131

Update the rates for the dedicated carrier ......................................................... 131 Update the cross dock charge on the hub .................................................................. 131

Update the cross dock charge ......................................................................... 131 Verify the tariff IDs ................................................................................................ 131

Determine the Tariff IDs ................................................................................ 131

Chapter 30. Create the carrier equipment availability constraints ............................... 133 Open an existing scenario ....................................................................................... 133

Open an existing scenario .............................................................................. 133 Create the constraints ............................................................................................ 133

Create the required carrier records .................................................................. 133 Create the required carrier availability records .................................................. 133 Update the carrier availability records with the constraints .................................. 133


Chapter 31. Solve the CEA Scenario ............................................................................. 135 Initial Strategy File for Carrier Equipment Availability .................................................. 135

Solve the model ............................................................................................ 136 Adjust penalties to deliver shipments ........................................................................ 136

Update the PenaltyShipmentNotDelivered ......................................................... 137 Solve the model ............................................................................................ 137

Add Domicile Resource Constraints ........................................................................... 137 Update the domicile resource constraint ........................................................... 137

Add Tariff Service Constraints .................................................................................. 138 Create the required tariff records .................................................................... 138 Create the required service record ................................................................... 138 Create the tariff service availability records ....................................................... 138 Update the tariff service availability record ....................................................... 139

Chapter 32. Dock scheduling modeling exercise .......................................................... 140 Model description ................................................................................................... 140

Scenario data ............................................................................................... 140 Parameter values .......................................................................................... 140 Rates .......................................................................................................... 141 Constraints .................................................................................................. 141 Analysis overview ......................................................................................... 141

Chapter 33. Create the dock scheduling scenario ........................................................ 142 Open the existing scenario ...................................................................................... 142 Remove the constraints and domiciles ...................................................................... 142

Remove the constraints ................................................................................. 142 Exclude the domiciles .................................................................................... 142 Edit optimizer parameters file ......................................................................... 143

Create the dock ..................................................................................................... 143 Create the dock ............................................................................................ 143 Create the dock at facility records ................................................................... 144 Set the type of dock ...................................................................................... 144


Chapter 34. Solve the dock scheduling scenario .......................................................... 145 Initial strategy file for dock scheduling ...................................................................... 145

Solve the model ............................................................................................ 145 Adjust the business hours at the dock ....................................................................... 146

Create the business hours .............................................................................. 146 Create the time windows for the business hours ................................................ 146 Set the time window ...................................................................................... 146 Assign the business hours to the dock and verify ............................................... 146

Set the time windows on the shipments .................................................................... 147 Set the shipment time windows ....................................................................... 147

Add multiple docks per location ............................................................................... 148 Create the dock ............................................................................................ 148 Create the dock at facility records ................................................................... 148 Set the type of dock ...................................................................................... 148 Create the business hours .............................................................................. 148 Create the time windows for the business hours ................................................ 148 Set the time window ...................................................................................... 149 Set the business hours at the docks ................................................................. 149

Enable the dock report ........................................................................................... 149 Enable the dock schedule report ...................................................................... 149

Restrict freight classes at the docks .......................................................................... 150 Create the commodities ................................................................................. 150 Set the commodity code on the shipments ........................................................ 150 Create the dock at facility commodity records ................................................... 150

Limit docks by equipment types ............................................................................... 151 Create the equipment type ............................................................................. 151 Create the dock at facility equipment type records ............................................. 151

Chapter 35. Tractor and Trailer Modeling Exercise ...................................................... 153 Model description ................................................................................................... 153

Scenario data ............................................................................................... 153 Parameter values .......................................................................................... 153 Rates .......................................................................................................... 153 Analysis overview ......................................................................................... 154

Chapter 36. Create the rates for tractor - trailer modeling .......................................... 155 Create required tariffs ............................................................................................ 155

Create the truckload tariff .............................................................................. 155 Create the rate range .................................................................................... 159

Add the equipment types to the rating database ........................................................ 159 Add the Equipment Types ............................................................................... 159 Associate the equipment types to the service .................................................... 159

Chapter 37. Create data for the tractor - trailer exercise ............................................. 161 Create locations .................................................................................................... 161

Add location data .......................................................................................... 161 Update LatLon and PostalCode ........................................................................ 162

Create shipments .................................................................................................. 162 Create carrier ........................................................................................................ 163 Create equipment types .......................................................................................... 163 Create domiciles .................................................................................................... 163 Create domicile vehicle availability ........................................................................... 164 Update optimizer parameters .................................................................................. 164 Save scenario ....................................................................................................... 165

Chapter 38. Solve the tractor - trailer scenario ............................................................ 166 Initial strategy file for tractor - trailer ....................................................................... 166

Solve the model and save the optimization log .................................................. 168 Evaluate addition of the common carrier ................................................................... 168

Add the common carrier ................................................................................. 168 Add the equipment type for the common carrier ................................................ 169 Add the common carrier rates ......................................................................... 169

Force assignment of a carrier .................................................................................. 171 Solve the model with the carrier assignment and save the optimization log ........... 171

Expand the dedicated fleet ...................................................................................... 172 Delete the common carrier ............................................................................. 172 Add the new equipment types for the dedicated fleet ......................................... 172 Add the rates for the expanded dedicated fleet .................................................. 173

Introduce a new domicile ........................................................................................ 176 Create the domicile vehicle availability records .................................................. 176 Delete the old domicile and domicile vehicle availability records ........................... 177 Solve the model with the new haven domicile and save the optimization log .......... 177 Force the equipment type ............................................................................... 178

Chapter 39. Green modeling exercise .......................................................................... 179 Model description ................................................................................................... 179

Scenario data ............................................................................................... 179 Parameter values .......................................................................................... 180 Rates .......................................................................................................... 180 Analysis overview ......................................................................................... 180

Chapter 40. Create the rates for green report modeling .............................................. 181 Create required tariffs ............................................................................................ 181

Create the truckload tariff .............................................................................. 181 Add the green charge to the rating database ............................................................. 184

Add the CO2 master charge ............................................................................ 184 Add the CO2 charge to the tariff ...................................................................... 185 Add the CO2 rate .......................................................................................... 185

Chapter 41. Create data for the green reporting scenario ............................................ 186 Create locations .................................................................................................... 186

Add location data .......................................................................................... 186 Update LatLon and PostalCode ........................................................................ 187

Create shipments .................................................................................................. 187 Update optimizer parameters .................................................................................. 188 Save scenario ....................................................................................................... 188

Chapter 42. Solve the green report scenario ............................................................... 189 Strategy file for Green Report .................................................................................. 189

Solve the model and save the optimization log .................................................. 189 Review the load charges ................................................................................ 189

Generate the Green Reports .................................................................................... 190 Export scenario data to the Access Rating Tool .................................................. 190 Set-up the green reports input parameters ....................................................... 190 Generate the green report data ....................................................................... 190 Display the Green Reports .............................................................................. 191

Evaluate addition of the dedicated fleet ..................................................................... 191 Add the dedicated fleet .................................................................................. 191

Add the equipment type for the dedicated fleet ................................................. 191 Add the dedicated fleet rates .......................................................................... 192 Add the dedicated fleet scenario to the Green Reports ........................................ 195

Evaluate the solution without the green charges ......................................................... 196 Remove the green charges ............................................................................. 196 Solve the model without the green charges and save the optimization log ............. 196

Expand the dedicated fleet ...................................................................................... 197 Add the new equipment types for the dedicated fleet ......................................... 197 Add the rates for the expanded dedicated fleet .................................................. 198 Add the Trailer Domicile scenario to the Green Reports ....................................... 200

Analysis of the three scenarios ................................................................................ 201 GHG Costing report ....................................................................................... 201 CO2 Emissions report .................................................................................... 201

Add a freight surcharge .......................................................................................... 202 Create the surcharge percentage ..................................................................... 202 Create a master surcharge ............................................................................. 203

Index ........................................................................................................................... 205

Introduction

Chapter 1. Introduction This guide provides overviews, illustrations, procedures, and examples for JDA Transportation Modeler. Transportation Modeler is an analytical and managerial tool that you can use to identify business opportunities for your company by:

• Analyzing shipment data.

• Optimizing business scenarios using the Solver engine.

• Creating reports to illustrate potential savings.

In other words, it is a decision support tool that when blended with your logistics, industry and modeling expertise helps you to make the best decisions for your business. You can use Transportation Modeler with other tools in the JDA suite.

Use Transportation Modeler Transportation Modeler uses shipment data from various sources. After mapping this raw input data to its internal tables, Transportation Modeler can optimize this data. The Transportation Modeler then generates reports that you can view on screen or print as maps and charts, or save as reports to files.

With Transportation Modeler, you can:

• Import data from and export data to Microsoft Access or other ODBC-compatible database formats.

• Produce a transportation strategy using the existing sophisticated tariff and entity setup.

• Perform what-if analysis by repeatedly reworking shipment data in different scenarios. What-if analysis shows you or your customers what business improvements are possible.

• Create multiple optimization scenarios for one model using the Solver engine. Apply operational parameters such as delivery days, hours, and maximum load weight. Optimize the scenarios to see how they compare to the original data and cost.

• Identify sophisticated less-than-truckload (LTL), truckload (TL), and hub utilization opportunities, including de-consolidation, consolidation, pooling, and zone skipping.

• Create standard or custom reports based on master or optimized data reports to verify possible time and cost savings.

Note: Using Transportation Modeler for decision support requires a firm understanding of the transportation scenario that you are analyzing and of the assumptions that you are using to construct the representative model in Transportation Modeler.

For more information, see the JDA Transportation Modeler User Guide.

JDA Transportation Modeler Getting Started Guide 1 © 1995-2015 JDA Software Group, Inc.- Confidential

Introduction

Transportation Modeler process The following diagram illustrates the transportation modeler process flows in Transportation Modeler.

Analyze data using Transportation Modeler This is a typical process followed by Transportation Modeler to analyze data:

• Input data

• Validate data

• Set up rates

• Set up Solver options and strategy files

• Optimize data

• View output results (optimized data and reports displayed in Summary)

• Make changes for "what-if" analysis

• Re-optimize data


Introduction

• View output results

Start Transportation Modeler Select Start > Programs > JDA Transportation Modeler > Transportation Modeler.

Alternate steps:

• Navigate to the Transportation Modeler directory (by default, C:\jda\tmod\9.0), then double-click TM32.exe or TM.exe (for 64 bit).

• Open a DOS Window. Change the directory to the one in which you installed Transportation Modeler (by default, C:\jda\tmod\9.0). On the command line, enter TM32.exe or TM.exe (for 64 bit).

Note:The first time that you start Transportation Modeler, you must register your software. For more information, see the JDA Transportation Modeler Installation/Administration Guide.

Exit Transportation Modeler 1. Select File > Exit ( ) from the ribbon.

Alternate steps:

• Press the Alt+F4 function keys.

• Select the window close button at the top right of the application window.

Before exiting, Transportation Modeler checks to see if:

• Any new model results (aggregate tables, maps, or summary views) are created.

• Any updates made to model results that are currently open.

• Any changes made to the current scenario.

For each of these conditions, Transportation Modeler prompts you to save changes before closing.

Modeling exercise overview This guide provides a series of modeling exercises to help you understand how to:

1. Enter and edit data in Transportation Modeler.

2. Build tariff data using the Access Rating Tool provided with Transportation Modeler.

3. Analyze results of a Transportation Modeler optimization.

The guide uses a set of cumulative exercises:

• "Truckload modeling exercise" (on page 19): In this exercise, you examine the shipper’s network and evaluate creation of multi-pick and multi-drop truckloads. The goal is to analyze potential savings by building better truckloads across the shipper's network.

• "LTL modeling exercise" (on page 65): This exercise expands the study by adding a less-than-truckload (LTL) carrier. You learn about LTL discounts and the effects of freight classes.

• "Hub modeling exercise" (on page 76): In this exercise, you examine the possible benefits of utilizing a hub for consolidation and deconsolidation opportunities.


Introduction

• "Continuous move modeling exercise" (on page 93): This exercise introduces the concept of continuous moves, in which you evaluate how best to transport backhaul shipments.

• "Equipment domicile modeling exercise" (on page 107): This exercise introduces the concept of equipment domiciles. You add domiciles to you model and evaluate their impact.

• "Carrier equipment availability modeling exercise" (on page 127): In this exercise, you introduce constraints on the resources in the scenario. These constraints are applied at the carrier, tariff-service and lane levels.

• "Dock scheduling modeling exercise" (on page 140): This exercise introduces docks and the scheduling requirements for docks. You observe the impact of the scheduling constraints imposed by docks.

For the Truckload Modeling Exercise, you are provided with complete instructions on how to create the shipments, locations and tariff data required. You build the tariffs using the TariffConverterExcelTemplate.xls Excel spreadsheet that is part of the access rating tool. You can then convert them to a Microsoft Access format database using the TariffConverter.mdb. You can create the locations and shipments in Transportation Modeler. You will learn how to set up Transportation Modeler solver options and edit the strategy and parameter files that control solver behavior.

In subsequent exercises, you are provided with overviews of the new or updated data requirements. You will create and edit tariffs in the access rating tool. In some cases, you need to add shipment data in Transportation Modeler and you will work with strategies and parameters to adjust how the solver behaves.

For all exercises, a series of questions are provided to help you learn how to analyze Transportation Modeler optimization results and how to adjust rates, strategies and parameters to affect the solver behavior.

Related documentation The Transportation Modeler documentation set includes the following items.

• Transportation Modeler Release Notes: Provides information about any new or updated functionality in Transportation Modeler.

• Transportation Modeler Installation/Administration Guide: Provides information about how to install Transportation Modeler.

• Transportation Modeler User Guide: Provides details about the Transportation Modeler user interface, modeling data in Transportation Modeler, and how to use the application.

• Transportation Modeler Strategies and Parameters Guide: Provides descriptions of the functions you can use with the Transportation Modeler strategy files. It also contains descriptions of the global parameters that you set to control Transportation Modeler.

• Transportation Modeler Getting Started: Provides an introduction to the Excel Rating Tool user interface, entities, relationships, and outviews. It describes the Excel Rating Tool modeling process, including tariff construction, optimization and analysis of results.

• Transportation Modeler Access Rating Tool User Guide: Provides information about how to use the Access and Excel based rating tool.

• Transportation Modeler Stand-Alone Rate Editor User Guide: Provides information about how to use Stand Alone Rate Editor.


Introduction

• Transportation Modeler Distance Engine User Guide: Provides information about how to use the Distance Engine generation tool.

Get additional help from JDA In addition to the provided documentation, many additional resources are available to help you understand and work with your JDA applications.

Note: The services provided may vary by application and implementation.

• JDA Support Services

JDA Support Services enhances your experience with JDA solutions throughout the lifetime of your relationship with JDA Software. Support Services provides many key values, including:

• Worldwide support provided locally for issue resolution, including functional and technical assistance

• Defined service levels and proactive escalation paths

• Special Interest Group (SIG) membership

• Access to new software releases

• Access to the JDA Customer Support website (http://support.jda.com/), which provides:

• Self-service user administration

• Online knowledge base

• Online case management and user communities

• Product documentation and release announcements

• JDA Education Services

To enhance the return on your JDA solution investment, JDA Education Services provides options to optimize your experience and knowledge. JDA Education Services offers high-quality training with e-learning and instructor-led training opportunities. JDA Education Services also offers the JDA Certification Program, which defines a curriculum that maximizes your knowledge and qualifications for a specific job. Certification programs employ a blend of learning methods that end with an industry-recognized exam. See the JDALearn website (http://www.jdalearn.com) for more information.

• JDA Consulting Services

JDA Consulting Services provides a broad range of services, including:

• Process definition and improvement

• Change management

• Program and project management

• Functional and technical consulting

• Performance engineering

• Solution delivery


http://support.jda.com/

http://www.jdalearn.com/

Introduction

Every solution deployment begins with the JDA Enterprise Methodology, which encompasses both technology and implementation expertise. JDA Consulting Services works collaboratively with you to help your business realize the results you need, on time and on budget.

• JDA Cloud Services

JDA Cloud Services enables you to achieve faster deployment, rapid time to value, investment protection, and improved cost structure with JDA supply chain solutions. This allows you to focus on your core business while JDA manages the JDA applications. Areas of specialty include:

• Solution availability management

• Performance management

• Issue resolution

• Change management

• Security management

• Optimization and analytics management

For more information on any of the JDA Services, see the JDA Services website (http://www.jda.com/services/services/).


http://www.jda.com/services/services/

Graphical user interface

Chapter 2. Graphical user interface The Transportation Modeler graphical user interface (GUI) is designed to provide multiple ways to access Transportation Modeler's features and views that you can customize.

Ribbon The Transportation Modeler ribbon allows you to quickly find the commands that you need to complete a task. It has the following elements:

• Menu and tabs: The File menu and Home, View, and Map tabs have commands organized in logical groups.

Notes:

• When the ribbon is minimized, only the tabs are displayed.

• In Office 2007 style, the File menu can be accessed by clicking the application icon .

• Buttons: The following buttons are displayed in the right corner of the ribbon:

• / : Displays or hides the ribbon.

• Recent Views: Selects the recently opened chart, summary or map views.

• Window: Applies a display style when multiple windows are opened.

• Style: Applies a display theme for Transportation Modeler. The default theme is Microsoft Windows 7.

• Help: Displays the following options:

• About JDA Transportation Modeler: Displays the software license information of Transportation Modeler.

• User Help Topics: Provides access to the online help for Transportation Modeler.

• Strategy and Parameters Help: Provides access to the online help for strategies and parameters.

• Save Performance Data: Saves performance data of all optimizations to the specified file.

The buttons on the tabs are activated based on the current view and the tasks that are performed. For example, if a map view is not open, the buttons on the Map tab are inactive.

File menu The File menu provides the following commands to work with files:

• New: Creates a new scenario.

• Open: Opens an existing scenario.

• Batch Process: Processes a batch file to configure and solve multiple scenarios sequentially.

• Save: Saves the active scenario.



• Save As: Saves the active scenario with a new name, to a different location, or both.

• Close: Closes the active scenario. Transportation Modeler prompts you to save an unsaved scenario before closing it.

• Exit: Closes Transportation Modeler.

Home tab The Home tab provides various command groups to work with a scenario.

Clipboard The Clipboard group provides the following commands to work with the clipboard content:

• Cut: Cuts the content of the selected data cells to the clipboard.

• Copy: Copies the content of the selected data cells to the clipboard.

• Paste: Pastes the content from the clipboard to the selected data cells.

Options The Options group provides commands to work with option files and solver options.

Display Options The Display Options drop-down list provides the following commands to work with option files:

• Edit: Modifies the display options in the Options dialog box.

• Load: Loads an option file.

• Save: Saves the modified option file.

You can perform one of the following tasks to display the Display Options dialog box:

• Click Display Options in the Options group.

• Select Display Options > Edit in the Options group.

Solver Options The Solver Options drop-down list provides the following commands to work with the solver options:

• Edit: Modifies the optimizer, rating and distance settings in the Solver Options dialog box.

• Load: Loads a solver options file.

• Save: Saves the modified solver options file.

• Auto Load: Identifies solver settings based on the current scenario or a directory (if no scenario is open).

You can perform one of the following tasks to display the Solver Options dialog box:



• Click Solver Options in the Options group.

• Select Solver Options > Edit in the Options group.

Scenario The Scenario group provides the following commands to optimize a scenario:


• Validate: Validates the data at the record level for the entire scenario.

• Solve: Starts the optimization process. During the process, the Solver dialog box is displayed with progress indicators.

Configuration The Configuration group provides the following commands to work with strategy and parameter files:

• Edit Strategy File: Edits the strategy files.

• Edit Parameter File: Edits the parameter files.

• Logging: Enables and disables the logging information for various categories.

• Reporting:Displays and creates or modifies optimization metrics that are calculated at the end of the optimization.

Utilities The Utilities group provides the following commands to work with various utilities:

• Plan Explorer: Displays a structured overview of the original shipments and optimization results, including the unroutables, loads, and trips.

• Opt Report: Displays the optimization report.

• Driving Reports: Displays PC*Miler driving reports, which include information such as states, tolls, free roads, direction of travel, segment distance, driving time, interchange points, leg mileage and time, cumulative load distance, and total load time..

• Road Map: Displays locations, shipments, loads, and trips in a PC*Miler map window. The Road Map drop-down list provides the following commands:

• Open: Opens a road map.

• Properties: Displays the properties of a road map.

• Data Utilities: Enables data utilities for city and postal code validation.

• License: Disables the Transportation Modeler license or transfers the license to a disk or another system. This icon is enabled only when no scenario is open.

Access The Access group provides the following commands to import or export batch files to a Microsoft Access database:



• Batch Import: Imports tables from a Microsoft Access database into your scenario.

• Batch Export: Exports tables to a Microsoft Access database from your scenario.

• Multi Scenario: Exports the data from the Transportation Modeler scenarios to the corresponding set of destination tables in the Access database.

ODBC The ODBC group provides the following commands to import or export batch files to an Open Database Connectivity (ODBC) database:

• Batch Import: Imports tables from the ODBC database into your scenario.

• Batch Export: Exports tables to a ODBC database from your scenario.

• Multi Scenario: Exports the data from the Transportation Modeler scenarios to the corresponding set of destination tables in the ODBC database.

Text The Text group provides the following commands to import XML files and export plan data:

• Import XML: Imports tables from an XML file into your scenario.

• Export Plan Output: Exports the results of the latest solver run to the specified location.

• Export Plan Input: Exports the current plan inputs to the specified location.

View tab The View tab provides various command groups to work with views.

Chart The Chart group provides the following commands to work with charts:

• New: Creates a new chart view.

• Properties: Modifies the display properties of a chart.

• Advanced: Modifies the advanced display settings of a chart, such as aggregate results and detail records.

Gantt The Gantt group provides the following command to work with Gantt charts:

• New: Creates a new Gantt view.

Summary The Summary group provides the following command to work with a summary view:

• New: Creates a new summary view.



Query The Query group provides the following commands to work with the Detail Table:

• Properties: Allows you to modify the field order and sort order of a view.

• Narrow Results to: Narrows the query results by selecting or deselecting the required rows.

• Assign Attributes: Assigns one or more attributes to the selected records in the Detail Table.

• Unassign Attributes: Unassigns one or more attributes from the selected records in the Detail Table.

Aggregate Table The Aggregate Table group provides the following commands to work with aggregate tables:

• Shipment: Creates a new aggregate table based on shipments.

• Load: Creates a new aggregate table based on loads.

• Trip: Creates a new aggregate table based on trips.

Metrics The Metrics group provides the following commands to work with optimization metrics:

• Add Comparisons: Reads optimization metrics from other solves to compare results.

• New Chart: Creates a chart based on one or more optimization metrics.

• Load Chart: Loads a chart definition from an existing file.

File The File group provides the following commands to open, save, and close a view:

• Open: Opens an existing view.

• Save: Saves the current view.

• Save As: Saves the current view with a new name, to a different location, or both.

• Close: Closes the current view. Transportation Modeler prompts you to save an unsaved view before closing it.

Windows The Windows group enables you to select or deselect the display of the event log and status bar. The following check boxes are available:

• Event Log: Displays events including UI actions and the names of the export tables or files and the related results.

• Status Bar: Displays the status bar.



Map tab The Map tab provides various command groups to work with maps.

Map View The Map View group provides the following commands to work with a map view:

• New: Creates a new map view.

• Properties: Modifies the display properties of a map.

• Query Point: Queries the latitude and longitude information of the selected map location.

• Copy: Copies the current map view and any displayed legends to the clipboard.

File The File group provides the following commands to open, save, and close a map view:

• Open: Opens an existing view.

• Save: Saves the current view and its settings.

• Save As: Saves the view with a new name, to a different location, or both.

• Close: Closes the view. Transportation Modeler prompts you to save an unsaved view before closing it.

Add The Add group provides the following commands to add locations or hubs:

• Location: Adds a location.

• Hub: Adds a hub.

Zoom The Zoom group provides the following commands to adjust the zoom settings on a map:

• In: Zooms in on the map display.

• Out: Zooms out on the map display.

Legends The Legends group enables you to select or deselect the display of the following legends:

• Location Icons

• Hub Icons

• Domicile Icons

• Shipment Links

• Load Links

• Trip Links



Projection The Projection group provides the following commands to view a map in different projections:

• Flat: Projects the map view on a flat background.

• Spherical: Projects the map view on a sphere.

Home Position The Home Position group provides the following command to set the home position on a map:

• Set: Sets the home position to the selected location.

Set Perspective The Set Perspective group provides the following commands to center the map:

• Screen Location: Centers the map on the selected location.

• Home Position: Centers the map on the home position.

Quick access toolbar This is a customizable toolbar that provides a quick access to a group of commands, regardless of the active tab on the ribbon.

By default, the following commands are displayed on the quick access toolbar:

• New: Creates a new scenario.

• Open: Opens an existing scenario.


• Edit Solver: Modifies the optimizer, rating and distance settings in the Solver Options dialog box.

• Solve: Starts the optimization process. During the process, the Solver dialog box is displayed with progress indicators.

• Opt Report: Displays the optimization report.

Use the drop-down list next to the default commands to perform the following customizations:

• Select or deselect the display of the default commands

• Add additional commands to the toolbar

• Restore the default settings of the toolbar

• Customize keyboard shortcuts for commands

• Move the toolbar above or below the ribbon

• Minimize the ribbon

Keyboard shortcuts The following keyboard shortcuts are available in the Transportation Modeler application:



Basic key Keyboard shortcut Description

Ctrl

Ctrl+N Creates a new scenario

Ctrl+O Opens an existing scenario

Ctrl+S Saves the active scenario

Ctrl+C, Ctrl+Insert

Copies the content of the selected data cells to the clipboard Copies the current map view and any displayed legends to the clipboard

Ctrl+X Cuts the content of the selected data cells and copies it to the clipboard

Ctrl+V Pastes the content from the clipboard to the selected data cells

Shift

Shift+Delete Cuts the content of the selected data cells and copies it to the clipboard

Shift+Insert Pastes the content from the clipboard to the selected data cells

Customize keyboard shortcuts 1. Select More Commands… from the drop-down list on the quick access toolbar. The Options dialog

box is displayed.

2. Click Customize… next to keyboard shortcuts. The Customize Keyboard dialog box is displayed.

Notes:

• The Categories list displays all tabs on the ribbon.

• The Commands list displays all commands for the tab selected in the Categories list.

• The Current keys list displays the existing keyboard shortcuts for the selected command.

3. Select the required category and command to customize the keyboard shortcuts.

4. To add a new keyboard shortcut, enter the keyboard shortcut in the Press new shortcut key field and click Assign.

5. To delete a keyboard shortcut, select it from the Current keys list and click Remove.

Note: You can also delete default keyboard shortcuts.

6. To restore default keyboard shortcuts, click Reset All.



7. Click Close to close the Customize Keyboard dialog box.

8. Click OK to save the customizations and close the Options dialog box.

Shortcut menus In addition to selecting functions from the "ribbon" (on page 7), you can also select functions from shortcut menus. Shortcut menus are context-sensitive and contain commonly used menu selections or data selection shortcuts. Right-click any Transportation Modeler view or function to access shortcut menus.

Shortcut menus are available in the following sections of Transportation Modeler:

• Query view

• Data view

• Control center

• Ribbon

• Quick access tool bar

Control center You can use the Scenario pane in the control center to create, build, and work with the "Data tables" associated with a scenario. The Control center is displayed when you open a scenario.

For more information, see "Dock or undock the control center" (on page 16).

The Scenario pane contains the following sections:

• Favorites: Displays shortcuts to data tables that you frequently use. By default, this section contains shortcuts to shipment, location, hub, load, and stop data tables.

• Model: Displays all input data tables that are used to model the current scenario.

• Carrier Equipment Availability: Displays data tables that contain information on the availability of lanes, tariffs, services, equipment types, domiciles, and zones.

• Plan Input: Displays pre-built trip and load data tables for replanning.

• Plan Output: Displays output data tables of the optimized plan.

• Display: Displays data tables that are used to view the maps.

• Attributes: Displays data tables to create and assign attributes to the model entities.

Customize the Favorites section

To customize the Favorites section 1. Select the Home tab on the ribbon.

2. Click Display Options in the Options group. The Options dialog box is displayed.

3. Select the Favorites tab.

4. Select or deselect the tables to display in the Favorites section.

5. Use the Move buttons to arrange the tables in the required order.



To add or delete tables of the Favorites section from control center 1. To add a table to the Favorites section, right-click the table name in the Control Center and select

Add to Favorites from the shortcut menu.

2. To remove a table from the Favorites section, right-click the table name in its respective section the Control Center or in the Favorites section and select Remove from Favorites from the shortcut menu.

Customize the control center sections 1. Select the Home tab on the ribbon.


3. Select the Control Center tab.

4. Select a section you want to customize from the Display Following Records in Control Center drop-down list. All tables of the section are displayed.

5. Select or deselect the tables to be displayed in the control center.

6. Use the Move buttons to arrange the tables in the order you want.

Dock or undock the control center 1. To dock the control center:

a. Right-click the title of the Scenario pane, then select Docking.

b. Drag the Scenario pane to an arrow at the required edge of the application window. The control center is docked at that edge.

2. To undock the control center, right-click the title of the Scenario pane, then select Floating. The control center is displayed as a floating window.

Manage data through the Control Center If you click a table name in the control center, the corresponding detail table is displayed in the data view.

Note: You can access the data tables and the import or export functions used with those data tables through the "shortcut menus" (on page 15). The shortcut menu is available only when a table name is highlighted in the Control Center.

The control center organizes the data tables into the following categories:

• Model: These records contain the user-defined values that comprise the TM model. Through the model records, you can create and modify locations, shipments, business hours, time windows, and hubs. Some of these record types are single-keyed entities, such as locations and shipments. Others are constructed through relationships of entities, such as time windows (business hours, days of the week).

You can view model records in the Shipment, Shipment Component, Consolidation Class, Merge-In-Transit Group, Order Group, Commodity Code, Commodity Exclusions, Location, Hub, Dock, Dock at Facility, Domicile, Carrier, Equipment Type, Business Hours, Time Window, Business Hours Exceptions, and Transit Override detail tables.

• Carrier Equipment Availability: These records contain information about Carrier, Service, Lane and Domicile availability. This data constrains the optimization process based upon contractual or physical limitations.



• Plan Input: Load Input and Trip Input records can be created as inputs to the optimization process. Loads or Trips created for replanning can be extended or combined. A Load Input without any shipments assigned to it defines a Skeleton Route to which the optimization attempts to assign plan shipments.

• Plan Output: Plans are generated by the optimization process. Transportation Modeler combines shipments, as defined in the Model section, into loads. Each load consists of a number of stops; each involves one or more of the shipments as a pick or drop. You can view plan records in the Trip, Trip Load, Load, Stop, and Pick/Drop detail tables. The Plan Output section also includes containerization information and dock, resource, and vehicle utilization information.

• Display: Display records allow you to set up geographic map zones for representation in a map view. You can view display records in the MapZone detail table.

• Attributes: Attributes are user-defined groups assigned to entities. The Attribute detail table allows you to define the grouping categories. The Entity Attribute detail table enables you to combine entities in the attribute groups so that you can easily group or modify entities for reporting and selection.

Note: You only use attributes for reporting and data selection; no data is specified at the attribute level. You can use them to select data and as a post-optimization reporting utility. Attributes defined on child entities are automatically assigned to loads and trips created by the Solver.

Status bar The status bar at the bottom of the Transportation Modeler window displays the status of the user interface.

To display or hide the status bar 1. Select the View tab on the ribbon.

2. Select or deselect the Status Bar check box in the Windows group.

Editable and non-editable fields Fields in output "Data tables" are non-editable. However, fields in input data tables are either editable (input data) or non-editable (calculated or optimized values).

By default, editable fields are not shaded, while non-editable fields (key or calculated fields) are displayed with shaded backgrounds.

To set shaded background colors for different field types 1. Select the Home tab on the ribbon.


3. Select the Display Settings tab.

4. Click the required field type in the Grid colors section. You can select an existing color or customize the colors.

5. Click OK.

For more information, see "System options".



Menu buttons Menu buttons allow you to control the selection of records. For example, menu buttons in detail tables allow you to select from the following options:

• Entity

• Attribute

• All Entities

To see all available options for a menu button, click the button. You can then select from the display of all options. A check box indicates the currently selected option.

"Aggregate tables" have a menu button below each list . This button is used to control the aggregation of records and offers the Group by Entity, Group by Attribute and No Grouping options.


Truckload modeling exercise

Chapter 3. Truckload modeling exercise This chapter provides an outline of the Truckload exercise. A description of the modeling problem, as well as the basic data, is provided.

Model description A shipper needs to be able to deliver a set of shipments from his distribution centers in Pennsylvania and Ohio to multiple stores throughout the country. He is contracted with a single truckload carrier that delivers all his truckload moves. Ideally, the shipper would like to minimize his transportation costs by using Transportation Modeler’s optimizer to create multi-pick and multi-drop truckloads. Currently, the shipper only consolidates at the DC since each DC operates its own outbound transportation plans and the shipper does not have good visibility across all its supply locations. This exercise helps analyze potential savings by building better truckloads across the shipper's network.

Shipments The shipment data is listed as follows:

Note: All shipments should be created with a Freight Class of 50.

• Pittsburgh, PA 15219 to Detroit, MI 48206

• 1 at 20,000 lbs

• 1 at 5,000 lbs

• Pittsburgh, PA 15219 to Chicago, IL 60608

• 1 at 10,000 lbs

• Pittsburgh, PA 15219 to Indianapolis, IN 46204

• 1 at 10,000 lbs

• Pittsburgh, PA 15219 to Louisville, KY 40217

• 1 at 10,000 lbs

• 1 at 5,000 lbs

• Pittsburgh, PA 15219 to Gary, IN 46402

• 1 at 10,000 lbs

• Cleveland, OH 44101 to Detroit, MI 48206

• 1 at 10,000 lbs

• 1 at 10,000 lbs

• Cleveland, OH 44101 to Chicago, IL 60608

• 1 at 10,000 lbs

• Cleveland, OH 44101 to Indianapolis, IN 46204

• 1 at 10,000 lbs



• Cleveland, OH 44101 to Louisville, KY 40217

• 1 at 10,000 lbs

• 1 at 5,000 lbs

• Cleveland, OH 44101 to Gary, IN 46402

• 1 at 10,000 lbs

Rates The rates for the particular moves are listed as follows:

Note: All stop charges are $50/stop.

• PA - MI $1.20/mile

• PA - IL $1.40/mile

• PA - IN $1.00/mile

• PA - KY $1.10/mile

• OH - MI $1.40/mile

• OH - IL $1.50/mile

• OH - IN $1.20/mile

• OH - KY $0.75/mile

The truckload carrier can carry up to 40,000 pounds per truckload on all moves.

It runs typical DOT rules: 11 hours driving, 10 off-duty, 10 hours off-duty max, and 14 max total on-duty.

Analysis overview The information provided in the description above should be enough to answer this set of questions.

1. The shipper in question would like to see a baseline of their current operation before looking at the possibility of consolidating the multiple origins in Pittsburgh and Cleveland. The shipper would like you to provide a strategy file, parameter file, and optimization log that describe the baseline behavior. The shipper runs both same origin – same destination truckloads and same origin – multiple destination truckloads. The strategy file should be as simple as possible and the parameter file should not limit any potential cost effective moves.

• Plan out your strategy before creating a strategy file. Users often jump into solving before coming up with an effective way to solve the problem. Write up a general approach to solving this particular problem and ensure you keep it for your solution. (For example: "Since I need to combine similar origins and destinations, I should run a __________________, and it should be run third after this other strategy."). Once you do this, you should implement your approach by creating a strategy file.

• Run a baseline scenario that only consolidates single origin to multiple destinations. Use the baseline strategies and parameters provided in the example.

• Run the modified baseline scenario that allows you to adjust strategies and parameters to improve your answer. This answer is the least cost plan shipping single-pick multi-drop loads.



2. The shipper now wants to see the cost improvement, if any, by attempting to run multiple pick TL's between Cleveland and Pittsburgh. Since we told the client that there were efficiencies in multi-pick scenarios for their network, the goal is for this to be shown.

• Come up with your best answer for the client considering multi-picks across origins. How much has the answer improved? Again, save the answers.


Create the TL rates with the Access Rating Tool spreadsheet

Chapter 4. Create the TL rates with the Access Rating Tool spreadsheet In this chapter, you will use the access rating tool, a Microsoft Access and Excel-based tariff editor for Transportation Modeler, to create the network of lanes required to move the goods represented by Transportation Modeler shipments. This rating engine provides the same rates as the rating engine you created in Costs and Network of Lanes with Stand-Alone Rate Editor.

Rating tool overview This section of the rating tutorial provides overviews, illustrations, procedures and examples for the access rating tool.

The TariffConverterExcelTemplate.xls file contains the fields you can populate in support of your modeling requirements. This file contains a set of worksheets: TL, LTL, SmallPackage, RateRange, Hub and Zones. The current truckload problem will require you to enter relevant details in the TL worksheets.

Note: JDA recommends that you create a copy of the TariffConverterExcelTemplate.xls file. Do not change the field names in TariffConverterExcelTemplate.xls. Do not copy data from another spreadsheet or worksheet to paste into the cells in the TariffConverterExcelTemplate.xls file. Many of the cells in the template spreadsheet are defined with a specific format. Copying and pasting data can result in a change in data types and error during conversion to the Access database format.

Once you enter the rates in the Excel spreadsheet, you will use the TariffConverter.mdb, an Access-format database, to convert the rates into an Access-based rating engine. This database contains a set of rating tables into which the spreadsheet data is populated using an Access macro. You can then set up Transportation Modeler to use the Access database as its rating engine.

Create required tariffs In this section, you can create the tariffs that are required to rate the shipments. To create the tariffs:

1. Enter the data for the carrier, tariff, service and rates.

2. Convert the data into an Access-format rating database.

Create a TL Tariff You can enter all required data onto the TL worksheet in the TariffConverterExcelTemplate.xls spreadsheet. Each record on this worksheet represents a lane, complete with its carrier/tariff/service information.

Create the TL tariff 1. Open the TariffConverterExcelTemplate.xls spreadsheet.

2. Select the TL worksheet.

3. For the first record, enter the data as shown in the following table.

Note: Do not change the field names in TariffConverterExcelTemplate.xls. Do not copy data from another spreadsheet or worksheet to paste into the cells in the TariffConverterExcelTemplate.xls file. Many of the cells in the template spreadsheet are defined with a specific format. Copying and pasting data can result in a change in data types and error during conversion to the Access database format.



Note: If no value is required, leave the field value blank. This results in the tool accepting the default value:

Field Description Value Carrier The identifier for the carrier. TLCARR

Service The name of the mode definition. You are defining a truckload tariff. TL

Tariff The tariff for the tariff service. If you do not define a Tariff value, the conversion macro will concatenate the Carrier value with the Service value to define the Tariff.

Equipment Describes the equipment used for the movement.

RateCode Use this field to specify a RateCode for the carrier/tariff/service/charge that already exists in the database. This enables you to define new lanes that use this RateCode. You can define multiple rows (multiple lanes) with the same RateCode. If you set the RateCode to *, the rating engine applies it to all lanes. If you leave the RateCode blank, the conversion macro in the Access database will create a unique RateCode for each lane.

DivisionCode Use this field to specify the division for the tariff records.

UOMType This field is the Unit of Measure Type. It should be set to imperial units since the rates are based on miles and the weight constraints are based on pounds.

Imperial

DimWeightFactor

Defines the factor that the rating engine uses to calculate dimensional weight. It multiplies/divides the volume by the factor to find the dimensional weight. It is only used when Lookup Type is set to Weight. If you do not enter a value for this field, it defaults to 1. 0 is not permitted.

UnitDivideFactor This field is the factor by which the ChargeType needs to be divided before determining the number of units and applying the PerUnit charge. The default value is 1.

ChargeType Indicates the measure on which the charge is levied. For example, if the ChargeType is Distance, the charge is levied per distance unit, such as per mile.

Distance

LookupType If you specify a value for this field, the rating engine uses this unit type to determine the cost per unit. It then multiplies this cost by the number of units of the specified ChargeType to get a total cost. If you do not specify a value for this field, the rating engine defaults it to the ChargeType value.

LookAheadRule Determines if the rating engine can select a rate at the previous or next given range break. The additional or reduced amount of quantity multiplied by the rate at the new range break must be cheaper than the current quantity multiplied by the rate at the current range break for the alternate range break to be used. Valid values are:

• LookAhead

• LookBack

• Disabled

The default value, if the field is not populated is Disabled.



Field Description Value RateType Identifies the method in which the rate is applied. For example, you

can apply a rate as a PerUnit (such as charging a rate per mile) or as a FlatCharge.

PerUnit

TeamDriver Determines whether or not the team drivers are used. When team drivers are used, DOT rules are not applied during scheduling.

MinCharge Identifies a minimum charge that must be levied.

MinChargeLocation

Use this field to define if the MinCharge is at the Service level, Charge level, Lane level, or Rate level.

PerUnitOrPercentOrFlatCharge

Specifies the rate that is levied. For the lane from PA to MI, the value is 1.2.

1.2

RateRangeID This field is the RateRangeID value from the RateRange worksheet when using a rate range.

OriginZoneCode Identifies the zone at which the lane originates. The specified zone code should refer to a zone defined on the Zones worksheet. In this example, the lanes are state to state and no zone code is required.

OriginHubID Identifies the Hub at which the lane originates. In this example, the lanes are state to state and no hub is required.

OriginPostalCode

Identifies the Postal Code at which the lane originates.

OriginPostalCodeEndRange

If you are specifying a Postal Code range for the origin, use the OriginPostalCode and this field to specify the range within which the lane originates.

OriginState Identifies the State in which the lane originates. PA

OriginCountry Identifies the Country in which the lane originates. USA

DestZoneCode Identifies the zone at which the lane terminates. The specified zone code should refer to a zone defined on the Zones worksheet. In this example, the lanes are state to state and no zone code is required.

DestHubID Identifies the Hub at which the lane terminates. In this example, the lanes are state to state and no hub is required.

DestPostalCode Identifies the Postal Code at which the lane terminates.

DestPostalCodeEndRange

If you are specifying a Postal Code range for the origin, use the DestPostalCode and this field to specify the range within which the lane terminates.

DestState Identifies the State in which the lane terminates. MI

DestCountry Identifies the Country in which the lane terminates. USA

TransitTime Defines the delivery schedule time (number of transit days) required to complete the movement (the schedule). If TransitTime is defined, a delivery schedule is created. If it is not defined or is 0, distance engine truck load scheduling is applied.

PointToPointOrRoundTrip

Determines whether the lane is modeled as a Point to Point lane or a Round Trip lane. In this case, you are modeling point to point tariffs. Empty miles are not being rated, so the point to point tariff rates the loaded miles for the movement.

PointToPoint



Field Description Value EligibleForContinuousMoves

Determines if the carrier movement between the origin-destination pair is eligible for continuous moves (trips). The default is N. In this case, you are not modeling trips, so you can accept the default. Note: This field also accepts T (for True) or F (for False)

F

MinimumValue1 Specifies the minimum value, in units specified by MinMaxValueType1, above which the tariff must be applied. Note: MinimumValue2, MinimumValue3, MinimumValue4, and MinimumValue5 fields are also available in the spreadsheet but not used in this example.

MaximumValue1 Specifies the maximum value, in units specified by MinMaxValueType1, for the movement. In this case, movements are limited to 40,000 pounds. Note: MaximumValue2, MaximumValue3, MaximumValue4, and MaximumValue5 fields are also available in the spreadsheet but not used in this example.

40000

MinMaxValueType1

This value identifies the unit on which the MinimumValue1 and MaximumValue1 restrictions are applied. Note: MinMaxValueType2, MinMaxValueType3, MinMaxValueType4, and MinMaxValueType5 fields are also available in the spreadsheet but not used in this example.

Weight

Other Comments

Enables you to enter optional comments detailing the tariff information. This field is not used in the conversion process.

Create the remaining lanes Use the same process to create the remaining seven lanes and their rates required for the Truckload problem. The values for the records are displayed in the following table:

Field Record 2 Record 3 Record 4 Record 5 Record 6 Record 7 Record 8 Carrier TLCARR TLCARR TLCARR TLCARR TLCARR TLCARR TLCARR

Service TL TL TL TL TL TL TL

Tariff blank blank blank blank blank blank blank

Equipment blank blank blank blank blank blank blank

DivisionCode blank blank blank blank blank blank blank

RateCode blank blank blank blank blank blank blank

UOMType Imperial Imperial Imperial Imperial Imperial Imperial Imperial

DimWeight Factor

blank blank blank blank blank blank blank

UnitDivide Factor


ChargeType Distance Distance Distance Distance Distance Distance Distance



Field Record 2 Record 3 Record 4 Record 5 Record 6 Record 7 Record 8 LookupType blank blank blank blank blank blank blank

LookAheadRule


RateType PerUnit PerUnit PerUnit PerUnit PerUnit PerUnit PerUnit

TeamDriver blank blank blank blank blank blank blank

MinCharge blank blank blank blank blank blank blank

MinCharge Location


PerUnitOr PercentOrFlat Charge

1.4 1 1.1 1.4 1.5 1.2 0.75

RateRangeID blank blank blank blank blank blank blank

OriginZoneCode


OriginHubID blank blank blank blank blank blank blank

OriginPostal Code


OriginPostal CodeEndRange


OriginState PA PA PA OH OH OH OH

OriginCountry

USA USA USA USA USA USA USA

DestZoneCode


DestHubID blank blank blank blank blank blank blank

DestPostalCode




DestState IL IN KY MI IL IN KY

DestCountry USA USA USA USA USA USA USA

TransitTime blank blank blank blank blank blank blank

PointToPointOr RoundTrip

PointTo Point

PointTo Point

PointTo Point

PointTo Point

PointTo Point

PointTo Point

PointTo Point

EligibleFor Continuous Moves

F F F F F F F

MinimumValue1




Field Record 2 Record 3 Record 4 Record 5 Record 6 Record 7 Record 8 MaximumValue1

40000 40000 40000 40000 40000 40000 40000

MinMaxValue Type1

Weight Weight Weight Weight Weight Weight Weight

Other Comments


Create the charge for stops For this rating model, a charge of $50 is levied at every stop. Create the record using the values in the following table:

Field Record 9 Carrier TLCARR

Service TL

Tariff blank

Equipment blank

DivisionCode blank

RateCode *

UOMType Imperial

DimWeightFactor blank

UnitDivideFactor blank

ChargeType Stops

LookupType blank

LookAheadRule blank

RateType PerUnit

TeamDriver blank

MinCharge blank

MinChargeLocation blank


50

RateRangeID blank

OriginZoneCode blank

OriginHubID blank

OriginPostalCode blank

OriginPostalCodeEndRange blank

OriginState blank

OriginCountry blank

DestZoneCode blank

DestHubID blank

DestPostalCode blank



Field Record 9 DestPostalCodeEndRange blank

DestState blank

DestCountry blank

PointToPointOrRoundTrip blank

EligibleForContinuousMoves

F

MinimumValue1 blank

MaximumValue1 blank

MinMaxValueType1 blank

Other Comments blank

Convert the data to a rating database Transportation Modeler provides an Access database that you can use to convert the data entered into the Excel spreadsheet into an Access-based rating engine. This database, TariffConverter.mdb, contains both the tables into which the rating data is populated and a macro that converts your Excel data.

Convert the excel data to a rating database 1. Save the TariffConverterExcelTemplate.xls spreadsheet in which you entered the rating data.

2. Open the TariffConverter.mdb file.

3. Select Macros.

4. Select the Convert Excel Data macro and click Run. The Convert Excel Data dialog box is displayed.

Alternate step:

• Select Database Tools > RunMacro. Select Convert Excel Data and click OK.

5. Enter the Excel spreadsheet path and filename or click Browse and navigate to the Excel TariffConverterExcelTemplate.xls spreadsheet and click Select.

6. Enable the Delete Existing Data option.

7. Click Convert. The data is converted and the conversion progress is displayed. The dialog indicates Conversion Complete when the process is finished.

8. Click Close.

Set the base currency You must establish the currency to be used as the system’s base currency. The base currency will have an exchange rate of 1. All other currency exchange rates are recalculated based on any change to the exchange rate of the base currency.

Specify the base currency 1. Open the TariffConverter.mdb file.

2. Select Macros.



3. Select the Entity Manager and click Run. The Entity Manager dialog box is displayed.

4. Expand the Currencies node.

5. Select USD as currency, click and select Make Base Currency.

Acceptable field values A number of the fields in the Excel spreadsheet and in the Access database, such as ChargeType and UOMType, have a limited set of acceptable values. The TariffConverter.mdb file contains a dialog box with acceptable values for a number of the fields in the Excel spreadsheet.

View the acceptable field values in the Access database 1. Open the TariffConverter.mdb file.

2. Select Macros.

3. Select the Convert Excel Data macro and click Run. The Convert Excel Data dialog box is displayed.

4. Click View Possible Column Values. A dialog box with the acceptable values for enumerated fields is displayed.

5. Click Close to return to the Convert Excel Data dialog box.

Following are the Acceptable field values:

• ChargeType and LookupType

• DeclaredValue

• UnloadedDistance

• TotalDistance

• Distance(Same as TotalDistance)

• FreightCosts

• UserInput

• Loads

• OrderValue

• Pieces

• Stops

• Shipments

• Skids

• Volume

• Weight

• ElapsedTime

• LoadingTime

• TotalWaitingTime



• LoadedDistance

• DirectDistance

• OutOfRouteDistance

• FixedItineraryDistance

• InitialRepositioningDistance

• InTransitUnloadedDistance

• ReturnDistance

• DrivingTime

• OnDutyTime

• OffDutyTime

• UnloadingTime

• PrimaryStops

• WeekendBreakTime

• TrailerDistance

• LoadSequenceOnTrip

• ExtendedWeightDistance

• Length

• Width

• Height

• Size

• MinMaxValueType

• Pieces

• Stop

• Weight

• Volume

• Skid

• Shipment

• Load

• ShipmentValue

• OrderValue

• LadenLength

• ElapsedTime



• ContainerWeight

• ContainerLength

• ContainerWidth

• ContainerHeight

• ContainerLongestSide

• ContainerSecondLongestSide

• ContainerShortestSide

• TotalWaitHours

• WaitBetweenLoadsHours

• ElapsedHours

• WaitStopHours

• OnDutyHours

• OffDutyHours

• OutOfRoutePercent

• OutOfRouteDistance

• LoadingHours

• UnloadingHours

• DeadheadDistance

• DeadheadPercent

• RepositioningDistance

• UnloadedTractorDistance

• UnloadedTrailerDistance

• MaxTotalDistance

• UOMType

• Imperial

• Metric

• RateType

• Flat

• Percentage

• PerUnit

• Allow Pick/Drop

• Yes



• No

• Conditional

• MinChargeLocation

• Service

• Charge

• Rate

• True/False, Yes/No

• T

• Y

• F

• N

• LookAheadRule

• LookAhead

• LookBack

• Disabled

• LocationType

• Unspecified

• LoadAt

• Consignee

• Hub

• DC

Note: For Transportation Modeler, use Unspecified.


Create locations and shipments

Chapter 5. Create locations and shipments This chapter provides information on Transportation Modeler scenarios and how to build model data and create location and shipment records using the Transportation Modeler user interface.

Understand Transportation Modeler data These topics provide information about the data that Transportation Modeler uses.

Scenarios A scenario is a database of Transportation Modeler. Scenarios consist of models and plans containing data that was either entered, imported, or system- generated. For this modeling exercise, you create a new scenario that stores the location and shipment information defined in this exercise.

Models are combinations of data tables. Data tables allow you to view and edit records. Viewing the data in a model helps you to analyze data and optimize business strategies.

Plans are system-generated records that allow you to view the results of optimizing. Plans rely on the information you input into the model. There are a number of ways to view the model results. You can display maps, summary views and aggregated data.

The building blocks of models and plans are records, which represent real-world elements.

Note: Not all input tables are required. The self-paced training will guide you through the necessary steps to create a valid scenario for optimization and result analysis.

Create a new scenario 1. Open Transportation Modeler.

2. Perform one of the following tasks:

• Do the following:

a. Select File menu from the ribbon.

b. Click New .

• Click on the quick access toolbar.

3. Select the File menu and click Save As The Save As dialog box is displayed.

4. Navigate to the folder in which you want to save the file.

5. Enter a name for your scenario file and select Transportation Modeler scenarios files (*.tm) from the Save as Type drop-down list.

Note: You can save a scenario as a Microsoft Access database by selecting Access Database (*.mdb) from the Save as Type drop-down list. This creates a Microsoft Access database file into which Transportation Modeler exports all information from the scenario.

Entities Entities are the building blocks of a Transportation Modeler shipment network. They are single-keyed records in which the key value must be unique across the table.



Entity requirements The minimum requirement for optimization is to have Locations and Shipments defined. For this exercise, since all locations in the model are assumed to be open 24/7 (24 hours a day, 7 days a week), you do not have to model default business hours. Transportation Modeler assumes that if a location does not have business hours associated with the location, then that location is open 24/7. In the case where locations have specific business hours, you must model time windows and business hours.

Create locations The first step in creating a data model is to create the location entities. Locations are the origins and destinations of goods flowing through the transportation network. Each location must have a valid country code, and:

• city/state or postal code, or

• city/state/postal code, or

• lat/lon position.

It is better to provide as much information as possible about the location, since the distance retrieval process between locations is more accurate when more information is provided.

This exercise will walk you through the process of entering raw locations in combination with using data utilities to provide all the necessary location data.

Create a new location entity record using New 1. Click Location on the Control Center or Right-click the table name on the Control Center, then

select Detail Table from the shortcut menu. The Location Detail Table is displayed.

2. Click New on the Detail Table. The Create New dialog box is displayed.

3. Enter the record name in the Name field. Use a recognizable description as the name. For this exercise, you can name each location ID by the city name. Enter Pittsburgh as the first location.

4. Click OK. You can now see the new entity in the grid.

5. Repeat steps 2 through 4 to create the remaining six unique location names:

• Detroit

• Chicago

• Indianapolis

• Louisville

• Gary

• Cleveland

Modify location records You can modify data records within Transportation Modeler. You can also choose to perform required data modifications completely outside of Transportation Modeler. Transportation Modeler supports data modification through a number of data modification utilities.



When you open a Detail Table in Data View, you can view specific information about that record in a spreadsheet-like format. The records displayed are based on the query specified in Query View. When you first open a Detail Table, all records are shown in the Data View. To limit the records shown, you can filter using the filter cells in the top row of the grid, or you can click Edit Query to go to the Query View.

You can also use data view to add data to fields or to modify existing field data.

Open the Location detail table in data view By default the table opens in the data view. If you have selected Edit Query to go to the query view, you can return to the data view by selecting records and clicking Execute.

This guide assumes that at the start of each new step, any table in that step is not already open. If the table is already open, then the table may be in Query view. To perform steps that take place in the Data view, select all keys and click Execute to return to the Data view.

Set the Sort Order Use the Display Properties dialog box to set the sort order of the records in your table.

1. Right-click on the data table, then select Display Properties from the shortcut menu. The Display Properties dialog box is displayed.

2. Click the arrow buttons until the data field is in the position you want. Or, drag the SORT BY ABOVE ITEMS bars below the last field by which you want to sort.

Note: If you do not want to use a data field to sort, move the field name below the SORT BY ABOVE ITEMS bar.

3. Click OK.

Add location data You can add data to the fields when the data table is displayed in Data View.

1. Click the Location table name on the Control Center or, right-click the table name on the Control Center and select Detail Table from the shortcut menu.

2. Select the field in the table and either enter information in it or select a value from the drop-down list. The following table shows the information that you should enter for the seven location records:

LocationID City State Country Postal Code Chicago Chicago IL USA 60608

Cleveland Cleveland OH USA 44101

Detroit Detroit MI USA 48206

Gary Gary IN USA 46402

Indianapolis Indianapolis IN USA 46204

Louisville Louisville KY USA 40217

Pittsburgh Pittsburgh PA USA 15219

Use data utilities to populate Lat/Lon information A series of data utilities provided with Transportation Modeler provides you with the ability to use values you have already defined in particular tables to derive the values in other fields.



The following Transportation Modeler data values are associated with data utilities:

• City

• PostalCode

• LatLon

This exercise requires you to use data utilities to set the lat/lon associated with each location. The lat/lon information is required for distance lookups in the default distance engine used in the exercise. The lat/lon is also required to properly draw information on the Transportation Modeler map views.

Use the data utilities There are three ways you can access the data utilities:

• Query view: The Set option provides drop-down lists of utilities for each of the fields that you can update.

• Data view: Each of the fields that you can update through a utility offers a pull-down list of the corresponding utilities.

• Map view: When you add or move a location on a map, the Set Location dialog box provides access to all corresponding utilities.

Following are the lookup utilities that affect each field:

• City: Closest by LatLon

• Postal Code: Closest by LatLon

• LatLon: City Centroid, Postal Code

For this exercise, use the Data View to set all lat/lon information for all locations. Before doing this, you first must load the location translation tables into your scenario.

Location translation tables To use one location value to determine the value of another, you must load the data utility location tables.

Load data utility tables 1. Select the Home tab from the ribbon.

2. Click Data Utilities in the Utilities group. The Data Utilities dialog box is displayed.

3. Select the City - Lat/Lon Translator or the Postal Code - Lat/Lon Translator check boxes (or both) to indicate the data utility table(s) that you want to load.

Note: The Data Utilities dialog box shows currently selected tables and their databases. If no tables are selected you must use the Data Utilities tab in the Options dialog box to select appropriate tables.

4. Click OK. The Progress dialog box is displayed as Transportation Modeler loads each database. The Progress window closes when the tables are successfully loaded. The data utility tables are displayed that are loaded in the Status Bar.



Location translation databases Location translation databases designate location sources and limits that provide translations. The City <->lat/lon source converts city, state, and country locations to their latitude and longitude (focal point used in distance calculations). The PostalCode <-> lat/lon source converts postal code and country locations (used by rate tariffs) to their latitude and longitude. You can define the limits for these translations in either miles or kilometers.

The Locations_V2000.mdb database in the Data Utilities folder (by default, C:\jda\tmod\9.0\datautilities) contains default tables with city, latitude/longitude, and postal code tables.

Modify the lat/lon Data Using Data View You can edit data in the fields and modify data using Set, Adjust, and Scale data modification utilities in Data View.

Access the data modification utilities You can edit data in the fields, or you can modify data using the Set, Adjust, and Scale data modification utilities in Data View.

To access the data modification utilities, peform one of the following tasks:

• Right-click on the gray part of the Detail Table and select Field Values from the shortcut menu.

• Right-click on a record in data view and select Field Values from the shortcut menu.

• Click a table name in control center and select a value in detail table to enable the Set, Adjust, and Scale data modification utilities.

Following are the functions to modify data:

• Set: Use this utility to define values for a specific record field (viewable in data view). The Set Values dialog box prompts you to select a record field for which you want to set a value. Clicking Set applies this value to this field for all selected entities.

• Adjust: Use this utility to adjust the value for certain record fields (viewable in data view). The Adjust dialog box prompts you to select which record field to adjust, and what value to adjust all records by. For example: If the OrderValue is 300 and you choose to Adjust by a value of 200, the new OrderValue value for the selected records is 500. Clicking Adjust applies this value to this field for all selected entities.

• Scale: Use this utility to scale the value for certain record fields (viewable in data view). The Scale dialog box prompts you to select which record field to scale, and by what value to scale all selected records. For example: If the OrderValue is 300 and you choose to Scale by a value of .5, the new OrderValue for the selected records is 150. Clicking Scale applies this value to this field for all selected entities.

Set the lat/lon 1. Click the Location table name on the Control Center. The Location Detail Table is displayed.

2. Select all records by clicking the top left of the grid.

3. Click Set.

4. Select LatLon in the Set Field Value dialog box.

5. Select City Centroid and click Set from the drop-down list.



6. Click OK to dismiss the message, that is displayed on the updated rows

7. Click Close.

Create shipments Shipments represent the transportation orders moving from an origin to a destination. Once locations are created, shipments consider these named locations as origins and destinations. Shipments contain information including weight, cube, early and late pickup and delivery windows, and other attributes.

Few of the shipment fields are required. At a minimum, you need Origin, Destination and one of the following: Weight, Cube, Pieces, or Skids. If no shipment windows are defined (that is, early or late pickup/delivery times), then the earliest scheduled date in the OptParameter.txt file will dictate the early horizon for the shipments.

For this exercise, you will create 14 unique shipment records. Once you create the shipment IDs, then you are able to modify those records and add the appropriate shipment characteristics. You will use the same techniques as you did when you added and modified location records.

Create the Shipment records 1. Click the Shipment table name on the Control Center. The Shipment Detail Table is displayed.


3. Enter the record name in the Name field. Each shipment requires a unique identifier. For this exercise, use integers as Shipment IDs. For the first shipment, enter 1.

4. Click OK. The dialog box closes and the new entity is displayed.

5. Repeat steps 2 through 4 to create the remaining 13 unique shipment IDs. When finished, you have shipments 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14.

Modify shipment records Set the display order You can use Display Properties to determine which fields you want to view in the Data View and the order (from left to right) in which you want to view them.


• Right-click on the selected data table, then select Display Properties from the shortcut menu. The Display Properties dialog box is displayed.


a. Select the View tab from the ribbon.

b. Click Properties in the Query group.

2. Select the data field in the Display Order list.

3. As required, drag the data field to the position you want:

• ANCHOR ABOVE ITEMS: Places the data field in a non-scrolling region at the left of the table.

• SHOW ABOVE ITEMS: Sets the display order in which you want to view data view records.

In this case, drag Origin, Destination, FreightClass and Weight into positions directly after the ShipmentID.



Alternate steps are:

• Click the arrow buttons until the data field is in the position you want above the ANCHOR ABOVE ITEMS or SHOW ABOVE ITEMS bar.

• Drag the ANCHOR ABOVE ITEMS or SHOW ABOVE ITEMS bars after the last field you want to display.

Note: If you do not want to see a data field in data view, move the field name after the SHOW ABOVE ITEMS bar.

4. Click OK.

Add shipment data You can add data to the fields when the data table is displayed in Data View.

1. Click the Shipment table name on the Control Center. The Detail Table is displayed.

Alternatively, Right-click the table name on the Control Center, then select Detail Table from the shortcut menu.

2. Select the field in the table and either enter information in it or select a value from the drop-down list. The following table displays the information you should enter for the 14 shipment records.

ShipmentID Origin Destination Freight Class Weight 1 Pittsburgh Detroit 50 20,000

2 Pittsburgh Detroit 50 5,000

3 Pittsburgh Chicago 50 10,000

4 Pittsburgh Indianapolis 50 10,000

5 Pittsburgh Louisville 50 10,000

6 Pittsburgh Louisville 50 5,000

7 Pittsburgh Gary 50 10,000

8 Cleveland Detroit 50 10,000

9 Cleveland Detroit 50 10,000

10 Cleveland Chicago 50 10,000

11 Cleveland Indianapolis 50 10,000

12 Cleveland Louisville 50 10,000

13 Cleveland Louisville 50 5,000

14 Cleveland Gary 50 10,000

Save scenario After creating all the location and shipment data required to solve the scenario, save the scenario.

Perform one of the following:


a. Select the File menu and click Save As .

b. Enter a name for the scenario, TLScenario1 and click Save.

• Click Save in the quick access tool bar.


Set solver options

Chapter 6. Set solver options This chapter provides information on how to set the options that the Transportation Modeler solver uses during optimization. These settings include:

• The file containing the strategies used during optimization.

• The file containing the parameters that constrain the solver.

• The distance engine used during optimization.

• The rating engine used during optimization.

Access values in the Solver Options dialog box The next step is to edit values in the Solver Options dialog box. These values determine the locations of rating engines, distance engines, strategies, and parameters to use, the output directories for optimization results, and other setup features.

The values for the options are stored in the registry. In addition, you can save the options to a text file that can be reloaded at any time.

Edit Solver options 1. Select the Home tab on the ribbon.

2. Click Solver Options in the Options group. The Solver Options dialog box is displayed.

3. Edit the options on the tabs within the Solver Options dialog box.

4. Click OK. The changes you have made are saved, and the Solver Options dialog box closes.

Required values for Solver settings Here are the expected values and the definitions of those values.

Optimizer tab The Optimizer tab contains a number of settings that allow you to specify the strategy and parameters files, the distance engine and options, the output files, and other options affecting optimization.

Option Description/Required Value Files

Strategy File Optimization Parameters File

These files control the behavior of the optimization. After setting these file name values in the solver options dialog, when you need to edit the strategy or parameter file, the respective editors will default to opening these named files. This allows for easy editing and subsequent solving of scenarios. Required Value:

• Strategy File Name is C:\jda\tmod\9.0\strategies\Strat.strat

• Opt Parameters Text File is C:\jda\tmod\9.0\OptParameters.param

Reports

Report Directory

This directory houses output data in text file formats that can provide additional output information or alternate formatted output data beyond what is viewable in the Transportation Modeler scenario. Required Value is C:\jda\tmod\9.0\Reports


Set solver options

Option Description/Required Value Generate Optimization Metrics

This controls whether optimization metrics are generated post-solve. When true, all active reports are run and results are written to the Optimization Metrics table.

Outputs

Optimization Log

This file is commonly referred to as the "optlog". This is an example of a file output that gives a line by line description of load details, stop and scheduling information. It also provides a summary of the strategies run during the optimization, their costs savings, and total number of loads built and distance traveled. Required Value is C:\jda\tmod\9.0\Reports\OptLog.txt

Shipment File Generation

The Pre-Solving and Post-Solving checkboxes control whether the Solver generates the shipment file before or after optimization.

XML (Metadata) Write Options

Write Metadata

Writing metadata will write an XML representation of the input and output to the Solver. The Metadata written can be used in Transportation Planner or used when comparing optimization metrics.

Output Directory

You can specify the directory to which the XML files are written.

Miscellaneous

Measurement System

The unit of measure for distance is miles for this example and the weight of the shipments is defined in imperial units. These global settings allow you to define the base units for distance and cube/weight. In this example, you populated shipment values and rates that are based on imperial units and miles. Required Value is Imperial

Uppercase Input Data

Data in the Transportation Modeler scenario may be compared against rating information from the rating source. This data is compared including case matching. To prevent case mismatch errors, Transportation Modeler can uppercase the scenario data when sending it to the Solver.

Optimization Threads

Set the number of processors that you want Transportation Modeler to use with the HubLoop, InitLoads, OptTLLoads, and CMove strategies. Required Value is 1

Load Configuration

Engine Specifies which load configuration should be used. Either LC or LC2 can be selected. LC2 supports 64bit as well as advanced product, cylinder, item packaging, and pallet building.

Rating Engine

Reload on Optimization

Reloading the rating engine on optimization will allow any future tariff changes to propagate into the model when resolving a scenario. Required Value is Yes


Set solver options

Rating tab The Rating tab contains settings that define the rating engine to be used in the scenario. Even though Transportation Modeler supports reading more complex rating structures from data stores like Transportation Manager, the Access Rating Tool is a fast and easy way to build a tariff in a Microsoft Access database format. This method for defining rates is sufficient for this example. The rating log can be a useful tool in debugging rates when unexpected costs are associated with rated loads. Increasing the log level can provide additional information.

Once you select the Rating Engine, you must click Edit Options to access the options specific to this type of engine.

• Rating Engine: This setting allows you to select the rating engine you want to use. The Access Rating Tool creates an Access format database that is similar in table structure to the Transportation Manager rating database.

Required Value is Manager

Click Edit Options to access the Manager-specific options.

• Edit Options:

Note: Set the Database Type to Access first

• Access File:

Note: If you do not see this setting, select Access as the Database Type. This is the path and filename for the TariffConverter.mdb file.

Required Value is c:\jda\tmod\9.0\art\TariffConverter.mdb

You should change the path based on where you have installed the TariffConverter.mdb file.

• Database Type: The type of database connection you are using. It can be Oracle, DB2, Access, or ODBC.

Required Value is Access

• Division: Specifies the division from which you prefer to ship.

Required Value is blank

• Currency: Specifies the currency that Transportation Modeler uses to calculate all rates and costs.


• Consider Carrier Performance: If you set this option to Yes, Transportation Modeler activates performance based rating for optimization.

Required Value is No.

• Uppercase Strings: If you set this option to Yes, Transportation Modeler converts all rating data to uppercase when it is read. This can help to prevent case mismatch errors between rating and model data.

• Rating Threads: When using an external rating source which supports multiple connections, you can set this value greater than 1 to match the number of connections you are using.

Required Value is 1

• Use Resources From DB: If you set this option to Yes, Carrier Equipment Availability resources defined in the rating source will override those in the Transportation Modeler scenario.

Required Value is No


Set solver options

• Use Performance Data From DB: If you set this option to Yes, Lane Performance data defined in the rating source will override any data defined in the Transportation Modeler scenario.

Required Value is No

• Resource Project Type: Carrier Equipment Availability data can be separated into multiple project types. This setting specifies which project type should be used. By default, CEA data has no project type.


• CZAR Rating Directory: This setting allows you to specify the directory that contains the CZAR rating files.


• RateWare Server: This option allows you to rate using the RateWare Server

• Server: The name of the server that is hosting the RateWare server.


• Port: The port number on the server that is hosting the RateWare server. The default port is 23700.


• Connections: If the RateWare Server license supports multiple simultaneous connections, specifying a value equal to the number of allowed connections will improve external rating performance.

• RateWareXL / CarrierConnectXL Engine Options: The settings in this section allow you to specify the connection information if you are using RateWareXL or CarrierConnectXL. The values for these settings will be provided by SMC when you purchase these products.

• Select RateWareXL Settings to define settings for rating using RateWareXL

• Select CarrierConnectXL Settings to define settings for scheduling using CarrierConnect Web Services

• Server: The URL to use to connect with XL web services

• Port: The port number to use to connect with XL web services (usually 80 or blank)

• License Key: The license key provided by SMC

• Username: The username provided by SMC

• Password: The password provided by SMC. This will be encrypted before being stored.

• Protocol: Select the protocol to use to connect to XL web services (usually HTTP 1.1)

Required Values are all blank


Set solver options

Distance tab Option Description/Required Value

Engine The distance engine being used is an i2 distance engine. The default engine provided contains limited information and produces simple "as the crow flies" distances for locations that have lat/lon information. This is sufficient for the example analysis in the self-paced training. Required Value is i2.

Unit of Measure

The unit of measure for distance is miles for this example and the weight of the shipments is defined in imperial units. These global settings allow you to define the base units for distance and cube/weight. In this example, you populated shipment values and rates that are based on imperial units and miles. Required Value is Miles

Distance Override File

Defines the name of the optional distance override file. The distance override file is a semi-colon delimited text file. It accepts the following formats: Location 1;Location 2;Distance;Time

Or, Location 1;Location 2;Distance;Time;Engine Type;Service Code;Tariff ID

Update Override File

If you select this check box, the Distance Override File is updated each time a call is made to the distance engine. This option requires write access to the Distance Override file.

i2 Distance Directory

You specify the location of the distance engine files with this field. Required Value is C:\jda\tmod\9.0\i2distanceengine.

Use Lat/Lon This allows the lat/lon from the location to be passed to the optimizer for distance calculations (required for this exercise). Required Value is Yes

Once you have defined the solver options, you can save the settings to an options text file. You can then reload the solver options at any time. The next two tasks are optional.

Save solver options 1. Select the Home tab on the ribbon.


• Select Save from the Solver Options drop-down list in the Options group. The Save Options dialog box is displayed.


a. Click Solver Options in the Options group. The Solver Options dialog box is displayed.

b. Right-click on the Solver Options dialog box and select Save Options. The Save Options dialog box is displayed.

3. Select the option categories you want to save and click OK.

4. Enter the name for the options file (the default name is Default.ops) and click Save. Transportation Modeler saves the selected options.


Set solver options

Load solver options 1. Select the Home tab on the ribbon.


• Select Load . from the Solver Options drop-down list in the Options group. The Open dialog box is displayed.


a. Click Solver Options in the Options group. The Solver Options dialog box is displayed.

b. Right-click on the Solver Options dialog box and select Load Options. The Open dialog box is displayed.

3. Navigate to the folder where you saved your Solver options file. The default extension for Solver option files is .ops.

4. Click Open. The Load Solver Options dialog box is displayed.

Note: The Load Solver Options dialog box allows you to select which categories of options to load from the options file. This dialog box only displays the categories of options that were previously saved in the selected file.

5. Select the option categories you want to load and click OK. The Load Solver Options dialog box closes and Transportation Modeler loads the selected options.


Baseline parameter and strategy file

Chapter 7. Baseline parameter and strategy file This chapter provides information on how to edit the Optimizer Parameters File and the Strategy File that affect the solution generated during the solve.

The Baseline parameters The next step in solving your scenario is to study the default parameters for the solution. The parameter file contains constraints that globally affect the solution. The default parameter file, OptParameters.txt, has typical default values for items like driver scheduling constraints, maximum load capacities and optimization tuning parameters affecting load composition.

The exercise asks you to ensure you to set the following driver on-duty values correctly:

• 11 hours driving time

• 10 hours off-duty time

• 10 hours off-duty maximum

• 14 hours maximum total on-duty

The Maximum Total Weight for any truck is 40,000 lbs.

This section provides a brief overview and description of the driver scheduling related parameters. There are several parameters that do not come into play for this exercise, so the description provided is for the subset of parameters affecting driver scheduling.

In the exercise, you will first set some of these values. You will then solve, then tune additional parameters beyond the first four and run subsequent solves to get a feel for the analysis phase of the exercise.

The Optimizer Parameters file is a text file that the Solver engine uses to control how it performs shipment optimization. Load, time, and carrier parameters allow you to control how the Solver engine combines shipments into loads.

The optimizer parameters file is named OptParameters.txt by default. You can override the name and location of the parameters file for individual optimizations on the Optimizer tab of the Solver Options dialog box.

You can use any text editor, or the Edit Parameter File function to make changes to the OptParameters file. You can also edit it with any standard text editor.

The format of the OptParameters file is simple:

• Each parameter is on its own line within the file.

• The value for the parameter is on the same line as the parameter, separated from the parameter by at least one space.

• The Solver engine ignores any line of the file in which it does not find a valid parameter name.

Use the Parameter File Editor to edit the Parameters File Open the Optimizer Parameters file for editing 1. Select the Home tab on the ribbon.

2. Click Edit Parameter File in the Configuration group. The Open file dialog box is displayed.



3. Select the parameters file that you want to edit. By default, the file is the one you set in the Solver Options dialog box: For example, C:\jda\tmod\9.0\OptParameters.param

4. Click Open. The parameters file opens in the Parameter File Editor.

The following Parameter File functions are available across the top of the dialog box:

• Disable Hints/Enable Hints: This function switches the Parameter File Hints on (Enable Hints) or off (Disable Hints).

• Save: This function saves changes to the Parameters file.

• Save As: This function saves the Parameters file to a new file. You must specify the file name and location.

• Close: This function closes the Parameter File Editor, prompting you to save any changes that have been made to the Parameters file.

If you enabled the Parameter File Hints, a separate dialog box is displayed containing information about the selected parameter.

Required values for the Parameter file Ensure that your Optimizer Parameters are set as displayed in the following list. Open the OptParameters.txt file, make required edits, and save the file.

• DriverMaxDriveTime: Set value to 11:00

This is synonymous with Max Drive Time. This is the maximum driving time between driver breaks. It is a portion of the DriverOnDutyTime and may not exceed the value of DriverOnDutyTime. The format is dd:hh:mm.

• DriverMaxOffDuty TimePerStop: Set value to 10:00

This is synonymous with Max Off Duty Time Per Stop or Max Break Time Per Stop. This is the maximum off duty time that a driver can take at a stop. The format is dd:hh:mm.

Note: All off duty time must be taken consecutively, so the Max Off Duty Time Per Stop should not be less than the total DriverOffDutyTime. This parameter is intended to prevent excessive break time being taken at any one stop.

• DriverOffDutyTime: Set value to 10:00

This is synonymous with Max Break Time or Max Off Duty Time. This is the amount of time a driver must break after the DriverOnDutyTime. Format is dd:hh:mm.

• DriverOnDutyTime: Set value to 14:00

This is synonymous with Total On-Duty Time. This is the maximum time between driver breaks. It includes the DriverMaxDriveTime, plus additional driver time for activities such as loading and unloading. Format is dd:hh:mm.

• MaxOutofRoutePct: Set value to 50

This is the total out of route percentage allowed for any load. This controls the "straightness" of the load. Smaller out of route percentages means that stops on the load are more generally in-line Out of route percentage is the total distance of the load minus the direct distance "distance from initial origin to final destination" divided by the direct distance times 100. (TD-DD)/DD*100

• MaxLoadWeight: Set value to 40000



Even though the max weight is set on the tariff service, the global max weight is important to set to a reasonable value, which is the largest TL capacity across all tariff/services. Setting the global maximums for weight/cube properly allows the solver to make better estimations in the solve during load building.

Save the Parameters file Click Save. The Parameter File Editor saves the Parameters file to its current file name with all modification.

Exit the Parameter File Editor 1. Click Close.

2. If you make any changes to the Parameters file, you are prompted to exit even though changes have been made. Click Yes to exit without saving changes to the file or No to continue editing the file.

Baseline Strategy file Now it is time to create a valid strategy file for the scenario you are solving. You need to understand the problem you are solving first, then apply strategies that you think will solve that problem. Most users need to iterate a number of times to tune the strategies in an effort to decrease cost and increase load efficiency. This exercise will bring you through that process.

Here is the first problem you need to solve based on the description at the beginning of the exercise:

• The shipper in question would like to see a baseline of their current operation before looking at the possibility of consolidating the multiple origins in Pittsburgh and Cleveland. The shipper would like to see you provide him a strategy file, parameter file, and opt log that describes the baseline behavior. The shipper runs both same origin - same destination truckloads and same origin - multiple destination truckloads. Remember, the strategy file should be as simple as possible.

• To understand how to craft a valid strategy file to solve this scenario, you must understand some things about strategies and how to edit them through the Strategy File Editor. This exercise will guide you through using common load building strategies to achieve your desired optimization result.

• Transportation Modeler provides very good default strategy sets for hub splitting, continuous moves, and load building; however, these strategies are meant to be a guide on the power and the flexibility of the strategy invocation within the tool. They are meant to be a good starting point. Ultimately, understanding how to create strategies in the proper sequence and how to tune them is the best way to achieve cost savings. Therefore, this exercise will not use the default strategy sets located in C:\jda\tmod\9.0\strategies, but instead will use a simplified version of strategies as a starting point for doing the baseline run. First, you will learn how to use the editor, then you will study the baseline strategy file.

Study the Baseline Strategy file Open the baseline strategy file. For example, C:\jda\tmod\9.0\strategies\Strat.strat.

By default, the strategy file editor should be pointing to this file since you configured the strategy file setting in the Solver Options Dialog.

The file has several strategy file lines for you to study. This information will help you answer the following:



• Plan out your strategy first before creating your strategy file. Often times users jump into solving before coming up with an effective way to solve the problem. Write up a general approach to solving this particular problem and ensure you to keep it for your solution. For example: "Since I need to combine like origins and destinations, I should run a __________________, and it should be run third after this other strategy.

• Once you write up this approach, you should implement your approach by creating a strategy file.

You can look at the definition of each strategy and the meaning of each argument by using the strategy file editor hints. By clicking on the parameters for each strategy in the editor, you will see a parameter definition pop-up in the hints dialog. Feel free to click around and look at the set of parameters per strategy. Most do not need to be altered to get quality answers from the solver. However, this exercise will focus on adjusting some of those parameters to improve cost savings.

Strategy approach Since the shipper runs same origin/same destination moves, you should use a ConSamePickAndDrop strategy. Since the shipper also runs single-pick multi-drop truckloads, you should run the Con strategy. The Con should have the origin radii set to zero, because this prevents any multi-picks from occurring. You should run the ConSamePickAndDrop first because you want to consolidate the like origin/destination pairs first. Once these potential stops are consolidated, it will make the Con more cost effective because you can make one stop and pick up multiple shipments at a stop going to the same destination stop.

You can see that the baseline strategy file follows this pattern. After the solver rates each shipment initially onto its own load (this step is done automatically by the solver without needing to define it in the strategy file), the ConSamePickAndDrop consolidates same origin/same destination loads from those initially rated individual loads. It then uses Con to build the multi-stop loads based on the end state of the ConSamePickAndDrop.

This process illustrates why the order of the strategies is so important. The strategies operate on the current state of the plan; therefore, you need to carefully plan out the invocation order of the strategies. There are more complex ways to save and retrieve multiple plans within the same solve, but for this exercise, those techniques (that use Plan Stack functions) are not required.

Baseline Strategy parameter settings The following baseline parameters and exercise guide you to adjust these values in the second baseline run. For now, simply note the following parameters and understand how you will affect change in the solver by adjusting these parameters in the exercise.

In the first baseline run, you will run these strategies "as-is". The following are the some of the parameters that can affect the plan results.

Strategy parameters that affect plan results are:

• ConSamePickAndDrop: No parameters to study - use defaults.

• Con:

• Origin Radius: Since the baseline only consolidates multi-drops, the origin radius should be 0.

• Destination Radius: The customer initially only consolidates destinations only within 350 miles.

• Max Insertion Percentage: This value is the default set to 50% - this means that when the Con and the OptTLLoads algorithm attempt to insert stops to create multi-stop loads, the maximum out of route between any two stops can be no more than 50% out of route.



• OptTLLoads:

• Origin Radius: Since the baseline only consolidates multi-drops. The origin radius should be 0.

• Destination Radius: The customer initially only consolidates destinations only within 350 miles.

• Max Legs to Move: 3 is the default, this is a performance parameter to limit number of combinations tried.

• MinDistanceImprovement: Default is 0.

• ResequenceStops:

• MinDistanceImprovement: Default is 0.

Edit a strategy file Open a strategy file for editing 1. Select the Home tab on the ribbon.

2. Click Edit Strategy File in the Configuration group. The Open file dialog box is displayed, which lists the strategy file.

3. Select the strategy file to edit. For example, C:\jda\tmod\9.0\strategies\Strat.strat.

4. Click Open. The selected strategy file is displayed in the Strategy File Editor.

The following Strategy File Editor functions are available across the top of the dialog box.

• Text/Wizard: This function switches the strategy file editor between the default Wizard Mode and a standard Text Mode.

• Disable Hints/Enable Hints: This function switches the Strategy Editor Hints on (Enable Hints) or off (Disable Hints).

• New Line: New Line inserts a new (blank) line immediately after the currently selected line.

• Toggle Comment: Comments and uncomments the selected part of the strategy file.

• Delete Line: Delete Line deletes the currently selected line. This function requires confirmation.

• Compile: This function checks the validity of the current strategy file.

• Save: This function saves changes to the strategy file. The strategy editor remains open.

• Save As: This function saves the current strategy file to a new file, with the name and location that you specify.

• Close: This function closes the strategy file editor, and prompts you to save changes to the strategy file.

Edit a line in the Strategy File 1. In the Strategy File View, select the line that you want to edit.

2. Use the Line Editor and Required Parameters sections to define or edit the line. Click the Type menu button, then select the type of line to create.



• If you select Comment as the type, enter text in the Comment field.

• If you select a type other than Blank Line or Comment, click the Function menu button to select the specific function, then adjust the parameters as needed. You can optionally enter text in the Comment field.

3. Move the cursor to another line in the Strategy File View to end the edit and post the changes. If you are adding or editing a comment, move the cursor to another line to post the changes.

The following Types and Functions are available in the Strategy File:

• Most Common: This section combines multiple types of functions which are commonly used

• Blank Line: A blank line, typically used to organize sections of the file.

Note: The Comment field is not available for Blank Line entries.

• Comment Line/Uncomment Line: This function inserts a pound sign (#) preceding the text entered. When a line of text is preceded by a #, the line is ignored by the compiler and the optimizer. If the selected line is already a comment line, the Type (in the list of Types) will change from Comment Line to Uncomment Line.

• Control Function: Use these functions to control the order in which Transportation Modeler reads the contents of the strategy file.

• Global Parameter Function: These functions enable you to reset some of the optimization constraints within the strategy file.

• Plan Comparison Function: Use plan comparison functions to compare two plans that you identify. You assign selected plans to plan variables for comparison.

• Constraint Function: These are functions that enable you to enforce constraints during optimization.

• Plan Stack Function: This functionality offers a simple way to loop through a series of plans. You can then merge the entire array of plans in the plan stack using one function.

• Log Function: Log functions enable you to control how and when the Solver engine creates information logs during optimization.

• Filter Function: Filter functions enable you to optimize a specified sub-section of your plan.

• Strategy Function: These functions control load and trip building during optimization.

• End of Block: Indicates the end of a block within the file that starts with one of the block functions: If, While, or For. You cannot select this type; it is set for an existing line by the Strategy Editor.

• All Commands: All possible functions

• Unknown: An unknown line type within the file. You cannot select this type; it is set for an existing line by the Strategy Editor.

Use the Line Editor and Required Parameters You can use the Line Editor and required Parameters sections of the Strategy File Editor together to make entering and editing strategy file lines easier, and to prevent errors.

Edit the strategy file 1. In the Strategy File View, select a line in the strategy file to edit.



Note: You can enter a blank line if you want to add new information to the file.

2. Click the Type menu button, then select the type. The Strategy File Editor updates the list of functions available to you to reflect the selected type.

Note: The Blank Line and Comment Line types do not offer Functions. You cannot select End of Block or Unknown; these types indicate lines that you have selected.

3. Click the Function menu button, then select the function. If the function requires parameters, the Strategy File Editor displays the parameters and their default values in the Required Parameters section of the dialog box.

4. Enter the Comment value. If you enter a comment value to a line that already contains another function, the Strategy File Editor adds the comment at the end of the function line, with the pound sign (#) preceding it. You must click on or tab to another line in the file to record the comment.

5. Edit the Parameters.

6. Click Save after making the changes to the strategy file. Alternatively, click Close if you want to close the file without saving changes.


Solve and analyze the baseline scenario

Chapter 8. Solve and analyze the baseline scenario In this chapter, you will solve the scenario and learn how to analyze the results.

Solve the scenario You are ready to optimize the scenario. You can validate the records prior to the solve. In order to solve, all the records must pass data validation steps. These steps ensure allowable values are set on a field by field basis. You can also simply solve without validation, but if there are issues with the data model validation, you will not be allowed to proceed with the solve.

Validate the scenario 1. Select the Home tab from the ribbon.

2. Click Validate in the Scenario group. Transportation Modeler validates the data at the record level for the entire scenario. If errors or warnings occur during validation, a message box is displayed specifying the total number of errors or warnings for the record type. If there are no errors or warnings, Transportation Modeler reports No invalid records detected.

3. Click OK.

If the validation step is successful, you can now optimize. If you do receive validation errors, you must review the invalid records and correct the invalid condition. The SolverValid field in the table provides information about why the record is invalid.

Optimize your scenario 1. Open the scenario that you want to optimize.

2. Select the Home tab from the ribbon.

3. Click Solve in the Scenario group. Transportation Modeler starts optimizing and the Solver dialog box is displayed with the progress indicators.

Once you start optimization:

• The Solver assumes control

• The real-time optimization status is displayed in the title bar of the dialog box.

When the Solver successfully optimizes the scenario, the Solver information and the optimization results is displayed. Observe some of the properties of the solve characteristics.

Algorithms Total Cost

Distance

Loads Trips Unroutable

Initial Loads 6,099 5,395 14 0 0

ConSamePickAndDrop(1 1 1…) 4,725 4,077 10 0 0

Con(0 0 350 50 0 1 1 1 100 1 0) 3,432 2,603 6 0 0

OptTLLoads(0 350 3 0 100 1000) 3,432 2,603 6 0 0

ResequenceStops(0) 3,432 2,603 6 0 0

4. Click Update Scenario to write out the load results to the scenario.



Analyze the results You can learn a lot of information from the solver dialog and the optimization log. The optimization log contains the information from the solver dialog. You will find it at the top of the file. Here is some information you can deduce from the solver dialog box:

1. All the shipments you created are initially routable. There are no unroutables. This means you successfully created tariffs that can rate the loads and you have set constraints that enable Transportation Modeler to schedule and build valid load composition.

2. ConSamePickAndDrop correctly aggregates all potential same origin / same destination loads. There are 10 unique origin destination combinations, and the total weight is not acting as a constraint to build consolidated same origin / same destination loads.

3. The Con builds some multi-drop loads and reduces the total load count to 6.

4. OptTLLoads and ResequenceStops do nothing to improve the results.

The total number of loads is a reasonable answer, however you probably want to tune some optimization and strategy parameters to see if you can improve the answers, especially in multi-drop load building.

Here is the list of views of output data to analyze:

• Optimization Log: The optimization log provides a summary log of all loads created and stops associated with those loads. It is a text file that is not particularly good to use from a reporting perspective, but it does provide a good summary view of data when you are deciding how to adjust your parameters and strategies for subsequent runs. You navigate to the Optimization Log directory (C:\jda\tmod\9.0\Reports\) and use a text editor to open OptLog.txt.

• Plan Output in the Scenario: The Plan section in the Control Center’s Scenario tab contains a set of output tables where you can observe load details and composition. The load details are located in the Load table. The stops and schedules associated with those stops are located in the Stop table. The Pick/Drop table contains information about the individual shipments picked and dropped at each stop. You can look in these tables to understand the difference in display between the summary optimization log and the table output. Use the skills you have learned in the location and shipment data setup to query, filter, and sort information in these tables.

These output tables can be exported into Access or Excel for further analysis. These tables provide the best exportable view of the output data.

• Load Plan Explorer: The Load Plan Explorer provides a tree view of the loads and the sub-nodal stops associated with the load. The shipments picked or dropped at a stop are sub-nodes of the stops. This view is a clear graphical view of the relationships between loads and stops and shipments.

• Map View: The Map View is a geographical view of data. There is a Road Map View that supports direct integration to PCMiler and its mapping interface; however, for this exercise, you can use Transportation Modeler's mapping features. For a summary of map use, refer to "View data in maps" (on page 54). Practice the concepts and attempt to assign different colors for differing load weights for all the loads you display on the map.

View data in maps You use the maps in Transportation Modeler to view a geographical representation of model input data and model results. Transportation Modeler provides two options for viewing data in maps: Map View or PC*Miler_ Road Map. The features for each map differ slightly.

You can use Map View to:



• Specify the map zones that you can view in the map.

• Display shipments, loads, trips, locations, hubs, and domiciles.

• Create, move, and delete locations and hubs.

Note: To create or move locations in Map View, you should load the Data Utilities.

Map view In addition to working with data in Detail Tables, you can display, modify, or create several data items through Map View. You can access Detail Tables and Aggregate Tables from maps, allowing you to "drill-down" into data table details from the map.

Define map zones Map zones provide the map "backgrounds" (states, provinces and countries) on which your location, shipment and load details are displayed in Map View. You define map zones in the Map Zone Detail Table in the Display section on the Scenario tab of the Control Center.

Note: If you do not define map zones, you do not see any land masses on the map.

You can populate the Map Zone Detail Table by:

• Creating new zones in the Map Zone Detail Table.

• Importing data from the Map Zone database.

Import map zones You can import Map Zones from a standard database that is provided with Transportation Modeler.

1. Right-click on the Map Zone table name in the display section of the Scenario tab in the control center. The context menu is displayed.

2. Click Import. The Import Map Zone dialog box is displayed.

3. Click Open button at the top right of the dialog box, and select Existing. The Open dialog box is displayed.

4. Browse to the folder where your map zones are installed (by default, C:\jda\tmod\9.0\mapzones) and select MapZones_v2000.mdb and click Open.

5. Select Show All Tables in the Select Table/Filter field.

6. Select N America - US - States and click Import. Confirmation of the records successfully imported, or a log of errors, if any, is displayed.

7. Click Close to close the Results of Importing and Import Map Zones dialog boxes.

8. Open the Map Zone Detail Table. The map zones that you imported are displayed.

Create a map view Create a map view 1. Select the Map tab on the ribbon.

2. Click New in the Map View group.

3. If the Map Zones is not displayed, then follow the following steps:



• Zoom In/Zoom Out: To display a more of the map in the map window, you can Zoom Out. You can then Zoom In to a specific area of the map.

• Set Home Position: If the map is centered on a point far from your Map Zones, you can select a new center point for the view.

Zoom in/zoom out 1. To zoom out, right-click on the map view and select Zoom > Out. The Map View now shows a

larger area.

2. To zoom in, right-click on the map view and select Zoom > In... The cursor changes to a crosshair. Use the cursor to define two opposing corners of the rectangle defining the zoom area.

Set the Home Position 1. Perform one of the following tasks:

• Right-click on the Map View and select Set Home Position. The cursor changes to a crosshair.


a. Select the Map tab on the ribbon.

b. Click Home Position in the Map View group.

2. Click on a position on the map to use at the center point of the view. The view is updated. You can return to this home position at any time by selecting Set Perspective > Home Position from the right-click menu.

Set map view display properties The information you can view on the map in Map View is based on user-defined or system-generated information (you can view this information in Detail Tables). You can use the following tabs on the Map Display Properties dialog box to set the information that you can view on the map:

• Location Icons

• Hub Icons

• Shipments

• Loads

• Trips

Open the Map Display Properties dialog box 1. Perform one of the following tasks:

• Right-click on the Map View and select Display Properties from the shortcut menu. The Map Display Properties dialog box is displayed.


a. Select the Map tab on the ribbon.

b. Click Properties in the Map View group.

2. On the Map Display Properties window, for each entity type (each tab) you can choose information such as:



• Whether entities of this type get displayed on the Map View.

• The output variable for grouping/display criteria on Map View.

• Whether the legend or names are displayed.

3. To set how the shading and borders, colors, link dimensions, and labels are displayed on Map View, use the Map Display tab in the Options dialog box.

Display your locations on the map 1. Right-click on the Map View and select Display Properties from the shortcut menu. The Map

Display Properties dialog box is displayed.

2. Click on Locations tab.

3. Select User-Defined as the Model Relationship. The Display Names option is enabled.

4. Click OK. Your locations are displayed on the map.

Display your loads on the map 1. Right-click on the Map View and select Display Properties from the shortcut menu. The Map

Display Properties window is displayed.

2. Click on the Loads tab.

3. Select Load as the Model Relationship, and select TraveledDistance as the Output Variable. The Show Direction option is enabled. The legend at the right of the tab indicates the colors used to display the loads based on their TraveledDistance value.

4. Click OK. The loads are displayed on the map.

Save a map view You can use the Save or Save As function in Map View to save your changes or save an existing Map View as a new one.

1. Right-click on the Map View and select Save from the shortcut menu (or Save As to save an existing Map View as a new Map View. The Save Map View Format As dialog box is displayed.

2. Enter a unique Map View file name. The program automatically saves the file with a .map extension.

3. Click Save. The window closes and Transportation Modeler saves the map view.

Note: When closing a Map View, if it is a new view or has been edited since the last time it was saved, Transportation Modeler prompts you to save it.

Open an existing map view If you have previously created and saved a Map View, you can re-open it at any time.

1. Select the Map tab on the ribbon.

2. Click Open in the File group.The Open Outview dialog box is displayed.

3. Navigate to the map view file.

4. Click Open. The map view is displayed.

Note: The new Map View displays the zoom level, perspective, and colors from the last viewed map. You do not automatically view the Location Icons, Loads, or the Load Link Legend.



Set map view options Right-clicking anywhere on a Map View displays the Map View shortcut menu. The following table describes the options available on the Map View shortcut menu.

Option Description Display Properties Opens the Display Properties Dialog Box. This option allows you to

select the locations, hubs, shipments, and trips to display on the map.

Legends This option allows you to turn on or off the display of one or more legends. Legends. You can move them as you wish and you can hide individual legends using the shortcut menu (available when the cursor is on the legend).

Add This option allows you to add a location or hub through the map interface. The program prompts you for location information for the position of the location on the map.

Query Point... This option allows you to query a map location to retrieve information about the location name. Indicate a point on the map and you can view information about the Map Zone or Lat/Lon Point.

Set Home Position...

This option changes the pointer to a crosshair, allowing you to select a position on the map as your home position center point. You can then use Set Perspective > Home Position to return to this perspective.

Zoom This option allows you to control the level at which you can view a map. To Zoom In, you define the zoom area by dragging a rectangular boundary. Zoom Out reduces the zoom factor of the map, enabling you to see more information. Transportation Modeler saves the zoom level when you save any map format.

Set Perspective This option allows you to adjust the way you can view a map.Select Set Perspective and click Screen Location to modify the location of the map you are looking at. Select Set Perspective and click

Home Position to return to the map to the home position.

Projection This option allows you to select whether you want to view the map as a flat projection or a spherical projection.

Copy This option copies the current map view, and any displayed legends, to the Windows clipboard. From the clipboard, you can paste the map into other Windows applications through use of the Windows Paste command.

Save This option saves the current map view and settings to the currently selected map view name.

Save As This option saves the current map view and settings to a new map view name. You can view a dialog box prompting you to enter the new map name.

Close This option closes the map view. If you have not saved a new map or changes made to a saved map, Transportation Modeler prompts you to save the map.

Location and hub options Click on a location or hub on the map view to display a menu with the following options.



Option Description Move This option allows you to move locations from one position to another. First,

relocate the location icon to a new position on the map. The Set Location dialog box is displayed, enabling you to specify the City, Lat/Lon, or PostalCode to determine the new position. You must load the location translation tables to use the City and PostalCode to Lat/Lon utilities. Otherwise, the Center and Centroid functions are unavailable.

Delete This option deletes the location or hub. Prior to deletion, you can view a message that prompts you to confirm deletion of the location or hub. All records dependent on the location are also deleted when you delete the location.

Detail Table (Hub or Location)

This option opens the Detail Table for the hub or location.

Access Links This option displays a menu of tables that are linked to the location. When you select a table, Transportation Modeler displays that table. When you use Access Links, the location becomes the selection for the table.


Tuning parameters and strategies

Chapter 9. Tuning parameters and strategies In this chapter, you will tune the parameters and strategies and re-solve the scenario.

Tuning analysis The initial baseline solve showed that you can potentially make some improvements in multi-drop load composition. In this section, you will make some recommended changes that will prove effective in building better loads for multi-drops.

The recommended changes relax some constraints to allow Transportation Modeler to try additional combinations to build better loads. This exercise suggests providing large values as relaxed parameters. This approach typically is acceptable for smaller numbers of shipments (For example: under 500 shipments.). However, for larger scenarios, opening up constraints too much may cause performance degradation in the solver. There is a tradeoff between cost savings opportunities by exhausting all possibilities, and limiting the search space for efficiency gains in the solver. This is a technique that you will learn over time, enabling you to understand the tradeoff between efficient runtimes and limiting the solution quality too much. The longer the solve takes, the less amount of time you will have in an engagement to adjust parameters and re-solve. Therefore, tuning should be done carefully and you will typically tune only a small set of parameters at one time.

You will now try to build better multi-stop loads. Use the procedures you learned in "Baseline parameter and strategy file" (on page 46) to edit the key parameters you will use to achieve that goal. These parameters are described in the following table:

Parameter Value/Description MaxOutofRoutePercentage

Set value to 1000 This is a non-constraining value that will allow the optimizer full flexibility to try more combinations of stops. This is the total out of route percentage allowed for any load. This controls the "straightness" of the route selected for the load. Smaller out of route percentages means that stops on the load are more generally in-line. Out of route percentage is the total distance of the load minus the direct distance (distance from initial origin to final destination) divided by the direct distance times 100. (TD-DD)/DD*100.

Strategy Parameter Settings ConSamePickandDrop

• No parameters to change.

Con • Origin Radius: Since the baseline only consolidates multi-drops, the origin radius should still be 0.

• Destination Radius: Set the value to 1000. Open up the solver to consolidate up to 1000 miles between destination locations. This will allow all combination of all destinations to potentially be tried for multi-drop consolidation.

• Max Insertion Percentage: Increase this value to 1000%. This means that when the Con and the OptTLLoads algorithm attempt to insert stops to create multi-stop loads, the maximum out of route between any two stops can be no more than 1000% out of route



Strategy Parameter Settings OptTLLoads • Origin Radius: Since the baseline only consolidates multi-drops.

The origin radius should be 0

• Destination Radius: Set this value to 1000

• Max Legs to Move: Set this value to 6. This will allow optimizer to try more shipments to move in swapping stops from one load to another

• MinDistanceImprovement: Set this value to - 500 (negative 500). This will allow the optimizer to potentially increase distance to find a cheaper lane into another state. This means that the optimizer can do a good job of finding cheap lanes to route, and then insert multiple stops on that load. Sometimes increasing distance can reduce total cost if these advantageous lanes can be exploited.

ResequenceStops • MinDistanceImprovement: Set this value to - 500 (negative 500). Again, this is a very relaxed parameter to try to resequence as many stops as possible.

Solve and Analyze Before you solve, you should back up your old optimization log and scenario by saving a copy of each file, or renaming a new target file for the optimization log entry in the Solver Options dialog. It is good practice to save multiple optimization logs and scenarios so you can compare, analyze and store the results. In this way, you can go back to any state of your modeling exercise.

You can now solve the scenario with your updated strategies and parameters. The results are as follows:


Distance Loads Trips Unroutable

Initial Loads 6,099 5,395 14 0 0

ConSamePickAndDrop(1 1 …) 4,725 4,077 10 0 0

Con(0 0 1000 1000 0 1 1 1 100 1 0)

3,406 2,604 4 0 0

OptTLLoads(0 1000 6 -500 100 1000)

3,175 2,421 4 0 0

ResequenceStops(-500) 2,806 2,465 4 0 0

Here are the results from the previous optimization for comparison.


Distance Loads Trips Unroutable

Initial Loads 6,099 5,395 14 0 0

ConSamePickAndDrop(1 1 1…) 4,725 4,077 10 0 0

Con(0 0 350 50 0 1 1 1 100 1 0) 3,432 2,603 6 0 0

OptTLLoads(0 350 3 0 100 1000) 3,432 2,603 6 0 0

ResequenceStops(0) 3,432 2,603 6 0 0



The following are analysis points:

1. Your Con algorithm did a better job in building multi-stops. It saved some money for a slightly higher distance, which means that your tuning parameters increasing the destination radius and minimum insertion percentage were effective in saving money.

2. There was a big improvement in the OptTLLoads and ResequenceStops algorithms. You can see a much larger cost improvement and load reduction in both strategies based on the edits you made to the parameters. You have saved over 600 dollars and reduced the plan by 2 loads versus the initial baseline where no parameter and strategy tuning was done.

The lesson here is that in order to get great results from the solver, you need to understand the proper parameters to tune, and relax some parameters to achieve even better results. Let's now analyze why the cost savings were so dramatic in the new run, especially between the OptTLLoads result and the ResequenceStops result. You can see that 369 dollars were saved while increasing load distance by 40 miles.

If you review the load composition of the four loads (use any of your preferred views of output data), you will see that the multi-drop loads are now terminating in Indiana and Kentucky, where the cheapest rates are for truckload movements. Look in particular at the Indiana loads. In the first solution, you can see that Chicago Illinois, which has a high cost of movement, is prevented from moving onto a Gary, Indiana bound load because the insertion percentage and out of route would be constrained, preventing that move from occurring.

Therefore, relaxing constraints proved useful in reducing costs. You have successfully finished the initial baseline and modified baseline scenarios. You will now move onto the multi-pick movements.


Tuning and solving multi-pick/multi-drop scenario

Chapter 10. Tuning and solving multi-pick/multi-drop scenario In this chapter, you will tune the parameters and strategies to allow for multi-picks and re-solve the scenario.

Tuning to support multi-picks The final step in this scenario is to allow for multi-picks and see whether you can further reduce cost by allowing multi-picks to occur.

You need to make changes to the strategies as described in the following table:

Strategy Parameter Settings Con • Origin Radius: Since the scenario now allows multi-picks, set the origin

radius high enough to encompass combining Cleveland and Pittsburgh. 1000 miles is plenty of distance to consolidate those two cities.

OptTLLoads • Origin Radius: Set this value to 1000 to allow multi-picks.

Solve and analyze for multi-picks Solve the scenario again. You should now see the results:

Algorithms Total Cost Distance

Loads

Trips Unroutable

Initial Loads 6,099 5,395 14 0 0


Con(0 1000 1000 1000 0 1 1 1 100 1 0)

2,434 2,154 4 0 0

OptTLLoads(1000 1000 6 -500 100 1000)

2,434 2,154 4 0 0


Compare your best single-pick multi-drop run:



Initial Loads 6,099 5,395 14 0 0


Con(0 0 1000 1000 0 1 1 1 100 1 0) 3,406 2,604 4 0 0

OptTLLoads(0 1000 6 -500 100 1000)

3,175 2,421 4 0 0


You have saved an additional 372 dollars by building better multi-stops with visibility into multi-picks.


Tuning and solving multi-pick/multi-drop scenario

Final strategy tuning The rates resulted in good cost savings using the multi-pick option because the TL rates out of Pittsburgh are generally better than the TL rates out of Cleveland. Therefore, a TL can originate in Pittsburgh, stop in Cleveland to get more freight, then go to multiple destinations. Therefore, you save money by saving the per mile rate increase out of Cleveland for the added $50 stop charge.

Adjust the values of the parameters on your Con strategy to better reflect your plan. The origin radius on the Con needs to be only 200 miles in order to combine Pittsburgh and Cleveland shipments for multi-picks. The destination radius needs to be at least 500.

To further improve the solution, adjust the Max Insertion Percentage in the Con and update the MaximumOutOfRoute value in the OptParameters file from 50 to 55.

Solve the scenario. You should have the same results as when you had the parameters wide open:

Algorithms Total Cost Distance Loads Trips Unroutable

Initial Loads 6,099 5,395 14 0 0


Con(0 200 500 55 0 1 1 1 100 1 0) 2,434 2,154 4 0 0

OptTLLoads(200 500 6 -500 100 1000)

2,434 2,154 4 0 0


Note: In this case, there is no improvement made with the OptTLLoads and ResequenceStops.

You have successfully completed the scenario.

Save the scenario 1. Select the Home tab from the ribbon.

2. Click Save in the Scenario group.


LTL modeling exercise

Chapter 11. LTL modeling exercise This chapter provides an outline of the Less-than-Truckload (LTL) exercise you use in this section. A description of the modeling problem, as well as the basic data, is provided.

LTL software requirements In order to determine LTL rates, Transportation Modeler uses CZAR tariff data and characteristics of the shipments (including Freight Class). To complete this exercise, you must own CZAR tariff data and have it installed. Transportation Modeler supports the use of RateWare XL, RateWare Server, or CZAR DLL in rating using CZAR tariff data. Both RateWare XL and RateWare Server products and the tariff data are available from the SMC3 website (http://www.smc3.com). CZAR DLL is no longer available from SMC3, but can still be used if you already have it. For more information, see the JDA Transportation Modeler Installation/Administration Guide.

Note: CZAR DLL can be used without any external component only from the Transportation Modeler 32-bit application. When you use the Transportation Modeler 64-bit application, you can use JDA External Rating Server to access CZAR DLL rates. For information on how to set up and run JDA External Rating Server, see the JDA Transportation Modeler Installation/Administration Guide.

Model description Now that the shipper has done a truckload study and want to expand the study to include his LTL contract as well. The shipper wants you to use the shipment data, rates, strategy file, and parameter file from the "Truckload modeling exercise" (on page 19) and expand on it by adding new location and shipment data and rates to the ones from the earlier exercise.

Shipments The shipment data is listed as follows:

• Cleveland, OH to Riverview, MI

• 1 shipment at Freight Class 50, 1000 lbs

• Cleveland, OH to Cicero, IL


• Cleveland, OH to Lawrence, IN


You will notice that all the other shipments from the earlier exercise have Freight Class 50.

All the shipments need to leave the origins on January 18, 2002 at some point during the day.

Rates The rates for the LTL moves are listed as follows.

• The shipper has a contract with his LTL carrier for all nationwide moves in the US. He receives a 71% discount on all LTL moves. The rate basis for LTL is CZARLITE with a tariff effective date of 1/1/1998. His LTL carrier picks up at his facilities at 5pm Monday through Friday and delivers this shipment within a span of 2 days. The shipper will not give the LTL carrier any loads greater than 10,000 lbs.


http://www.smc3.com/

LTL modeling exercise

• The truckload carrier can now carry up to 42,000 pounds per truckload. He runs typical DOT rules: 11 hours driving, 10 hours break time, 10 hours maximum off-duty, and 15 hours maximum on-duty.

Analysis Overview The information provided in the description above should be enough to answer this set of questions.

1. Using the final strategy file from the "Truckload modeling exercise" (on page 19), what is the quickest way to adjust the strategy file to initially rate the loads before attempting consolidation?

2. Look at the three new shipments that you added to the scenario. Look at their unconsolidated, initial costs. Save the optimization log file. Try to answer these questions and statements about LTL shipping. If you need to perform a proof-of-concept, adjust one of the new shipments and test these questions against your LTL rates.

• All things being equal (same shipment details, vary only weight) The higher the weight, ________ the cost. (the higher/the lower/no impact to)

• All things being equal (same shipment details, vary only freight class) The higher the freight class, ________ the cost. (the higher/the lower/no impact to)

• Describe the nature of a shipment that dictates increase in Freight Class.

• As freight class increases, density _____________(increases/decreases)

• As freight class increases, crushability _____________(increases/decreases)

• As freight class increases, stackability _____________(increases/decreases)

• As freight class increases, handling ease ___________(increases/decreases)

• Given your answers in i, ii, and iii, why are LTL companies justified in their pricing structure in regards to freight class increase?

Generally, shipments that have a higher freight class take up more space for a given weight (less dense). Since LTL's rates are based on weight, as the freight class gets higher, the carrier is able to put less commodity on a given trailer. In order to offset the costs of shipping less commodity per trailer, they increase the cost for less dense, more crushable, less stackable, "uglier" freight.

3. Compare the initial loads from your LTL exercise run versus the initial loads from the "Truckload modeling exercise" (on page 19) run. What do you think is the major factor in the decrease in cost with the LTL exercise run for InitLoads?

Now that there is a lower cost alternative (LTL rating) to route a single shipment, the initial cost decreases. However, you will see when running the full strategy that there will still be savings in performing consolidation.

4. Run the full strategy. Save the optimization log file. The client is angry that the cost has increased. Help the client get over his momentary lapse in judgment by explaining why the cost increased overall at the end of this run versus the "Truckload modeling exercise" (on page 19) final run.

5. There should be one load for your LTL exercise run that goes LTL. The client is curious why this shipment did not get added on the TL that runs Pittsburgh > Cleveland > Indianapolis > Louisville. The client says, "The TL is going right by that location. What is going on???" Give him the proper analysis to explain why the optimizer made the proper decision to send the Cleveland > Lawrence shipment using LTL.


Create LTL shipments

Chapter 12. Create LTL shipments In this chapter, you add the location and shipment data required for the LTL exercise. You add this data to the Transportation Modeler scenario created for the "Truckload modeling exercise" (on page 19) and save it as new scenario.

Open an existing scenario 1. Open Transportation Modeler.

2. Select the File menu from the ribbon.

3. Click Open .

4. Select the TLScenario1.tm file you created in the earlier exercise. The scenario dialog box is displayed.

5. Click OK. The dialog box closes.

Create additional locations The new LTL shipments originate in Cleveland, which is already defined. However, they terminate in new locations – Cicero, IL, Lawrence, IN, and Riverview, MI.

Create the new location records 1. Perform one of the following tasks:

• Click Location on the Control Center. The Location Detail Table is displayed.

• Right-click the table name on the Control Center, then select Detail Table from the shortcut menu.


• Click New on the Detail Table. The Create New dialog box is displayed.

• Right-click on the gray part of the Detail Table and select Record > New from the shortcut menu.

3. Enter Cicero.


5. Repeat steps 2 through 4 to create the remaining location names:

• Lawrence

• Riverview

Modify the new location records You have to populate location data that enables Transportation Modeler to calculate distances.

Add the location data Enter the information in the table below.

Note: You can either enter your own value or select a value from the drop-down list.



The table shows the information you should enter for the new location records:

LocationID City State Country

Cicero Cicero IL USA

Lawrence Lawrence IN USA

Riverview Riverview MI USA

Use data utilities to populate Lat/Lon and postal code information You have to load the location translation tables into your scenario.


2. Click Data Utilities . in the Utilities group The Data Utilities window is displayed.

3. Select the City - Lat/Lon Translator and Postal Code - Lat/Lon Translator checkboxes.

4. Click OK. The Progress window as Transportation Modeler loads each database. The Progress window closes when all the tables are successfully loaded. The data utility tables that are loaded are displayed in the Status Bar.

Set the lat/lon 1. Click Edit Query on the Location Detail Table. The new records should be selected.

2. Click Set on the Detail Table.

3. Select the LatLon field in the Set Field Value dialog box.

4. Select City Centroid from the To drop-down list, and click Set. A message is displayed indicating that the rows are updated.

5. Click OK to dismiss the message.

6. Click Close.

Set the postal code 1. Select the new location records.


3. Select the PostalCode field in the Set Field Value dialog box.

4. Select Closest by LatLon from the To drop-down list and click Set. A message is displayed indicating that the rows are updated.


6. Click Close.

Create LTL shipments For this exercise, you will create three additional shipment records. For LTL shipments, the FreightCost and Weight values are significant.



Create the LTL Shipment records 1. Click the Shipment table name on the Control Center. The Shipment Detail Table is displayed.


3. Enter the record name in the Name field. You already have 14 shipments from the original Truckload modeling exercise. Enter 15 as the shipment ID.


5. Repeat steps 2 through 4 to create the remaining two LTL shipment IDs.

Modify the LTL shipment records Add the LTL shipment data Select the field in the table and enter the value.


The following table displays the information you should enter for the new shipment records.

ShipmentID Origin Destination Freight Class Weight 15 Cleveland Riverview 50 1000

16 Cleveland Cicero 60 800

17 Cleveland Lawrence 70 500

Save the scenario You have now successfully created all the location and shipment data required to solve the new LTL scenario. Save the scenario as a new scenario file before proceeding.


2. Click Save .

3. Enter LTLScenario1 and click Save.


Create the LTL rates

Chapter 13. Create the LTL rates In this chapter, you use the Access Rating Tool to create the LTL rates for the "LTL modeling exercise" (on page 65).

The TariffConverterExcelTemplate.xls file contains the fields you have to populate in lieu of your modeling requirements. This file contains a set of worksheets: TL, LTL, SmallPackage, RateRange, Hub, and Zones. The current truckload problem will require you to enter relevant details in the TL and LTL worksheet.

Caution: Do not change the field names in TariffConverterExcelTemplate.xls. Do not copy data from another spreadsheet or worksheet to paste into the cells in the TariffConverterExcelTemplate.xls file. Many of the cells in the template spreadsheet are defined with a specific format. Copying and pasting data can result in a change in data types and error during conversion to the Access database format.

Once you enter the rates in the Excel spreadsheet, you use the TariffConverter.mdb, an Access-format database, to convert the rates into an Access-based rating engine. This database contains a set of rating tables into which the spreadsheet data is populated using an Access macro. You can then set up the Transportation Modeler to use the Access database as its rating engine.

Create required tariffs In this section, you will update the TL tariffs you created and also create the LTL tariffs that are required to rate the shipments. The steps required to create the tariffs are:

• Update the TL tariff values.

• Enter the data for the LTL tariffs.

• Convert the data into an Access-format rating database.

Update the TL tariffs Ensure that you have the records as defined. There are distance-based rates and one stop based rate. The total weight that can be carried by the Truckload carrier has been changed to 42000. Therefore, the only change you need to make to the Distance-based tariffs you created is to change the MaximumValue1 to 42000.

1. Open the TariffConverterExcelTemplate.xls spreadsheet.


3. Enter 42000 as the MaximumValue1 for all distance-based rates.

Creating an LTL Tariff You will enter all required data onto the LTL worksheet in the TariffConverterExcelTemplate.xls spreadsheet. Each record on this worksheet represents a lane, complete with its carrier/tariff/service information.

Create the LTL tariff 1. Open the TariffConverterExcelTemplate.xls spreadsheet.

2. Select the LTL worksheet.

3. Enter the data as shown in the following table.




Field Description Value Carrier The identifier for the carrier. LTLCARR

Service The name of the mode definition. You are defining an LTL tariff.

LTL

Tariff The tariff for the tariff service. If you do not define a Tariff value, the conversion macro will concatenate the Carrier value with the Service value to define the Tariff.

Equipment The code describing the equipment used for the movement.


UOMType The Unit of Measure Type. It should be set to imperial units since the rates are based on miles and the weight constraints are based on pounds.

Imperial

SMCTariffCode The tariff code that is used when looking up information in the SMC tariffs to retrieve the LTL rates.

LITECZ02

TariffEffectiveDate

Specifies the effective date for the tariff. Note: This field is defined as a text field in Excel to allow you to enter the date as mm-dd-yyyy. This format is required for the TariffEffectiveDate value.

01-01-1998


MinChargeLocation

Use this field to define if the MinCharge is at the Service level, Charge level, or Rate level.

Discount This is the discount percentage offered for the tariff. 71


• LookAhead

• LookBack

• Disabled

The default value if the field is not populated is Disabled.

OriginZoneCode Identifies the zone at which the lane originates. The specified zone code should refer to a zone defined on the Zones worksheet. In this example, the lanes are state to state and no hub is required.



Field Description Value OriginHubID Identifies the Hub at which the lane originates. In this

example, the lanes are state to state and no hub is required.

OriginPostalCode Identifies the Postal Code at which the lane originates.

OriginPostalCode EndRange


OriginState Identifies the State in which the lane originates.


DestZoneCode Identifies the zone at which the lane terminates. The specified zone code should refer to a zone defined on the Zones worksheet. In this example, the lanes are state to state and no hub is required.





DestState Identifies the State in which the lane terminates.



2

MinimumValue1 Specifies the minimum value, in units specified by MinMaxValueType1, above which the tariff must be applied. Note: MinimumValue2, MinimumValue3, MinimumValue4, and MinimumValue5 fields are also available in the spreadsheet, but not used in this example.

MaximumValue1 Specifies the maximum value, in units specified by MinMaxValueType1, for the movement. In this case, movements are limited to 10,000 pounds. Note: MaximumValue2, MaximumValue3, MaximumValue4, and MaximumValue5 fields are also available in the spreadsheet, but not used in this example.

10000

MinMaxValueType1

This value identifies the unit on which the MinimumValue1 and MaximumValue1 restrictions are applied. Note: MinMaxValueType2, MinMaxValueType3, MinMaxValueType4, and MinMaxValueType5 fields are

Weight



Field Description Value also available in the spreadsheet, but not used in this example.

Other Comments Enables you to enter optional comments detailing the tariff information. This field is not used in the conversion process.

Use the process defined in "Convert the data to a rating database" (on page 28) to convert the Access Rating Tool spreadsheet into an Access database you can use as a rating engine.


Solve the LTL scenario

Chapter 14. Solve the LTL scenario In this chapter, you solve the scenario with the LTL data and tune the parameters and strategies as required to improve the solution.

Tune to support LTL Shipments In order to perform the analysis required, you need to:

• Update the rating settings to include the LTL tariffs.

• Verify the parameters to support the increased maximum weight.

• Update the strategy file to allow you to initially rate unconsolidated loads to determine the basic cost for the new shipments see "Analysis overview" (on page 66).

Rating Engine changes There are some changes you need to make to support LTL rating. Since you are using a CZAR tariff, you must ensure that the tariff data is installed and that Transportation Modeler is set up to use that data. You specify the tariff data location in the Solver Options dialog.

Update the solver options 1. Select the Home tab on the ribbon.

2. Click Solver Options in the Options group. The Solver Options dialog box is displayed.

3. Click the Rating tab.

4. Enter the path to the folder where your CZAR tariff data is installed, in the CZAR Rating Directory field.

Parameter file changes Ensure that the parameter file is not constraining the new maximum weight supported per load.

• MaxLoadWeight: Set value to 42000. This is the maximum total weight per load.

Strategy file changes You have to limit the optimization to building initial loads only. In this way, you can get a base cost for each shipment. One way to do this is to put QUIT() at the beginning the strategy file. Since InitLoads is run automatically, the QUIT() ends the optimization before the remaining strategies are run.

Solve and analyze for LTL Solve the scenario. You should now see 17 loads built, one for each shipment:


Initial Loads 4,188 6,305 17 0 0

Save the OptLog.txt from this initial run. Look at the cost per load when each is one shipment sent LTL.

Now run the full strategy file from the final truckload exercise, using the LTL scenario:


Solve the LTL scenario


Distance Loads

Trips Unroutable

Initial Loads 4,188 6,305 17 0 0


Con(0 200 500 55 0 1 1 1 100 1 0)

2,593 2,522 5 0 0

OptTLLoads(200 500 6 -500 100 1000)

2,593 2,522 5 0 0


You should have one load that was sent LTL. This would be the Cleveland to Lawrence shipment. Why is this shipment not added to the Pittsburgh to Louisville TL load?

Look in the OptLog.txt at the cost of the load from Cleveland to Lawrence or open the Load Detail Table in Transportation Modeler and check the cost of the load that is using LTLCARR. It should be about $49. If you were to add another stop to the Pittsburgh to Louisville TL load, what additional cost would be incurred? Remember, the TL tariff charges $50 per stop, so adding the stop is more expensive than creating the LTL load.

Comparing to your best truckload run:



Initial Loads 6,099 5,395 14 0 0


Con(0 200 500 55 0 1 1 1 100 1 0) 2,434 2,154 4 0 0

OptTLLoads(200 500 6 -500 100 1000)

2,434 2,154 4 0 0


The client is angry that the overall cost has gone up. How is this justified? Keep in mind that while the Total Cost has gone up, you have added 3 shipments to the plan.


Hub modeling exercise

Chapter 15. Hub modeling exercise This chapter provides an outline of exercise where you add a hub to the scenario you built earlier in the Truckload and LTL exercises. A description of the modeling problem, as well as the basic data, is provided.

Model description Now that the shipper has done a truckload study and an LTL study, he wants to study the effectiveness of a centrally located hub optimizing the same 17 shipments from the "LTL modeling exercise" (on page 65). The shipper wants you to use the shipment data, rates, strategy file, and parameter file from the "LTL modeling exercise" (on page 65) and expand on it by adding a new hub record and the rates to support the hub in his transportation network.

Hub The hub is located in Fort Wayne, IN, 46801. The TL carrier owns the hub. Both LTL and TL carriers are allowed to pick and drop at the facility. The hub is open 24 hours a day, 7 days a week.

Rates The shipper has a contract with his TL carrier providing special rates inbound and outbound from the hub.

• The rates inbound to the hub from the origins PA and OH are $0.75/mile and $50/stop.

• The rates outbound from the hub to IL, IN, KY, and MI are $0.75/mile and $50/stop.

The cross dock rate is $0.40 per hundredweight.

The parameters file should remain the same as in the "LTL modeling exercise" (on page 65) study.


1. In order to ensure that all your shipments can split through the hub, you should first run a HubAssignment by itself and ensure your arguments are configured properly.

• If you have 17 shipments, how many shipment legs would you expect to see if everything split through a hub?

• What should be your maximum number of origin and destination hubs? You can determine this without running any solves.

• How large should your radii be for origin and destination radii? Sometimes, the best way to tell is to make those values very large, do a run, and look at the optimization log to see the total set of inbound and outbound distances to and from the hub.

• By using the default values in HubAssignment and playing with the number of hubs and hub radii, you should see a few shipments that still do not split through a hub. What other parameter could you alter that may constrain the few shipments from splitting? (Hint: Think about the direct distance from origin to destination, then think about the distance added by splitting the shipment through a hub). What is the correct value for this parameter (to the nearest 25)?


Hub modeling exercise

2. Now that you have the HubAssignment set properly, you should be able to incorporate the hub portion of your strategy into the base strategy from the previous study.

• The client wants to run the HubAssignment by splitting unconsolidated shipments first, then consolidating the split legs. However, he wants to run the hub section of the strategy after the baseline strategy that does normal consolidation. You will have to create a new Set ( variable GETPLAN () ) to later retrieve the plan where nothing is consolidated. Where should you set the "unconsolidated" plan in the strategy file?

• Once you retrieve this plan, you should run HubAssignment and then consolidate your split legs. Use a ConSamePickDrop and subsequently a Con with the same values as the multi-pick/multi-drop Con strategy you have in the existing strategy file.

• What is the correct way to merge this plan with the other two plans in order to have an all-encompassing merge that considers direct single-pick/multi-drop, direct multi-pick/multi-drop and hub splitting with consolidation of split legs?

3. Once you create your strategy file, you can run it. What is the cost difference between sending the freight direct single-pick/multi-drop, direct multi-pick/multi-drop, and hub splitting with consolidation of split legs? What did the merge ultimately choose as the most cost effective plan?

4. The hub plans on increasing the cross dock charge at Fort Wayne to $0.52/CWT because a new labor contract has increased the operating expenses of the dock. How does this affect the solution? What is the cheapest alternative now?


Create the hub

Chapter 16. Create the hub In this chapter, you will add the hub to the Transportation Modeler scenario you created for the LTL modeling exercise, then save this as a new scenario.

Open an existing scenario If you do not currently have the scenario opened from the LTL modeling exercise, you should do so now.

Open the existing scenario 1. Open Transportation Modeler.


3. Click Open .

4. Select the LTLScenario1.tm file you created in the earlier exercise. The scenario dialog box is displayed.

Create the hub The new record is a hub in Fort Wayne, IN.

Create the new hub record 1. Perform one of the following tasks:

• Click Hub on the Control Center. The Hub Detail Table is displayed.





3. Enter FW.


Modify the new hub records You have to populate data similar to location data that enables Transportation Modeler to calculate distance values.

Add the hub data 1. Select the new hub displayed in the Hub Detail Table.

2. Select the field in the table and enter the value.


The following table displays the information you should enter for the new hub record:


Create the hub

HubID City State Postal Code Country FW Fort Wayne IN 46801 USA

Use data utilities to populate Lat/Lon information You have to load the location translation tables into your scenario.


2. Click Data Utilities . in the Utilities group The Data Utilities dialog box is displayed.

3. Select the City - Lat/Lon Translator and Postal Code - Lat/Lon Translator check boxes.

4. Click OK. The Progress is displayed as Transportation Modeler loads each database. The Progress dialog box closes when all the tables are successfully loaded. The data utility tables that are loaded are displayed in the Status Bar.

Set the lat/lon 1. Click Edit Query on the Hub Detail Table. The new record should still be selected.


3. Select the LatLon field in the Set Field Value dialog box.

4. Select Postal Code Centroid from the To drop-down list and click Set. A message is displayed indicating that the rows are updated.


6. Click Close.

Save the scenario You have now successfully created all the data required to solve the new Hub scenario. Save the scenario as a new scenario file before proceeding.

Save the scenario 1. Select the File menu.

2. Click Save As .

3. Enter HubScenario1.

4. Click Save.


Create the hub rates

Chapter 17. Create the hub rates In this chapter, you will use the Access Rating Tool to create the Hub rates for the "Hub modeling exercise" (on page 76).

As with the earlier exercise using the Access Rating Tool, the TariffConverterExcelTemplate.xls file contains the fields you must populate in support of your modeling requirements. This file contains a set of worksheets: TL, LTL, SmallPackage, RateRange, Hubs, and Zones. The current problem will require you to enter relevant details in the Hub and TL worksheets.



Create the hub record In this section, you will create the record for the shipper’s hub in Fort Wayne, IN.

Create the hub 1. Open the TariffConverterExcelTemplate.xls spreadsheet.

2. Select the Hubs worksheet.



Field Description Value HubID The identifier for the hub. FW

City Identifies the city in which the hub is located. Fort Wayne

State Identifies the state in which the hub is located. IN

PostalCode Identifies the postal code in which the hub is located. 46801

Country Identifies the country in which the hub is located. USA

AllowPick If you set this field to Yes, shipments can be picked up at this hub by a carrier other than the hub owner. If you set this field to No, shipments cannot be picked up at this hub by other carriers. A value of Conditional allows a carrier other than the hub owner to pick up shipments at this hub when a lane specifies this hub as the origin. Values allowed for this field are Yes, No and Conditional.

Yes



Field Description Value AllowDrop If you set this field to Yes, shipments can be dropped off at

this hub by a carrier other than the hub owner. If you set this field to No, shipments cannot be dropped off at this hub by other carriers. A value of Conditional allows a carrier other than the hub owner to drop shipments at this hub when a lane specifies this hub as the destination. Values allowed for this field are Yes, No and Conditional.

Yes

Carrier Identifies the carrier who operates the hub. TLCARR


CrossDockCostPer Unit

This value is the per unit rate at which the cross-dock charges at the hub is levied.

0.40

UnitType Indicates the measure on which the charge is levied. For example, if the UnitType is Weight, the charge is levied per weight unit, such as per pound.

Weight


LookAheadRule

This field determines if the rating engine can select a rate at the previous or next given range break. The additional or reduced amount of quantity multiplied by the rate at the new range break must be cheaper than the current quantity multiplied by the rate at the current range break for the alternate range break to be used. Valid values are:

• LookAhead

• LookBack

• Disabled


UnitDivideFactor

This field is the factor by which the ChargeType needs to be divided before determining the number of units and applying the PerUnit charge. The default value is 1.

100

DimWeightFactor

Defines the factor that the rating engine uses to calculate dimensional weight. It multiplies/divides the volume by the factor to find the dimensional weight. It is only used when Lookup Type is set to Weight. If you do not enter a value for this field, it defaults to 1. A value of 0 is not permitted.


Imperial



Create required rates In this section, you will create the rates needed to support the inclusion of the Fort Wayne hub. You need lanes from the origin states to the hub and from the hub to the destination states.

Create the TL Rates for the Hub You will enter all required data onto the TL worksheet in the TariffConverterExcelTemplate.xls spreadsheet. Each record on this worksheet represents a lane, complete with its carrier/tariff/service information.





Field Description Value Carrier The identifier for the carrier. TLCARR

Service Name of the mode definition. You are defining a truckload tariff.

TL

Tariff This is the tariff for the tariff service. If you do not define a Tariff value, the conversion macro will concatenate the Carrier value with the Service value to define the Tariff.


RateCode Use this field to specify a RateCode for the Carrier/Tariff/Service/Charge that already exists in the database. This enables you to define new lanes that use this RateCode. You can define multiple rows (multiple lanes) with the same RateCode.

• If you set the RateCode to *, the rating engine applies it to all lanes.

• If you leave the RateCode blank, the conversion macro in the Access database will create a unique RateCode for each lane.



Imperial

DimWeightFactor




Field Description Value UnitDivideFactor



Distance


LookAheadRule

Determines if the rating engine can select a rate at the previous or next given range break. The additional or reduced amount of quantity multiplied by the rate at the new range break must be cheaper than the current quantity multiplied by the rate at the current range break for the alternate range break to be used. Valid values are:

• LookAhead

• LookBack

• Disabled


RateType Identifies the method in which the rate is applied. For example, you can apply a rate as a PerUnit (such as charging a rate per mile) or as a FlatCharge.

PerUnit

TeamDriver Determines whether or not team drivers are used. When team drivers are used, DOT rules are not applied during scheduling.


MinChargeLocation



Specifies the rate that is levied. .75

RateRangeID This field is the RateRangeID value from the RateRange tab when using a rate range.

OriginZoneCode

Identifies the zone at which the lane originates. The specified zone code should refer to a zone defined on the Zones worksheet. In this example, the lanes are state to state and no hub is required.


FW

OriginPostalCode




Field Description Value OriginPostalCodeEndRange


OriginState Identifies the State in which the lane originates. IN




DestPostalCode

Identifies the Postal Code at which the lane terminates.



DestState Identifies the State in which the lane terminates. IL





PointToPoint


Determines if the carrier movement between the origin-destination pair is eligible for continuous moves (trips). The default is N. In this case, you are not modeling trips, so you can accept the default. Note: This field also accepts T (for True) or F (for False) as well as Y or N.

F

MinimumValue1

Specifies the minimum value, in units specified by MinMaxValueType1, above which the tariff must be applied. Note: MinimumValue2, MinimumValue3, MinimumValue4, and MinimumValue5 fields are also available in the spreadsheet, but not used in this example.

MaximumValue1

Specifies the maximum value, in units specified by MinMaxValueType1, for the movement. In this case, movements are limited to 42,000 pounds. Note: MaximumValue2, MaximumValue3, MaximumValue4, and MaximumValue5 fields are also available in the spreadsheet, but not used in this example.

42000



Field Description Value MinMaxValueType1

This value identifies the unit on which the MinimumValue1 and MaximumValue1 restrictions are applied. Note: MinMaxValueType2, MinMaxValueType3, MinMaxValueType4, and MinMaxValueType5 fields are also available in the spreadsheet, but not used in this example.

Weight

Other Comments


Create the remaining lanes Use the same process to create the remaining seven lanes and their rates required for the Truckload problem. The values for the records are displayed in the following table.

Note: The Stop charge remains the same as in the earlier exercises.

Field Record 10 Record 11 Record 12 Record 13 Record 14 Carrier TLCARR TLCARR TLCARR TLCARR TLCARR

Service TL TL TL TL TL

Tariff blank blank blank blank blank

Equipment blank blank blank blank blank

DivisionCode blank blank blank blank blank

RateCode blank blank blank blank blank

UOMType Imperial Imperial Imperial Imperial Imperial

DimWeight Factor blank blank blank blank blank

UnitDivide Factor blank blank blank blank blank

ChargeType Distance Distance Distance Distance Distance

LookupType blank blank blank blank blank

LookAheadRule blank blank blank blank blank

RateType PerUnit PerUnit PerUnit PerUnit PerUnit

TeamDriver blank blank blank blank blank

MinCharge blank blank blank blank blank

MinCharge Location

blank blank blank blank blank


0.75 0.75 0.75 0.75 0.75

RateRangeID blank blank blank blank blank

OriginZoneCode blank blank blank blank blank

OriginHubID FW FW FW blank blank



Field Record 10 Record 11 Record 12 Record 13 Record 14 OriginPostal Code blank blank blank blank blank



OriginState IN IN IN PA OH

OriginCountry USA USA USA USA USA

DestZoneCode blank blank blank blank blank

DestHubID blank blank blank FW FW

DestPostalCode blank blank blank blank blank



DestState IN KY MI IN IN

DestCountry USA USA USA USA USA

TransitTime blank blank blank blank blank


PointTo Point

PointTo Point

PointTo Point

PointTo Point

PointTo Point


F F F F F

MinimumValue1 blank blank blank blank blank

MaximumValue1 42000 42000 42000 42000 42000

MinMaxValue Type1

Weight Weight Weight Weight Weight

Other Comments blank blank blank blank blank



Solve the hub scenario

Chapter 18. Solve the hub scenario In this chapter, you will solve the scenario with the hub data and tune the parameters and strategies as required to improve the solution.

Tuning to support hubs In order to perform the analysis required, you need to:

• Update the rates to include the hub. The rate changes are described in "Create the hub rates" (on page 80).

• Update the strategy file to support the use of the hub.

Initial strategy file changes for hubs The strategy functions include functions specifically used to control the behavior of the solver with hubs. In this case, you are using the HubAssignment strategy.

For the first question in the "Analysis overview" (on page 66), create a strategy file with HubAssignment only. Set the parameters wide open to see how many shipments are split through the hub.

You need to create a strategy file as described below:

Strategy Parameter Settings HubAssignment

• Max Con Hub Distance: This is the maximum distance that a load's origin can be from a con hub for that hub to be considered for the load. Set this value to a large number to prevent it from being constraining. 500 miles is plenty of distance between the hub and other locations.

• Max Con Hubs to Try: We only have one hub, so the default is fine.

• Max Decon Hub Distance: This is the maximum distance that a load's destination can be from a decon hub for that hub to be considered for the load. Set this value to a large number to prevent it from being constraining. 500 miles is plenty of distance between the hub and other locations.

• Max Decon Hubs to Try: We only have one hub, so the default is fine.

• Max Insertion Percentage: Do not consider inserting a hub that will increase total distance greater than MaxInsertionPercentage. For now, leave this at the default value of 50.

You can leave the other parameters at their default values.

HubAssignment ( 500 3 500 3 50 0 ANY 0 100 100 100 TRUE TRUE ANY TRUE TRUE 0 FALSE FALSE TRUE TRUE )

Solve the scenario and note how many shipments split through the hub. You should have 12 out of the 17 shipments splitting.

You need to adjust the MaxConHubDistance and MaxDeconHubDistance to get the most reasonable distance (within 50 miles) and still have the same number of split shipments.



Since the problem is considering one hub only, the problem is dictated by a deconsolidation solution. By definition, when splitting through only one hub, HubAssignment will split shipments through one hub considered as a decon hub. However, both radii can dictate a constraint. Therefore, the destination radius should be set to a value that encompasses the largest distance from the hub to any destination.

If you examine the OptLog, you will see that the largest distance between the FW hub and the destination is about 273 miles. Therefore, setting your MaxConHubDistance and MaxDeconHubDistance to 300 will not constrain the shipment splitting.

Split the remaining shipments You still need to adjust one of the HubAssignment parameters to allow the remaining shipments to split through the hub. The shipments from Pittburgh and Cleveland to Detroit and from Cleveland to Riverview are not splitting through Fort Wayne. This is because the distance they would incur through the split would be greater than that allowed by the MaxInsertionPercentage. Currently, this value is 50, meaning the distance cannot increase by more than 50 percent to support the split.

Adjust MaxInsertionPercentage until all 17 shipment split through the hub. Start with a large value (such as 1000).

Once all shipments split through the hub, adjust MaxInsertionPercentage to a value (within 25 percent) that allows the split, but does not leave the constraint completely open. Think about the direct distance from origin to destination, then think about the added distance splitting the shipment through a hub. You will find that a value of 250 allows all to split (the shipments most affected are those originating in Cleveland).

Improve the hub model Once you have determined how to use HubAssignment and what parameter impacts which shipments split through the hub, you can now create a more sophisticated strategy file to perform the analysis as described in the remaining questions in the "Analysis overview" (on page 66).

Create an initial unconsolidated plan The client wants to run the hub assignment by splitting unconsolidated shipments first, then consolidating the split legs. However, he wants to run the hub section of the strategy after the baseline strategy that does normal consolidation, as defined in the earlier studies.

You can use the Set function in combination with GETPLAN () to retrieve the plan and give it a name for use later in the optimization.

Add the following line to the very beginning of your strategy file. This will retrieve the plan immediately after the InitLoads step and saving it as a named plan called HUBINITIAL.

Set ( HUBINITIAL GETPLAN() )

Create the hub assignment plan Next, you are going to create a section of the strategy file that retrieves the unconsolidated plan and runs your HubAssignment. You will also add the ConSamePickAndDrop and Con that you used in your best Multi-Pick/Multi-Drop strategy from the earlier study.

In this case, you use the SetPlan function to retrieve the plan called INITIAL and set it as the current plan, then include the HubAssignment, ConSamePickAndDrop and Con:

SetPlan ( HUBINITIAL )




ConSamePickAndDrop ( TRUE TRUE TRUE FALSE ANY ANY 0 TRUE FALSE FALSE FALSE )

Con ( 0 200 500 55 FALSE TRUE TRUE TRUE 100 TRUE 0 )

Create the original consolidation plans Now that you have the initial plan and the plan with the hub assignment set up, you need to include the Single-Pick/Multi-Drop and Multi-Pick/Multi-Drop plans from the earlier study.

Define two sections in the strategy before the SetPlan and HubAssignment to create these plans. The # indicates a comment. You can put comments anywhere you need them in your strategy file.

# You are running the original Single-Pick/Multi-Drop plan

ConSamePickAndDrop ( TRUE TRUE TRUE FALSE ANY ANY 0 TRUE FALSE FALSE FALSE ANY )

# Create a plan with the initial ConSamePickAndDrop results

Set ( CONINITIAL GETPLAN () )


# Retrieve the original ConSamePickAndDrop plan

SetPlan ( CONINITIAL )

# You are running the original Multi-Pick/Multi-Drop plan


Use the stack to merge plans First, you will create a named stack. Then you will push the various plans you have defined to the stack. At the end of the strategy, you will merge all the plans currently on the stack.

You can create the stack at any point before you want to add plans to it. In this case, you are creating a plan stack called STACK:

CreatePlanStack ( STACK )

Next, after each of the three plans (the single-pick/multi-drop, the multi-pick/multi-drop, and the HubAssignment with consolidation), you push the plan to the stack.

After each consolidation section, include the following line:

PushToPlanStack ( STACK GETPLAN () )

This gets the current plan and pushes it to the stack called STACK. At the end of this process, there are three plans on the stack.

Finally, you need to merge the three plans on the stack to get the best result. Add the following line to the end of the strategy file:

MergeSolvePlanStack ( STACK FALSE ANY FALSE )

The final strategy file should look like this:

Note: The comments are provided for informational purposes - they are not required.



# Take the original unconsolidated plan and call it HUBINITIAL

Set ( HUBINITIAL GETPLAN () )

# Create the Plan Stack







# Put the Single-Pick/Multi-Drop plan on the stack


# Go back to the original ConSamePickAndDrop state of the plan


# You are running the original Multi-Pick/Multi-Drop plan


# Put the Multi-Pick/Multi-Drop plan on the stack


# Go back to the original unconsolidated plan


# Run the HubAssignment section and push this plan to the stack







# Have the solver get the best plan

MergeSolvePlanStack ( STACK FALSE ANY FALSE FALSE )

Analyze the results You have built three runs for study and built a strategy file to examine them:

• Single-Pick/Multi-Drop

• Multi-Pick/Multi-Drop

• Hub Splitting

Solve the scenario and save the OptLog.txt file for analysis.

Comparing to your best run from the earlier study:


Initial Loads 4,188 6,305 17 0 0


Con(0 200 500 55 0 1 1 1 100 1 0) 2,593 2,522 5 0 0

OptTLLoads(200 500 6 -500 100 1000)

2,593 2,522 5 0 0


What is the cost difference between sending the freight in each of the plans in your current solution?

• Single-Pick/Multi-Drop

• Multi-Pick/Multi-Drop

• Hub Splitting

You can determine this by reviewing the results of your current solution:


Initial Loads 4,188 6,305 17 0 0


Con(0 0 500 55 0 1 1 1 100 1 0) 2,970 2,962 6 0 0

Con(0 200 500 55 0 1 1 1 100 1 0) 2,593 2,522 5 0 0

HubAssignment(300 1 300 1 250 0 ...)

6,019 8,552 34 0 0

ConSamePickAndDrop(1 1 ...) 2,513 2,936 13 0 0

Con(0 200 500 50 0 1 1 1 100 1 0) 2,435 2,568 11 0 0

MergePlanStack(0 0 ANY 0 0) 2,435 2,568 11 0 0

The plan costs are:

• Single-Pick/Multi-Drop: $2,970

• Multi-Pick/Multi-Drop: $2,593



• Hub Splitting: $2,435

The solver chose the Hub Assignment with consolidation of split legs as the most cost effective plan.

Assess increase in the cross dock charge The hub plans to increase the cross dock charge at Fort Wayne from $0.40 / CWT to $0.52 /CWT because a new labor contract has increased the operating expenses of the dock.

Adjust the cross dock charge 1. Edit the TariffConverterExcelTemplate.xls spreadsheet and change the

CrossDockCostPerUnit on the Hubs tab from 0.40 to 0.52.

2. Save the TariffConverterExcelTemplate.xls file.

3. Use the TariffConverter.mdb to convert the spreadsheet into the rating database as described in "Convert the data to a rating database" (on page 28).

Solve the scenario using the strategy file with the merged plan stack. You should see that a different plan is actually the cheapest.

Merged solution with Hub Assignment

Algorithms Total Cost Distance Loads Trips Unroutable Initial Loads 4,188 6,305 17 0 0


Con(0 0 500 55 0 1 1 1 100 1 0) 2,970 2,962 6 0 0

Con(0 200 500 55 0 1 1 1 100 1 0)

2,593 2,522 5 0 0

HubAssignment(300 1 300 1 250 0 ...)

6,184 8,552 34 0 0

ConSamePickAndDrop(1 1 ...) 2,678 2,936 13 0 0

Con(0 200 500 50 0 1 1 1 100 1 0)

2,600 2,568 11 0 0

MergePlanStack(0 0 ANY 0 0) 2,593 2,522 5 0 0

The Hub Assignment plan has now become more expensive ($2,600) and the Multi-Pick/Multi-Drop solution is the best ($2,593).


Continuous move modeling exercise

Chapter 19. Continuous move modeling exercise This chapter provides an outline of an exercise in which you look at continuous moves options with additional shipments to find backhaul opportunities. A description of the modeling problem, as well as the basic data, is provided.

Model description The shipper is comfortable considering hubs in their TL and LTL decisions in the optimization. Now, the shipper is ready to look into some of their continuous moves options with additional shipments providing backhaul opportunities.

Shipments The shipper has three backhaul opportunities to consider. He would like to model the backhaul shipments as 25,000 lb shipments at Freight Class 50. The shipments originate in Chicago, Detroit, and Louisville and are all destined for Indianapolis.

Rates The shipper has available to him trailers that can take freight outbound from the hub at Fort Wayne to anywhere in the country for $0.65/mile round trip, with no stop charge. The shipper also needs to add some inbound lanes provided by his TL carrier to handle the new shipment data. You need to add lanes from IL and from MI to the Fort Wayne hub at $0.95/mile, and from KY to Fort Wayne hub at $0.75/mile. The stop charge on each lane is $50/stop. The TL carrier also offers direct lanes for the direct moves for the three shipments at $1.20/mile and $50/stop.

After much debating, the hub decided to set their cross dock rate to $0.41/CWT. Ensure that you do this before beginning the exercise.


1. Since you typically want to run a Cmove at the end of your strategy file, put the strategy after the merge and leave the parameters wide open (large MaxDeadhead value, large MaxLoads value, CostImprovementRequired = TRUE) to see what opportunities exist. Optimize and save this optimization log, calling it PS5Log1.txt. Analyze this optimization log:

• Take the Excel spreadsheet PS5.xls and fill in the fields for PS5Log1.txt.

• Look at the HubAssignment. How many shipments legs would you expect if all 20 shipments split? How many shipments are left unsplit? What argument do you need to adjust to make all 20 shipments split (to the nearest 50)?

2. Once you adjust your HubAssignment, run your scenario again and save the log as PS5Log2.txt. Analyze this optimization log:

• Once again go to the Excel spreadsheet and fill in the fields for PS5Log2.txt.

• Can you explain why the final answer is more expensive than PS5Log1.txt? Why do not you see any trips built?

It seems like the proper approach might be to see what happens if you exclude the new shipments from the HubAssignment by using filtering.


Continuous move modeling exercise

3. Set up a filter to exclude the three shipments in the HubAssignment and subsequent consolidation routines. You may want to set up a filter on state where you exclude origin states. Once you set up the filter properly to not consider the new shipments, rerun the scenario and save the log as PS5Log3.txt. Analyze this optimization log:

• How many shipment legs do you expect to see in the HubAssignment now? You will know whether the three were excluded if the number syncs up with your answer.

4. Now it is time to analyze all three runs together. Which run had the best merged cost? Which run had the best final cost? Is the best final cost run a scalable solution?

5. Bonus Question: It is pretty clear that the best answer is not to exclude the large heavy shipments originating at the new locations from splitting through the hubs. It is also clear that including all of them in HubAssignment is not the best solution either. What can you do? The client says that your algorithms are greedy and do not consider trying some of the backhaul shipments in different combinations during HubAssignment. What can you tell him (consider filters again)?


Create backhaul shipments

Chapter 20. Create backhaul shipments In this chapter, you will add the shipment data required for the continuous move exercise. You will add this data to the Transportation Modeler scenario you created for the previous modeling exercise, then save this as a new scenario.

Open an existing scenario If you do not currently have the scenario opened from the Truckload modeling exercise, you should do so now.



3. Click Open . The Open dialog box is displayed.

4. Select the HubScenario1.tm file you created in the earlier exercise. The scenario is displayed.

Create the backhaul shipments For this exercise, you have to create additional shipment records.

Create the backhaul shipment records 1. Click the shipment table name on the Control Center. The Shipment Detail Table is displayed.


3. Enter the record name in the Name field. You already have 17 shipments from the earlier modeling exercises. Enter 18 as the shipment ID.


5. Repeat steps 2 through 4 to create the remaining two shipment IDs.

Modify the backhaul shipment records Add the backhaul shipment data 1. Select the new shipment IDs in the list in the Shipment Detail Table.

2. Select the field in the table and enter the value.


3. The following table displays the information you should enter for the 3 new shipment records.

ShipmentID Origin Destination Freight Class Weight 18 Chicago Indianapolis 50 25000

19 Detroit Indianapolis 50 25000

20 Louisville Indianapolis 50 25000


Create backhaul shipments

Save the scenario You have now successfully created all the location and shipment data required to solve the new continuous move scenario. Save the scenario as a new scenario file before proceeding.

Save the scenario 1. Select the File menu from the ribbon.

2. Click Save As .

3. Enter CMoveScenario1 and click Save.


Create the continuous move rates

Chapter 21. Create the continuous move rates In this chapter, you will use the Access Rating Tool to create the rates required to examine the continuous move opportunities.

As with the earlier exercise using the Access Rating Tool, the TariffConverterExcelTemplate.xls file contains the fields you must populate in support of your modeling requirements. This file contains a set of worksheets: TL, LTL, SmallPackage, RateRange, Hubs, and Zones. The current problem will require you to enter relevant details in the TL worksheet.



Create required tariffs In this section, you will create the tariffs that support the continuous move opportunities with the new shipments.

Create the tariff You will enter all required data onto the TL worksheet in the TariffConverterExcelTemplate.xls spreadsheet. In this case, you will create a new carrier, TLCARR2, who supports the round trip moves.

Create the TL tariff for continuous moves 1. Open the TariffConverterExcelTemplate.xls spreadsheet.




Note: If no value is required, leave the field value blank. This results in the tool accepting the default value for the field.

Field Description Value Carrier The identifier for the carrier. TLCARR2

Service This is the name of the mode definition. You are defining a truckload tariff.

TL




Field Description Value Equipment The code describing the equipment used for the movement.

RateCode Use this field to specify a RateCode for the Carrier/Tariff/Service/Charge that already exists in the database. This enables you to define new lanes that use this RateCode. You can define multiple rows (multiple lanes) with the same RateCode. If you set the RateCode to *, the rating engine applies it to all lanes. If you leave the RateCode blank, the conversion macro in the Access database will create a unique RateCode for each lane.



Imperial

DimWeightFactor


UnitDivideFactor



Distance



• LookAhead

• LookBack

• Disabled


RateType The field identifies the method in which the rate is applied. For example, you can apply a rate as a PerUnit (such as charging a rate per mile) or as a FlatCharge.

PerUnit



MinChargeLocation




Field Description Value PerUnitOrPercentOrFlatCharge

Specifies the rate that is levied. This rate is from the hub to anywhere in the USA.

0.65


OriginZoneCode

Identifies the zone at which the lane originates. The specified zone code should refer to a zone defined on the Zones worksheet. Note: This is an optional field. Define OriginZoneCode, OriginHubID, or a combination of the Origin address fields.

OriginHubID Identifies the Hub at which the lane originates. Note: This is an optional field. Define OriginZoneCode, OriginHubID, or a combination of the Origin address fields.

FW

OriginPostalCode




OriginState Identifies the State in which the lane originates. In this case, the lane is going from the hub to the entire country, so the HubID is enough to identify the hub.

OriginCountry Identifies the Country in which the lane originates. In this case, the lane is going from the hub to the entire country, so the HubID is enough to identify the hub.

DestZoneCode Identifies the zone at which the lane terminates. The specified zone code should refer to a zone defined on the Zones worksheet. In this example, the lane is from an origin hub to a country.

DestHubID Identifies the Hub at which the lane terminates. In this example, the lane is from an origin hub to a country.








Determines whether the lane is modeled as a Point to Point lane or a Round Trip lane. In this case, you are modeling a round trip tariff, which starts and ends at the point of origin.

RoundTrip


Determines if the carrier movement between the origin-destination pair is eligible for continuous moves (trips). The default is N. Note: This field also accepts T (for True) or F (for False) as well as Y or N.

T



Field Description Value MinimumValue1


MaximumValue1

Specifies the maximum value, in units specified by MinMaxValueType1, for the movement. Note: MaximumValue2, MaximumValue3, MaximumValue4, and MaximumValue5 fields are also available in the spreadsheet, but not used in this example.

MinMaxValueType1


Other Comments


Create the remaining Lanes Use the same process to create the remaining six lanes and their rates required for the new backhaul shipments. The values for the records are displayed in the following table:

Field Record 16

Record 17

Record 18

Record 19

Record 20

Record 21

Carrier TLCARR TLCARR TLCARR TLCARR TLCARR TLCARR

Service TL TL TL TL TL TL

Tariff blank blank blank blank blank blank

Equipment blank blank blank blank blank blank

DivisionCode blank blank blank blank blank blank

RateCode blank blank blank blank blank blank

UOMType Imperial Imperial Imperial Imperial Imperial Imperial

DimWeight Factor

blank blank blank blank blank blank

UnitDivide Factor


ChargeType Distance Distance Distance Distance Distance Distance

LookupType blank blank blank blank blank blank

LookAheadRule


RateType PerUnit PerUnit PerUnit PerUnit PerUnit PerUnit

TeamDriver blank blank blank blank blank blank

MinCharge blank blank blank blank blank blank



Field Record 16

Record 17

Record 18

Record 19

Record 20

Record 21

MinCharge Location



0.95 0.95 0.75 1.2 1.2 1.2

RateRangeID blank blank blank blank blank blank

OriginZoneCode


OriginHubID blank blank blank blank blank blank

OriginPostal Code




OriginState IL MI KY IL MI KY

OriginCountry

USA USA USA USA USA USA

DestZoneCode


DestHubID FW FW FW blank blank blank

DestPostalCode




DestState blank blank blank IN IN IN

DestCountry blank blank blank USA USA USA

TransitTime blank blank blank blank blank blank


PointTo Point

PointTo Point

PointTo Point

PointTo Point

PointTo Point

PointTo Point

EligibleForContinuous Moves

F F F F F F

MinimumValue1


MaximumValue1

42000 42000 42000 42000 42000 42000

MinMaxValue Type1

Weight Weight Weight Weight Weight Weight

Other Comments


Update the cross dock charge The contract with the hub has changed the cross dock charge to 0.41 per hundredweight.



Update the cross dock charge 1. Open the TariffConverterExcelTemplate.xls spreadsheet.


3. Change the CrossDockCostPerUnit to 0.41.



Solve the continuous move scenario

Chapter 22. Solve the continuous move scenario In this chapter, you will solve the scenario using a continuous move strategy.

Tuning to support continuous moves In order to perform the analysis required, you need to:

• Update the rates to support continuous moves. The rate changes are described in "Create the continuous move rates" (on page 97).

• Update the strategy file to support continuous moves.

Initial strategy file Changes for continuous moves The strategy functions include functions specifically designed to build continuous moves, or trips.

For the first question in the "Analysis overview" (on page 93), add the Cmove strategy to the end of your existing strategy file from the previous exercise. Leave the strategy parameters at their defaults for the initial analysis.





Con ( 0 0 500 55 FALSE TRUE TRUE TRUE 100 TRUE 0 0 FALSE )






HubAssignment ( 300 1 300 1 200 0 ANY 0 100 100 100 TRUE TRUE ANY TRUE TRUE TRUE FALSE FALSE TRUE TRUE )





CMove ( 100 5 TRUE ANY ANY 0 ANY ANY 0 0 FALSE 2 FALSE )

Solve the model and save the optimization log 1. Select Home > Scenario from the ribbon.

2. Click . The model is solved and the optimization log is automatically written.

3. Click Update Scenario.



4. Navigate to the folder where the optimization log is written. Based on the Solver Options you set in "Set solver options" (on page 40), the default path and filename is C:\jda\tmod\9.0\Reports\OptLog.txt.

5. Rename OptLog.txt to PS5Log1.txt. This solution has 3 trips and a distance of 3,072.

Improve the continuous move model Once you have determined how to use Cmove, you can now create a more sophisticated strategy file to perform the analysis as described in the remaining questions in the "Analysis overview" (on page 76).

Examine the hub assignment Examine the results from the first optimization. You need to adjust a HubAssignment parameter to enable all 20 shipments to split. In the first case, how many shipments remained unsplit? If you examine PS5Log1.txt, you can view that there were 37, rather than 40, loads created by the HubAssignment.

None of the new shipments result in the need to increase the origin or destination radius values, so you need to determine another setting that can impact the hub splitting.

Increase the MaxInsertionPercentage to allow the total distance to be greater when the shipments are split through the hub. A value of 250 should enable this behavior.

Solve the model and save the optimization log 1. Select the Home tab from the ribbon.

2. Click Solve in the Scenario group.The model is solved and the optimization log is automatically written.



5. Rename OptLog.txt to PS5Log2.txt.

Note: In this case, no trips are built and the plan cost increases. The new shipments should, therefore, not be included in the hub split. You will next learn another way to prevent the new shipments from being included in the hub split than through setting MaxInsertionPercentage.

Filter to exclude new shipments In this case, you will exclude the new backhaul shipments from being split by the HubAssignment. You will use one of the strategy Filter functions to select and exclude these shipments.

The backhaul shipments have origin states that are not used by any of the other shipments. You can, therefore, filter based on these origin state values and exclude these shipments from the HubAssignment section of your strategy file. The parameter settings for the FilterState function should be as displayed in the following table:

Parameter Value/Description ExclusionSwitch If set to TRUE, then the filter is to exclude loads rather than include

them (default). In this case, we want to exclude the shipments, so set this value to TRUE.



Parameter Value/Description FilterStyle Consider the origin/destination of load/shipments/shipmentLegs.

OriginWithinState If TRUE, consider the state of origin when filtering. This value should be TRUE.

DestinationWithinState

If TRUE, consider the state of destination when filtering. This value should be FALSE.

AnyStopsWithinState

If TRUE, consider the state of any stop when filtering. This value should be FALSE.

State This is one of the set of states to filter. This value should be "IL" Be sure to enclose the value within quotes.

State This is one of the set of states to filter. This value should be "MI" Be sure to enclose the value within quotes.

State This is one of the set of states to filter. This value should be "KY" Be sure to enclose the value within quotes.

Note: The FilterState function must be paired with an end statement.

The section of your strategy file that performs the HubAssignment should look like:

FilterState ( TRUE 0 TRUE FALSE FALSE "IL" "MI" "KY" )





end


2. Click Solve in the Scenario group. The model solves. The optimization log is automatically written.




BONUS: Tuning the use of FilterState In order to consider different combinations of the backhaul shipments in the HubAssignment, you can define a series of FilterState sections in the strategy file. Each will limit which origin state or states are excluded. You can also try adjusting the MaxInsertionPercentage (200 vs. 250) on the HubAssignment. This will give you a thorough evaluation of hub splitting with the backhaul shipment.

The FilterState combinations are:



• FilterState ( TRUE 0 TRUE FALSE FALSE "IL" "MI" "KY" )

• FilterState ( TRUE 0 TRUE FALSE FALSE "IL" "MI" )

• FilterState ( TRUE 0 TRUE FALSE FALSE "IL" "KY" )

• FilterState ( TRUE 0 TRUE FALSE FALSE "MI" "KY" )

• FilterState ( TRUE 0 TRUE FALSE FALSE "IL")

• FilterState ( TRUE 0 TRUE FALSE FALSE "MI")

• FilterState ( TRUE 0 TRUE FALSE FALSE "KY")

You will run each of these, first with MaxInsertionPercentage set to 250, then again with MaxInsertionPercentage set to 200. The format of each is the same as your original FilterState:


FilterState ( TRUE 0 TRUE FALSE FALSE "IL" "MI" "KY" )

HubAssignment ( 300 1 300 1 250 0 ANY 0 100 100 100 TRUE TRUE ANY TRUE TRUE TRUE FALSE FALSE TRUE )




end


Equipment domicile modeling exercise

Chapter 23. Equipment domicile modeling exercise This chapter provides an outline of an exercise in which you model a domicile and the equipment that originates at that domicile. This model represents a dedicated fleet for transporting shipments. A description of the modeling problem, as well as the basic data, is provided.

Model description The shipper is going to use a dedicated fleet. In support of the dedicated fleet, there are domiciles, which are locations from which equipment is sourced and to which the equipment returns. The equipment must travel from the domicile to the origin and from the destination back to the domicile. The added distance may result in additional cost and must be reflected in the model.

Scenario Data You must create a domicile within your Transportation Modeler scenario. The domicile record is defined by:

Location + Carrier + Equipment Type + Component

In this example, there is a domicile located in Pittsburgh. This location has already been defined in the scenario, so no additional locations are required.

You will create a Carrier called TLCARR2 to represent the dedicated fleet. The Equipment Type at this domicile is 48FT. The Component is just an integer used to identify the unique domicile resource.

You will also need to exclude shipments 18, 19 and 20 from inclusion in the optimization.

Rates You will create a new set of TL rates for the dedicated carrier alone (TLCARR2). A rate of $0.51/mile will enable you to cover the cost of running the dedicated carrier. This rate applies anywhere in the United States and, with the dedicated fleet, the rate applies for a round trip. The carrier can carry up to a maximum weight of 42000 lbs per load.

You will use the global parameters you defined in the previous exercise (with respect to driver hours).

Analysis Overview After you create the required elements and update your rates, you run the scenario.

1. How many loads and trips are formed? What is the total cost and distance?

2. Next, create another domicile at a more central location. You can use the Fort Wayne hub. Exclude the Pittsburgh domicile and run the scenario. What is the difference in cost and distance? Explain the difference in cost and distance when you change the domicile location.

3. Run the scenario with both the domiciles included in the solve. What do you observe?

4. Next, create a domicile in Louisville for TLCARR2 and exclude the other two domiciles. Do all the shipments get routed? If not, why not? Is there any other parameter that you must adjust for this domicile to be considered for the unroutable shipments? If so, what change is required?

5. From the analysis so far, the customer knows that he can use his domicile at Pittsburgh for this assignment, but he wants to reduce the cost further by assigning part of the results to a common carrier. He has offers from the common carrier TLCARR for rates on lanes as follows:

• PA – MI: $1.20/mile


Equipment domicile modeling exercise

• PA – IL: $1.40/mile

• PA – IN: $1.00/mile

• PA – KY: $1.10/mile

• OH - MI@: $1.40/mile

• OH – IL: $1.50/mile

• OH – IN: $1.20/mile

• OH – KY: $1.00/mile

6. The common carrier is also permitted to use the hub owned by the customer at an additional cross dock cost of $0.4 per hundredweight. The lanes to the hub from PA and OH and from the hub to IL, IN, KY and MI are $0.75 each. The stop charge for the common carrier is $50 per stop. Now what is the outcome?

7. Is the answer obtained with a mix of the common and dedicated fleet better than the output you got from the first question, in which you had only a dedicated fleet? If no, what further modifications can ensure a better output? (Hint: Think of changes or additions to the strategy file that can make this possible.)


Create domicile

Chapter 24. Create domicile In this chapter, you will add the domicile to the Transportation Modeler scenario you created for the hub modeling exercise, then save this as a new scenario.

Open an existing scenario If you do not currently have the scenario opened from the hub modeling exercise, you should do so now.

Open the existing scenario, do the following 1. Open Transportation Modeler.

2. Select the File menu.from the ribbon.

3. Click Open .

4. Select the HubScenario1.tm file you created in the earlier exercise. The scenario is displayed.

Create the domicile and exclude shipments A domicile requires a location, a carrier and an equipment type. You are creating the domicile at an existing location, Pittsburgh, so you do not need to create a new location. However, you must create both the carrier and the equipment type.

Create the new Carrier record 1. Perform one of the following:

• Click Carrier on the Control Center. The Carrier Detail Table is displayed.


2. Perform one of the following:



3. Enter TLCARR2


Create the new Equipment Type record 1. Perform one of the following:

• Click Equipment Type on the Control Center. The Equipment Type Detail Table is displayed.





Create domicile


3. Enter 48FT.


Create the new Domicile record The new domicile record is a relationship record that combines a Location, Carrier, Equipment Type and Component value.


• Click Domicile on the Control Center. The Domicile Detail Table is displayed.


2. If not already in the Query View, click New to go to the Query View.

3. Select these values from the entity list boxes:

• LocationOrHub: Pittsburgh

• Carrier: TLCARR2

• Equipment Type: 48FT

• Component: 1

4. Click New. A message box is displayed to confirm the creation of the domicile record.

5. Click Yes. The record is created and a confirmation message is displayed.

6. Click OK to dismiss the message box.

Exclude shipments not required 1. Click Shipment on the Control Center. The Shipment Detail Table is displayed.

2. Select shipments 18, 19 and 20.

3. Click Set.

4. Select SolverInclude and set the value to No and click Set. The value is set for the 3 records.

5. Click OK to dismiss the message box, then click Close.

Save the scenario You have now successfully created all the data required to solve the new Domicile scenario. Save the scenario as a new scenario file before proceeding.

1. Select the File menu.

2. Click Save As .

3. Enter DomScenario1 and click Save.


Create the rates for the domicile exercise

Chapter 25. Create the rates for the domicile exercise In this chapter, you will use the Access Rating Tool to create the rates for the dedicated carrier for the "Equipment domicile modeling exercise" (on page 107).

You will use the same process as in earlier exercises to enter the data into the Access Rating Tool spreadsheet, TariffConverterExcelTemplate.xls, then convert the data to the Access database using the TariffConverter.mdb.

Create the dedicated carrier rates In this section, you will create the record for the dedicated carrier. You will not need the rates from the common carrier, TLCARR.

Note: You may want to create a backup copy of your existing spreadsheet to keep the rates for TLCARR for later use.

Create the rates for the dedicated carrier 1. Open the TariffConverterExcelTemplate.xls spreadsheet.

2. If there are existing rates defined on the TL, LTL, or Hubs worksheet, delete them - the first exercise requires rates for the dedicated carrier only.




Field Description Value

Carrier The identifier for the carrier. TLCARR2


TL


Equipment This field is the code describing the equipment used for the movement.

48FT

RateCode Use this field to specify a RateCode for the Carrier/Tariff/Service/Charge that already exists in the database. This enables you to define new lanes that use this RateCode. You can define multiple rows (multiple lanes) with the same RateCode. If you set the RateCode to *, the rating engine applies it to all lanes.




If you leave the RateCode blank, the conversion macro in the Access database will create a unique RateCode for each lane.



Imperial

DimWeightFactor Defines the factor that the rating engine uses to calculate dimensional weight. It multiplies/divides the volume by the factor to find the dimensional weight. It is only used when Lookup Type is set to Weight. If you do not enter a value for this field, it defaults to 1. A value of 0 is not permitted.



Distance



• LookAhead

• LookBack

• Disabled



PerUnit



MinChargeLocation



Specifies the rate that is levied. 0.51




RateRangeID This field is the RateRangeID value from the RateRange tab when using a rate range.

OriginZoneCode Identifies the zone at which the lane originates. The specified zone code should refer to a zone defined on the Zones worksheet. In this example, the lanes are state to state and no hub is required.

OriginHubID Identifies the Hub at which the lane originates. In this example, the lanes are state to state and no hub is required

OriginPostalCode Identifies the Postal Code at which the lane originates.















RoundTrip

EligibleFor ContinuousMoves


T

MinimumValue1 Specifies the minimum value, in units specified by MinMaxValueType1, above which the tariff must be applied. Note: MinimumValue2, MinimumValue3, MinimumValue4, and MinimumValue5 fields are also available in the spreadsheet, but




not used in this example.

MaximumValue1 Specifies the maximum value, in units specified by MinMaxValueType1, for the movement. In this case, movements are limited to 42,000 pounds. Note: MaximumValue2, MaximumValue3, MaximumValue4, and MaximumValue5 fields are also available in the spreadsheet, but not used in this example.

42000

MinMaxValueType1


Weight

Other Comments Enables you to enter optional comments detailing the tariff information. This field is not used in the conversion process.



Solve the domicile scenario

Chapter 26. Solve the domicile scenario In this chapter, you will solve the scenario using the strategy you defined in the earlier continuous move exercise.

Initial strategy file for domiciles You can use the strategy file you defined for the continuous move exercise:






















Your plan should have 4 loads (no trips), with a cost of 2135 and a distance of 4187. All the loads begin and end at the Pittsburgh domicile.



Create and test alternate domiciles In this set of tasks, you will evaluate the use of alternate domiciles in the scenario optimization.

Create the alternate Fort Wayne domicile You will now create an alternate domicile, located at the Fort Wayne hub. In the first case, you must then exclude the Pittsburgh domicile.

Create the new domicile record 1. Perform one of the following tasks:

• Click Domicile on the Control Center. The Domicile Detail Table dialog box is displayed.




• LocationOrHub: FW



• Component: 1

and click New. A message box is displayed to confirm the creation of the domicile record.

4. Click Yes. The record is created and you can view a confirmation message.


Exclude the Pittsburgh domicile 1. Click Domicile on the Control Center. The Domicile Detail Table is displayed.

2. Select:




• Component: 1

and click Execute. The domicile record is displayed.

3. Scroll to the SolverInclude field and set the value to No.

Solve the model with the Fort Wayne domicile and save the optimization log 1. Select the Home tab from the ribbon.







6. Review the new optimization log to determine if there is a difference in the Cost and Distance when using the Fort Wayne domicile, rather than the Pittsburgh domicile.

With only the Fort Wayne domicile, your plan should have 4 trips and one standalone load (not on a trip). The cost is 2317 and the distance is 4544. All the loads and trips begin and end at the Fort Wayne domicile. Fort Wayne is not located near the shipment origins or near the destinations. Therefore, use of this domicile forces an increase in the distance and an associated increase in cost.

Solve with both domiciles Next, you will see what the effect is on the solve when you include both domiciles:

Include the Pittsburgh domicile 1. Click Domicile on the Control Center. The Domicile Detail Table dialog box is displayed.

2. Select the domicile record for Pittsburgh, TLCARR2, 48FT with Component 1.

3. Select the value Yes in the SolverInclude field.

Solve the model with both domiciles and save the optimization log 1. Select the Home tab from the ribbon.





6. Review the new optimization log to determine the effect of including both domiciles.

With both domiciles included, you get better results than with either domicile on its own. Your plan should have 4 loads. The cost is 1996 and the distance is 3913.

Two of the four loads use the Pittsburgh domicile, while the other two loads take advantage of the Fort Wayne domicile. In the cases where the Fort Wayne domicile is selected, the extra distance traveled due to the domicile inclusion is 941.6 miles (546 + 395.6). If the domicile had been at Pittsburg for this case, the additional distance would have been 1153.7 miles (547.4 + 606.3), so the use of Fort Wayne was appropriate.

Create the alternate Louisville domicile You will now create an alternate domicile at the Louisville location. You will evaluate the scenario with only this domicile, so you must exclude the other two domiciles.

Create the new domicile record 1. Perform one of the follwing:



• Click Domicile on the Control Center. The Domicile Detail Table is displayed.




• LocationOrHub: Louisville



• Component: 1

and click New. A message box is displayed to confirm the creation of the domicile record.

4. Click Yes. The record is created and you can view a confirmation message.


Exclude the Pittsburgh and Fort Wayne domiciles 1. Click Domicile on the Control Center. The Domicile Detail Table is displayed.

2. Select:

• LocationOrHub: Pittsburgh, FW



• Component: 1

and click Execute. The domicile records are displayed.

3. Scroll to the SolverInclude field and set the value to No for both records.

Solve the model with the Louisville domicile and save the optimization log 1. Select the Home tab from the ribbon.





6. Review the new optimization log to determine the effects of using the Louisville domicile in place of Fort Wayne and Pittsburgh.

While this scenario results in 3 loads, you can see that five shipments do not get routed. You must determine what is preventing these shipments from being routed when the domicile is Louisville and the shipments are in the north (Pittsburg to Detroit, and Cleveland to Riverview and Detroit).



The issue with Louisville is that use of this domicile results in a greater out of route percentage than the current optimizer parameter (55) allow.

Edit the Optimizer Parameters file 1. Select the Home tab on the ribbon.


3. Select the parameters file that you want to edit. By default, the file is the one you set in the Solver Options dialog box.


5. Increase the MaxOutOfRoutePct value and save the parameters file.

6. Solve the scenario to see if the remaining shipments are routed.

You will find that a MaxOutOfRoutePct of 65 (increased from 55) permits all shipments to be routed using the Louisville domicile.

In this case, you get three trips and three standalone loads, all using the Louisville domicile. The cost is 3224 and the distance is 6321.

Introduce the common carrier to the scenario The previous exercises enabled you to understand the effect of the various domiciles available to the dedicated carrier and you will use the Pittsburgh domicile going forward.

You now want to evaluate what happens when the common carrier can be used in additional to the dedicated carrier. You need to add the rates for the common carrier. The rates include:

• a set of point to point lanes from origin states to destination states,

• a set of point to point lanes from the origin states to the Fort Wayne hub and from the Fort Wayne hub to the destination states,

• a stop charge to apply to all lanes, and

• the hub at Fort Wayne.

Create the lanes from the origins to destinations 1. Open the TariffConverterExcelTemplate.xls spreadsheet.


3. Enter the data for the common carrier’s lane and rates as shown in the table:

Data for truckload lanes from origins to destinations

Field Record 1

Record 2

Record 3

Record 4

Record 5

Record 6

Record 7

Record 8

Carrier TLCARR TLCARR TLCARR TLCARR TLCARR TLCARR TLCARR TLCARR

Service TL TL TL TL TL TL TL TL

Tariff blank blank blank blank blank blank blank blank

Equipment blank blank blank blank blank blank blank blank

DivisionCode blank blank blank blank blank blank blank blank

RateCode blank blank blank blank blank blank blank blank



Field Record 1

Record 2

Record 3

Record 4

Record 5

Record 6

Record 7

Record 8

UOMType Imperial

Imperial

Imperial

Imperial

Imperial

Imperial

Imperial Imperial

UnitDivide Factor

blank blank blank blank blank blank blank blank

ChargeType Distance

Distance

Distance

Distance

Distance

Distance

Distance Distance

RateType PerUnit PerUnit PerUnit PerUnit PerUnit PerUnit PerUnit PerUnit

TeamDriver blank blank blank blank blank blank blank blank

MinCharge blank blank blank blank blank blank blank blank

MinCharge Location


PerUnitOrFlat Charge

1.2 1.4 1.0 1.1 1.4 1.5 1.2 1.0

RateRangeID blank blank blank blank blank blank blank blank

OriginZoneCode


OriginHubID blank blank blank blank blank blank blank blank

OriginPostal Code




OriginState PA PA PA PA OH OH OH OH

OriginCountry

USA USA USA USA USA USA USA USA

DestZoneCode


DestHubID blank blank blank blank blank blank blank blank

DestPostalCode




DestState MI IL IN KY MI IL IN KY

DestCountry USA USA USA USA USA USA USA USA


PointTo Point

PointTo Point

PointTo Point

PointTo Point

PointTo Point

PointTo Point

PointTo Point

PointTo Point


F F F F F F F F

MinimumValue1


MaximumValue1

42000 42000 42000 42000 42000 42000 42000 42000



Field Record 1

Record 2

Record 3

Record 4

Record 5

Record 6

Record 7

Record 8

MinMaxValueType1

Weight Weight Weight Weight Weight Weight Weight Weight

Other Comments


Create the lanes to and from the Fort Wayne hub 1. Open the TariffConverterExcelTemplate.xls spreadsheet.


3. Enter the data for the common carrier’s lane and rates as shown in the table:

Field Record 1 Record 2 Record 3 Record 4 Record 5 Record 6 Carrier TLCARR TLCARR TLCARR TLCARR TLCARR TLCARR

Service TL TL TL TL TL TL

Tariff blank blank blank blank blank blank

Equipment blank blank blank blank blank blank

DivisionCode blank blank blank blank blank blank

RateCode blank blank blank blank blank blank

UOMType Imperial Imperial Imperial Imperial Imperial Imperial

UnitDivide Factor


ChargeType Distance Distance Distance Distance Distance Distance

RateType PerUnit PerUnit PerUnit PerUnit PerUnit PerUnit

TeamDriver blank blank blank blank blank blank

MinCharge blank blank blank blank blank blank

MinCharge Location


PerUnitOrFlat Charge

0.75 0.75 0.75 0.75 0.75 0.75

RateRangeID blank blank blank blank blank blank

OriginZoneCode


OriginHubID blank blank FW FW FW FW

OriginPostal Code






Field Record 1 Record 2 Record 3 Record 4 Record 5 Record 6 OriginState PA OH blank blank blank blank

OriginCountry USA USA blank blank blank blank

DestZoneCode blank blank blank blank blank blank

DestHubID FW FW blank blank blank blank

DestPostalCode




DestState blank blank MI IL IN KY

DestCountry blank blank USA USA USA USA


PointTo Point

PointTo Point

PointTo Point

PointTo Point

PointTo Point

PointTo Point


F F F F F F

MinimumValue1


MaximumValue1

42000 42000 42000 42000 42000 42000

MinMaxValue Type1

Weight Weight Weight Weight Weight Weight

Other Comments


Create the stop charge 1. Open the TariffConverterExcelTemplate.xls spreadsheet.


3. Enter the data for the stop charge:

Field Carrier TLCARR

Service TL

Tariff blank

Equipment blank

DivisionCode blank

RateCode *

UOMType Imperial

UnitDivideFactor blank

ChargeType Stops



Field RateType PerUnit

TeamDriver blank

MinCharge blank

MinChargeLocation blank

PerUnitOrFlatCharge 50

RateRangeID blank


OriginHubID blank

OriginPostalCode blank

OriginPostalCodeEndRange blank

OriginState blank

OriginCountry blank


DestHubID blank

DestPostalCode blank

DestPostalCodeEndRange blank

DestState blank

DestCountry blank

PointToPointOrRoundTrip blank


F

MinimumValue1 blank

MaximumValue1 blank

MinMaxValueType1 blank

Other Comments blank

Create the hub 1. Open the TariffConverterExcelTemplate.xls spreadsheet.



Field Description Value Hub This field is the identifier for the hub. FW

City Identifies the city in which the hub is located. Fort Wayne

State Identifies the state in which the hub is located. IN

PostalCode Identifies the postal code in which the hub is located. 46801

Country Identifies the country in which the hub is located. USA



Field Description Value AllowPick If you set this field to Yes, shipments can be picked up at

this hub by a carrier other than the hub owner. If you set this field to No, shipments cannot be picked up at this hub by other carriers. A value of Conditional allows a carrier other than the hub owner to pick up shipments at this hub when a lane specifies this hub as the origin. Values allowed for this field are Yes, No and Conditional.

Yes

AllowDrop If you set this field to Yes, shipments can be dropped off at this hub by a carrier other than the hub owner. If you set this field to No, shipments cannot be dropped off at this hub by other carriers. A value of Conditional allows a carrier other than the hub owner to drop shipments at this hub when a lane specifies this hub as the destination. Values allowed for this field are Yes, No and Conditional.

Yes

Carrier Identifies the carrier who operates the hub. TLCARR


CrossDockCostPer Unit

This value is the per unit rate at which the cross-dock charges at the hub is levied.

0.40

UnitType Indicates the measure on which the charge is levied. For example, if the UnitType is Weight, the charge is levied per weight unit, such as per pound.

Weight


100


Imperial


You will include only the Pittsburgh domicile before solving.

Include only the Pittsburgh domicile 1. Click Domicile on the Control Center. The Domicile Detail Table is displayed.

2. Scroll to the SolverInclude field and set the value to Yes for Pittsburgh and No for Louisville and Fort Wayne.

Solve the model with the Pittsburgh domicile and save the optimization log 1. Select the Home tab from the ribbon.







6. Review the new optimization log to determine the effect of including the common carrier in the Pittsburgh domicile scenario.

Your plan should have five loads. The cost is 2431 and the distance is 4539. This result is not as good as your initial optimization with the dedicated carrier only. You need to look for ways using the strategy file to improve the solution.

Improve the Solution You can use the OptMove strategy to have the solver consider moving shipment legs from one load to another in an effort to reduce distance (and, therefore, cost). The best place to include the OptMove strategy is after the shipments have been consolidated onto loads using the Con strategy:



ConSamePickAndDrop ( TRUE TRUE TRUE 0 ANY ANY 0 TRUE FALSE FALSE FALSE ANY )


OptMove ( 200 500 1 0 100 1000 0 TRUE TRUE TRUE )










Solve the model with the new strategy and save the optimization log Note: Ensure to update your strategy file as shown above and save the changes.








6. Review the new optimization log to determine the effect of including the common carrier in the Pittsburgh domicile scenario.

Your improved plan should have four loads. The cost and distance have both been reduced, to 2114 and 4146 respectively.


Carrier equipment availability modeling exercise

Chapter 27. Carrier equipment availability modeling exercise This chapter provides an outline of an exercise in which you introduce additional constraints to the model. You are going to introduce constraints at three levels – Carrier, Tariff-Service and Lane Availability – to control the way in which the shipments are transported. A description of the modeling problem, as well as the basic data, is provided.

Model description In this exercise, you will use the same data as in the previous "Equipment domicile modeling exercise" (on page 107). You will control the solver behavior using various Constraints (on page 127).

Scenario data You need to update the Shipment ID values to be alphanumeric (as opposed to numeric). You are making use of Tariff IDs as they are defined in the rating database. These IDs are numeric and cannot have the same values as any of the Shipment IDs. Since you can control the Shipment ID values, you will change these to accommodate the Tariff IDs.

Parameter values The constraints that you are going to set up can make use of penalties in order to influence solver decisions. A number of these parameters are defined in the optimizer parameter file.

• PenaltyMaxLoads: 0

• PenaltyMinLoads: 0

• PenaltyPerDayStartDelay: 0

• PenaltyPerPerformancePoint: 100

• PenaltyShipmentNotDelivered: 1000

• PenaltyTransferHubEquipment: 0

• PenaltyTransitMode: 1000

• PenaltyVendorSequencingViolation: 1000

• PenaltyWaitTimePerHour: 0

Rates The only change to the rates is that the rate per mile for the dedicated carrier has been increased to 0.71 for all of the United States.

The hub at Fort Wayne is operating with a cross-dock charge of 0 for this exercise.

Constraints On the Carrier level, you will define constraints for the number of loads that the solver can build using the dedicated and common carriers available. Each carrier is allowed two loads. The penalty for exceeding the maximum number of loads for the dedicated carrier is $10,000, while the penalty for exceeding the constraint for the common carrier it is $15,000.


Carrier equipment availability modeling exercise

In later analysis, you will create and apply alternate constraints and penalties to observe how they impact the solver.

Note: Keep in mind that penalties are used to impact solver behavior only. They are not included in the actual plan cost.

Analysis overview 1. You need to update the strategy file to ensure that the penalties are reflected correctly. What are

the additions required to the strategy file?

2. After you enforce the constraints, what is the change in load formation? Are any penalties incurred or are any shipments left as unroutables? Is the output justified by the data? Give appropriate reasons to support your view on this.

3. Having realized that it is mandatory for all shipments to be delivered, the shipper has decided to increase the penalty for not delivering shipments to 25,000. What is the output you expect?

4. The shipper now requires a constraint on the maximum number of resources that TLCARR2 can use from the Pittsburgh domicile. He has imposed an additional penalty of 10,000 for exceeding two resources for the carrier at this domicile. How does this affect the carrier selection?

5. On the Tariff Service level, the shipper wants to ensure that the tariff-service combination for TLCARR2 and TL service gets a minimum of 4 loads, with a penalty of 22,000 for violating this minimum load restriction.

Note: The Tariff ID is automatically generated in the Access rating database. You need this ID to create your Tariff Service constraints. After you convert the Excel file to Access, you can refer to the TFF_T table within the Access database to determine the Tariff ID.


Create the carrier equipment availability scenario

Chapter 28. Create the carrier equipment availability scenario In this chapter, you will update the shipment IDs in the Transportation Modeler scenario you created for the domicile modeling exercise, then save this as a new scenario.

You will define the constraints that you want to impose on the solver. You will also define the penalties that are incurred if the solver exceeds these constraints.

Open an existing scenario If you do not currently have the scenario opened from the domicile modeling exercise, you should do so now.



3. Click Open .

4. Select the DomScenario1.tm file you created in the earlier exercise. The scenario is displayed.

Update the shipment IDs In order to ensure that there are no data conflicts, you need to edit the Shipment IDs and give them an alphanumeric prefix. Entities within Transportation Modeler require unique ID values. You need the numeric values when you create Tariff IDs in order to match those generated in your rating database.

Update the Shipment IDs 1. Click Shipment on the Control Center. The Shipment Detail Table is displayed.

2. Edit the value in the Shipment field to prefix the ID with "SH". For example:

1 becomes SH1

17 becomes SH17

Edit Optimizer Parameters file 1. Select the Home tab on the ribbon.




5. Ensure the parameters are defined in the following table:





Create the carrier equipment availability scenario







Set the domiciles If you still have active domiciles from the previous exercise, you need to exclude all except the Pittsburgh domicile from the scenario.

Exclude all but the Pittsburgh domicile 1. Click Domicile on the Control Center. The Domicile Detail Table is displayed.

2. Scroll to the SolverInclude field and set the value to No for all records except the Pittsburgh domicile.

Save the Scenario Save the scenario as a new scenario file before proceeding.

Save the scenario 1. Select the File menu on the ribbon.

2. Click Save As .

3. Enter CEAScenario1 and click Save.


Update the rates for the CEA exercise

Chapter 29. Update the rates for the CEA exercise In this chapter, you will use the Access Rating Tool to update the rates for the dedicated carrier and the hub cross dock charge for the "Carrier equipment availability modeling exercise" (on page 127).

You will use the same process as in earlier exercises to enter the data into the Access Rating Tool spreadsheet, TariffConverterExcelTemplate.xls, then convert the data to the Access database using the TariffConverter.mdb.

Update the dedicated carrier rates You need the TL rates for both the common carrier, TLCARR, and the dedicated carrier, TLCARR2.

You need the tariff for the dedicated carrier as defined in "Create the rates for the domicile exercise" (on page 111), but the per mile rate for the dedicated carrier, TLCARR2, is increased.

Update the rates for the dedicated carrier 1. Open the TariffConverterExcelTemplate.xls spreadsheet.


3. Change the PerUnitOrFlatCharge value for the TLCARR2 record to 0.71 and save the spreadsheet.

Update the cross dock charge on the hub In this exercise, there is no longer a cross dock charge incurred at the Fort Wayne hub.

Update the cross dock charge 1. Open the TariffConverterExcelTemplate.xls spreadsheet.


3. Change the CrossDockCostPerUnit value for the FW hub record to 0 and save the spreadsheet.


Verify the tariff IDs You have to determine the numeric tariff IDs created by the Access Rating Tool when it converted the spreadsheet into the Access rating database. While you will see the tariff as a concatenation of the Tariff and Service, the actual ID for the tariff is a unique numeric identifier.

Determine the Tariff IDs 1. Open the TariffConverter.mdb database.

2. Select Tables.

3. Open the TFF_T table. The records for all tariffs you have created are displayed.

4. Find the numeric TFF_ID values for:

• TLCARR_TL

• TLCARR2_TL


Update the rates for the CEA exercise

5. Close the database.

Note: You are able to verify the tariff ID values once you solve a scenario in the OptLog.txt file. For each load, the OptLog lists the Carrier and the Tariff, using the Tariff ID from the TFF_T table.


Create the carrier equipment availability constraints

Chapter 30. Create the carrier equipment availability constraints In this chapter, you define the constraints that you want to impose on the solver. The penalties you set in the optimizer parameters (in "Create the carrier equipment availability scenario" (on page 129)) are incurred if the solver exceeds these constraints.

Open an existing scenario If you do not currently have the scenario opened for the CEA modeling exercise, you should do so now.

Open an existing scenario 1. Open Transportation Modeler.

2. Select File menu from the ribbon.

3. Click Open

4. Select the CEAScenario1.tm file you created in the earlier exercise. The scenario is displayed.

Create the constraints In the first case, you will create constraints at the carrier level.

Create the required carrier records 1. Click the carrier table name on the Control Center. The Carrier Detail Table is displayed. You need

to have records for both carriers, TLCARR and TLCARR2.


3. If you do not have records for both carriers, enter the carrier name required and click OK. The dialog box closes and the new entity is displayed.

Create the required carrier availability records 1. Click the carrier availability table name on the Control Center. The Carrier Availability Table is

displayed. You need to have an availability record for each carrier.

2. If you are on the Data view, click New to go to the Query view.

3. Select TLCARR and TLCARR2 and Component 1.

4. Click New on the Query view. Two new records are created.

Update the carrier availability records with the constraints 1. Click the Carrier Availability table name on the Control Center. The Carrier Availability Detail

Table is displayed.

2. Enter the constraint values as shown in the following table:

Carrier SolverInclude MaxLoads MaxPenalty TLCARR Yes 2 15,000

TLCARR2 Yes 2 10,000


Create the carrier equipment availability constraints

Save the scenario You have now successfully created all the data required to solve the new Carrier Equipment Availability scenario. Save the scenario before proceeding. Select the File menu and click Save


Solve the CEA Scenario

Chapter 31. Solve the CEA Scenario In this chapter, you will update the strategy file from the earlier domicile exercise to support the Carrier Equipment Availability resources you have defined. You will then solve the scenario to determine the effects of your constraints.

Initial Strategy File for Carrier Equipment Availability You can start with the strategy file you defined for the domicile exercise, but you need to add items to this file to support the constraints you have defined. The strategy file will require a constraint function and a new strategy function:

• EnforceResourceConstraints: This constraint function turns on or off resource constraints through its Resource Constraints Switch argument. You can add this function at the beginning of the strategy file and set the Resource Constraints Switch to True.

• OptResourceConstraints: This strategy function attempts to select the best resource allocations for the whole plan based on resource constraints. You can include this strategy prior to pushing the plan to the plan stack. The solver will evaluate the plan based on the available resources.

EnforceResourceConstraints ( TRUE. TRUE 0 FALSE 0 )






OptResourceConstraints ( ANY 1 FALSE FALSE 0 FALSE )













Solve the model 1. Select the Home tab from the ribbon.



Optimization results with constraints are:

Algorithm Cost Distance Loads Trip

s Unroutab

les Carrier

Constraints Penalty

Cost Initial Loads 7,549 6,305 17 0 0 FALSE 0

ConSamePickAndDrop

6,856 6,851 13 0 0 TRUE 125000

Con 3,732 4,792 5 0 0 TRUE 20000

OptMove 3,323 3,741 5 0 0 TRUE 10000

OptResourceConstraints

3,324 3,741 5 0 0 TRUE 10000

HubAssignment 11,882 16,544

34 0 0 TRUE 375000

ConSamePickAndDrop

3,447 4,761 13 0 0 TRUE 125000

Con 3,158 4,108 9 0 0 TRUE 65000

OptMove 3,149 4,096 9 0 0 TRUE 65000

OptResourceConstraints

3,149 4,096 9 0 0 TRUE 65000

MergePlanStack 2,764 3,082 4 0 2 TRUE 0

CMove 2,764 3,082 4 0 2 TRUE 0

Note: If you want to keep the log, navigate to the folder where the optimization log is written and rename the OptLog.txt file. Based on the Solver Options you set in "Set solver options" (on page 40), the default path and filename is C:\jda\tmod\9.0\Reports\OptLog.txt.

Notice the Carrier Penalty values and the final outcome of the optimization in the optimization log. Each carrier is allowed only two loads, so only four loads are built. There are two unroutables (from Cleveland to Indianapolis and Lawrence), each of which displays the message "Not enough resources or the penalty for not delivering is too small". Because the penalty for shipments not delivered is only 1000, it is cheaper not to deliver these two shipments than to incur the penalty of building another load that exceeds the carrier constraint. Even if the solver used the carrier with the lower penalty (TLCARR2), it would incur a penalty of 10,000.

Adjust penalties to deliver shipments The shipper needs to have all shipments delivered, so you need to adjust the penalties to allow the unroutables to be put on loads.

One way to force the shipments to be put on loads is to increase the PenaltyShipmentNotDelivered optimizer parameter.



Update the PenaltyShipmentNotDelivered 1. Select the Home tab on the ribbon.

2. Click Edit Parameter File in the Configuration group.and select your default optimizer parameters file.

3. Set PenaltyShipmentNotDelivered to 25000 and click Save.




4. You can optionally rename the optimization log.

What do you expect the solver to do with the new penalty? Since it is now more expensive to leave the shipments unroutable (25,000 per shipment) than to exceed the maximum number of loads in the carrier constraint (a penalty of 10,000 for TLCARR2 or 15,000 for TLCARR), the solver builds a 5th load and you can see a penalty cost of 10,000.

Add Domicile Resource Constraints There is now an additional penalty for exceeding 2 loads for carrier TLCARR2 at the Pittsburgh domicile. You can control this by creating an equipment resource constraint on the Domicile record.

Update the domicile resource constraint 1. Click the Domicile table name on the Control Center. The Domicile Detail Table dialog box is

displayed.

2. Enter the constraint values for the Pittsburgh domicileas shown in the following table:

Location or Hub Carrier Equipment

Type Componen

t MaxResourc

es PenaltyMax Resources

Pittsburgh TLCARR2 48FT 1 2 10,000




Note: The change in the carrier selection made by the solver. In this case, it is cheaper to incur the 15,000 penalty for exceeding the 2 load limit on TLCARR than to incur the total penalty of 20,000 (10,000 in carrier constraints and 10,000 in domicile resource constraints) for using TLCARR2 to transport 3 loads.

It is also interesting to note that the Total Cost for the latest solution with 3 loads going to TLCARR is 2,710, which is cheaper than the previous solution with 3 loads going to TLCARR2. The previous solution was 3,324. Remember that the penalties are used to influence solver behavior, but do not actually affect the real transportation cost. In the previous case, the penalties forced a solution that actually had a higher cost.



Add Tariff Service Constraints In the previous exercise, TLCARR2 was assigned 2 loads, while carrier TLCARR had 3 loads. The shipper wants to ensure that the tariff service for carrier TLCARR2’s TL service gets a minimum of 4 loads. If the tariff service is not assigned at least 4 loads, there is a penalty of 22,000.

You will create constraints at the Tariff Service Availability level to control how many loads can be built for each carrier. You need the following entities:

• Tariff

• Service

and the following relationship records:

• Tariff Service Availability: This relationship enables you to provide minimum and maximum loads per tariff-service and penalties for violating either of these constraints.

While the tariff ID you can see in the database is the concatenation of the Tariff and Service, the actual ID for the tariff is a unique numeric identifier. Use the process described in "Verify the tariff IDs" (on page 131) to determine the actual tariff ID. Most likely, the value will either 1 or 2, as you have defined two tariffs in your rating database at this time.

Create the required tariff records 1. Click the Tariff table name on the Control Center. The Tariff Detail Table is displayed.


3. Enter one of the tariff IDs you identified in the TFF_T table of the TariffConverter.mdb and click OK. The dialog box closes and the new entity is displayed.

4. Repeat steps 2 and 3 for the other Tariff ID.

Create the required service record 1. Click the Service table name on the Control Center. The Service Detail Table is displayed.


3. Enter TL and click OK. The dialog box closes and the new entity is displayed.

Create the tariff service availability records 1. Click the Tariff Service Availability table name on the Control Center. The Tariff Service

Availability Detail Table is displayed.



• Tariff: The tariff ID for TLCARR2 as you found in the TFF_F table.

• Service: TL

and click New. A message box is displayed to confirm the creation of the tariff service availability record.

4. Click Yes. The record is created and a confirmation message is displayed.




Update the tariff service availability record 1. Click the Tariff Service Availability table name on the Control Center. The Tariff Service


2. Enter the constraint values as shown in the following table:

Tariff Service ID MinLoads MinPenalty

<tariff ID for TLCARR2> TL 4 22,000

Note: You must use the tariff ID from the TFF_T table in the TariffConverter.mdb to identify the record or review the OptLog.txt file from the previous exercise to identify the tariff ID for TLCARR2.




Now you will see that 4 loads are built and all use the TL service of carrier TLCARR2. If the solver had violated the tariff service constraint, it would have incurred a penalty of 22,000. This penalty is greater than that incurred by violating the Carrier MaxLoads penalty of 10,000 plus the Domicile MaxResources penalty of 10,000 for TLCARR2.


Dock scheduling modeling exercise

Chapter 32. Dock scheduling modeling exercise This chapter introduces another level of complexity to the model – docks and dock scheduling. The solver will now have to consider the operating hours of the dock and equipment types. A description of the modeling problem, as well as the basic data, is provided.

Model description To ensure that you understand how docks are used, you will turn off the penalties and constraints you set up in the "Carrier equipment availability modeling exercise" (on page 127). To this model, you add a dock, Dock A. All facilities have this dock and it is operational all hours of the day, every day. All locations also have 24 hour x 7 day business hours. In the OptParameter file, you must ensure that the parameter UseDocks is set to True.

Based on the movement of the shipments, note that all docks at Pittsburgh and Cleveland are outbound (support outbound shipments only), the dock at the Fort Wayne hub is both inbound and outbound, and all other docks work on inbound shipments only.

Scenario data You need to create the docks and set them up with appropriate business hours and inbound/outbound status.

In the subsequent exercises, you will limit the business hours on the docks and create additional docks. You will also create commodities and equipment types to observe their impact when assigned to docks.

Parameter values You need to enable the UseDocks parameter and ensure that the penalties you set up in the "Carrier equipment availability modeling exercise" (on page 127) have been reset in the following table:

• DriverMaxBreakTime: 00:00

• DriverMaxDriveTime: 10:00

• DriverOffDutyTime: 08:00

• DriverOnDutyTime: 15:00










• UseDocks: TRUE


Dock scheduling modeling exercise

Rates You can use the rates as defined for the previous "Carrier equipment availability modeling exercise" (on page 127).

Constraints As mentioned earlier, you need to remove or exclude all the constraints you established in the "Carrier equipment availability modeling exercise" (on page 127).

Analysis overview 1. After creating the initial set of docks, you will solve the new dock scheduling scenario and save the

Optimization Log. The customer then experiences some trouble at the dock at Indianapolis. Although the location is available for use 24 hours a day, 7 days a week, Dock A is available only from 9 am to 6 pm on Thursdays. Does this alter the schedule of the shipments?

2. Next, you will further narrow the scheduling by specifying time windows for the 17 shipments. The customer requires that each shipment is picked up within the time frame of 02/01/07 12:00:00 AM to 02/01/07 11:59:59 PM and each shipment must be delivered between 1:00:00 AM on 02/01/07 and 11:59:59 PM on 02/02/07. All dates are in MM/DD/YY format. When you solve this scenario, are all the shipments routed? If no, then give an explanation for the unroutables using the error message provided for the unroutable in the OptLog.txt file.

3. If the customer is allowed any liberty, then suggest four ways in which the shipments to Indianapolis can be routed correctly again.

4. The customer would like to try a multiple-dock-per-location trial to see the difference in outcome. He plans to create two new docks, Dock B and Dock C at all his locations. But due to the additional cost of managing these new docks, he has planned to operate all three docks at each location for only 2 hours every Thursday and Friday (from 9 AM to 11 AM) to suit his requirements. Do you think this is a better move?

5. The customer decides to retain the multiple-dock model but wants to examine the Dock Report to identify potential areas of cost reduction in the usage of docks. You must determine how a dock report can be generated.

6. If the customer wishes to limit the use of docks based on the freight class of each shipment, how would you ensure that shipments of freight class 60 and 70 are not permitted to load or unload at any Dock C?

7. From the dock report, you can observe that only Dock C at each facility is being used when no other constraints are in place. What would be the expected behavior if the Dock C at every location is reserved for only equipment TRU32, which neither of the carriers have access to?


Create the dock scheduling scenario

Chapter 33. Create the dock scheduling scenario In this chapter, you will remove the constraints you previously defined and exclude the domiciles. In this way, you can more clearly observe the effects of the dock scheduling exercises.

You will create the business hours and docks that you require, then associate the business hours to the locations and docks.

Open the existing scenario If you do not currently have the scenario opened for the CEA modeling exercise, you should do so now.

1. Open Transportation Modeler.

2. Select File menu from the ribbon.

3. Click Open .

4. Select the CEAScenario1.tm file you created in the earlier exercise. The scenario is displayed.

Remove the constraints and domiciles We want to concentrate on the dock scheduling only, so you will first remove the constraints you created in "Carrier equipment availability modeling exercise" (on page 127).

To remove constraints, you can use a variety of mechanisms. In some cases, you can delete the records (you cannot do this for the Carrier records, since the constraints are on the carriers and you still need the Carrier records). You can remove the constraint values from the fields in the records. In the case of the Carrier constraints, you can disable the constraints within the carrier records.

Remove the constraints 1. Click Carrier Availability on the Control Center. The Carrier Availability Detail Table dialog box is

displayed.

2. Set the SolverInclude field to No for both records.

3. Click Domicile on the Control Center. The Domicile Detail Table is displayed.

4. Remove the MaxResources and PenaltyMaxResources values.

5. Click Tariff Service Availability on the Control Center. The Tariff Service Availability Detail Table is displayed.

6. Set the SolverInclude value to No.

Exclude the domiciles 1. Click Domicile on the Control Center. The Domicile Detail Table is displayed.

2. Select Select All by clicking in the top left of the grid.

3. Click Set.

4. Select the SolverInclude field and set the value to No.

5. Click Set. A confirmation of the update is displayed.

6. Click OK, then click Close.



Edit optimizer parameters file 1. Select the Home tab on the ribbon.




5. Ensure the parameters are defined as displayed in the following table:

Parameter Value DriverMaxBreakTime 00:00

DriverMaxDriveTime 10:00

DriverOffDutyTime 08:00

DriverOnDutyTime 15:00

PenaltyMaxLoads 0

PenaltyMinLoads 0

PenaltyPerDayStartDelay 0

PenaltyPerPerformancePoint 100

PenaltyShipmentNotDelivered 1000

PenaltyTransferHubEquipment 0

PenaltyTransitMode 1000

PenaltyVendorSequencingViolation

1000

PenaltyWaitTimePerHour 0

UseDocks TRUE

Create the dock You first create the dock using the Dock table. You can then control the operation of the dock using one or more of the associated tables:

• Dock at Facility

• Dock at Facility Commitment

• Dock at Facility Commodity

• Dock at Facility Equipment Type

• Dock at Facility Loading Type

Create the dock 1. Click Dock on the Control Center. The Dock Detail Table is displayed.


3. Enter Dock A and click OK. The dialog box closes and the new entity is displayed.



Create the dock at facility records 1. Click Dock at Facility on the Control Center. The Dock at Facility Detail Table is displayed


3. Click Select All to select all the LocationOrHub values and the Dock ID.

4. Click New on the Detail Table. A message box is displayed to confirm the creation of 11 Dock at Facility records.

5. Click Yes. A confirmation dialog is displayed.

6. Click OK.

Set the type of dock Note: The default for DockType is Both (both inbound and outbound). You need to change those docks that only support inbound or outbound shipments.

1. Click Dock at Facility on the Control Center. The Dock at Facility Detail Table is displayed.

2. Select the records for Cleveland and Pittsburgh, Dock A.

3. Click Set. The Set Field Values dialog box is displayed.

4. Select DockType and select Outbound from the drop-down list.

5. Click Set. A confirmation message box is displayed.

6. Click OK to dismiss the confirmation box, then click Close.

7. Repeat steps 2 through 7, selecting Chicago, Cicero, Detroit, Gary, Indianapolis, Lawrence, Louisville and Riverview as the LocationOrHub values and Inbound as the DockType.

Save the scenario Save the scenario as a new scenario file before proceeding.


2. Click Save As .

3. Enter DockScenario1 and click Save.


Solve the dock scheduling scenario

Chapter 34. Solve the dock scheduling scenario In this chapter, you will use the strategy file you created for the domicile exercise. You will adjust the docks and shipment time windows to observe the behavior using the docks.

Initial strategy file for dock scheduling You can start with the strategy file you defined for the domicile exercise. This strategy file does not include the EnforceResourceConstraints constraint function and OptResourcesConstraints strategy function that you added for the Carrier Availability modeling exercise.


















Note: If you want to keep the log, navigate to the folder where the optimization log is written and rename the OptLog.txt file. Based on the Solver Options you set in "Set Solver options" (on page 40), the default path and filename is C:\jda\tmod\9.0\Reports\OptLog.txt.

Notice the arrival time for the shipment to Indianapolis – 02/01/07 at 10:59 PM. You are going to restrict the available hours for the dock at this facility and verify that this change impacts the schedule.



You can determine the arrival time in several ways:

• Review the OptLog.txt file and find the load with the shipments to Indianapolis (SH4 and SH11). The Arrival time is 02/01/07 22:59.

• Use Home> Utilities > Plan Explorer and expand the load to Indianapolis. Right-click on the Stop icon for Indianapolis and select Details. The Arrival time is displayed.

• Open the Stop Detail table and find the records with a Location value of Indianapolis. Verify the ArrivalTime value.

Adjust the business hours at the dock There is an issue with the dock at Indianapolis; it is now only open on Thursdays from 9 AM to 6 PM. You use the Business Hours and Time Windows tables to define the business hours for the dock.

Create the business hours 1. Click Business Hours on the Control Center. The Business Hours Detail Table is displayed.


3. Enter ThuLimited and click OK. The dialog box closes and the new entity is displayed.

Create the time windows for the business hours 1. Click Time Window on the Control Center. The Time Window Detail Table is displayed.


3. Select:

• Business Hours: ThuLimited

• Day of Week: Thu

and click New on the Detail Table. A message box is displayed to confirm the creation of the Time Windows record.

4. Click Yes. A confirmation dialog box is displayed.

5. Click OK.

Set the time window 1. Select the new record.

2. Enter the following values:

BusinessHours DayOfWeek OpenTime1 CloseTime1 ThuLimited Thu 09:00 am 06:00 pm

Assign the business hours to the dock and verify 1. Click Dock at Facility on the Control Center. The Dock at Facility Detail Table is displayed.

2. Select ThuLimited for the BusinessHours value for Indianapolis, Dock A.






You will see that the schedule for the load with the shipment to Indianapolis has changed to accommodate the restrictions on the dock’s business hours. The load now arrives at this location at 9:00 AM on 02/08/07.

Set the time windows on the shipments You will now limit the time windows for the 17 shipments. All will have the same time window values:

• Pickup between 02/01/07 12:00:00 AM and 02/01/07 11:59:59 PM

• Delivery between 02/01/07 1:00:00 AM and 02/02/07 11:59:59 PM

Set the shipment time windows 1. Click Shipment on the Control Center. The Shipment Detail Table is displayed.

2. Select all records.

3. Click Set.

4. For the EarliestShipTime, enter 02/01/07 12:00:00 AM and click Set. A confirmation message box is displayed.

5. Click OK.

6. Repeat steps 3 through 5 to set the:

• LatestShipTime to 02/01/07 11:59:59 PM

• EarliestDeliveryTime to 02/01/07 1:00:00 AM

• LatestDeliveryTime to 02/02/07 11:59:59 PM

7. Click Close.




In this case, are all the shipments routed? Due to the combination of the restricted shipment time windows and the limit on the business hours at the Indianapolis dock, the shipment from Pittsburgh to Indianapolis is now unroutable. In the Optimization Log, you can view the message:

Arrival window missed: The arrival for Indianapolis must be before 02/02/07 23:59:59, but the earliest computed arrival time is 02/08/07 09:00:00.

This is because Dock A does not operate on 02/02/07 which is a Friday, due to the restricted business hours. There are a number of ways in which this conflict can be resolved. These include:

• Changing the time windows specified for the shipment concerned,

• Changing the business hours of Dock A,

• Creating a business hours exception record for Dock A on 02/02/07 that enables the dock for a set of working hours,

• Creating a new dock, Dock B, at Indianapolis that works on Fridays.



Add multiple docks per location Next, you will update the scenario to support multiple docks at each location. In this case, you will create two new docks, Dock B and Dock C, and assign them to all locations. To offset the cost of managing the additional docks, you will restrict the operating hours for all 3 docks to only 9:00 AM to 11:00 AM on Thursdays and Fridays.

Create the dock 1. Click Dock on the Control Center. The Dock Detail Table is displayed.


3. Enter Dock B and click OK. The dialog box closes and the new entity is displayed.

4. Repeat steps 2 and 3 to create Dock C.

Create the dock at facility records 1. Click Dock at Facility on the Control Center. The Dock at Facility Detail Table is displayed.


3. Click Select All to select all the LocationOrHub values and select docks Dock B and Dock C.

4. Click New on the Detail Table. A message box is displayed to confirm the creation of 22 Dock at Facility records.


6. Click OK.

Set the type of dock 1. Click Dock at Facility on the Control Center. The Dock at Facility Detail Table is displayed.

2. Select the records for Cleveland and Pittsburgh, Docks B and C.


4. Select DockType and select Outbound from the drop-down list.

5. Click Set. A confirmation box is displayed.


7. Repeat steps 2 through 6, selecting Chicago, Cicero, Detroit, Gary, Indianapolis, Lawrence, Louisville and Riverview as the LocationOrHub values and Inbound as the DockType.

Create the business hours 1. Click Business Hours on the Control Center. The Business Hours Detail Table is displayed.


3. Enter ThuFriLimited and click OK. The dialog box closes and the new entity in the Entity list box is displayed.

Create the time windows for the business hours 1. Click Time Window on the Control Center. The Time Window Detail Table is displayed.




3. Select:

• Business Hours: ThuFriLimited

• Day of Week: Thu and Fri

and click New on the Detail Table. A message box is displayed to confirm the creation of the Time Windows record.


5. Click OK.

Set the time window 1. Click Time Windows on the Control Center. The Time Windows Detail Table is displayed.

2. Enter the following values for ThuFriLimited:

BusinessHours DayOfWeek OpenTime1 CloseTime1 ThuFriLimited Thu 09:00 am 11:00 am

ThuFriLimited Fri 09:00 am 11:00 am

Set the business hours at the docks 1. Click Dock at Facility on the Control Center. The Dock at Facility Detail Table is displayed.

2. Select all rows in the table.


4. Select BusinessHours and select ThuFriLimited from the drop-down list.






Is this a better solution than the single dock in the previous exercise? In fact, the cost has increased because the solver has to manipulate the loads to accommodate the business hours restriction. Some of the loads that were scheduled earlier in time have to be split to accommodate the 2 hour span for the first pick and the last drop.

Enable the dock report To get a clearer picture of how the docks are being scheduled as a result of the optimization, you can have the solver generate a dock report. This report can be used to example the dock usage and help you to analyze how to use the docks more cost effectively.

Enable the dock schedule report 1. Edit the strategy file and add the TryDockScheduling strategy to the end of the file.

2. Save the strategy file.




4. Click Solve in the Scenario group. The model solves. Both the optimization log (OptLog.txt) and the dock schedule report (DockReport.txt) are automatically written to the folder you specified for the Report Directory in the Solver Options.


You can review the DockReport.txt to see how the docks are used and get the scheduling details.

Restrict freight classes at the docks With the multiple dock per facility model, the shipper wants to limit which docks can handle specific freight classes. Specifically, he wants to exclude freight classes 60 and 70 from Dock C at all locations.

To accomplish this, you need to create commodity codes representing the three freight classes. You assign these commodity codes to the shipments based on their actual FreightClass values. You can then create Dock at Facility Commodity records (these act as exclusion records) to exclude the commodities for freight classes 60 and 70 from all Dock C instances.

Create the commodities 1. Click Commodity Code on the Control Center. The Commodity Code Table is displayed.


3. Enter 50 and click OK. The dialog box closes and the new entity is displayed.

4. Repeat steps 2 and 3 to create records for commodity codes 60 and 70.

Set the commodity code on the shipments 1. Click Shipment on the Control Center. The Shipment Detail Table is displayed.

2. Filter the FreightClass column to 50. Select SH1 through SH15.


4. Select CommodityCode and select 50 from the drop-down list.



7. Repeat steps 2 through 6, selecting SH16 and setting the CommodityCode to 60, then repeat the steps again, selecting SH17 and setting the CommodityCode to 70.

Create the dock at facility commodity records Note: These records define commodities that are excluded from the dock at facility.

1. Click Dock at Facility Commodity on the Control Center. The Dock at Facility Commodity Detail Table dialog box is displayed.


3. Select:

• LocationOrHub: all entities

• Dock: Dock C

• Commodity Code: 60 and 70



4. Click New on the Detail Table. A message box is displayed to confirm the creation of 22 Dock at Facility Commodity records.


6. Click OK. Commodities 60 and 70 will now be excluded at all instances of Dock C.




You can review the DockReport.txt to see how the commodity exclusions have affected the dock assignments. Shipments 16 (FreightClass 60) and 17 (FreightClass 70) are now handled by Dock B.

Limit docks by equipment types Before you added the commodity codes, Dock C was being used at all the facilities. The shipper wants to know what would happen if Dock C is reserved for a specific type of equipment, TRU32. This piece of equipment is currently unavailable to your existing carriers. As of the last exercise, Dock C was used everywhere except in the case that a commodity exclusion prevented it.

You will create a new equipment type and assign it to Dock C at all locations. After solving, you can see the effect of this assignment in the dock report.

Create the equipment type 1. Click Equipment Type on the Control Center. The Equipment Type Table is displayed.


3. Enter TRU32 and click OK. The dialog box closes and the new entity is displayed.

Create the dock at facility equipment type records 1. Click Dock at Facility Equipment Type on the Control Center. The Dock at Facility Equipment Type

Detail Table is displayed.


3. Select:

• LocationOrHub: all entities

• Dock: Dock C

• Equipment Type: TRU32

4. and click New on the Detail Table. A message box is displayed to confirm the creation of 11 Dock at Facility Equipment Type records.


6. Click OK.






You can review the DockReport.txt to see how the new equipment type affected the dock assignments. Since neither of your carriers uses the new equipment type, TRU32, Dock C cannot be assigned to any of the loads.


Tractor and Trailer Modeling Exercise

Chapter 35. Tractor and Trailer Modeling Exercise This chapter introduces you to concepts of specific equipment types at domiciles. You can see how equipment availability at domiciles, capacity restrictions and penalties translate into equipment selection for tractors and trailers. A description of the modeling problem, as well as the basic data, is provided.

Model description In this case, there is a customer who has a dedicated fleet (DED). The fleet has two equipment types – tractors (DED-TTR) and trailers (DED-TLR). The customer has a domicile at Fort Wayne. One unit of each of the equipment types is available at the domicile; the total initial capacity of the fleet is restricted to one tractor and one trailer.

The customer has 7 shipments, each weighing 1,000 lbs. The shipments have defined time windows within which they must be shipped:

Shipment ID Origin Ship Time Range Destinatio

n Delivery Time Range

SH1 Fort Wayne 1/1/08 12:00:00 AM – 1/1/08 1:00:00 AM

Toledo 1/1/08 3:30:00 AM – 1/1/08 4:00:00 AM

SH2 Toledo 1/1/08 3:30:00 AM – 1/1/08 4:00:00 AM

Cleveland 1/1/08 7:30:00 AM – 1/1/08 8:00:00 AM

SH3 Cleveland 1/1/08 7:30:00 AM – 1/1/08 8:00:00 AM

Pittsburgh 1/1/08 9:45:00 PM – 1/1/08 10:15:00 PM

SH4 Pittsburgh 1/1/08 9:45:00 PM – 1/1/08 10:15:00 PM

Fort Wayne

1/2/08 6:30:00 PM – 1/2/08 7:00:00 PM

SH5 Fort Wayne 1/1/08 12:00:00 AM – 1/1/08 1:00:00 AM

Chicago 1/1/08 5:30:00 AM – 1/1/08 6:00:00 AM

SH6 Chicago 1/1/08 5:30:00 AM – 1/1/08 6:00:00 AM

Indianapolis

1/1/08 10:00:00 PM – 1/1/08 10:30:00 PM

SH7 Indianapolis 1/1/08 10:00:00 PM – 1/1/08 10:30:00 PM

Fort Wayne

1/2/08 2:15:00 AM – 1/2/08 2:45:00 AM

The customer has approximated the cost of running the dedicated fleet to $1.381 per mile up to 600 miles and $1 per mile for distances over 600 miles. The penalty for each shipment that is not delivered is $1000.

Scenario data You will create a new scenario and all required data for this exercise. This will include the Locations, Shipments, Carrier, Equipment Types, Domicile and Domicile Vehicle Availability records.

Parameter values Ensure that the PenaltyShipmentNotDelivered parameter has a value of 1000.

Rates You will create a new set of rates, including rate ranges, for the dedicated carrier.


Tractor and Trailer Modeling Exercise

Analysis overview 1. Once you create the scenario and rating engine, solve the model to determine how many loads and

trips are created. Are there any unroutables? If so, explain why those shipments would be unroutable.

2. The customer wants to add a common carrier in order to deliver the shipments that cannot be accommodated by his dedicated fleet. The common carrier, COMM, uses one equipment type (COMM-TT), which is a tractor-trailer. The rates provided by the common carrier are:

Lane Rate per mile IN – OH 1.31

OH – OH 1.31

OH – PA 1.31

PA – IN 1.31

IN – IL 2.25

IL – IN 2.25

IN – IN 2.25

When you solve the scenario with this additional carrier, what is the result? Is the new output justified?

3. The customer wants to be able to service shipment SH1 with his own dedicated carrier, rather than let the common carrier handle it. Can this be done? If so, how?

4. The customer now decides he wants to do away with the common carrier and expand the dedicated fleet. He now has 2 types of trailers available sourced out of the Fort Wayne domicile, a 24 foot (DED-TLR24) and a 48 foot (DED-TLR48). Since the costs differ based on the kind of equipment that is used, he changes his rating model to be equipment based:

Equipment Type Rate per mile DED-TTR (tractor) 1

DED-TLR24 0.25

DED-TLR48 0.3

The dedicated fleet has only one each of the two trailers, DED-TLR24 and DED-TLR48. It has 7 tractors, DED-TTR, available.

When you solve this scenario, what is the equipment configuration used in the output and why?

5. If the trailer equipment was available at a domicile in New Haven, IN, rather than Fort Wayne, how does this affect the solution when you solve the scenario?

6. If the customer wants to guarantee that shipment SH1 is only serviced by trailer DED-TLR48, is this feasible? If so, how?


Create the rates for tractor - trailer modeling

Chapter 36. Create the rates for tractor - trailer modeling In this chapter, you will use the Access Rating Tool to model the rates required for the exercise described in "Tractor and Trailer Modeling Exercise" (on page 153).

The TariffConverterExcelTemplate.xls file contains the fields you can populate in support of your modeling requirements. This file contains a set of worksheets: TL, LTL, SmallPackage, RateRange, Hubs and Zones. The exercise requires you to enter relevant details in the TL worksheet.

Caution: JDA recommends that you create a copy of the TariffConverterExcelTemplate.xls file. Do not change the field names in TariffConverterExcelTemplate.xls. Do not copy data from another spreadsheet or worksheet to paste into the cells in the TariffConverterExcelTemplate.xls file. Many of the cells in the template spreadsheet are defined with a specific format. Copying and pasting data can result in a change in data types and error during conversion to the Access database format.


Create required tariffs In this section, you create the tariffs that are required to rate the shipments using the dedicated fleet described in the exercise. In this case, the actual rate is based on weight breaks. You will define a truckload tariff and rate ranges for each of the weight breaks.

Create the truckload tariff Enter the required data onto the TL worksheet in the TariffConverterExcelTemplate.xls spreadsheet. You do not need any of the data that was defined for previous exercises. If you already have data in the spreadsheet, you can delete all existing records prior to creating the new data.



3. Delete all existing data from previous exercises.



Note: If no value is required, leave the field value blank. This results in the tool accepting the default value:


Carrier This field is the identifier for the carrier. DED





TL


Equipment This field is the code describing the equipment used for the movement.

RateCode Use this field to specify a RateCode for the Carrier/Tariff/Service/Charge that already exists in the database. This enables you to define new lanes that use this RateCode. You can define multiple rows (multiple lanes) with the same RateCode. If you set the RateCode to *, the rating engine applies it to all lanes. If you leave the RateCode blank, the conversion macro in the Access database will create a unique RateCode for each lane.

RateCode

DivisionCode Use this field to specify the division for the tariff records. DivisionCode


Imperial

DimWeightFactor


UnitDivideFactor



Distance






• LookAhead

• LookBack

• Disabled



PerUnit



MinChargeLocation



Specifies the rate that is levied.


RR1

OriginZoneCode



OriginPostalCode



















RoundTrip



Y

MinimumValue1


MaximumValue1

Specifies the maximum value, in units specified by MinMaxValueType1, for the movement. In this case, movements are limited to 40,000 pounds. Note: MaximumValue2, MaximumValue3, MaximumValue4, and MaximumValue5 fields are also available in the spreadsheet, but not used in this example.

MinMaxValueType1


Other Comments




Create the rate range For this rating model, the charge incurred is based on the distance. For distances up to 600 miles, the rate is $1.381. For distances over 600 miles, the rate is $1.


2. Select the RateRange worksheet.

3. Create the records using the values in the table that follows:

Field Record 1 Record 2 RateRangeID RR1 RR1

RateType PerUnit PerUnit


1.381 1

BaseCharge blank blank

RangeMax 600 99999

Clip blank blank


Add the equipment types to the rating database You need to create the two Equipment Types, DED-TTR and DED-TLR, and associate them with the truckload service for the dedicated carrier. You will use the Entity Manager in the TariffConverter.mdb to create the records.

Add the Equipment Types 1. Open the TariffConverter.mdb file.

2. Select Macros.

3. Select the Entity Manager and click Run. The Entity Manager dialog box is displayed.

4. Click on the equipment node and select Add Equipment. The Add Equipment dialog box is displayed.

5. Enter DED-TTR for the Equipment Code.

6. Select Tractor for the Equipment Category.

7. Click Add. The tractor equipment is added.

8. Enter DED-TLR for the Equipment Code.

9. Select Trailer for the Equipment Category.

10. Click Add. The trailer equipment is added.

Associate the equipment types to the service 1. Open the TariffConverter.mdb file.

2. Select Macros.



3. Select the Entity Manager macro and click Run. The Entity Manager dialog box is displayed.

4. Expand the Carriers node to the Services level.

5. Expand the DED_TL node. The TL service dialog box is displayed.

6. Select the TL service node, click and select Update Service. The Update Service dialog box is displayed.

7. In the Equipment area, click Add. The Select Equipment dialog box is displayed.

8. Select DED-TTR from the drop-down list and click Add. The Equipment is associated with the service.


10. Select DED-TLR from the drop-down list and click Add. The Equipment is associated with the service.

11. If the default equipment, *DFT, is associated with the service, select *DFT in the Equipment list and click Remove.

12. Click Update to exit from the Update Service dialog box.



Create data for the tractor - trailer exercise

Chapter 37. Create data for the tractor - trailer exercise Create the location, shipment, carrier, equipment type, domicile and domicile vehicle availability records for this exercise.

Create locations The new scenario requires a set of six locations.

1. Select the File menu on the ribbon and click New to start a new scenario.


• Click Location on Control Center. The Location Detail table is displayed.

• Right-click the table name on Control Center, and select the Detail table from the shortcut menu.


• Click New on the Detail table. The Create New dialog box is displayed.

• Right-click on the gray part of the Detail table and select Record > New from the shortcut menu.

4. Enter the record name in Name.

5. Click OK. Name each location ID by the city name:

• Chicago

• Cleveland

• Fort Wayne

• Indianapolis

• Pittsburgh

• Toledo

Add location data 1. Perform one of the following tasks:

• Click Location on Control Center. The Detail table is displayed.


2. Enter information in the fields or select values from the drop-down lists. The following table shows the information you should enter for the location records:

LocationID City State Country Chicago Chicago IL USA

Cleveland Cleveland OH USA



LocationID City State Country Fort Wayne Fort Wayne IN USA

Indianapolis Indianapolis IN USA

Pittsburgh Pittsburgh PA USA

Toledo Toledo OH USA

Update LatLon and PostalCode 1. Select the Home tab from the ribbon.


3. Select City - Lat/Lon Translator and/or Postal Code - Lat/Lon Translator checkboxes to indicate the data utility tables you want to load.

4. Click OK. The Progress dialog box is displayed, as Transportation Modeler loads each database. The data utility tables in the Status Bar are displayed on completion.

5. Click the Location table name on Control Center. The Location Detail table is displayed.

6. Select all rows on the Detail table

7. Click Set on the Detail table. The Set Field Value dialog box is displayed.

8. Select LatLon.

9. Select City Centroid in To: and click Set. A message box indicating that six rows have been updated is displayed.


11. Select PostalCode.

12. Select Closest by Lat/Lon in To: and click Set.

13. Click OK.

14. Click Close to close the Set dialog box.

Create shipments For this exercise, create seven unique shipment records.

1. Click the Shipment table name on Control Center. The Shipment Detail table is displayed.

2. Click New on the Detail table. The Create New dialog box is displayed.

3. Enter the record name in Name. Each shipment requires a unique identifier. For the first shipment, enter SH1.

4. Click OK to close the dialog box. The new entity is displayed.

5. Repeat steps 2 to 4 to create the remaining six unique shipment IDs.

6. Set the weight to 1000 for all shipments.

7. Enter the data for the shipments as shown in the following table:



Shipment ID Origin EarliestShipTim

e LatestShipTim

e Destinati

on EarliestDelivery

Time LatestDelivery

Time SH1 Fort

Wayne 1/1/08 12:00:00 AM

1/1/08 1:00:00 AM

Toledo 1/1/08 3:30:00 AM

1/1/08 4:00:00 AM

SH2 Toledo 1/1/08 3:30:00 AM

1/1/08 4:00:00 AM

Cleveland 1/1/08 7:30:00 AM

1/1/08 8:00:00 AM

SH3 Cleveland

1/1/08 7:30:00 AM

1/1/08 8:00:00 AM

Pittsburgh

1/1/08 9:45:00 PM

1/1/08 10:15:00 PM

SH4 Pittsburgh

1/1/08 9:45:00 PM

1/1/08 10:15:00 PM

Fort Wayne

1/2/08 6:30:00 PM

1/2/08 7:00:00 PM

SH5 Fort Wayne

1/1/08 12:00:00 AM

1/1/08 1:00:00 AM

Chicago 1/1/08 5:30:00 AM

1/1/08 6:00:00 AM

SH6 Chicago 1/1/08 5:30:00 AM

1/1/08 6:00:00 AM

Indianapolis

1/1/08 10:00:00 PM

1/1/08 10:30:00 PM

SH7 Indianapolis

1/1/08 10:00:00 PM

1/1/08 10:30:00 PM

Fort Wayne

1/2/08 2:15:00 AM

1/2/08 2:45:00 AM

Create carrier For this exercise, create one carrier record.

1. Click the Carrier table name on Control Center. The Carrier Detail table is displayed.


3. Enter DED in Name and click OK. The dialog box closes and the new entity is displayed.

Create equipment types For this exercise, create two equipment type records.

1. Click the Equipment Type table name on Control Center. The Equipment Type Detail table is displayed.


3. Enter DED-TTR in Name and click OK. The dialog box closes and the new entity is displayed.

4. Repeat steps 2 and 3 to create the DED-TLR equipment type.

Create domiciles For this exercise, create a record for each equipment type at the Fort Wayne location.

1. Click the Domicile table name on Control Center. The Domicile Detail table is displayed.


3. Select:

• LocationOrHub: Fort Wayne

• Carrier: DED



• EquipmentType: DED-TLR and DED-TTR

• Component: 1

4. Click New on the Detail table.

5. Click Yes to verify creation of the new records. Two new records are created.

6. Select both the records and click Execute.

7. Enter 1 for MaxResources for both records.

8. Select Tractor as DomicileType for DED-TTR and Trailer as DomicileType for DED-TLR.

Create domicile vehicle availability 1. Click the Domicile Vehicle Availability table name on Control Center. The Domicile Vehicle

Availability Detail table is displayed.

2. If not already in the Query View, click New to go to the Query View

3. Select:


• Carrier: DED

• EquipmentType: DED-TLR and DED-TTR

• Component: 1



6. Select both the records and click Execute.

7. Enter 1 for NumVehicles for both records.

Update optimizer parameters You can specify global penalties to ensure that the equipment restrictions are enforced during optimization.

1. Select the Home tab on the ribbon.


3. Select the parameter file to edit. By default, the file is the one you set in the Solver Options dialog box.

4. Click Open. The parameter file is displayed in Parameter File Editor.

5. Ensure that the parameters are defined as follows:

• MaxOutOfRoutePct: 65





Save scenario Having created all the location and shipment data required to solve the scenario, save the scenario to proceed.

1. Select the File menu and click Save As .

2. Enter a name for the scenario, for example TractorTrailerScenario1.

3. Click Save.


Solve the tractor - trailer scenario

Chapter 38. Solve the tractor - trailer scenario In this chapter, solve the scenario using a strategy file that includes the EnforceResourceConstraints constraint function and the OptResourceConstraints strategy function. These functions force the solver to consider the domicile equipment constraints you created.

Initial strategy file for tractor - trailer Use the strategy file as shown. Following are the uses of the new functions:

• EnforceResourceConstraints: Use this to enforce constraints for carrier, tariff/service, lane and domicile resources. The arguments for EnforceResourceConstraints are:

Argument Type Description Default

Lower limit

Upper limit

Allow ‘ANY’

ResourceConstraint Switch

Boolean

If you set this value to True, this function enforces resource constraints. Resources include carriers, tariff/services, lanes, and domiciles.

False 0 None False

EnforceVehicle Constraints

Boolean

If you set this value to True, Transportation Modeler considers the maximum penalty for vehicle constraints throughout the solve.

False 0 None False

OverlapTolerances Integer Specify the maximum number of minutes by which the availability window for a vehicle and the time window for a load can overlap. Providing some overlap allows the scheduling of vehicle that might otherwise be excluded by strict time windows.

0 0 None False

• OptResourceConstraints: Use this to have the solver consider alternate routes available for shipments once they are placed on loads. For example, the alternatives could be different carriers or services. The arguments for OptResourceConstraints are:


Lower limit

Upper limit

Allow ‘ANY’

MaxRoutesPerLoad Float Do not consider more than MaxRoutesPerLoad alternatives during the OptCarrierAssignment strategy.

20 0 None True




Lower limit

Upper limit

Allow ‘ANY’

TryResourceSwap Boolean

If you set TryResourceSwap to True, the Solver engine also uses a heuristic approach and attempts to swap shipments in an effort to find alternate carriers or services.

True 0 None False

GenerateColumns Boolean

If you set this value to True, the solver determines whether to consider routes and resource assignments on the fly. This setting may have some advantage when the problem has complex resource constraints.

False 0 None False

UnrouteShipments Boolean

If you set this value to True, the solver unroutes shipments if the ‘shipment not delivered’ penalties are less than the resource penalties and transportation cost. If you set this value to False, the ‘shipment not delivered’ penalty is not considered.

False 0 None False

EnforceResourceConstraints ( TRUE TRUE 0 FALSE 0 )


Set ( INITIAL GETPLAN () )






SetPlan ( INITIAL )


CMove ( 500 10 FALSE ANY ANY 0 ANY ANY 0 0 FALSE 2 FALSE )



TryDockScheduling ( FALSE TRUE FALSE 0 0 1 TRUE FALSE 10 FALSE FALSE TRUE 50 TRUE 0 FALSE FALSE 0 Infinity 0



Set ( LATER GETPLAN () )


ReOptTLTrips ( 85 0 0 1000 1000 3 0 100 1000 )


MergeSolvePlanStack ( STACK FALSE ANY FALSE TRUE )


2. Click Solve in the Scenario group. A message box with warnings for the seven shipment records is displayed. The SolverValid field on the shipment records indicates that FreightClass is null and is not required for this exercise.

Note: The Validation tab in the Options dialog box controls whether specific conditions are considered warnings (message only) or errors (prevents optimization). You can change the result by double-clicking Condition.

3. Click OK to dismiss the message. The model solves and the optimization log is automatically written.




Your plan should have one trip, no standalone loads and three unroutable shipments, with a cost of $796 and a distance of 796. Shipments SH5, SH6 and SH7 are unroutable. Evaluating the penalty for not delivering shipments against the capacity limit of one tractor and one trailer, Transportation Modeler unroutes the trip with the fewest shipments.

Evaluate addition of the common carrier Evaluate the impact of adding a common carrier with its own equipment resources.

Add the common carrier For this, create one carrier record:



3. Enter COMM in Name and click OK. The dialog box closes and the new entity is displayed.



Add the equipment type for the common carrier For this, create one additional equipment type record.



3. Enter COMM-TT in Name and click OK. The dialog box closes and the new entity is displayed.

Add the common carrier rates The customer wants to include a common carrier, COMM, to service the shipments that were unroutable. The carrier uses tractor-trailer equipment called COMM-TT. The rates per mile provided by the common carrier are:

• IN – OH: 1.31

• OH – OH: 1.31

• OH – PA: 1.31

• PA – IN: 1.31

• IN – IL: 2.25

• IL – IN: 2.25

• IN – IN: 2.25

1. Open the TariffConverterExcelTemplate.xls spreadsheet and select the TL tab.

Add rates as shown in the following table:

Field Record 2 Record 3 Record 4 Record 5 Record 6 Record 7 Record 8

Carrier COMM COMM COMM COMM COMM COMM COMM

Service TL TL TL TL TL TL TL

Tariff blank blank blank blank blank blank blank

Equipment COMM-TT

COMM-TT

COMM-TT

COMM-TT

COMM-TT

COMM-TT

COMM-TT

DivisionCode blank blank blank blank blank blank blank

RateCode blank blank blank blank blank blank blank

UOMType Imperial Imperial Imperial Imperial Imperial Imperial Imperial

DimWeight Factor


UnitDivide Factor


ChargeType Distance Distance Distance Distance Distance Distance Distance

LookupType blank blank blank blank blank blank blank

LookAheadRule





RateType PerUnit PerUnit PerUnit PerUnit PerUnit PerUnit PerUnit

TeamDriver blank blank blank blank blank blank blank

MinCharge blank blank blank blank blank blank blank

MinCharge Location



1.31 1.31 1.31 1.31 2.25 2.25 2.25

RateRangeID blank blank blank blank blank blank blank

OriginzoneCode


OriginHubID blank blank blank blank blank blank blank

OriginPostal Code




OriginState IN OH OH PA IN IL IN

OriginCountry

USA USA USA USA USA USA USA

DestzoneCode


DestHubID blank blank blank blank blank blank blank

DestPostalCode




DestState OH OH PA IN IL IN IN

DestCountry USA USA USA USA USA USA USA

TransitTime blank blank blank blank blank blank blank


PointTo Point

PointTo Point

PointTo Point

PointTo Point

PointTo Point

PointTo Point

PointTo Point


N N N N N N N

MinimumValue1


MaximumValue1


MinMaxValue Type1





Other Comments



2. Use the TariffConverter.mdb to convert the spreadsheet into the rating database as described in "Convert the data to a rating database" (on page 28). Caution: Do not select the Delete Existing Data option when converting the data. Keep the existing data that was defined for the DED carrier.

Caution: If you select Delete Existing Data when converting the spreadsheet, redefine the equipment for the dedicated carrier (DED) as defined in "Add the Equipment Types to the rating database" (on page 159).

In this case, since there was only one equipment type, which was included in the tariff definition, the equipment type and association with service were created during the conversion from the spreadsheet.

Solve the model with the common carrier and save the optimization log 1. Select the Home tab from the ribbon.

2. Click Solve in the Scenario group. The model solves and the optimization log is automatically written.




6. Review the new optimization log to determine how the shipments are allocated and if this allocation is justified.

In this case, four standalone loads and one trip are built. There are no unroutable shipments. The cost is $1839 and the distance is 1372. DED is assigned to the trip with shipments SH5, SH6 and SH7. The common carrier is assigned the loads for the other four shipments, incurring a cost of $1042. If the assignments had been reversed, DED, with shipments SH1 to SH4, would incur a cost of $796 for this trip and COMM, with shipments SH5 to SH7, would incur a cost of $1297 for a total of $2093.

Force assignment of a carrier The customer would ensure that shipment SH1 is serviced by the dedicated carrier. You can accomplish this by assigning an outbound carrier on the shipment record. Transportation Modeler provides fields for specifying outbound carriers, tariffs, services, and other assignments at the origin, or any of the three possible hubs.

1. Click Shipment table name on Control Center. The Shipment Detail table is displayed.

2. Filter to Shipment SH1.

3. Select OutboundCarrierOrigin and set the value to DED.

Solve the model with the carrier assignment and save the optimization log 1. Select the Home tab from the ribbon.







6. Review the new optimization log to determine the effect of forcing the carrier assignment.

In the new solution, the cost increased to $2093 while the distance is still 1372. This is because the trip with shipments SH1 to SH4 has now been assigned to carrier DED (at a cost of $796) and shipments SH5 to SH7 to carrier COMM (at a cost of $1297).

Expand the dedicated fleet The customer would eliminate the use of the common carrier. To do this, the dedicated fleet is expanded to have two types of trailers sourced out of the Fort Wayne domicile. The cost to use each equipment types is different. There is one each of these trailers available, while the fleet now has seven available tractors.

The equipment and rates per mile are as follows:

• DED-TLR24: $0.25

• DED-TLR48: $0.3

• DED-TTR: $1.0

Delete the common carrier You can delete the records for the carrier and equipment type that were set up for the common carrier.


2. Select COMM and click Delete.

3. Click Yes to confirm the deletion.

Delete the equipment type record 1. Click the Equipment Type table name on Control Center. The Equipment Type Detail table is

displayed.

2. Select COMM-TT and click Delete.

3. Click Yes to confirm the deletion.

Add the new equipment types for the dedicated fleet For this exercise, create one additional equipment type record and rename one of the existing records.



3. Enter DED-TLR48 in Name and click OK. The dialog box closes and the new entity is displayed.



Rename the existing equipment type record 1. Click the Equipment Type table name on Control Center. The Equipment Type Detail table is

displayed.

2. Change the DED-TLR equipment type to DED-TLR24.

Create the domicile records 1. Click the Domicile table name on Control Center. The Domicile Detail table is displayed.


3. Select:


• Carrier: DED

• EquipmentType: DED-TLR24, DED-TLR48 and DED-TTR

• Component: 1


5. Click Yes to verify creation of the new records. One new record is created (two already exist).

6. Select all records and click Execute.

7. Enter 1 for MaxResources for DED-TLR24 and DED-TLR48.

8. Enter 7 for MaxResources for DED-TTR.

9. Select Trailer as DomicileType for DED-TLR24.

Create the domicile vehicle availability records 1. Click the Domicile Vehicle Availability table name on Control Center. The Domicile Vehicle

Availability Detail table dialog box is displayed.


3. Select:


• Carrier: DED

• EquipmentType: DED-TLR24, DED-TLR48 and DED-TTR

• Component: 1


5. Click Yes to verify creation of the new records. One new record is created (two already exist).


7. Enter 1 for NumVehicles for DED-TLR24 and DED-TLR48.

8. Enter 7 for NumVehicles for DED-TTR.

Add the rates for the expanded dedicated fleet Modify the rating data directly in the rating database to create the equipment-specific charges. You can also delete the rating data for the common carrier.



Remove the common carrier data 1. Open the TariffConverter.mdb file.

2. Select Macros.

3. Select the Entity Manager macro and click Run. The Entity Manager dialog box is displayed.

4. Expand the Carriers node, select COMM, click and select Delete Carrier.

5. Click OK to confirm the deletion.

6. Expand the Equipment node, select COMM-TT, click and select Delete Equipment.


Update the equipment type for the dedicated carrier 1. Expand the Equipment node, select DED-TLR, click and select Delete Equipment.


3. Select the Equipment node, click and select Add Equipment.

4. Create or verify the following equipment code and category:

• DED-TTR: Tractor

• DED-TLR24: Trailer

• DED-TLR48: Trailer

Associate the equipment type to the service 1. Expand the Carriers node to the Services level.

2. Expand the DED_TL node. The TL service is displayed.



5. Select DED-TLR24 and click Add.

6. Repeat steps 4 and 5 to add DED-TLR48 to the service.

Create master charges for the equipment charges 1. Select the Master Charges node, click and select Add Master Charges.

2. Create the following master charges:

Charge code Equipment specific charge Equipment category

DED-TTR-CHG Yes Tractor

DED-TLR24-CHG Yes Trailer

DED-TLR48-CHG Yes Trailer

Update the charges for the tariff 1. Expand the DED Carriers node to see the Charges node.



2. Select the Distance-ALL charge and click Delete Charge.


4. Select the Charges node and click Add Charge.

5. Select:

• Charge Code: DED-TTR-CHG

• Charge Unit Type: Distance

• Lookup Unit Type: Distance

6. Click Add.

7. Repeat steps 4 to 6 to add the DED-TLR24-CHG and DED-TLR48-CHG charges. Ensure that Unit Type is set to Distance.

Update the rates for the tariff 1. Expand the DED Carriers nodes to see the Rates node.

2. Select *Rate and click Update / View Rate.

3. Select the Rates node under DED-TLR24-CHG, select the matching Equipment Code from the drop-down DED-TLR24, and click Add. A new rate is added to the charge.

4. Select the new rate (*FAK/DED-TLR24) in the Rates tree and click Add Range. The Add Range dialog box is displayed.

5. Enter .25 as Unit Rate and click Add.

6. Repeat steps 3 to 5 to associate the Equipment Code to the other two charges and create the Range for each:

• DED-TLR48-CHG: .3

• DED-TTR-CHG: 1


Solve the model with the expanded dedicated fleet 1. Select the Home tab from the ribbon.



4. Navigate to the folder where the optimization log is written. Based on the Solver Options you set in "Set solver option" (on page 40), the default path and filename is C:\jda\tmod\9.0\Reports\OptLog.txt.


6. Review the new optimization log to determine the effects of using the expanded dedicated fleet. Identify the combination of equipment used in the solution.

The solution now has two trips, with a cost of $1744 and a distance of 1372. The longer trip, with shipments SH1 to SH4, is assigned to the less expensive equipment type combination, DED-TTR plus DED-TLR24. The cost for this trip is $995 (796 * (1.00 + 0.25)). The shorter trip, with shipments SH5 to SH7, is assigned to the more expensive equipment type combination, DED-TTR plus DED-TLR48. The cost for this trip is $749 (576 * (1.00 + 0.30)).



Introduce a new domicile The customer is interested in evaluating the effect on the solution if the trailers are sourced from his domicile in New Haven, IN.

1. Click Location on Control Center. The Location Detail table is displayed.

2. Click New, enter New Haven for Name and click OK.

3. Enter the following values for the new domicile location:

• City: New Haven

• State: IN

• Country: USA

• PostalCode: 46815


5. Click Data Utilities in the Utilities group and click OK to load the data utilities.

6. In the New Haven Location records, select City Centroid for LatLon. The actual LatLon is displayed by Transportation Modeler.

7. Click Domicile table name on Control Center. The Domicile Detail table is displayed.


9. Select:

• LocationOrHub: New Haven

• Carrier: DED

• EquipmentType: DED-TLR24 and DED-TLR48

• Component: 1

10. Click New and confirm the creation of the new records.

11. Select the new records and set 1 for MaxResources and Trailer as the Domicile Type for both records.

Create the domicile vehicle availability records 1. Click the Domicile Vehicle Availability table name on Control Center. The Domicile Vehicle

Availability Detail table is displayed.


3. Select:

• LocationOrHub: New Haven

• Carrier: DED


• Component: 1






7. Enter 1 for NumVehicles for DED-TLR24 and DED-TLR48.

Delete the old domicile and domicile vehicle availability records 1. Click Domicile on Control Center. The Domicile Detail table is displayed.

2. Select the rows for the following:


• Carrier: DED


• Component: 1

3. Click Delete and confirm the deletion of the records.

4. Click Domicile Vehicle Availability on Control Center. The Domicile Vehicle Availability Detail table is displayed.

5. Select the rows fro the following:


• Carrier: DED


• Component: 1

6. Click Delete and confirm the deletion of the records.

Solve the model with the new haven domicile and save the optimization log 1. Select the Home tab from the ribbon.





6. Review the new optimization log to determine the effect of sourcing the trailers from the New Haven domicile.

The solution still has two trips and no unroutables. However, the distance has increased to 1404 and the cost to $1784, which is a result of the extra distance that the tractor must travel to pick up the trailer at New Haven before continuing to the first shipment origin.



Force the equipment type The customer would find out whether it is possible to service the shipment SH1 using the DED-TLR48 trailer. Within the Shipment table, specify the required tractor equipment type using OutbountTractorEquipmentType. You can specify the required trailer at the origin and at each of the three available hubs.

Force the equipment type assignment, do the following 1. Click Shipment on Control Center. The Shipment Detail table is displayed.

2. Filter to Shipment SH1.

3. Select OutboundTractorEquipmentType and set the value to DED-TTR.

4. Select OutboundEquipmentTypeOrigin and set the value to DED-TLR48.

Solve the model with the equipment type assignment and save the optimization log 1. Ensure that you update your strategy file as shown above and save the changes.






7. Review the new optimization log to determine the effect of forcing the trailer equipment for shipment SH1.

The scenario solves with two trips and the same distance as the previous case, 1404. The cost has increased to $1795 because the longer trip (with shipment SH1) is now forced to use the more expensive trailer.


Green modeling exercise

Chapter 39. Green modeling exercise This chapter provides ways in which you can model Transportation Modeler scenarios to evaluate the environmental impact of carrier selection and load creation during optimization. In order to evaluate the ’green’ impact of the scenario, you must:

• Create ‘green’ charges in the tariff model.

• Solve the scenario, generating output that respects the ‘green’ tariff model.

• Translate the output into reports that tabularize the carbon footprint information for analysis.

A description of the modeling problem and the basic data follows.

Model description For this scenario, the customer has the following shipments, each weighing 20,000 pounds:

• SH1: From Cleveland, OH to Detroit, MI

• SH2: From Cleveland, OH to Fort Wayne, IL

• SH3: From Pittsburgh, PA to Chicago, IN

• SH4: From Pittsburgh, PA to Roanoke, VA

• SH5: From Pittsburgh, PA to Roanoke, VA

A common carrier offers to transport the shipments within the US at $1.00/mile. The carrier can carry a maximum of 42,000 lbs per load.

According to the company’s latest corporate policy, to monitor the carbon footprint of all the transportation activities within the firm, the company wants to incorporate an additional $9.25 per 1000 ton-miles based on the standard rates of CO2 emission. A ton-mile is one ton of freight shipped one mile, when the System Unit of Measure is Imperial. For Metric units, the measure is in metric ton-kilometers.1

In the second part, you study what happens when the scenario uses a mix of common and dedicated fleet.

• You create a dedicated fleet comprising two straight trucks that operate out of a domicile at Pittsburgh.

• The dedicated carrier DED can be operated at $0.50/mile between any two locations in the US.

• The CO2 charge described for the common carrier also applies to the dedicated carrier.

• The dedicated carrier also carries a maximum load weight of 42,000 lbs.

In the third part, the customer keeps the common and dedicated carriers. However, the dedicated fleet is altered to comprise tractors and trailers instead of straight trucks. Two tractors are available at the domicile in Homestead, PA and the Pittsburgh domicile currently holds two trailers. The rates for operating the trailers and tractors are $0.20 and $0.30/mile.

Scenario data Create a new scenario and all required data for this exercise, including Locations and Shipments. In later parts of the study, add a carrier, equipment and domiciles.


Green modeling exercise

Parameter values Ensure that the maximum weight of the load is not violated.

Rates Create a new set of rates, including the ‘green’ charges.

Analysis overview 1. What is the output of the solve when the carbon footprint is tracked in the form of an additional

green charge? This charge has an ID of ‘CO2’. What is the CO2 charge associated with each load created by the optimization?

2. Generate the green reports for the costs associated with CO2. Do the costs associated with CO2 emissions differ in the two reports? If so, why?

3. When the dedicated fleet is added to the scenario in the second part of the study, what is the output of the solve with this mix of carriers?

4. Do you think that this new solution would be different if the CO2 charges were not levied along with the distance charges for the common and dedicated tariffs? Provide an explanation for your response.

Note: 1.Standard rate of CO2 emissions per Ton-Mile is taken as 0.0000925 Tons of CO2/Ton-Mile. As per various websites, the suggested "carbon tax" for a ton of CO2 varies widely from as little as $.10 per ton to as much as $150 per ton. Examples in this exercise use a cost of $100.00/ton. Therefore the calculated cost of CO2 emissions is $ 0.00925/Ton-Mile or $ 9.25 per 1000 Ton-Miles.

5. In the third part of the study, when the second domicile is added and you are considering tractors and trailers, what is the output of the optimization?

6. Select the most cost-effective and environment-friendly scenario of the three you have studied. Use the reports generated for the scenarios in the three parts of the study. Support your selection with appropriate reasons.

7. Finally, the customer wants to include a freight surcharge of 30% of the freight cost, and this surcharge to apply to only the per-mile charge and not the CO2 charge that has been modeled. Is it possible to incorporate this into Transportation Modeler? If so, what is the output of this optimization?


Create the rates for green report modeling

Chapter 40. Create the rates for green report modeling In this chapter, use the Access Rating Tool to model the rates required for the exercise described in "Green modeling exercise" (on page 179).

The TariffConverterExcelTemplate.xls file contains the fields you can populate in support of your modeling requirements. This file contains a set of worksheets (TL, LTL, SmallPackage, RateRange, Hubs, and Zones). The exercise requires you to enter relevant details in the TL worksheet.

Caution: Create a copy of the TariffConverterExcelTemplate.xls file and do not change the field names in it. Do not copy data from another worksheet to paste in the TariffConverterExcelTemplate.xls file. The cells in the template spreadsheet are defined with specific formats. Copying and pasting data can result in a change in data types and error during conversion to the Access database format.

On entering the rates in the Excel spreadsheet, use the TariffConverter.mdb, an Access-format database, to convert the rates into an Access-based rating engine. This database contains a set of rating tables into which the spreadsheet data is populated using an Access macro. You can then set up Transportation Modeler to use the Access database as its rating engine.

Create required tariffs In this section, create the tariff that is required to rate the shipments using the distance-based charge and the ‘green’ charge. For the distance-based charge, you can either set up the tariff, rate in the Access Rating Tool Excel spreadsheet, and convert the data, or create it directly in the TariffConverter.mdb. The following descriptions use the spreadsheet conversion method. Create the ‘green’ charge directly in the TariffConverter.mdb.

Create the truckload tariff Enter the required data in the Truckload (TL) worksheet in the TariffConverterExcelTemplate.xls spreadsheet. You do not need any data that was defined for previous exercises. If there is data in the spreadsheet, delete all existing records before creating the new data.



3. Delete all existing data from previous exercises.


Note: If no value is required, leave the field blank. The tool accepts the default value.

Field Description Value Carrier The identifier for the carrier. COMM-CARR

Service The name of the mode definition. You are defining a truckload tariff.

TL

Tariff The tariff for the tariff service. If you do not define a Tariff value, the conversion macro concatenates the Carrier value with the Service value to define the Tariff.




Field Description Value RateCode Specifies a RateCode for the Carrier, Tariff, Service or

Charge that exists in the database. This enables you to define new lanes that use this RateCode. You can define multiple rows (lanes) with the same RateCode. If you set the RateCode to *, the rating engine applies it to all lanes. If you leave the RateCode blank, the conversion macro in the Access database creates a unique RateCode for each lane.

DivisionCode Specifies the division for the tariff records.

UOMType The Unit of Measure Type. It should be set to Imperial units since the rates are based on miles and the weight constraints on pounds.

Imperial

DimWeightFactor

Defines the factor that the rating engine uses to calculate dimensional weight. It multiplies or divides the volume by the factor to find the dimensional weight. It is only used when Lookup Type is set to Weight. If you do not enter a value for this field, it defaults to 1. A value of 0 is not permitted.

UnitDivideFactor

The factor by which the ChargeType needs to be divided before determining the number of units and applying the PerUnit charge. Default is 1.

ChargeType Indicates the measure on which the charge is levied. If the ChargeType is Distance, the charge is levied per distance unit, such as mile.

Distance



• LookAhead

• LookBack

• Disabled

The default value if the field is not populated is disabled.

RateType Identifies the method in which the rate is applied. For example, you can apply a rate as a PerUnit (such as charging a rate per mile) or as a FlatCharge.

PerUnit



Field Description Value TeamDriver Determines whether team drivers are used. When team

drivers are used, DOT rules are not applied during scheduling.


MinChargeLocation

Defines if the MinCharge is at the Service level, Charge level, or Rate level.


Specifies the rate that is levied. 1

RateRangeID The RateRangeID value from the RateRange worksheet when using a rate range.

OriginZoneCode


OriginHubID Identifies the hub at which the lane originates. In this example, the lanes are state to state and no hub is required.

OriginPostalCode

Identifies the postal code at which the lane originates.


If specifying a postal code range for the origin, use the OriginPostalCode and this field to specify the range within which the lane originates.

OriginState Identifies the state in which the lane originates.

OriginCountry Identifies the country in which the lane originates. USA


DestHubID Identifies the hub at which the lane terminates. In this example, the lanes are state to state and no hub is required.

DestPostalCode Identifies the postal code at which the lane terminates.


If specifying a postal code range for the origin, use the DestPostalCode and this field to specify the range within which the lane terminates.

DestState Identifies the state in which the lane terminates.

DestCountry Identifies the country in which the lane terminates. USA

TransitTime Defines the delivery schedule time (number of transit days) required to complete the movement (schedule). If TransitTime is defined, a delivery schedule is created. If it is not defined or is 0, distance engine truck load scheduling is applied.


Determines whether the lane is modeled as a point to point lane or a round trip lane. In this case, you are modeling point to point tariffs. Empty miles are not rated, so the

PointToPoint



Field Description Value point to point tariff rates the loaded miles for the movement.


Determines if the carrier movement between the origin-destination pair is eligible for continuous moves (trips). Default is N. In this case, you are not modeling trips, so you can accept the default. Note: This field also accepts T (True) or F (False) and Y or N.

MinimumValue1

Specifies the minimum value, in units, specified by MinMaxValueType1, above which the tariff must be applied. Note: MinimumValue2, MinimumValue3, MinimumValue4, and MinimumValue5 fields are also available in the spreadsheet, but not used in this example.

MaximumValue1

Specifies the maximum value, in units, specified by MinMaxValueType1, for the movement. In this case, movements are limited to 40,000 pounds. Note: MaximumValue2, MaximumValue3, MaximumValue4, and MaximumValue5 fields are also available in the spreadsheet, but not used in this example.

MinMaxValueType1

Identifies the unit on which the MinimumValue1 and MaximumValue1 restrictions are applied. Note: MinMaxValueType2, MinMaxValueType3, MinMaxValueType4, and MinMaxValueType5 fields are also available in the spreadsheet, but not used in this example.

Other Comments


Use the process defined in "Converting the data to a rating database" (on page 28) to convert the Access Rating Tool spreadsheet into an Access database you can use as a rating engine.

Note: If you have other rating data defined in the TariffConverter.mdb file, you can enable the Delete Existing Data option. Otherwise, you may have unwanted tariffs in the rating engine.

Add the green charge to the rating database You need to create the ‘green’ charge that is used to monitor the carbon footprint of the transportation in this study. Predefined reports within the Access Rating Tool calculates CO2 emissions and costs for three greenhouse gas. To have these calculated in the reports, you must use the following specific charge IDs:

• CO2

• CH4

• N2O

Add the CO2 master charge 1. Open the TariffConverter.mdb file.

2. Select Macros.



3. Select Entity Manager and click Run. The Entity Manager dialog box is displayed.

4. Click the Master Charges node and select Add Master Charge. The Add Master Charge dialog box is displayed.

5. Enter CO2 as the Master Charge Code and click Add. The default values for the other fields apply.

Add the CO2 charge to the tariff 1. Click the Carrier node and expand. The Charges entry is displayed.

2. Click the Charges node and select Add Charge. The Add Charge dialog box is displayed.

3. Select CO2 for the Charge Code.

4. Select ExtendedWeightDistance for the Charge Unit Type. This unit type uses the ton-miles incurred.

5. Select ExtendedWeightDistance for the Lookup Unit Type.

6. Set the Unit Divide Factor to 1000. The charge is per 1000 ton-miles.

7. Select Yes for the Green Charge.

8. Click Add. The CO2 charge is added.

Note: The name in the Entity Manager is displayed in a green font to indicate that the Green Charge flag is set to Yes.

Add the CO2 rate 1. Click the Carrier node and expand until the Rates node is expanded.

2. Click rate code 1 and select Update/View Rate. The Update Rate dialog box is displayed.

3. In the Rates tree, expand the Charges node. The Rates entry is displayed under the CO2 charge.

4. Click the Rates node under CO2, and click b. A rate for *FAK is added to the Rates node.

5. Expand the Rates node, and click the *FAK node.

6. Click Add Range. The Add Range dialog box is displayed.

7. Enter 9.25 for the Unit Rate and click Add.

8. Click Close to exit the Add Rate dialog box.

9. Click OK to exit the Entity Manager, and close the database.


Create data for the green reporting scenario

Chapter 41. Create data for the green reporting scenario Create the location, shipment, carrier, equipment type, domicile and domicile vehicle availability records for this exercise.

Create locations The new scenario requires a set of six locations.

1. Select the File menu and click New to start a new scenario.


• Click Location on Control Center. The Location Detail table is displayed.



• Click New on the Detail table. The Create New dialog box is displayed.

• Right-click on the gray part of the Detail table and select Record > New from the shortcut menu.

4. Enter the record name in Name.

5. Name each location ID by the city name:

• Chicago

• Cleveland

• Detroit

• Fort Wayne

• Pittsburgh

• Roanoke

Add location data 1. Click Location on Control Center. The Detail table is displayed.

Alternately, right-click the table name on Control Center, and select the Detail table from the shortcut menu.

2. Enter information in the fields or select values from the drop-down lists. The following table shows the information you should enter for the location records:

LocationID City State Country Chicago Chicago IL USA

Cleveland Cleveland OH USA

Detroit Detroit MI USA

Fort Wayne Fort Wayne IN USA



LocationID City State Country Pittsburgh Pittsburgh PA USA

Roanoke Roanoke VA USA

Update LatLon and PostalCode 1. Select the Home tab from the ribbon.


3. Select the City - Lat/Lon Translator and/or Postal Code - Lat/Lon Translator checkboxes to indicate the data utility tables you want to load.

4. Click OK. The Progress dialog box is displayed, as Transportation Modeler loads each database. The data utility tables in the Status Bar are displayed on completion.

5. Click the Location table name on Control Center. The Location Detail table is displayed.

6. Select all rows.

7. Click Set on the Detail table. The Set Field Value dialog box is displayed.

8. Select LatLon.

9. Select City Centroid in To: and click Set. A message box indicating that six rows have been updated, is displayed.


11. Select PostalCode.

12. Select Closest by Lat/Lon in To: and click Set.

13. Click OK.

14. Click Close to close the Set dialog box.

Create shipments For this exercise, create five unique shipment records.

1. Click the Shipment table name on Control Center. The Shipment Detail table is displayed.


3. Enter the record name in Name. Each shipment requires a unique identifier. For the first shipment, enter SH1.

4. Click OK to close the dialog box. The new entity is displayed.

5. Repeat steps 2 to 4 to create the remaining four unique shipment IDs.

6. Set the weight to 20,000 for all shipments.

7. Enter the data for the shipments as shown in the following table:

Shipment ID Origin Destination SH1 Cleveland Detroit

SH2 Cleveland Fort Wayne

SH3 Pittsburgh Chicago



Shipment ID Origin Destination SH4 Pittsburgh Roanoke

SH5 Pittsburgh Roanoke

Update optimizer parameters In the initial study, the maximum load weight is 42,000 lbs. Allowing Transportation Modeler to ignore the ’last-in, first-out’ (LIFO) rule, when building loads, gives it more flexibility during optimization. Later, specific equipment costs for tractors and trailers are discussed. The UseTimeBasedRating parameter is enabled to ensure that trailer costs are included in the calculations.



3. Select the parameter file to edit. By default, the file is the one you set in the Solver Options dialog box.

4. Click Open. The parameter file is displayed in Parameter File Editor.

5. Ensure that the parameters are defined as follows:

• IgnoreLIFO: True

• MaxLoadWeight: 42,000

• MaxOutOfRoutePct: 50

• UseTimeBasedRating: True

Save scenario Having created all the location and shipment data required to solve the scenario, save the scenario to proceed.

1. Select the File menu and click Save As .

2. Enter a name for the scenario GreenScenario1.

3. Click Save.


Solve the green report scenario

Chapter 42. Solve the green report scenario In this chapter, you solve the scenario using a simple strategy file that includes the EnforceResourceConstraints constraint function and the OptResourceConstraints strategy function.

Strategy file for Green Report You can use the strategy file for green reporting as follows:

EnforceResourceConstraints ( TRUE TRUE 0 FALSE 0 )






2. Click Solve in the Scenario group. The warning message for the 5 Shipment records is displayed. The SolverValid field on the Shipment records indicates that the FreightClass is null. The FreightClass is not required.

Note: The Validation tab in the Options dialog controls whether or not specific conditions are considered warnings (message only) or errors (prevents optimization). You can change the Result by double-clicking on the Condition.

3. Click OK to dismiss the message. The model solves. The optimization log is automatically written.


5. Navigate to the folder where the optimization log is written. Based on the Solver Options set in "Set solver options" (on page 40), the default path and filename is C:\jda\tmod\9.0\Reports\OptLog.txt.


Plan should have 3 loads, with a cost of $1166 and a distance of 1022. You can review the charges that were applied to each of the 3 loads in the Charge Detail table.

Review the load charges Click Charge on the Control Center, to open the Charge Detail table.

Note: Each load has both a CO2 charge and a Distance charge. The CO2 charge is flagged as a GreenCharge. The number of units that are charged are the RatedAs value divided by 1000.

LoadOrTripID Tariff ChargeID ChargeUnit UnitRate NetCharge GreenCharge Load1 1 CO2 1297 9.25 12.00 Yes

Load2 1 CO2 8570 9.25 79.27 Yes

Load3 1 CO2 5700 9.25 52.73 Yes



Generate the Green Reports The Access Rating Tool has predefined reports that are used to analyze the greenhouse gas emissions and associated charges based on the green charges applied to the scenarios. The reports use scenario data that export from Transportation Modeler to the TariffConverter.mdb file and a set of InputParameters defined in the Access database to generate these reports. The process required:

• Export the scenario data from Transportation Modeler to the TariffConverter.mdb file by

selecting the Home tab in the ribbon and clicking Multi Scenario in the Access group. You export the Trip, Load, Stop and Charge tables.

• Edit the values in the InputParameters table in TariffConverter.mdb file.

• Use the Green Reports macro in the TariffConverter.mdb file to generate the report data.

• Run the report to see the greenhouse gas emission and cost data.

Export scenario data to the Access Rating Tool 1. Select the Home tab in the ribbon.

2. Click Multi Scenario in the Access group.

3. Navigate to the TariffConverter.mdb file, select the file and click Save. The Batch Export - Select Tables dialog box is displayed.

4. Enter a Scenario value, such as Green_Q3.

5. Click Deselect All to deselect the tables for export.

6. Select only the following tables:

• Trip

• Load

• Stop

• Charge

7. Click OK.

Set-up the green reports input parameters 1. Open the TariffConverter.mdb file.

2. Select Tables.

3. Double-click on InputParameters, to open the table. Use the default record for this exercise:

InputParameterID MPGRating CostPerTon 1 5.5 10

Generate the green report data 1. Open the TariffConverter.mdb file.

2. Select Macros.

3. Click Green Reports.



4. Select the:

• Scenario ID you exported: Green_Q1

• Input Parameter ID (the default): 1

5. Click Generate Report. The Access Rating Tool populates two tables with the green report data.

Display the Green Reports 1. Open the TariffConverter.mdb file.

2. Select Reports. There are two pre-defined reports:

• CO2Emissions: Provides a load-by-load summary of CO2 emissions.

• GHGCosting: Provides a load-by-load summary of costs incurred for charges that are defined for greenhouse gases (CO2, CH4, N2O)

3. Double-click on the report you want to view. The report is generated and displayed.

Evaluate addition of the dedicated fleet In this set of tasks, you evaluate the impact of adding a dedicated fleet with its own equipment resources.

Add the dedicated fleet For this exercise, you must create one carrier record.

Create the carrier record 1. Click Carrier table name on the Control Center, to open the Carrier detail table.

2. Click New on the Detail Table. Create New dialog box opens.

3. Enter DED-CARR in the Name field and click OK. The new entity is added.

Add the equipment type for the dedicated fleet For this exercise, you must create one additional equipment type record.

Create the equipment type record 1. Click Equipment Type table on the Control Center. The Equipment type detail table is displayed.

2. Click New on the Detail Table. Create New dialog box is displayed.

3. Enter DED-TT in the Name field and click OK. The new entity is added.

Create the domicile record 1. Click the Domicile table name on the Control Center.


3. Select:


• Carrier: DED-CARR



• EquipmentType: DED-TT

• Component: 1

4. Click New on the Detail Table.

5. Click Yes to verify the new record.


7. Enter 2 for the MaxResources value for the DED-TT record.

8. Select Straight Truck as the DomicileType for DED-TT.

Create the domicile vehicle availability record 1. Click the Domicile Vehicle Availability table name on the Control Center.


3. Select:



• EquipmentType: DED-TT

• Component: 1


5. Click Yes to verify the new record.


7. Enter 2 for the NumVehicles value for the DED-TT record.

Add the dedicated fleet rates The customer wants to include a dedicated fleet, DED-CARR. The carrier uses a straight truck equipment type called DED-TT. The dedicated fleet offers a rate of $0.50/mile between any two locations in the US. The CO2 charge also applies to this carrier and it has a maximum load weight limit of 42,000 lbs like the common carrier. The following are steps to add the dedicated fleet rate:

1. Open the TariffConverterExcelTemplate.xls spreadsheet and select the TL tab.

Add the rate as shown in the following table:


• Service: TL

• Tariff: blank

• Equipment: DED-TT

• DivisionCode: blank

• RateCode: blank

• UOMType: Imperial

• DimWeight Factor: blank

• UnitDivide Factor: blank



• ChargeType: Distance

• LookupType: blank

• LookAheadRule: blank

• RateType: PerUnit

• TeamDriver: blank

• MinCharge: blank

• MinCharge Location; blank

• PerUnitOr PercentOrFlat Charge: 0.50

• RateRangeID: blank

• OriginZoneCode: blank

• OriginHubID: blank

• OriginPostal Code: blank

• OriginPostal CodeEndRange: blank

• OriginState: blank

• OriginCountry: USA

• DestZoneCode: blank

• DestHubID: blank

• DestPostalCode: blank

• DestPostalCodeEndRange: blank

• DestState: blank

• DestCountry: USA

• TransitTime: blank

• PointToPointOr RoundTrip: RoundTrip

• EligibleFor Continuous Moves: Y

• MinimumValue1: blank

• MaximumValue1: blank

• MinMaxValue Type1: blank

• Other Comments: blank


3. Use the TariffConverter.mdb to convert the spreadsheet into the rating database as described in "Convert the data to a rating database" (on page 28). DO NOT select the "Delete Existing Data" option when converting the data. You want to keep the existing data that was defined for the COMM-CARR carrier.



Update the DED-TT equipment 1. Open the TariffConverter.mdb file.

2. Select Macros.

3. Click Entity Manager.

4. Click on the Equipment node.

5. Click on the DED-TT node and select Update/view Equipment. The Update Equipment dialog box opens.

6. Enter 42000 as the Max Load Weight and set the Equipment Category to Tractor/Trailer.

7. Click Update.

Add the CO2 Charge to the dedicated fleet tariff 1. Open the TariffConverter.mdb file.

2. Select Macros.


4. Click on the Carrier node and expand the DED-CARR node until you can view the Charges entry.

5. Click on the Charges node and select Add Charge. The Add Charge dialog box opens.

6. Select CO2 for the Charge Code.

7. Select ExtendedWeightDistance for the Charge Unit Type. This unit type uses the ton-miles incurred.

8. Select ExtendedWeightDistance for the Lookup Unit Type.

9. Set the Unit Divide Factor to 1000. The charge is going to be per 1000 ton-miles as described in the overview.

10. Select Yes for the Green Charge.

11. Click Add. The CO2 charge is added.

Note: The name in the Entity Manager is displayed in a green font to indicate that the Green Charge flag is set to Yes.

Add the CO2 Rate 1. Click on the Carrier node and expand the Rate node.

2. Click on the Rate Code and select Update/View Rate. The Update Rate dialog box is displayed.

3. In the Rates tree, expand the Charges node until the Rates entry under the CO2 charge is displayed.

4. Click Rates node under CO2, then click Add. A rate for *FAK is added to the Rates node.

5. Expand the Rates node, then click on the *FAK node.

6. Click Add Range to display the Add Range dialog box.

7. Enter 9.25 for the Unit Rate and click Add.

8. Click Close to exit the Add Rate dialog box, click OK to exit the Entity Manager, then close the database.



Solve the model with the dedicated fleet and save the optimization log 1. Select the Home tab from the ribbon.



4. Navigate to the folder where the optimization log is written. Based on the Solver Options set in "Set solver options" (on page 40), the default path and file name is C:\jda\tmod\9.0\Reports\OptLog.txt.



In this case, 3 loads are created with a cost of $1152 and a distance of 1602. Two of these loads are assigned to COMM-CARR and the third is assigned to DED-CARR.

Add the dedicated fleet scenario to the Green Reports Export this scenario to the TariffConverter.mdb file; include this in your green reporting analysis.

Export scenario data to the Access Rating Tool 1. Select the Home tab in the ribbon.


3. Navigate to the TariffConverter.mdb file, select the file and click Save. The Batch Export - Select Tables dialog box is displayed.




• Trip

• Load

• Stop

• Charge

7. Click OK.

Generate the Green Report data 1. Open the TariffConverter.mdb file.

2. Select Macros.

3. Click Green Reports to open the dialog box.

4. Select the:





5. Click Generate Report. The Access Rating Tool populates two tables with the green report data. This data is added to the existing scenario data.


2. Select Reports, the two pre-defined reports is displayed:



3. Double-click on the name of the report you want to view. The report is generated and displayed.

Evaluate the solution without the green charges In this section, you assess the solution when the green charges are not incurred to see what differences may occur.

Remove the green charges Note: Prior to editing the database, make a backup copy. You need to have the CO2 charges in place in a later part of the study.


2. Select Macros.

3. Click Entity Manager, the entity manager dialog box is displayed.

4. Under each of the carriers, expand the nodes until the Charges node is displayed.

5. Click on the CO2 charge and select Delete Charge. Confirm the deletion prompt is displayed.

6. Click OK. Ensure you delete the CO2 charge for COMM-CARR and DED-CARR.

Solve the model without the green charges and save the optimization log 1. Select the Home tab from the ribbon.






As in the previous case, two loads are assigned to COMM-CARR and one is assigned to DED-CARR. In this case, the cost is $991 and the distance is 1568. The loads for COMM-CARR have not changed, but there is a new route for the load for DED-CARR. In the original load, the route was:



• Pittsburgh (Domicile) to Pittsburgh (Pick SH3) to Cleveland (Pick SH2) to Fort Wayne (Drop SH2) to Chicago (Drop SH3) for a distance of 1187.1 miles and a cost of $593.55.

The new load route is:

• Pittsburgh (Domicile) to Pittsburgh (Pick SH3) to Cleveland (Pick SH2) to Chicago (Drop SH3) to Fort Wayne (Drop SH2) for a distance of 1152.9 miles and a cost of $576.45.

In the second route, the ton-miles incurred are higher based on SH2 traveling longer. Since we are not incurring the CO2 charge, Transportation Modeler can take the shorter route. When the CO2 charge is incurred, the distance is compromised for a leaner carbon footprint.

Expand the dedicated fleet The customer wants to update the dedicated fleet to use tractors and trailers instead of straight trucks. The original Pittsburgh domicile has 2 trailers, while another domicile at Homestead, PA has 2 tractors.

The equipment and rates are as follows:

• DED-TTR: $0.3

• DED-TLR: $0.2

Add the new equipment types for the dedicated fleet For this exercise, you have to create one additional equipment type record and rename one of the existing records. The following is the process to create the equipment type record:

1. Click Equipment Type table name on the Control Center. The Equipment Type Detail Table is displayed.


3. Enter DED-TTR in the Name field and click OK. The dialog box closes and the new entity is displayed.

Rename the existing equipment type record 1. Click Equipment Type table name on the Control Center. The Equipment Type Detail Table is

displayed.

2. Select the DED-TT equipment type and change the Name to DED-TLR.

Create the new location record 1. Click Location table name on the Control Center. The Location Detail Table is displayed.


3. Enter Homestead in the Name field and click OK.

4. Enter the following values for the new location:

• City: Homestead

• State: PA

• Country: USA

5. Load the Data Utilities, if not loaded.

6. Set the LatLon to City Centroid and PostalCode to Closest by LatLon.



Create the new domicile record 1. Click Domicile table name on the Control Center. The Domicile Detail Table is displayed.


3. Select:

• LocationOrHub: Homestead

• Carrier: DED

• EquipmentType: DED-TTR

• Component: 1


5. Click Yes to verify creation of the new record.

6. Select all records and click Execute. The original Pittsburgh record and the new record for the Homestead domicile is displayed.

7. For the Pittsburgh DED-TLR record, set the MaxResources to 2 and the DomicileType to Trailer.

8. For the Homestead DED-TTR record, set the MaxResources to 2 and the DomicileType to Tractor.

Create the Domicile Vehicle Availability records 1. Click Domicile Vehicle Availability table name on the Control Center. The Domicile Vehicle



3. Select:

• LocationOrHub: Homestead

• Carrier: DED

• EquipmentType: DED-TTR

• Component: 1


5. Click Yes to verify creation of the new records.


7. Enter 2 for the NumVehicles value for both records.

Add the rates for the expanded dedicated fleet The rating data is modified directly in the rating database in order to create the equipment-specific charges. You must use the version of the rating database that has the CO2 charges defined. You can also delete the rating data for the common carrier.

Update the equipment types for the dedicated carrier 1. Open the TariffConverter.mdb file.

2. Select Macros.

3. Click Entity Manager, the Entity Manager dialog box is displayed.



4. Expand the Equipment node, select DED-TT, click and select Delete Equipment. Confirm the deletion prompt is displayed.


6. Select the Equipment node, click and select Add Equipment.

7. Create or verify the following Equipment:

• DED-TTR: Tractor

• DED-TLR: Trailer

Associate the equipment types to the service 1. Expand the Carriers node to the Services level.

2. Expand the DED-CARR_TL node. The TL service is displayed.



5. Select DED-TTR and click Add.

6. Repeat steps 4 and 5 to add DED-TLR to the service.

Create Master Charges for the equipment charges 1. Select the Master Charges node, click and select Add Master Charges.

2. Create the following Master Charges:

Charge Code Equipment Specific Charge

Equipment Category

DED-TTR-CHG Yes Tractor

DED-TLR-CHG Yes Trailer

Update the Charges for the tariff 1. Expand the DED-CARR Carriers node until the Charges node is displayed.

2. Select the Distance charge and click Delete Charge.


4. Select the Charges node and click Add Charge.

5. Select:

• Charge Code: DED-TTR-CHG

• Charge Unit Type: Distance

• Lookup Unit Type: Distance

6. Click Add and repeat the steps 4 through 6 to add the DED-TLR-CHG charge. Be sure to set the Unit Type fields to Distance.

Update the Rates for the tariff 1. Expand the DED-CARR Carriers nodes until the Rates node is displayed.



2. Select the rate value and click Update / View Rate.

3. Select the Rates node under DED-TLR-CHG, select the matching Equipment Code from the drop-down DED-TLR, and then click Add. A new rate is added to the charge.

4. Select the new rate (*FAK/DED-TLR) in the Rates tree and click Add Range. The Add Range dialog box is displayed.

5. Enter 2 as the Unit Rate and click Add.

6. Repeat steps 3 through 5 to associate the Equipment Code to the DED-TTR-CHG and set the Unit Rate to .3


Solve the model with the expanded dedicated fleet 1. Select the Home tab from the ribbon.





6. Review the new optimization log to determine the effects of using the expanded dedicated fleet. Identify the combination of equipment used in the solution.

The solution now has 3 loads, with a cost of $1158 and a distance of 1614. This is a slight increase in cost compared to the earlier study (with the green charges enabled). It results from the use of the new domicile at Homestead.

Add the Trailer Domicile scenario to the Green Reports Export this scenario to the TariffConverter.mdb file; include this in your green reporting analysis.

Export scenario data to the Access Rating Tool 1. In Transportation Modeler, select the Home tab from the ribbon.


3. Navigate to the TariffConverter.mdb file, select the file and click Save. Select Tables dialog box from Batch Export.




• Trip

• Load

• Stop

• Charge



7. Click OK.

Generate the Green Report data 1. Open the TariffConverter.mdb file.

2. Select Macros.

3. Click Green Reports.

4. Select the following values:



5. Click Generate Report. The Access Rating Tool populates two tables with the green report data. This data is added to the existing scenario data.


2. Select Reports. The two pre-defined reports are displayed:



3. Double-click on the report to view. The report is generated and displayed.

Analysis of the three scenarios You exported data from the scenarios at three points:

• With the common carrier only

• With the common carrier and the dedicated fleet, using straight trucks (one domicile)

• With the common carrier and the dedicated fleet, using tractors and trailers sourced from separate domiciles.

Now, you can review the GHGCosting report and the CO2Emissions report to analyze the scenarios.

GHG Costing report In this report, GHGCosting, the CO2 Cost is the same for all three scenarios. This cost uses a calculation based on Extended Ton-Miles. Regardless of the carrier or equipment, the loaded distance remains the same across the scenarios; therefore, the CO2 cost remains the same. The additional distance incurred in the scenarios with the dedicated fleet was the result of domicile and return distances. To see the environmental impact of the added distance, you can review the CO2Emissions report.

CO2 Emissions report In this report, CO2Emissions, between the two scenarios that used the dedicated fleet (Green_Q3 and Green_Q5), Green_Q3 is better in both total cost ($1152 < $1158) and CO2 emissions cost ($32.33 < $32.56). Both Green_Q3 and Green_Q5 have a lower total cost than Green_Q1 ($1166).

Scenario Green_Q1 has the lowest CO2 emissions cost ($20.62).



When you combine these costs across the scenarios and compare for both total cost and emission cost, scenario Green_Q3 is the best:

Scenario Total Cost (Per Mile + Ton Mile)

CO2 Emissions Cost

Grand Total

Green_Q1 1166.00 20.62 1186.62

Green_Q3 1152.00 32.33 1184.33

Green_Q5 1158.00 32.56 1190.56

Add a freight surcharge The customer now wants to include a freight surcharge of 30% on the per-mile charge (not the CO2 charge). There are two ways to model this:

• As a Surcharge Percentage on the Charge records for the distance and equipment-specific charges,

• As a new Surcharge Master Charge, then adding it to each of the Tariff/Service/Lane list of charges.

Create the surcharge percentage The surcharge percentage is directly added to the charges in the TariffConverter.mdb file. The following are steps to add the surcharges:


2. Select Macros.


4. In the Carriers node, expand the COMM-CARR to the Charges node.

5. Click on Distance and select Update/View Charge.

6. Enter 30 for the Surcharge Percentage and click Update.

7. Repeat steps 4 through 6 for the two equipment-specific charges for carrier DED-CARR.

Solve the model with the surcharge percentage 1. Select the Home tab from the ribbon.




5. Rename OptLog.txt to PS10Log7a.txt.

The cost with this solution is $1462 and the distance is 1614. You can review the Charge Detail table to see the effect of the Surcharge Percentage. When you open this table, the charges with ChargeIDs of DISTANCE, DED-TTR-CHG and DED-TLR-CHG all have values in the SurchargeDiscount field. The NetCharge is calculated as the Charged plus the SurchargeDiscount value.



LoadOrTripI

D

Tariff ChargeID ChargeUnit

UnitRate

Charged Surcharge

Discount

NetCharge

Load1 1 CO2 1297 9.25 12.00 12.00

Load1 1 DISTANCE 129.7 1.00 129.70 38.91 168.61

Load2 2 CO2 8570 9.25 79.27 79.27

Load2 2 DED-TLR-CHG 1198.8 0.20 239.76 71.93 311.69

Load2 2 DED-TTR-CHG 1198.8 0.30 359.64 107.89 467.53

Load3 1 CO2 5700 9.25 52.73 52.73

Load3 1 DISTANCE 285 1.00 285.00 85.50 370.50

Create a master surcharge You can alternately create a Master Charge that represents the surcharge and add it to the charges for the specific tariffs. You need to revert to the previous version of the TariffConverter.mdb file, or you must remove the Surcharge Percentage value of 30 from the distance and equipment-specific charges.

Remove the surcharges Note: You must perform this step if you have not saved a previous version of the TariffConverter.mdb file.


2. Select Macros.


4. In the Carriers node, expand the COMM-CARR to the Charges node.

5. Cick on Distance and select Update/View Charge.

6. Remove the 30 in the Surcharge Percentage and click Update.

7. Repeat steps 4 through 6 for the two equipment-specific charges for carrier DED-CARR. For this carrier, you must update the DED-TTR-CHG and the DED-TLR-CHG.

Create the master surcharge 1. Open the TariffConverter.mdb file.

2. Select Macros.


4. Click on the Master Charges node, click and select Add Master Charge.

5. Enter Surcharge as the Master Charge Code and click Add.

6. Expand the COMM-CARR to the Charges node.

7. Click on Charges and select Add Charge.

8. Select Surcharge as the Charge Code.

9. Select FreightCosts for the Charge Unit Type and the Lookup Unit Type.

10. Set the Charge Sequence to 2 or higher and click Add. This forces the Surcharge to be calculated after the other charges.



You must exclude the CO2 charges from the FreightCosts used for the new Surcharge.

11. Click on the CO2 charge and click Update/View Charge.

12. Set the Include in Rating Units for Freight field to No, then click Update.

13. Click on the rate value under Rates and click Update/View Rate.

14. Click on Surcharge under Charges, then select Rates and click Add.

15. Click on *FAK under Rates and click Add Range.

16. Select Percentage as the Charge Type and enter 30 as a Unit Rate.

17. Repeat steps 6 through 15 for the charges for carrier DED-CARR.

Solve the model with the surcharge percentage 1. Select the Home tab from the ribbon.




5. Rename OptLog.txt to PS10Log7b.txt.

The cost with this solution is $1462 and the distance is 1614, as with the previous implementation of the surcharge. You can review the Charge Detail table to see the effect of the Surcharge master charge. When you open this table, you can see additional ChargeID of Surcharge. The ChargeUnit shows the FreightCosts being used to determine the surcharge. The NetCharge is the Surcharge UnitRate multiplied by the ChargeUnit.

LoadOrTripID Tariff ChargeID ChargeUnit UnitRate Charged Surcharge Discount

NetCharge

Load1 1 CO2 1297 9.25 12.00 12.00

Load1 1 DISTANCE 129.7 1.00 129.70 129.70

Load1 1 SURCHARGE 129.7 30 38.91 38.91

Load2 2 CO2 8570 9.25 79.27 79.27

Load2 2 DED-TLR-CHG 1198.8 0.20 239.76 239.76

Load2 2 DED-TTR-CHG 1198.8 0.30 359.64 359.64

Load2 2 SURCHARGE 599.4 30 179.82 179.82

Load3 1 CO2 5700 9.25 52.73 52.73

Load3 1 DISTANCE 285 1.00 285.00 285.00

Load3 1 SURCHARGE 285 30 85.50 85.50


Index A Access Rating Tool • 71, 81, 98, 112, 132, 156, 182

B continuous move;trips • 96 business hours • 141, 147, 148

C Carrier • 22, 110

constraints carrier • 134

carrier equipment availability (CEA) • 128 data utilities

data utilities data utilities

data utilities • 35

Cmove • 104, 105 commodities • 141 commodity codes • 151 Con • 50, 61, 64 ConSamePickAndDrop • 50, 61, 89 constraints • 130, 134, 136

carrier tariff service

lane;carrier;lane • 128

penalties penalties • 137

RoundTrip • 98 Control Center • 15

Customize the Favorites section • 15 CreatePlanStack • 90 cross dock charge • 77, 93, 103, 132 CZAR • 66, 75 CZAR Rating Directory • 75 CZARLITE • 66

D data

Set Adjust

Scale

modify

modify data using

modify data using • 37

data utilities • 80 postal code lat/lon;lat/lon • 69

requirements for Map View • 55 location translation tables location translation

translation utilities • 36

using in data view • 36

query view using in query view • 36

Microsoft Access Microsoft Access • 33

dock • 144, 147 Outbound Inbound • 145

dock report • 150 dock scheduling • 141 docks • 141 domicile • 108, 110, 111, 116, 117, 118, 119

constraints domicile resource • 138

driver on-duty times • 47 DriverMaxDriveTime • 48 DriverMaxOffDutyTimePerStop • 48 DriverOffDutyTime • 48 DriverOnDutyTime • 48

E EarliestDeliveryTime • 148 EarliestShipTime • 148 EnforceResourceConstraints • 136 entities

create new entities • 34, 38, 68, 70, 79, 96, 110, 111, 117, 118, 119, 125, 130, 131, 134, 138, 139, 140, 143, 144, 145, 147, 149, 150, 151, 152

modifying • 68 overview entities


descriptions • 33

equipment type • 110, 152 equipment types • 141 exiting

Parameter File Editor • 49

F FilterState • 105

H Hub • 22, 156, 182 HubAssignment • 77, 88, 89 hubs • 77, 79, 81

TL rates • 83, 86 multi-pick;multi-drop

splitting shipments • 92

I import

map zones data • 56

L LatestDeliveryTime • 148 LatestShipTime • 148 Less-than-Truckload (LTL) • 66, 71 Load Plan Explorer • 55 charges

green;green charges;CO2;CH4 • 185, 186 logs

specifying directory for • 41 LTL • 22, 66, 75, 156, 182

M Map View • 55

create Map View • 56

data utilities using

in Map View • 36

set display properties Map View • 57

legends • 59 location options hub options

Map View • 59

open existing • 58 set options Map View • 59

save Map View • 58

map zones define map zone

define map zones • 56

MaxLoadWeight • 48 MaxOutofRoutePct • 48, 120 MaxOutofRoutePercentage • 61 MaxRoutesPerLoad • 167 MergeSolvePlanStack • 90 multi-pick • 64

O solving • 54 OptLog.txt • 55 OptMove • 126 OptParameters file

about • 47 OptParameters.txt • 47 OptResourceConstraints • 136 OptTLLoads • 50, 61, 64 OverlapTolerances • 167

P parameter file

editing • 47, 48, 49 Parameter File Editor • 47 PC*Miler Road Map • 55 penalties • 130, 138, 140, 165 PenaltyMaxLoads • 130 PenaltyMinLoads • 130 PenaltyPerDayStartDelay • 130 PenaltyPerPerformancePoint • 130 PenaltyShipmentNotDelivered • 130, 137 PenaltyTransferHubEquipment • 130 PenaltyTransitMode • 130 PenaltyVendorSequencingViolation • 130 PenaltyWaitTimePerHour • 130 plan output • 55 PushToPlanStack • 90


Q Quick access toolbar • 13

customize keyboard shortcuts • 14 Keyboard shortcuts • 13

R RateRange • 22, 156, 182 Rates • 22 RateWare • 66 TariffConverter.mdb

converting • 28 rating engines

reload on optimization reload rating engines prior to • 41

reports specifying directory for • 41

ResequenceStops • 50, 61 ResourceConstraintSwitch • 167 Ribbon • 7

File menu • 7 Home tab • 8 Map tab • 12 View tab • 10

S scenarios

create new new scenario • 33, 79, 96, 110, 130, 134

Service • 22 shipment ID • 128 shipments

time windows • 148 SmallPackage • 22, 156, 182 Solver Options • 75 solver results • 62 SolverInclude • 111, 117 solving • 54

plan output • 55 BaselineStrat.opt

baseline • 49, 50 strategy file • 41, 49

default • 49 strategy file

editing • 51 strategy file

editing • 51

strategy file editing • 52

strategy file editing • 52

strategy file tuning tuning • 61

strategy file constraints enforcing in the strategy file • 136

strategy file enabling dock report • 150

Strategy File Editor • 49, 51 functions • 51 types of items • 51 using • 52

T tables

add data in data view data view

add to tables • 35, 39

LTL tariff LTL • 71

truckload tariff truckload;TL • 25 truckload • 27 truckload • 22

truckload tariff truckload • 156




Tariff • 22 tariff ID • 128

TFF_T table • 132 tariff service

constraints tariff service • 139

TariffConverter.mdb • 22, 71, 81, 156, 182 acceptable field values • 29

TariffConverterExcelTemplate.xls • 22, 28, 71, 81, 156, 182


TFF_T tariff ID table • 132

time windows • 147 TL • 22, 156, 182 backhaul • 94 continuous move • 104 TryDockScheduling • 150 TryResourceSwap • 167

U UseDocks • 141 IgnoreLIFO • 189

V validate

scenario validation • 54

W load weight

maximum for load • 47


transportation modeler 9.0.0.0 getting started guide

Documents

document jda

jda warranty

jda application

jda license agreement

jda software license

jda patents website

jda valuable trade secrets

technical documentation