Partners who integrate PC*MILER with a Transportation Management System (TMS) or other application may need to make software or configuration changes in order to continue calculating routes for trucks with 53-foot trailers in PC*MILER 38. 


In previous versions, PC*MILER generated 53-foot routes in the U.S. when National Network routing was selected in the route settings or the pcmserve.ini configuration file. In PC*MILER 38, which is expected to be released in June 2024, specific vehicle dimensions will need to be set in order for PC*MILER to calculate 53-foot routes.


This change is necessary because PC*MILER 38 will include enhancements that generate more direct (and sometimes shorter) routes for 53-foot trailers. The routing algorithm will take into account the state-by-state exceptions to the requirement that 53-foot trailers be routed along the U.S. National Network. However, to do this, PC*MILER needs the vehicle dimensions because different states have different rules based on either the width or the trailer length of the truck.


In this article:


History of this change

The 53-foot routing enhancement was first introduced in PC*MILER 37 in June 2023. Currently:

  • Vehicle dimensions need to be set to take advantage of this enhancement.
  • The National Network routing setting can still be used alone to generate traditional 53-foot routes, without the newly added state exceptions.


In PC*MILER 38, vehicle dimensions must be set to take advantage of this enhancement. However: 

  • The National Network routing setting alone will not consistently generate 53-foot routes.
  • If vehicle dimensions are not set to a 53-foot trailer, PC*MILER 38 will generate routes for 48-foot trailers, which is the default setting. As a result, you may see mismatches in mileage compared with the same trucking lanes in previous PC*MILER versions.


What you need to do

No change is required if your application already allows users to select specific vehicle dimensions that are passed into PC*MILER. However, users should be encouraged to double-check those settings prior to calculating a 53-foot route.


Changes are necessary if your application only allows users to select National Network routing, and not specific vehicle dimensions. The required changes depend on the platform you use to integrate PC*MILER. Below are our recommendations for each platform.


PC*MILER Connect Windows DLL

PC*MILER Connect is a locally installed DLL that a client application, such as a TMS, uses to retrieve PC*MILER distances, driving times, state-by-state mileage breakdowns, and detailed driving instructions. Below are the options for updating your Connect integration.



Option 1

(No software changes are required. Configuration settings may need to be changed.)


The PCMSERVE.INI file sets default trip options so that these options are active each time you use PC*MILER Connect. In PC*MILER 38, a new setting will be available that allows you to set a default Vehicle Routing Profile. A profile is a collection of vehicle dimensions and other settings that ensure the routing algorithm knows the type of vehicle being driven. PC*MILER includes preset profiles for the most common types of commercial vehicles in North America.


For 53-foot trailers, the correct preset profile is named Heavy Duty Semitrailer. In the .ini file, the profile is set using a new configuration setting, RoutingProfileName, under the [Defaults] heading.


[Defaults]
RoutingProfileName=Heavy Duty Semitrailer


Option 2

(Software changes to your application are likely required.)


While it will likely require software changes, a preferred option is to give your TMS users the ability to directly select a Vehicle Routing Profile. Profiles are passed when building a route by calling the PCMSSetRoutingProfileName API prior to running a trip. The 53-foot profile is called Heavy Duty Semitrailer. In the Connect API call, it looks like this:


PCMSSetRoutingProfileName(TripID, Heavy Duty Semitrailer)


Option 3

(Software changes to your application are likely required.)


A final option is to give users the option to directly set four vehicle dimensions: Length (which should represent Trailer Length), Width, Height, and Weight. Dimensions are set in PC*MILER Connect by calling the PCMSSetVehicleConfig function prior to running a trip. To set a 53-foot trailer, the Connect API call would be: 

PCMSSetVehicleConfig(TripID, 0, 0, 162, 102, 53, 80000, 5, 0)


PC*MILER Web Services 

PC*MILER Web Services include a range of web-based APIs used  to retrieve PC*MILER distances, driving times, state-by-state mileage breakdowns, and detailed driving instructions.


Option 1

(Software changes to your application are likely required.)


The preferred method to set vehicle dimensions is to give your TMS users the option to select a Vehicle Routing Profile. Profiles are passed in route report requests using the profileName parameter. PC*MILER provides preset Routing Profiles for a wide variety of commercial vehicle types. 


The 53-foot profile is called Heavy Duty Semitrailer. In the POST body of a request, it looks like this:

"profileName": "Heavy Duty Semitrailer",


Option 2

(Software changes to your application are likely required.)


Alternatively, users can be given the option to directly set four vehicle dimensions: Length (which should represent Trailer Length), Width, Height, and Weight.  Dimensions are passed in route report requests using a TruckCfg object.


In the POST body of a routing request, a TruckCfg for a 53-foot truck looks like this: 


},
     "TruckCfg": {
       "Axles": 5,
       "Height": "162",
       "LCV": false,
       "Length": "636",
       "MaxWeightPerAxleGroup": 34000,
       "TireCount": 8,
       "Units": 0,
       "Weight": "80000",
       "Width": "96"
     },