Implementation Roadmap

The TMS Implementation RoadMap is a series of tangible deliverables that will define the implementation and rollout requirements associated with the deployment of a TMS. It establishes a clear picture of the Total Cost of Deployment (TCD) for the project by identifying all resource requirements and levels of commitment (schedule and budget) from all parties involved in order to deploy the TMS solution.

The TMS Implementation RoadMap allows you to:

  • Monitor, manage and plan the execution required to ensure the project’s success.
  • Leverage a methodology and documentation that will drive the deployment of a successful project.
  • Understand the resource requirements for executing a successful startup.
  • Defines the project organizational structure and the lines of communication.
  • Sets realistic expectations.
  • Provides individual accountability and facilitates solid scheduling.

Differences between Successful TMS Implementations and those that fail:

  • Understanding resource requirements from all involved parties
  • Understanding the operational constraints of the TMS business owners involved in the implementation
  • NO standard implementation methodology and approach
  • Inability to effectively deploy the use of a project plan
  • Lack of Project Manager capability
  • Inability to implement business process change efficiently
  • Focused on solving 100% of the business process issues
  • NO executive sponsorship from the VP of Transportation or Supply Chain – who ‘owns’ the project?
  • Poor deployment strategy – implement baseline processes and roll-out more advanced functionality once stabilized
  • Poor communication or lack of involvement by cross-functional areas directly impacted by the TMS implementation (i.e. Customer Service, Warehouse Operations, Purchasing, Finance)
  • NO clear understanding of the TMS project goals and objectives – service, cost metrics
  • Shortcutting user acceptance testing (UAT)
  • Lack of go-live support from the TMS vendor
  • Lack of proper transition from the implementation to customer support teams

Practices