Kargo Nexus TMS vs. Trimble Fleet Mobility

Appian is well suited for optimization of routes and contrary to what Appian claims, it is not well suited for scheduling.

• Appian is excellent for use in both the analysis arena and ongoing operations support. The speed to solution and quality of solution is at the top of the market.
• The configurability of the system gives the user the flexibility to address almost any route problem imaginable. Analysts have the ability to recreate the "world" to fit their customer's needs rather than forcing the customer into a predetermined framework.
• The installation of the software is flexible and can be structured to fit any work group's format, from a centralized core to a distributed mobile analysis team.

• Transit times are sometimes inaccurate/inconsistent.
• Software can slow down as a route file undergoes many changes.
• Large quantity of input files can sometimes create confusion/inconsistency when route files are shared by multiple users.

Many issues with the system and I will probably recommend other type of software if the question arises. Because of the investment my company has made, I will use the system for now.

Appian was best suited for an analysis environment both functionally and from a cost structure standpoint. Other packages are targeting ongoing operations and their cost structures reflect that goal. The purely analytical environment can underestimated in these situations. There is definitely a need for non operation specific analysis tools in the marketplace.

• Improved service to customers by being more aware of ETA's and how they relate to each store's receiving hours.
• Reduced transportation costs in dynamic environment where routes are optimized daily using Direct Route.
• Better customer service to field by generating e-mail notifications for following day's ETA's, along with notifications when trips are behind schedule.