1. Identify the Environments of Existing Systems, Including Web-Based Platforms or On-Premise Solutions

At the onset of the process to integrate a TMS, it is essential to identify the environments of existing systems. For example, a Windows IIS server or Lenox Apache server is necessary to enable the standard integration through Cerasis. Knowing the situations in operating systems of your current systems will streamline integration and ensure your software developer understands your needs.

2. Drill Down into the Details for Standard Versus Web Services Integration

Depending on the capabilities of your software vendor, you may be able to go through a standard implementation and integration process or a Web services process. It depends on whether your solution will reside within the cloud or leverage your on-premise capabilities and servers. At this point, it is essential to visit with your software vendor and thoroughly review the details and functionality of standard versus Web services integration.

3. Develop a Realistic Integration Timeline and Objective

Next, it is vital to think about the schedule for integration. While everyone is focused on the return on investment, focus on realistic goals. This will help ensure the TMS provides the maximum ROI within the shortest period. However, creating unrealistic goals will only serve to build hostility within your organization and could lead to a loss of shareholder support for integration.

4. Set Aside Appropriate Resources for Integration

Shippers should also set aside appropriate IT and labor resources to enable optimum integration. Although the software vendor knows how to integrate your platform, the experience and on-premise familiarity with your existing systems will make the IT team’s involvement invaluable. Furthermore, allocate plenty of resources to eliminate delays from an inability to complete tasks. This initial assembly of your team will also lay the groundwork for change management in order to get TMS adoption throughout the enterprise.

5. Follow the Steps Provided by the TMS Provider for Integration

Your TMS software vendor will also provide a list of steps and actions to take to complete integration. It is essential to follow these steps thoroughly, and if any issues arise, contact the TMS developer for clarification or advice.

6. Take Advantage of the Testing Environment

The testing environment is the area where the TMS developers and your internal IT staff will work together to put together new functions and ensure the TMS performs the appropriate calls to retrieve information from your other systems and execute functions based upon them. In other words, the testing environment is the preemptive phase of use of the TMS before your go-live date. It is crucial to take advantage of the testing environment fully.

7. Proceed with the Certification Process

After the integration is complete, shippers will also undergo a certification process, verifying that data called through the TMS is routed accordingly. This is essentially a final step of testing, and once it is complete, shippers will be given production access to the TMS.

8. Receive Your Production Access

Receiving their production access is the first real step in moving data from your existing systems and putting the TMS to use in your facility.

9. Train Your Team on How to Use the System Properly

Finally, any successful integration will also depend on your ability to build support for the new systems integration in your existing operations and train your team on how to use it appropriately.

10. Update Accordingly

Although initial integration may take place relatively fast compared to developing a TMS within your organization, it will be necessary to update the system according to manufacturer and developer specifications routinely. Fortunately, those leveraging Web services integration and cloud-based platforms do not have the added worry of downtime when the system updates.