Oracle Transportation Management Cloud

What went well: - Availability of new functionalities every quarter - Fewer issues post quarterly updates (21A, 21C ) - Turn around time on Idea requests for new features in less than 9 months What did not go well: - Quarterly Release notes on updates/fixes and new functionality needs to be more elaborate...still struggling with clarity of features and necessary setups needed ( Suggestion would be to provide a simulation of the feature to understand the feature) - Quarterly Release bugs that are acknowledged should be immediately posted in the Release Content Notes to make all aware of the issue

I rate OTM as a great tool to manage transportation but if I consider it to manage end to end transportation solution then OTM struggles. OTM: For transportation - highly flexible to build it specific to an organizational needs Load builder - is bad and struggles ( SAP TMS is much better and SAP TMS provides integration with Handling unit seamlessly) Freight billing - It struggles to give specific requirements and lot of customization is needed to give a stable solution but still an issue ----->SAP TMS has better billing solution Dock Booking - It is bad and not give realistic solution, needs lot of customization Spot tendering - it is not user friendly and needs customisation Integration - Integration with SAP is not seemless and we need to spend huge time/money to integrate it and lot of money drains out into it So many times I feel SAP TMS is better and no effort is needed on integration , it is plug and play and more over One SAP solution

Oracle provides a top-notch TMS that fulfills nearly any requirement at nearly any level of volume. Cloud is a little more difficult to use than on-premises versions due to the security requirements and some of those elements have been hard to work around.

The implementation went fairly well. Our biggest issue was end user acceptance. After 14 months we are finally seeing our end users working better with the system.