IBM i Trucking and Logistics Software Buyer's Guide

AS400 trucking software still ships, and the vendors have names

If you went looking for AS400 trucking software expecting a dead category, the answer is no. It is a live market with named products and named owners, and the first useful thing a buyer can do is learn who owns what now.

Trimble sells TL2000, carrier dispatch and operations software built on the IBM System i. TMW Systems developed it over roughly two decades before Trimble acquired the business. TMW also bought Innovative Computing Corporation in December 2009, picking up around 300 IBM i customers and the Innovative Enterprise Software line that Access Plus came out of. Trimble has offered subscription versions of Innovative Access, Access Plus and TL2000, so this is not a category where the only commercial shape is a perpetual license signed in 1998.

Varsity Logistics builds ShipSoft Parcel and ShipSoft Freight and describes ShipSoft as built for the IBM i, covering parcel, LTL, truckload and rail rating with add-on modules for rate shopping, pick and pack, containerization, tracking and audit. AR Traffic Consultants sells a freight rating, routing, bid analysis, bill of lading, claims and audit suite on IBM i that integrates with BPCS, MAPICS-XA, PRMS and ERP-LX.

That is the honest starting point. Not one product. Not zero products. A short list of specific products with real installed bases and real acquisition histories you should ask about directly, because acquisition history is what determines whether the release you are being shown is still the one the vendor invests in.

Dispatch and TMS: map what the box actually owns

Before evaluating anything, write down which system owns each transaction: order entry, load tender acceptance, driver and equipment assignment, rating, dispatch, status updates, settlement, driver pay and customer billing. At a lot of IBM i carriers one green screen application owns most of that list, and nobody has drawn the picture in fifteen years.

That map matters because vendors sell against it. A cloud TMS demo that looks better than your 5250 screens is comparing a front end to a system of record, and those are different purchases. TL2000 already has a web edition built on Profound Logic's Profound UI, which put configurable screens, mouse support, dashboards and mapping visualization over the same IBM i application. If the complaint from the dispatch floor is the interface, the interface is a solvable problem that does not require touching the rating engine underneath it.

What you are actually deciding is whether the business logic stays on the box. Answer that first and most of the shortlist writes itself.

• Which system creates the load, and which one accepts or rejects a customer tender
• Where rating happens, and how much of it is still hand keyed or held in a spreadsheet
• Which system pays the driver and which one bills the customer
• What happens to dispatch if the link to an off-platform vendor drops for four hours on a Friday

Fleet maintenance is a separate decision until someone proves otherwise

Trimble's TMT Fleet Maintenance covers work orders, technician time, preventive maintenance, parts inventory and a maintenance cost dashboard, with optional modules for road calls, shop floor scheduling, warranty recovery and tire tracking. It has IBM i lineage. IT Jungle covered a TMT Fleet Maintenance edition for IBM i alongside TL2000 when both received web front ends, and Trimble has listed asset maintenance modules for its SQL and IBM i platforms as subscription offerings.

What Trimble's current fleet maintenance product page says today is cloud. It does not mention IBM i at all. That is not proof the IBM i edition is gone, and it is not proof it is current either. Ask the vendor which deployment they are selling and supporting for new customers at your fleet size, get the answer in writing, and do it before that assumption ends up load-bearing in a project plan.

Underneath the product question is a structural one. Is maintenance the same system as dispatch, or a second system that shares data? Both arrangements are common in this category, and evaluating an integration claim is impossible until you know which one you actually have.

Multi-carrier rating and shipping is where the gap usually is

In most IBM i transportation shops the dispatch system is fine and the shipping side is where things quietly break. Rates get keyed by hand. One carrier gets used because that is who the shipping clerk knows. Nobody rate shops on a Tuesday because there is no time.

This is the gap ShipSoft was built for. Varsity Logistics splits it into ShipSoft Parcel for small package shipping, which handles carrier selection, pricing optimization and labeling compliance on IBM i Power systems, and ShipSoft Freight, a multi-modal rating engine for LTL, truckload and rail across North America. The add-on modules read like a list of the things people do manually: ShipSelect for carrier rate shopping, ShipPack for pick and pack, ShipOptimizer for automated containerization, FreightPlan for LTL and full truckload load planning and consolidation, ShipTalk for shipment tracking, SpeedWeigh for automated weighing, and Transdata for shipping analytics.

AR Traffic covers overlapping ground from a different angle, with CALCRATE for freight rating, CALCROUTE for routing optimization and CALCPAK for parcel. The useful evaluation question is not whether a product supports multi-carrier rating in the abstract. It is which specific carriers, which modes, and who maintains the rate tables when a carrier reissues a tariff.

• Name the exact carriers and modes in scope, then make each vendor confirm coverage carrier by carrier
• Ask who updates rate tables and tariffs, how often, and whether that is included or billed
• Confirm whether accessorial charges, fuel surcharges and dimensional weight are rated or estimated

Freight audit is the module that either pays for itself or does not

Freight audit is the least glamorous line on a transportation software quote and often the only one with a payback you can measure. Carriers and shippers overpay quietly: duplicate invoices, wrong accessorials, rates that do not match the contract, shipments billed at a class nobody agreed to.

Both of the shipping-side vendors in this category sell into that problem. Varsity offers ShipAudit and FreightAudit for parcel and LTL invoice auditing. AR Traffic sells CALCBAN as an LTL bid analyzer and CALCBID for truckload, alongside CALCCLAIM for claims and CALCTRAK for shipment tracking.

If you are trying to get a transportation project funded and the dispatch modernization case is soft, this is usually the piece with a number attached. Pull six months of freight invoices, sample them against contracted rates by hand, and take the variance to the meeting. That evidence tends to move a budget conversation faster than a modernization argument does, and it also tells you honestly whether an audit module is worth buying at your volume.

EDI with shippers and brokers is a transportation problem, not a generic one

General EDI software and transportation EDI are not the same evaluation. Shippers and brokers send a specific, well-defined set of documents, and a platform that handles retail purchase orders beautifully may have never processed a load tender.

The transaction sets that matter here are the transportation ones: the 204 motor carrier load tender, the 990 response to that tender, the 214 shipment status message that keeps a shipper's visibility screen current, and the 210 freight invoice, with 997 functional acknowledgements underneath the whole exchange. If your customers grade you on a scorecard, the 214 is usually where the grade comes from, and late or missing status messages cost freight even when every truck ran on time.

The practical question for an IBM i shop is where translation happens and who owns it. On-platform translation keeps the exchange close to the dispatch data that generates it. Off-platform or managed translation moves the operational burden to someone else and adds a hop. Neither is automatically right. What sinks projects is nobody owning partner change requests, so a broker updates a spec and the tenders stop arriving with no alert until a customer calls.

Native IBM i, cloud or hybrid, and the ERP that quietly decides it

The deployment argument usually gets framed as modern versus legacy, which is the least useful framing available. The real constraint is the ERP already on the box.

If order, inventory and invoice transactions live in BPCS, MAPICS-XA, PRMS or ERP-LX, the shortlist narrows quickly to products that have integrated with those systems before. AR Traffic states that integration explicitly and positions itself as an Infor solution partner. Varsity describes ShipSoft as integrating with legacy, ERP and order entry systems on IBM i Power. Those claims are checkable, and they should be checked against named reference accounts running the same ERP and a similar IBM i release, not against a slide.

Hybrid is the shape most of these buyers land on, and it is a legitimate answer rather than a compromise. Dispatch and rating stay native because that is where the correct logic lives and the risk of moving it is real. Rate shopping, document capture, driver mobile workflows and analytics go somewhere newer because those are additive and can fail without stopping a truck. Decide which side of that line each capability sits on before a vendor decides it for you.

If the driver behind the whole question is that the system is old rather than that it is wrong, be honest about that in the room. A migration undertaken for its own sake carries real operational risk against a payoff nobody has written down.

Staffing risk, AI, and the questions to ask before the shortlist

The largest risk in this category is not the software. It is that the people who understand the rating logic are retiring, and the documentation is the code.

This is where AI has an honest use today, and it is a narrower one than the marketing suggests. Code explanation tools such as IBM Bob can read undocumented RPG and CL and describe what a rating routine actually does, which is worth more at the start of a project than any feature comparison. On the operations side, the capability that has verifiably shipped in this space is automated document extraction: Carrier Logistics added an AI bill of lading extraction module to FACTS, its freight management system for asset-based LTL carriers, which reads a scanned bill of lading and creates or updates the shipment automatically. Carrier Logistics does not publish the platform lineage of FACTS, so treat that as an adjacent example of what the category is shipping rather than as an IBM i product claim. What has not broadly shipped is AI dispatch or AI route optimization inside these IBM i products. If a vendor claims either, ask to watch it run against your own data.

The questions below are the ones worth asking before a shortlist exists, not after.

• Which release are you selling and supporting for new customers today, and on which deployment?
• Name three reference accounts running our ERP, our IBM i release and our fleet size
• Which carriers and modes are rated natively, and who maintains the rate tables?
• Is fleet maintenance the same system as dispatch, or a separate product sharing data?
• Which transportation EDI transaction sets are supported, and who owns partner change requests?
• What does a rollback look like if we cut over and dispatch does not work on Monday morning?
• Show any AI capability running against a real document or a real load, not a prepared demo

Go deeper on this topic

• AI for trucking companies on IBM i What is shipping into transportation on IBM i versus what is still a demo.
• Trucking and Logistics Preferred Partners How to scope dispatch and rating risk before committing to a partner.
• AS400 Trucking, TMS and Logistics Software The category page, with the product landscape and the questions buyers ask most.

Sources

• IT Jungle: TMW Unveils New Web Version of IBM i-Based TL2000 Trucking App
• IT Jungle: TMW Systems Buys Innovative Computing, Including 300 i OS Customers
• Heavy Duty Trucking: Trimble Takes Fleet Management Solutions to the Cloud
• Trimble: TMT Fleet Maintenance
• Varsity Logistics: ShipSoft Parcel and ShipSoft Freight
• AR Traffic Consultants: Logistics Software
• PR Newswire: Carrier Logistics Unveils AI-Powered Tool to Streamline LTL Operations