{"id":197274,"date":"2025-04-08T17:00:12","date_gmt":"2025-04-08T07:00:12","guid":{"rendered":"https:\/\/www.railfreight.com\/?p=61378"},"modified":"2025-04-08T17:00:12","modified_gmt":"2025-04-08T07:00:12","slug":"intermodal-pro-15-years-of-tos-development","status":"publish","type":"post","link":"https:\/\/www.vibewire.com.au\/?p=197274","title":{"rendered":"Intermodal Pro: 15 years of TOS development"},"content":{"rendered":"

Tideworks Technology, a known name in the terminal operating system (TOS) market, recently marked its 25th anniversary in September 2024. While starting in the maritime sector, the company moved into the intermodal sector 15 years ago with its Intermodal Pro (IPro) solution. Tideworks now leverages this 15-year experience and expertise in intermodal operations to provide adaptable TOS solutions globally.<\/strong>
\n<\/span>Tideworks has implemented IPro in over 85 terminals globally, including North American Class I operations and major European sites like Freightliner UK. This gives the company experience in meeting different operational needs. RailFreight.com spoke with Mark Bromley, VP of client management at Tideworks, about Intermodal Pro’s development, standardisation challenges, new configurable tools, and the future of TOS technology in rail.<\/p>\n

\"\"
Mark Bromley. VP of client management at Tideworks. Image: \u00a9 Tideworks.<\/figcaption><\/figure>\n

RailFreight.com<\/strong>: Tideworks is 25 years old, and Intermodal Pro is 15. During this period, you have implemented the TOS in about 85 terminals. These terminals differ significantly in size and needs. How has Tideworks managed this, adapted the product, and what have you learned?<\/p>\n

Mark Bromley<\/strong>: That is correct. We recently celebrated our 25th anniversary, and Intermodal Pro is 15. Tideworks has evolved, adding rail to its existing marine services about 15 years ago. We see the biggest growth opportunities in the rail industry, so we continue to evolve and grow with the sector, aiming to lead in the terminal operating space.<\/p>\n

We have certainly seen many different terminal operations, ranging from North American Class I’s and European rail to inland intermodal hubs. This required working closely with clients to understand their specific needs. At the same time, we built a product we could demonstrate, showing its capabilities. Clients have adapted their business processes well to the TOS’s existing functions. Ultimately, success depends on effectively integrating people, processes, and technology.<\/p>\n

A clear plan is essential. It starts with the client’s vision for the TOS and goals, which allows us to align and work towards those objectives. Implementation always brings challenges. Our experience covers terminals moving from basic manual processes to complex semi-automated facilities requiring systems integration and thorough testing. Manual operations might allow more learning on the job. Having covered this full range, we believe we offer a complete solution for the rail market.<\/p>\n

\"\"
IPRO in action. Image: \u00a9 Tideworks.<\/figcaption><\/figure>\n

RailFreight.com:<\/strong> Regarding complete solutions, Intermodal Pro is used by three of the six US Class I railroads. What challenges arose working with these major railways, and what lessons have informed other projects?<\/p>\n

Mark Bromley<\/strong>: Yes, we work with three US Class I railroads. Our portfolio also includes large European operations like Freightliner UK, using our solution across over 20 terminals. This experience across continents provides valuable insights. A key challenge is standardising business processes. Clients often ask us about standard practices, looking to Tideworks for systems expertise and process knowledge. Achieving standardisation has been challenging but also a key success achieved with our clients.<\/p>\n

Also, the large scale and different types of operations within the Class 1s helped us develop many software features and options. Now, when clients present what seems like a unique case, we likely have already handled similar situations and have a solution.<\/p>\n

RailFreight.com<\/strong>: You mentioned new tools allowing customers to set their own business rules. What are these rules, and how do they affect terminal operations?<\/p>\n

Mark Bromley<\/strong>: Correct. This is a newer feature in Intermodal Pro. We expect it to give terminal operators more operational freedom. Previously, terminals needed Tideworks to build new features to change operational needs. Operations constantly change, and software development cannot always match the speed of specific business opportunities.<\/p>\n

The business rules engine gives control back to the customer. It offers more flexibility within the software to make decisions for their specific situation. Even within one company, terminals might operate differently. For example, in a ‘flip’ operation (moving a container between rail cars), one terminal might plan it to a specific yard area, while another plans it directly to a rail car. The system now lets users set these rules internally. This automates the process based on their settings and allows specific actions based on certain conditions.<\/p>\n

\"\"
IPRO in action. Image: \u00a9 Tideworks.<\/figcaption><\/figure>\n

RailFreight.com<\/strong>: Is flexibility the main thing customers want from a TOS, or are other factors more important?<\/p>\n

Mark Bromley<\/strong>: That is a good question; priorities likely vary by client. Flexibility is certainly a known feature of our TOS. Being in both the marine and rail sectors possibly offers more flexibility than rail-only TOS solutions. We can use features from marine terminals, especially as rail and marine operations sometimes merge. The business rules engine is a clear example of this flexibility.<\/p>\n

However, client feedback often highlights the system’s ease of use. It is seen as user-friendly for staff. The platform supports a wide range of terminals, from small sites to semi-automated ones, all within one TOS. This range of options allows customers to run different business models.<\/p>\n