Messaging Service is the central hub that moves millions of inbound and outbound transactions daily between railroads and their global trading partners, and through Railinc applications such as Umler®, RailSight™, Interline Settlement System®, Forward and Store, and the Damaged and Defective Car Tracking system.

Railinc also interconnects with other leading North American Value Added Networks (VANs) to help ensure the exchange of messages with virtually any trading partner’s network services.

In addition to message exchange, Messaging Service provides a messaging console along with integration services, including translation and implementation. For additional information contact the Railinc Customer Success Center (CSC) at 877-RAILINC (877-724-5462) or send an email directly to csc@railinc.com.

Railinc Messaging Console

The Railinc Messaging Console (RMC) enables customers to view messages sent and received through Railinc, retrieve information about message routing configurations and usage patterns, and look up information about trading partners.

Translation Services

Translations are provided in a seamless process, sending and receiving data in formats native to customer systems including XML, ERP, CSV, EDI documents and versions, and TRAIN messages.

Scroll down to access detailed technical information about Railinc's communication protocols, message formats, and connectivity options.

Messaging Implementation Services

There are two levels of implementation services:

Standard Onboarding is for customers with the technical expertise and staff to coordinate testing and confirmation directly with their trading partners.

Enhanced Coordination and Test is for customers who require more than standard onboarding. Railinc will define a message implementation project plan, which can include the following additional services:

  • connectivity and security requirements verification
  • coordination and scheduling of testing with trading partners
  • coordination and scheduling of go-live events with trading partners
More On This Page:
Railinc Messaging Console (RMC) Demos

These demos provide quick overviews on how to perform the following procedures in the Railinc Messaging Console (RMC) application.

Click on the videos below to open and click the box in the bottom right to expand the video to full screen. Be sure to turn on/up your speakers to hear the demos.

Technical Information

Railinc's business is data, specifically data associated with the railroad industry. The source of the vast majority of this data is messages, millions of them - in fact over 5 million per day - sent by trading partners as well as internal applications. The railroad industry is dependent on messages being delivered and received on time. Messages are delivered using a variety of communication protocols, message formats, and connectivity options.

Communication Protocols

Communication protocols define how customers connect to Railinc. Customers can use any of the following:

  • FTP; FTPS; s/FTP – File Transfer Protocol (FTP) is a standard network protocol used to transfer computer files from one host to another host over a TCP-based network. FTPS and s/FTP provide additional security and/or speed. Railinc provides FTP services, which enable customers to perform file transfers.  Many short line railroads, car owners, and shippers use this protocol.

  • HTTP; HTTPS – Hypertext Transfer Protocol (HTTP) is the foundation of data communication for the World Wide Web.

  • SMTP – Simple Mail Transfer Protocol (SMTP) is an Internet standard for electronic mail (email) transmission.

  • TCP/IP – Transmission Control Protocol and the Internet Protocol (TCP/IP) is the computer networking model and set of communications protocols used on the Internet and similar computer networks.

  • IBM MQ Series – IBM MQ provides assured one-time delivery of messages across a wide variety of platforms. The product emphasizes reliability and robustness of message traffic, and ensures that a message should never be lost if MQ is appropriately configured. This protocol is widely used by Class I railroads and customs agencies.

Message Formats

Railinc switches and translates a wide variety of message formats, including the following:

  • CLM – Car Location Message (CLM) is a specialized type of EDI message that is used by the railroad industry to track the movements of railcars.

  • TRAIN II – The TRAIN II System provides a wide variety of information of North American rail equipment as reported by over 460 railroads. TRAIN II is a subset of EDI X12.

  • EDI X12 – EDI X12 (Electronic Data Interchange) is a data format based on ASC X12 standards. It is used to exchange specific data between two or more trading partners.

  • EDIFACT – United Nations/Electronic Data Interchange For Administration, Commerce and Transport (UN/EDIFACT) is the international EDI standard developed under the United Nations. The EDIFACT standard provides a set of syntax rules to structure data, an interactive exchange protocol (I-EDI), and standard messages that allow multi-country and multi-industry exchange. This format is widely used by customs agencies.

  • Flat File – A plain text file usually containing one record per line such as a comma separated values (CSV) file. Shippers may communicate with Railinc using this simple format.

  • XML – Extensible Markup Language (XML) is a markup language that defines a set of rules for encoding documents in a format that is both human-readable and machine-readable. It is commonly used for the interchange of data over the Internet and it is widely used for the representation of arbitrary data structures such as those used in web services. This format is widely used by many rail industry leaders.

  • iDoc – Intermediate Document (iDoc), is an SAP document format for business transaction data transfers.

  • ERP – Enterprise Resource Planning (ERP) is business management software—typically a suite of integrated applications—that a company can use to collect, store, manage and interpret data from many business activities.

Connectivity Options

Customers can connect to the Railinc network through any of the following modes:

  • FTP Mailbox – Uses the Internet protocol.

  • VPN (Virtual Private Network) – Uses router communication.

  • Frame relay-ISDN (Integrated Services Digital Network) – Uses dedicated telephone lines.

  • MPLS (Multi-Protocol Label Switching) – Uses a high-performance telecommunications network.

  • Web Services – Uses application-to-application connectivity.