PC*MILER v39 vs. v36 Upgrade & Comparison Report

Prepared for: IT Department / Fleet Operations Group

Document Version: 1.0

Focus: Core Routing Logic and Map Database Expansion

Executive Summary

Upgrading from PC*MILER v36 to PC*MILER v39 introduces significant structural advancements designed for modern fleet management, commercial vehicle routing, and mileage calculation. Key advancements include strict polygonal site boundary (gate-path) routing, localized 53-foot trailer state exemption logic and years of cumulative map data updates including tens of thousands of newly geofenced commercial locations.

1. Core Routing Logic & Algorithm Enhancements

The routing engine in v39 handles street networks and commercial restrictions with far greater rigidity and precision than v36. Below are the primary algorithmic changes:

Site Boundary & Gate Path Routing: One of the largest structural changes since v36 is the shift from standard point-to-point (lat/long or street address) routing to polygonal site boundaries. Version 39 maps the actual perimeter of distribution centers, truck stops, manufacturing facilities, and intermodal yards. Crucially, it routes trucks specifically through designated truck entry and exit gates rather than a generic front-office address, eliminating dangerous last-mile turns or routing down restricted delivery alleys.
53-Foot Trailer State-Specific Exemptions: In v36, selecting a 53-foot twin-trailer profile heavily restricted routes to the National Network (NN), occasionally resulting in highly inefficient, circuitous paths. Version 39 incorporates updated state-by-state legal exemptions, allowing the routing engine to utilize state-approved non-NN roads where 53-foot trailers are legally allowed, yielding more realistic miles and highly accurate ETA calculations.
Strict Preference Enforcement: In older versions like v36, user preferences regarding elevation limits, time-based closures, and hazmat warnings were heavily weighted as "influences" but could occasionally be bypassed by the engine if the detour was mathematically extreme. In v39, these configurations act as hard road closures within the routing logic. If a road is restricted for a chosen profile, the engine will strictly route around it.
Hazmat Tunnel & Weight Restrictions: Version 39 includes fully updated data regarding municipal tunnel designations (including updated categories for hazardous materials) and localized weight restrictions on state-maintained secondary highways.

2. Database Expansion & Map Data Updates

Running an older version like v36 means missing multiple years of continuous infrastructure changes, toll restructures, and commercial data curation. Version 39 delivers an expanded database:

Commercial Site Geofencing: Over 43,000+ new commercial sites—including major distribution hubs, retail centers, intermodal facilities, and fueling stations—have been fully coded and geofenced with distinct gate access points.
Highway Infrastructure: Thousands of miles of newly constructed highway lanes, bypasses, and adjusted exit ramps across North America have been fully integrated into the base network.
Turn Restrictions: Massive expansion of truck-specific turn restrictions in dense urban centers to prevent dangerous or illegal U-turns and tight radius maneuvers.
Comprehensive Toll Restructuring: Complete updates to electronic tolling discount programs (e.g., E-ZPass adjustments) and structural congestion pricing implementations, including localized adjustments for mid-Atlantic and northeastern corridors.