Transportation Modeler 9.0.0.0 Release Notes

Release Notes 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 http://jda.com/JDAPatents. 1303a

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. Installation and upgrade ..................................................................................................... 1

Installation notes ...................................................................................................................................... 1

Chapter 2. Enhancements .................................................................................................................... 2

Chapter 3. Resolved issues ................................................................................................................... 8

Chapter 4. Information alerts ............................................................................................................. 10

Installation and upgrade

Chapter 1. Installation and upgrade This chapter provides version-specific installation notes for JDA Transportation Modeler 9.0.0.0. Review these notes in addition to the JDA Transportation Modeler Installation/Administration Guide.

Installation notes Transportation Modeler 9.0 provides a full installation of the product. For complete information about the full installation of Transportation Modeler, refer to the JDA Transportation Modeler Installation/Administration Guide. Transportation Modeler 9.0 requires the Microsoft Visual C++ 2012 redistributable package ATL security update. This software is installed as part of the Transportation Modeler 9.0 installation.

JDA Transportation Modeler Release Notes 1 ©1995-2015 JDA Software Group, Inc. Confidential

Enhancements

Chapter 2. Enhancements This chapter describes new features introduced in Transportation Modeler 9.0.

Dynamic shipment splitting Dynamic shipment splitting has been enhanced in Transportation Modeler 9.0. When this feature is enabled, the optimizer may split shipments into two or more parts to improve load efficiency or make un-routable shipments routable. Shipment splitting allows configuration of the smallest shippable unit; for example, a container with three pieces cannot be split into four parts.

In previous releases, the terms shipment splitting and hub splitting were both used to refer to the insertion of one or more hubs into a shipment itinerary, thereby splitting the shipment into multiple legs. With this release, the term shipment splitting refers to the process of splitting a larger shipment into multiple smaller shipments, each of which may then be executed separately. The process of inserting one or more hubs into a shipment itinerary is referred to as hub splitting.

Shipment splitting can now be constrained by settings at the shipment, shipment component, location, and optimization parameter levels. The method of splitting can be defined in the Shipment Detail Table and Shipment Component Detail Table. Possible methods include splitting by pieces, pallets, units, weight or volume, and containers. If a shipment designates that splitting should be done by containers, each shipment component may further designate its own method of splitting.

Shipment splitting rules can be defined at the location and optimization parameter levels. At the location level, controls have been introduced in the Location Detail Table and Location Split Rule Detail Table to limit the number of times a shipment may be split, the minimum pick and delivery windows it must have, and its minimum dimensions. MaxShipmentSplitTimes, MinShipmentSplitSize, MinShipmentSplitSizeBasis, and MinShipmentSplitWindowLength are the optimization parameters introduced to define shipment splitting rules at the optimization parameter level. See the JDA Transportation Modeler Strategies and Parameters Guide and the JDA Transportation Modeler User Guide for more information.

Skeleton routes Transportation Modeler 9.0 extends the capability to fill prebuilt loads based on skeleton routes. Intermediate stops may now be identified as pick/drop stops. When empty stops exist on a load, Transportation Modeler internally creates dummy shipments to make the load valid. Dummy shipments now support default dimensions. They affect routing and rating only as long as there is no actual shipment with the same itinerary on the load. Dummy shipments do not affect the details of the load returned, and are not displayed as output by Transportation Modeler.

Four new optimization parameters, DummyShipmentWeight, DummyShipmentVolume, DummyShipmentPieces, and DummyShipmentSkids, have been introduced to define default quantities for dummy shipments. These parameters can be used to model the expected shipment dimensions such that routing and rating approximate the final route and cost better once actual shipments replace the dummy shipments. Additionally, the cost calculated for the dummy shipments incentivizes the optimization to replace the dummy shipments with actual shipments.

Skeleton routes have been enhanced with additional controls for scheduling, stop insertion, and stop reordering. Skeleton routes are defined using Pick/Drop Input and Load Input records. A new property of the Load Input record, MustStartOnEarliestDepartureDay, can be used to fix a specific starting day for a prebuilt load. Service windows can be defined on each Pick/Drop Input record. Each Pick/Drop Input record can additionally define the default handling time, the commodity of the

JDA Transportation Modeler Release Notes 2 © 1995-2015 JDA Software Group, Inc. – Confidential

Enhancements

shipments which can be picked or dropped at the stop, restrictions on the number of stops that can be inserted before or after the Pick/Drop Input stop, and restrictions on how far an inserted stop may be from the stop. A new flag on the Pick/Drop Input record, CanBeReordered, determines whether the relative order of the Pick/Drop Input stop may be changed.

The optimization has been improved to identify eligible shipments to fill prebuilt loads earlier in the process. Optimization decisions are based on reduced cost and better resource utilization. A new strategy, SetConsolidateToNonFreeLoadsOnly, has been added to allow portions of a strategy file to focus on filling prebuilt loads, including skeleton loads.

See the JDA Transportation Modeler User Guide for more information.

Shipment priority Transportation Modeler 9.0 has been enhanced with additional support for shipment priority. Based on their priority, the optimization can prioritize shipments during consolidation, resource assignment, dock usage, throughput usage, and a number of solver strategies.

A new parameter, PriorityCalculationMethod, has been introduced to determine the priority of a load based on its constituent shipments. The following are the accepted values for PriorityCalculationMethod:

• 0: The load’s priority is the lowest numeric priority of all shipments on the load.

• 1: The load’s priority is the highest numeric priority of all shipments on the load. This is the default value.

• 2: The priorities of the shipments on the load are prorated by the weight of the shipments to arrive at the priority for the load.

• 3: The priorities of the shipments on the load are prorated by the volume of the shipments to arrive at the priority for the load. For shipments with a volume of 0, a volume of 1 is used instead.

Loading type exclusions for docks Transportation Modeler now supports the definition of loading types that cannot be managed at a dock. The loading type exclusions can be defined in the Dock at Facility Loading Type Detail Table. When determining the eligible docks for a stop, the loading type of each container handled at the stop is determined. A dock will not be eligible for a stop if one or more of the loading types determined are excluded from the dock. This restriction enables proper dock scheduling for loading types which require specific handling features or personnel.

Equipment capacity degradation and non-3D containers Capacity degradation can now be modeled in the rating engine when using Transportation Manager or ART rating. Transportation Modeler 9.0 will read the information from the rating model in addition to reading records specified in the scenario file.

Transportation Modeler 9.0 supports the identification of shipment components as either 3D or non-3D. A non-3D shipment component is a container which should not be considered during load configuration. Additionally, equipment types can indicate whether they can be used to transport non-3D containers. An equipment type with a LC type of None cannot be used to move a load that has any 3D containers. A new Opt Parameter, AllowMixedLCAndNonLCLoads, determines whether 3D containers and non-3D containers can be consolidated onto the same load.


Enhancements

When capacity degradation records are defined with min/max product types or min/max loading types, a new optimization parameter, Exclude3DItemsFromLoadingPctConstraint, controls whether 3D containers are included when determining the number of products and loading types. It also controls whether 3D containers are included when determining the accumulated loading percentage of the equipment.

When load configuration is enabled and a load being verified has both 3D and non-3D containers, the 3D containers will be loaded into a reduced portion of the equipment. The portion of the equipment available for the 3D containers will be reduced by the percentage of the equipment used by non-3D containers. If equipment capacity degradation is defined, the portion of the equipment used by non-3D containers will be adjusted based upon the degradation percentage.

Product modeling enhancements Variable handling time can be overridden on dock, hub, and location records. Handling time for pick or drop locations can be specified for product types and loading types. Dock, hub, and location records can specify a HandlingTimeID. The HandlingTimeID references one or more Handling Time Product Loading records. If a handling time product loading record matches the product types or loading types at a stop, variable handling time calculations will use the matching record’s handling rates.

When specifying package level information, origin and destination zone details can also be specified along with origin and destination locations. When the optimization applies packaging for a shipment component, the rating engine will be queried to find all matching zones for the shipment origin and shipment destination. The matching origin and destination zones will be used to identify product loading factors. Product loading factors may also specify min and max transit times and min distance. If a load’s transit time is less than the min transit time, or greater than the max transit time, the product loading factor does not apply. If the load’s traveled distance is less than the min distance, the product loading factor does not apply.

Additionally, support for a new shipment dimension, Units, has been added. Units represent the number of packages at the highest packaging level used. For example, consider a container of 500 pieces shipped using 8 pallets of 60 pieces and 20 loose pieces. The Units of the loading detail with information about the 8 pallets would be 8, and the Units of the loading detail with information about the 20 loose pieces would be 20. Units can be used in defining shipment splitting rules, variable handling times, and when calculating load efficiency.

Loading and unloading duration As an enhancement to the loading and unloading time computation, two new optional attributes, loading type and product type, have been added to the existing shipment attribute of variable loading and unloading factor definitions. For a given shipment attribute, if there are multiple eligible variable rates for different combinations of loading type and product type, then the one with the highest priority is applied. The order of priority is as follows:

• Product type and loading type are both defined

• Only loading type is defined

• Only product type is defined

• Neither product type nor loading type are defined

When stops have multiple loading types and product types, the total variable time will be equal to the sum of the computed variable times for each loading type and product type combination.


Enhancements

Additionally, if a stop has variable time, a buffer percentage can be defined to adjust variable time before the total stop loading or unloading time is determined. Loading and unloading buffers may be defined to increase the variable time by a certain percentage, based on the number of product types loaded or unloaded at the stop. A new opt parameter, ApplyBufferTimeToDockOnly, controls whether buffer time is included only when computing variable times for locations with docks or whether buffer time will also be included when computing variable times for locations without docks, and for locations with docks when the load route does not require dock scheduling.

Note: In Transportation Modeler 9.0, Units has been added as a dimension of shipment containers and loads. Units represent the packaging of pieces to various package levels. In addition to the existing dimensions, Units can also be used when defining variable loading and unloading rates.

Loading/Unloading Duration has also been introduced as a location throughput group unit type. Location and dock throughput can be defined in terms of the amount of handling time available. The computed loading or unloading duration for a stop or dock commitment will be used to compute the available remaining throughput capacity. A new opt parameter, ApplyBufferTimeToThroughputConstraints, controls whether or not the optimizer includes the applicable buffer time when calculating consumption amounts for Loading/Unloading Duration.

For more information on this enhancement, refer to the JDA Transportation Modeler User Guide and the JDA Transportation Modeler Strategies and Parameters Guide.

Axle balancing improvements Axle balancing in Transportation Modeler 9.0 has been enhanced to support default equipment compartments and to avoid loading patterns that are not allowed. Axle balancing was introduced in Transportation Modeler 8.2 using the Equipment Axle and Trailer Compartment override files. Axle balancing applies when UseAxleBalancing is true in the optimization parameters and load configuration is active. In TMod 9.0, equipment axle information can be read from Transportation Manager and ART rating models. Both rating models support an unlimited number of axles for each equipment type. When trailer compartments are not defined for an equipment type, the entire equipment is assumed to be a single compartment.

Two new parameters, AxleBalancingAllowStaggeredLoading and AxleBalancingMaxFrontGap, can be used to prevent extra space or loading patterns which are not symmetric at the front of the equipment.

For more information, see the JDA Transportation Modeler Strategies and Parameters Guide.

External rating server prefetch and caching In Transportation Modeler 9.0, a cache file can be defined for JDA External Rating Server; cached rates are saved to the file at the defined Cache Save Frequency. The cached rates are based on origin zip code, destination zip code, weight break, and freight class.

The cache file is read each time the application starts. When a call is made for a zip code/weight break/freight class combination for which the rate is already cached, JDA External Rating Server applies the rate without a call to SMC3® RateWare Server or SMC3® RateWareXL.

Note: Your contract with SMC3® must allow for caching of RateWare rates in order to use this functionality.

Additionally, you can now create prefetch definitions to configure a set of calls that can be run in a batch. The server will make calls based on the postal combinations, freight classes, and weight breaks that you define. The rates can then be cached for use at a later time. The prefetch definitions can also be saved and loaded at a later time. By configuring prefetch definitions that cover the majority of your


Enhancements

expected LTL rate needs, optimization performance can be significantly improved by avoiding longer duration calls to RatewareXL.

For more information, see the JDA Transportation Modeler Installation/Administration Guide.

Enum filtering In Transportation Modeler 9.0, grid filtering has been enhanced to support the filtering of enumerated (Enum) fields, which have a limited set of valid values. A list of all possible values for the field is displayed when you click the filter cell of an Enum field column. You can select the check boxes corresponding to one or more of the listed values to define the filter criteria for the column. By default, all values are selected. For more information on this enhancement, see the JDA Transportation Modeler User Guide.

Strategy improvements The following strategies have modified parameters in Transportation Modeler 9.0:

• HubMove: The new boolean parameter, Hub Pair Move, allows HubMove to consider moving two hubs at the same time for a load to improve solution quality.

• OptResourceConstraints: The Try Resource Swap parameter supports a new value, 3. When it is set to 3, only resource swaps are tried; resource moves will not be tried.

• TryDockScheduling: The Try OptResource parameter supports a new value, 2. When it is set to 2, OptResourceConstraints is called with a Try Resource Swap value of 3.

• OptCapacityPlanning: The Try OptResource parameter supports a new value, 2. When it is set to 2, OptResourceConstraints is called with a Try Resource Swap value of 3.

The following strategies are new in Transportation Modeler 9.0:

• SetConsolidateToNonFreeLoadsOnly: Determines whether consolidation should consider only non-Free loads. When this strategy is True, Free loads are not considered for consolidation until this strategy is set to False. This strategy can be used to prioritize consolidation to skeleton loads, prebuilt loads, or other replanned loads. Additionally, if new loads have been set to Picked, Packed, or Locked by the SetLoadStatus strategy, these loads will also be considered.

• SetShipmentSortOrder: Allows control of how shipments are sorted in subsequent strategies. Multiple sort orders can be defined. Sort criteria can be based on shipment windows, shipment dimensions, various priority and criticality values, and distance calculations.

• FilterShipmentPriority: Filters loads whose shipment priority is within a defined range.

Scheduling enhancements In addition to various scheduling improvements and fixes, two new scheduling parameters have been added in Transportation Modeler 9.0. UnLoadingInsideDeliveryWindow controls whether all unloading must occur within a shipment’s delivery window. Previously, it was necessary for only the start of unloading to occur during the delivery window. Now, when this parameter is set to True, unloading must be completed within the window. AllowIllegalWaitTimeBeforeBreak has been added to preserve backward compatibility. Previously, extremely restrictive DriverMaxBreakTime and long WaitTime resulted in the scheduling of illegal wait time before a break. This will no longer occur, unless AllowIllegalWaitTimeBeforeBreak is set to True.


Enhancements

The EnforceVehiclesAtAllTimes parameter has been deprecated in this release. As of this version, vehicles will always be assigned and vehicle windows will always be considered during scheduling. Scheduling will enforce vehicle start and end times for routes which use domiciles with vehicle availability definitions. Reuse of vehicles, and consideration of vehicle start by time is still handled by the TryDockScheduling and OptCapacityPlanning algorithms.


Resolved issues

Chapter 3. Resolved issues This chapter describes issues that have been resolved in this release of Transportation Modeler.

Note: JDA is improving its communication of resolved issues. This section now includes customer reported issues as well as non-customer reported issues. This change provides a better understanding of all improvements made within each product release.

Case ID (Defect ID) Resolved issue

00409689 Issue: Optimizer Request failures. Solution: Fixed a solver crash during stop insertion.

00388339 Issue: Equipment Priority is not considered correctly. Solution: Fixed an issue where Trailer priority was not being considered.

00386607 Issue: WriteDistanceMatrix issue when TM and TP have Distinct Distance and Time By Direction. Solution: Fixed an issue in WriteDistanceMatrix() when distance/time is direction specific.

00382823 Issue: Large negative costs on optimization. Solution: Fixed a cost reporting issue during optimization.

00369242 Issue: Tariffs - Effective/Expiry Date is used improperly. Solution: Use the tariff effective/expiration dates to limit scheduling start time.

00368809 Issue: OPT requests taking along time in OptResourceConstraints & TDS strategies. Solution: Performance improvement in OptResourceConstraints().

00337481 Issue: Error during rating due to Wait Time. Solution: Fixed a scheduling issue when a load is forced to break at the first stop.

00329757 Issue: ltl multi class is not working. Solution: Fixed an issue with the wrong lookup weight being used for MFC calls with RatewareXL.

00317657 Issue: Equipment priority is not considered by optimizer when rating load. Solution: Fixed an issue with equipment priority was not being considered correctly.

00304786 Issue: Issue with vehicle assignments. Solution: Fixed an issue where vehicle assignments were changed post solve.

00415010 (TMOD-1943)

Issue: Distance engine returned an invalid distance when the customer has country specific DOT rules defined for the country 'CHN'. Solution: When the breakdown is unavailable or the distance engine does not support breakdowns, Transportation Modeler will use the origin country DOT rules.


Resolved issues

Case ID (Defect ID) Resolved issue

00409247 (TMOD-1939)

Issue: Costing related issue on specific rate lanes in few scenarios. Solution: Fixed an issue with the caching mechanism where the cache was returning the wrong lane for some zip code combinations.

00390715 (TMOD-1910)

Issue: There is an inconsistency with min transit time on domicile to origin. With PC Miler "shortest", TMOD does not respect the min transit time of 15 minutes on the journey between domicile and co-located DC. Solution: Added support for min transit time when using the PC Miler distance engine.

00390633 (TMOD-1907)

Issue: ART - Entity Manager does not show any information. Solution: Added a fix in the ART mdb to handle tables with more than 65,535 records.

00385703 (TMOD-1890)

Issue: Issue with MaxDistanceFromHub parameter in Reship. Solution: Fixed an issue with PenaltyTransferHubEquipment when EnforceResourceConstraint parameter is used.

00382823 (TMOD-1886)

Issue: Large negative costs are displayed in optimization. Solution: Fixed an issue with penalty calculated due to PenaltyLateDelivery.

00362075 (TMOD-1870)

Issue: Start / End Dates in Model results are not populated to Load, Stop, and Pick/Drop tables. Solution: Fixed an issue in populating dates in TMod from optimization results.

Issue: User is getting out of memory error when solving the scenario. Solution: Fixed an issue in handling 'Product Inventory at Facility' records. There was an issue if a record is included, but there is no shipment in the optimization with the facility location as an origin or destination.


Information alerts

Chapter 4. Information alerts This chapter provides alert information for this release of Transportation Modeler.

Case ID (Defect ID) Issue

(TMOD-1841) Issue: Not able to re-launch the TMOD application when PCM Road Maps are opened in TMOD. Workaround: Open Windows Task Master and kill the Transport Modeler process. Restart Transport Modeler.


Documents

Transportation Modeler 9.0.0.0 Release Notes