Simplified Rail Rate Cases not Simple Enough
“We continue to pursue changes to the simplified guidelines that would achieve the dual statutory goals [established by Congress in 1995] of providing captive shippers meaningful access to regulatory remedies for rail rates that are unreasonable. . ..” said a decision by the Surface Transportation Board (STB Ex-Parte No. 656 Sub. No. 1).
After 10 years, no rate disputes were decided under the Simplified Guidelines. The STB proposed creating a simplified stand-alone cost (Simplified SAC) procedure to use in medium-size rate disputes. And objective of the Simplified SAC method is to restrain a railroad from exploiting market power over a captive shipper by charging more than it needs to earn a reasonable return on the replacement cost of the infrastructure used to serve that shipper. It would also detect and eliminate the costs of inefficiencies in a carrier’s investments or operations.
The Simplified SAC method is described in a Surface Transportation Board Decision dated July 28. It is available at http://www.stb.dot.gov/decisions/readingroom.nsf/WebDecisionID/37206?OpenDocument
Want to use this article? Click here for options!
© 2012 Penton Media Inc.
Advertisement
Feature Article
2012 Top 10 Predictions for the Supply Chain in 2012
2012 will see the consumer take a more prominent role in directing the course of supply chain management, as volatile demand has become the new norm.
More Feature Articles
- How Lift Truck Fleet Management Helped a 3PL Improve Service
- Commentary: Why Logistics and Politics Need to Mix — for the Economy’s Sake
- It Only Takes a Moment to Win - or Lose - a Customer
More Web Exclusive Features
More from the January Issue
MH&L Video Spotlight
Kuna Foodservice, a food distributor based in St. Louis, Mo., expanded to a 98,000 sq. ft. distribution center that includes a refrigerated receiving dock, freezer and storage area for paper and canned goods. Learn more.
Featured Suppliers
Advertisement
Advertisement
Advertisement
Advertisement








Acceptable Use Policy blog comments powered by Disqus