The federal Surface Transportation Board on Dec. 30 issued a decision under which it is proposing to require the nation's Class I rail carriers to permanently report certain rail service metrics on a weekly basis.

The proposal would make permanent the STB's Oct. 8 order that Class I railroads and Class I railroads whose tracks transit or interchange traffic through Chicago are required to file weekly rail service reports on an interim basis containing specific performance data. Currently, the STB requires that the major rail carriers report, among other things, weekly average train speeds, weekly average terminal dwell times, weekly average cars online, the number of trains held short of destination or scheduled interchange points, and various loading metrics for grain, coal, automotive and other categories of service.

"The permanent collection of (rail service) performance data on a weekly basis would allow continuity of the current reporting and improve the (STB's) ability to identify and help resolve future regional or national service disruptions more quickly, should they occur," the agency said in its decision, adding that the weekly filings already being submitted have enabled the agency to begin developing baseline rail performance data. "Transparency also would benefit rail shippers and other stakeholders, by helping them to better plan operations and make informed decisions based on publicly available, near real-time data, and their own analysis of performance trends over time."

Both of these points had been made by the NGFA in testimony presented at an STB hearing in April 2014, as well as subsequently, as reasons for urging the STB to require reporting of rail service metrics by Class I railroads.

In its proposal, the STB sought input on several potential changes to the current data-reporting structure in what the agency said is an attempt to improve the relevance, value and utility of the information. Proposed changes on which the agency is seeking comment include the following:

  • Capturing average dwell time for "loaded" unit trains at origin "or interchange receipt," and clarify that such data is to be reported by the railroad receiving the loaded train at a shipper facility or interchange location.
  • Clarify that carriers are to report every instance during a reporting week in which specific types of loaded or empty trains are held at a location on the reporting railroad's system short of destination or scheduled interchange for longer than six consecutive hours. Similarly, the STB said it is intending to capture reports on average daily snapshots of cars in specific service that have not moved for 48 to 120 hours, and for greater than 120 hours.
  • Clarify that it is seeking average daily car "volume" at the key Chicago rail yards - meaning cars on hand, rather than cars processed.
  • Clarify the method for deriving trains held outside the Chicago gateway.
  • Adding a new request for quarterly listings of all rail project work-in-progress, major rail infrastructure projects (including project location by state), the planned completion date for each project, the percent to which the project is completed at the time of reporting, and a description of the project and its purpose. The STB proposal defines "work-in-progress" as projects on which ground-breaking has occurred, while "major rail infrastructure projects" refers to projects designed to expand or enhance capacity (excluding maintenance-of-way projects) that are budgeted to cost $25 million or more over the life of the project.

In addition, the STB said it is seeking comments on an appropriate measurement to capture performance data for grain unit train shipments.

Comments on the proposal are due March 2, with reply comments due April 29. The NGFA's Rail Shipper/Receiver Committee will be reviewing the STB proposal extensively to respond to the agencies inquiries on which data offer the most utility, and whether additional or revised reporting metrics are needed to assist shippers, receivers and the STB in better tracking rail service performance.

As chief operating officer, Randy Gordon is responsible for implementing the policies of the Board of Directors and for planning, coordinating and implementing the NGFA's programs, services and budget.

distributed by