Strategic Railroading

Three years ago in this blog I introduced a category of postings referred to as the “Teddy Bears” (TBs), as listed on the right side of the home page. Simply stated, TBs are convenient, but ill-justified, statements and beliefs that too many traditionalists in the industry (whether they be regulators, railroaders, or suppliers) fatuously cling to justify their perspective of railroad operations as to safety and/or efficiency. Unfortunately, these TBs are also restricting the opportunities to improve operations via the deployment of advancing technologies and associated business processes. Why these traditionalists do so, whether knowingly or not, is very likely due to the following:
1. They truly don’t consider the bottom line of railroading by not providing cost-effect technology strategies aligned with a strategic business plans;
2. Railroads relies on technicians instead of Technologists who can make a business case in sync with a technology strategy; and
3. Railroads’ upper management is focused on short-term goals to maximize their annual bonuses; and
4. There is little to no business strategy as to the advancement of operations across the railroads as an industry.

The TBs that I have covered so far include the following:
• No Time For Strategy (November 2010);
• CAD Delivers Traffic Management (October 2010);
• Train Dispatching is Too Difficult for That Math Stuff (August 2010);
• Digital Authorities are Vital (July, 2010);
• PTC is Vital (June 2010);
• Operating a Railroad Safely Requires Signaling (June 2010);
• There’s Nothing Vital in Dark Territory (May 2010);
• PTC Delivers Business Benefits (May 2010);
• We Run a Scheduled Railroad (May 2010).

There are other TBs that have yet to be covered in this blog including:
• Real time data is the Real Thing for structuring technology solutions;
• The lack of reliable interchange by other railroads is a real problem for our railroad.
• The railroad environment is unique and therefore requires unique technology solutions. Hence the railroads’ technicians must do the design;
• Only traditional suppliers can possibly understand railroad operations;
• It’s all about the main line – yards operations are secondary;
• As regulators, we can only accept “zero-tolerance” for operational risk;
• The Service Design folks can’t deal with all of the exceptions that occur;
• Don’t question, yet alone criticize; and lastly
• Just a couple more years and it will be somebody else’s problem.

Most of the above TBs, if not all, still exist to a great extent across North America’s freight railroads, arguably the World’s most sophisticated freight operation. So! What chance is there for the antiquated and developing railroads across the globe that are being forced-fed the “conventional” traffic control and traffic management systems which are based upon century-old technologies?

Within the next several months I will have articles published in Railway Age , International Railways Journal (IRJ), and possibly another international journal that addresses vehicular technologies regarding the Virtual Centralized Train Control (VCTC) system I designed with my associates to address the requirements for the Egyptian National Railways (ENR), as well as many, many other railroads across the globe that are critical for expanding the commerce of their respective countries. Those articles in concert with the attached video, take on many of the TBs addressed above as to safe and efficient rail operations without the use of traditional, conventional solutions that are justified only for high density rail operations.

I should note that the ENR engagement was paid for by the U.S. Trade Development Agency (USTDA). SO! SHOULD THERE BE COUNTRIES OUT THERE THAT MAY WISH TO HAVE A SIMILAR STUDY MADE OF THEIR OPERATIONS, THEN LET ME KNOW AND PERHAPS USTDA WILL FUND SUCH A STUDY.

Lastly, I encourage you to suggest other TBs for my consideration of a possible posting.

Based upon the study my team just completed in Egypt to evaluate the safety and efficiency of the Egyptian National Railways (ENR), I have posted a video on youtube, and is provided below, as to the design for a new traffic control, traffic management, and enforcement system. This system is referred to as Virtual CTC + Enforcement. It offers small to medium railroads across the globe, both freight and passenger, a cost-effective and pragmatic solution to delivering both efficient and safe railroading with enforcement capability that exceeds PTC, ETCS, and ATC. VCTC does not require either the extensive capital investment or extensive on-going maintenance of conventional or advanced traffic control systems.
Check it out!

THE GOODS

Given my now–completed engagement in Egypt to design a new traffic control, traffic management, and enforcement system, titled Virtual CTC + Enforcement, for the majority of the Egyptian National Railways (ENR), I have an even increased appreciation of 2 primary GOODs of railroad operations in the U.S. that do not exist in Egypt and many other countries across the globe. First, U.S. railroads are privately-owned in a capitalistic society that promotes the investment in those operations based upon the bottom financial line, simply stated as optimizing the return on investment. Second, the Federal Railroad Administration (FRA) provides the regulatory oversight without which inscrutable railroad operators have and could tradeoff the bottom safety line for the financial one. This blend of regulated safety and fiduciary responsibility has well serviced the railroads and the public alike since the Staggers Act of 1980 that deregulated the railroad market. As such, I dare say that nearly every decision by the railroads is a financial one, including those that deal with safety issues alone and not operations. Arguably, however, there here have been several exceptions as is the case of BNSF’s pursuit of PTC.

For most railroads, PTC as an overlay system, was never seriously considered to be a pursuit given that the costs of deploying PTC far, far exceed the projected safety benefits. The first PTC system, CSX’s CBTM for which I was the architect, was pursued because its engineer was at fault in the 1996 Silver Spring, MD accident in which there were 11 fatalities.  Especially given the accident’s location within the DC Beltway, CSX feared that Feds would force some type of  driver-enforcement system, and the only system being tested at that time was a pathetically over-designed concept referred to as Precision  Train Control. This PTC was not an overlay, enforcement-only concept. This PTC was an overly ambitious and, at the time, technically-unachievable moving block concept. Hence, CSX’s decision was a defensive one to develop a pragmatic approach, and that I did with CBTM providing the foundation for the overlay PTC systems being pursued to meet the Federal mandate. Subsequent to CSX’s efforts, BNSF expanded on CBTM’s scope of dark territory to include signaled territory, and it did so because “it was the right thing to do!” according to one BNSF top executive. There did not seem to be any immediate financial justification for BNSF’s efforts . . . except for a possible hidden agenda to move to one-man crews at some point. Nonetheless, BNSF had seemingly made a too-rare decision to invest in safety for safety sake without the immediate financial justification.

THE BADS

The other railroads were clearly not following the leads of CSX and BNSF. The business case was clearly not there to make such a financial investment. However, those individuals and organizations that wanted PTC at any cost promoted analyses and statements about the business benefits of improved asset management (e.g., track time, capacity, locomotives, crews) that PTC could reportedly provide so as to falsely justify their position.  These individuals and organizations were without the willingness, perhaps intelligence, to understand the difference between traffic control and enforcement. Simply explained, traffic control generates movement authorities and therefore is the means of achieving asset management effectiveness.  PTC only uses the parameters of the authorities generated to provide enforcement. With the simplest of understanding and rational thinking, one will realize that it is the ability of a locomotive to reports its position AND speed that supports more effective generation of movement authorities, which determines the management of railroad’s assets. To provide locomotive position and speed data simply requires a wireless data path, which happens to be a requirement of PTC as well. But, a railroad does not need PTC to get the wireless data path, as readily demonstrated recently by several Class Is that are obtaining those alleged PTC business benefits without PTC.  Nonetheless, after very credible reports from both private and government entities that belie the existence of PTC business benefits, there are still lingering comments that surface occasionally claiming the business benefits of PTC. For example, it has only been in the last year that the FRA finally removed such fatuous statements from its Website.

The net of the above is that BNSF initiated and continued its pursuit of PTC for altruistic reasons, it seems, while CSX did so to prevent a mandate of an overly expensive, if even achievable, enforcement solution. But that truly was it for the industry until the end of 2008 even though were occasional meetings of AAR technical committees with purported PTC interests.

Even with the regulatory processes in the U.S. for primary industries such as the railroads, the Congress can bypass the regulators and create laws without consideration of the bottom line of the corporations affected. Such is the case with the Railroad Safety Improvement Act of 2008 (RSIA) that was a knee-jerk reaction in less than 2 months following the horrific Metrolink / UP collision in September of that year that resulted in 25 fatalities.  This Act mandated the implementation of PTC across major segments of freight and passenger operations.

So! What do the various parties do when 1. They (the Feds) want something at any cost, a cost that they don’t have to pay … or … 2. They (the RRs) are being forced to make very substantial investments in systems that are not cost justified, but are mandated to do so for the sake of zero tolerance for unsafe operations. Simply stated, “What price safety?” … and “Who pays the tab?” This is where it gets ugly.

THE UGLIES

When so confronted with Congressional mandates, a company has the choice to pay the price, pull up stakes, fight the action through the courts,  ….  and / or   ….. to delay, lie, misdirect, fake it, and/or use lobbyists to influence the Congress to amend such mandates in some fashion.  In the case of the PTC mandate of RSIA, those railroads other than BNSF, and possibly CSX, have clearly demonstrated an amazing amount misdirection, faking it, if not just outright lying, to obtain at least delays in the PTC mandate. The high mark of this activity to date was the NTSB conference on PTC, February 27, 2013.  I did not attend the conference, but I have reviewed the presentations of the various speakers, and provide below my perspective on both the credible and irresponsible, if not mischievous, points that were made.

Having been involved with PTC from the beginning, even before the FRA RSAC-PTC process a decade or so ago, I know most of the presenting individuals very well and could “hear” their oratory as I reviewed the decks. Hence, I was not surprised by most of the points made, but yet saddened and angered at what the railroaders find necessary to do to attempt to avoid the unjustifiable expense of PTC. Simply stated, they seemed obligated for their company’s sake (if not their job) to purposely mislead, misrepresent, and even lie about critical points that they believed would helpful in delaying the implementation of PTC and its tremendous capital outlay. At the same time, I was surprised and gladdened by some of the reversals in falsehoods that had been made by railroaders following the mandate. Below, I summarize and separate the uglies and the reversals into 4 categories of PTC Functionality, and the primary technologies that are involved with PTC and other primary applications associated with a railroad’s operations:  Communications, Intelligence Processing, and Positioning.

PTC Functionality

• One presenter, at least, noted that PTC is much more complicated than anyone expected. However, its not PTC that is complicated, but rather it is a combination of Interoperabitity and the over-engineered communication, positioning, and intelligence processing solutions that ITC has been developing unchecked by senior management as to costs per necessary objectives (as discussed further below).

• Again, as discussed above, PTC has nothing to do with asset management and the associated business benefits (other than preventing occasional disruptions due to accidents).

• The various forms of “vital” have been used in confusing ways across the industry in addressing PTC. In the early days of RSAC-PTC I introduced the concept of functional vitality to separate the purpose of PTC from that of traffic control systems, e.g., signaling, dark territory. To be short, PTC is not functionally vital in that it does not generate authorities. Nor does the PTC BOS need to be a vital, fail-safe system, with I refer to as hardware vitality. There is an argument, however, for making a fail-safe on-board system so as to minimize the occurrences of traffic congestion as a train limps to the next yard due to regulated speed restrictions due to non-working PTC systems.

• The comparison of PTC to European ERTMS / ETCS is totally inappropriate and purposely misleading. ERTMS is an integrated traffic control/ traffic management/ and enforcement system designed for high speed / high density traffic.  PTC is an overlay system, meaning that it acts independently of the traffic control / management systems already in place. Hence, the complexity, costs, and timeliness of implementing ERTMS, which is functionally vital, provides NO points of comparison for overlay, non-functional vital PTC.

• A PTC-reliability study performed by ARINC was mentioned as a point of concern. Really! ARINC has a tremendous potential conflict of interest with the railroads and is clearly not in a position to be declared objective.

• Two years ago I was the Chairman of the first World PTC Congress. During that meeting I challenged the attendees, including FRA, suppliers, and Class I railroads to explain why it was necessary, or just important, to monitor and enforce intermediate signals.  No one has ever stepped up to that question other than retired FRA employees who stated it clearly wasn’t necessary. Of course, it isn’t necessary since PTC provides a braking curve to the end of the authority. Nonetheless, the railroads have added this significant complexity, and associated cost of additional WIUs, to meet this unnecessary requirement. Originally, the first estimate for WIUs following the mandate was 75,000.  It’s now down to 35,000, and I’m pushing for 20,000 at the most.

• Early on in the RSAC-PTC process it was agreed that grade crossings should not be an enforcement objective.  The reason was two-fold. First, it’s the railroad property and therefore they should not have to pay for the necessary infrastructure.  Second, and arguably most important, the pure physics of bringing a freight train to a stop would mean an excessive amount of gate down time, thereby possibly increasing the risks of vehicles running around the gates.

Communications

• Contrary to what was noted by several presenters, it is clear that there was no true analysis of the data requirements for PTC for the railroads to make an actual evaluation of the need for 220, especially over that of 160. This is admitted to in the filings by PTC-220 with the FCC, and as identified (and not contested by PTC-220) in my written statements to the FCC regarding the same filing. Both my statements and those of PTC-220 in its filing for more 220 spectrum are available upon request to me. When last checked, the FCC had rejected PTC-220’s request.  On a positive note, the presentation by NS regarding PTC-220 was refreshingly honest compared to those statements and filings under the previous UP presidency of that entity. The individual noted that there is no expected need for additional 220 spectrum for most of the railroad operations.

• As to why 160 was not considered by the railroads for PTC has little to nothing to do with the amount of spectrum available. Rather it has to do with the way in which the railroads proceeded to meet a FCC requirement to “narrowband” the frequency. To be short, they pursued conventional channel assignments instead of using “trunking” which is critical for effective usage of the spectrum in metropolitan areas.

• It should be noted that UP / NS purchased the 220 spectrum the year before the PTC mandate – before the MetroLink/UP accident. Why they purchased the spectrum is unclear, but given their resistance to voluntarily pursuing PTC, it is doubtful that they did it for PTC. It was after the mandate that BNSF and CSX were “persuaded” to forego their own communication solutions for PTC, each of which was much less robust, yet adequate, then the required wireless claims stated without proof by PTC-220. Subsequently, PTC-220 purchased Meteorcomm from BNSF to produce the locomotive radios even though Meteorcomm had neither the proven technical nor available manufacturing capabilities to provide the radios.

Intelligence Processing

• The Back Office Server (BOS) was suggested to be a portion of the critical path to meet the deadline. In my opinion there are 3 possibilities that this could be, with only one that makes any sense at this point. First, the functionality of the BOS is very, very straightforward and has already been achieved by BNSF with some minor changes remaining due to changes in the operating rules to address interoperability, as agreed to by the railroads during the conference. Second, the concept of vitality, as to failing safe, is clearly a red hearing. An overlay system can hardly fail other than safe in that it doesn’t generate authorities and instead only targets based upon the authorities generated. Even more misleading, one presenter likened the vitality of the BOS to the vitality of the European ERTMS. This is a purposeful misdirection. The vitality of ERTMS is that of the generation of authorities and the integration of the enforcement processes.  PTC is an overlay only and the functional vitality of generating authorities does not exist. Only the third reason has any merit. That is, linking the BOS with the individual Traffic Control systems in place for each railroad could be difficult. This is not due to technical reasons, but due to social/political conflicts that may exist between any given railroad and the suppliers involved, most importantly Ansaldo, formerly Union Switch & Signal. While Wabtec’s and Ansaldo’s HQs are only miles apart in Pittsburgh, their mindsets and willingness to cooperate between themselves and the railroads involved could span oceans, if you will.

• PTC is locomotive-centric, meaning that all processing of data for enforcement takes place within the on-board computer. Normally, this would not need to be stated, but the fact that the conference included a presentation on ARES suggests that someone thought there was some value in understanding the pursuit and the ultimate rejection of ARES.  To be clear, ARES was a clever traffic control and traffic management concept that integrated some PTC-like enforcement capability in the back office systems for signaled territory. However, it really has nothing to do with locomotive-centric, overlay PTC systems that are designed for both dark and signaled operations.  CBTM established the threshold for PTC, and the Singularly Disillusioned individual (SD) that has been inappropriately promoting both the supposed vitality and business benefits of PTC based upon his ARES experiences has actually done some harm in advancing PTC in a credible fashion, as exemplified by the horrendous FRA-funded report on PTC benefits performed by ZetaTech several years ago.

Positioning

• I didn’t note any significant comments regarding the issues of positioning, other than those of SD in the ARES presentation. Again, his comments are way out of fashion as to his focus on DGPS, as well as the fact that it was in my designing of CBTM that I introduced the monitoring of switch position in dark territory for “routing” trains, and which subsequently became relevant for the 4^th objective of PTC of preventing movement through misaligned switches.

• From my previous evaluation of ITC activities for a client, it became clear that the ITC technicians were way over-designing the accuracy of the positioning platform – I mean way, way overdesigning. The major effect of this is excessive cost for the on-board platform that could be in the range of $10,000 to $20,000 per locomotive, hence raising the cost of nation-wide PTC by several $100 millions

I would like to think that the NTSB recognizes that a number of presentations made at the conference to support an extended implementation period were highly prejudiced and even purposely misleading in some cases. Fortunately, PTC is beyond the need to evaluate the feasibility of its functional capabilities.  PTC does work. The primary constraints that are being presented by the railroads are a technical nature, as noted above.  Hence, if NTSB requires an objective analysis of PTC implementation issues, it requires a Blue-Ribbon Technical Committee, independent of the FRA, the railroads, and the likely suppliers, that can make such evaluations. The railroads will likely object to such evaluations. But, cannot any extension in time for the mandate be made conditional on such evaluations?

Outside of North America

For those railroads outside of North America that may be considering some type of enforcement system, e.g., V-CTC + Enforcement in Egypt, the above discussion as to the cost / benefit analysis of PTC does not likely apply. For example, the V-CTC + Enforcement system that I designed will prevent accidents due to mechanical interlocking operators and level crossing guards. In fact, my presentation of the final system design of V-CTC + Enforcement to Egypt’s MOT / ENR officials in December, 2012 was delayed several weeks due to two accidents, one each regarding the interlocking operator and crossing guard, that resulted in 5 and 50 fatalities respectively. V-CTC + Enforcement would have prevented those accidents; PTC as designed for the U.S. would not. Accordingly, Egypt’s Prime Minister directed MOT / ENR the following day to proceed with testing V-CTC + Enforcement.

I played a decent amount of basketball in my high school years.  However, being 6’3” was not enough by itself to compensate for my lousy shooting. And, I wasn’t a good shot because I was unwilling to practice enouigh to build that “muscle memory” of the physics associated with putting the ball in the hoop. Therefore, I spent my court time mastering the interception of passes between the opposing team players by anticipating their moves. I was really good at “reading” their intentions in the passing of the ball.  My skill, it seems, was a combination of perception and the ability to fake where my attention was in the other team’s handling of the ball. My strategy was if I could intercept their passes, then I could pass the ball to my team members who could make the shots. The point here is that there are those individuals that grab the ball, and there are those that can make the points once they have the ball.  This is one ideal “team” perspective in my opinion given so very few individuals can do both.  Unfortunately, in the U.S. railroads today, those who have the responsibility for obtaining the ball also have the responsibility for taking the shots – and they really suck at shooting. I am referring to the railroads’ technicians and their free-hand at designing and installing technologies without responsible upper management oversight. Simply stated: I think there is a great deal of faking going on in railroad management, whether it be intentional or just the nature of the organization.

Is there any doubt that there are times that each of us fakes it personally and professionally . . . but not necessarily for the wrong reasons? That is, we present viewpoints and take on tasks that are beyond our actual knowledge and skill set with the expectation (based upon past experiences) that we will succeed … and with the hope that our audience won’t be able to contest us either due to their lack of on-point knowledge or their lack of intestinal fortitude to take on the “authority”.  Unfortunately, however, in the railroads I see faking-it to be a two way street between the technical and operational managers that is resulting in a horrific waste of capital and, in the case of wireless, the waste of valuable RF spectrum. That is, the technicians fake that they have done their due diligence in promoting that there technical solutions are absolutely the most cost-effective . . . and the operators feign (or worse don’t even participate) that they have done their due diligence in challenging and understanding what they are offered by the technicians. While I am sure that there are some excellent examples where it is clear the technicians and the operators have worked together to deliver cost-effective technical solutions, there are too many examples where they have not. Arguably, the most egregious is that of the ITC efforts to address the interoperability challenges of PTC. There are 3 primary examples.

1. I have already exposed in this blog as well my articles in Railway Age, and my submissions to the FCC, that the grab for more and more 220 MHz by the Class Is is an intentional scam (IMHO). This is faking-it taken to an unprecedented level for the industry because it is not a single railroad that is the perpetrator, but rather a class(1)action, if you will.
2. Having spoken recently with a supplier of NXDN, a digital wireless protocol, I am of the opinion that the availability of the significant increase in channels  by narrowbanding VHF has afforded the railroad technicians the opportunity to once again forego their responsibility of using at least the 160 MHz band in a good-citizen, yet cost-effective fashion.
3. As to positioning accuracy for PTC, the technicians are striving for levels of accuracy that are far, very far, exceed that which is really necessary due to their inability to understand what is really required, and rather to ensure that they will never be at fault regardless of the cost.

Fortunately, there are several railroads that don’t buy into these fatuous technology activities and recognize that there are solutions that are much more cost-effective. It would seem that these railroads have a team perspective of obtaining the ball and making the shot. But unfortunately for too many railroads, there is a lack of upper-management understanding and support for doing the right thing for the right reason. That is, for too many railroads the exploits of technologies by technicians goes unchallenged by the management teams that have the responsibility for their railroad’s bottom line, with or without consideration of what makes sense for a country with constrained RF capacity.

THE bottom line is that the technicians are in fact faking it as to providing technology-based solutions that are grounded in responsible economics. They are doing so because, IMHO, 1. they believe that it is their responsibility to provide the best (most complex) technology regardless of the cost and regardless of whether or not such complexity is required, and 2, railroad management has failed to get involved in understanding the business perspective of technology decisions. So! Who is at fault?  In my opinion, it is the RRs’ senior management failure in developing a business strategy in sync with a technology strategy that has set up the situation. Could the focus on the current year’s bonus plan have anything to do with this? Hmmmm!

So!   I ask you: When you fake it, are you doing so for the right reasons?  Are you avoiding the critical issues important to your organization so as to “kiss up” to your management or to your annual bonus, whether you work for a railroad or a supplier? . . . or . . . Are you realistic as to what can be achieved and willing to speak up? . . .  or  . . . Do you really care one way or the other? As an independent consultant I don’t fake it with my clients.  They will get both a short-term tactical and a long-term strategic perspective whether they want it or not. I will grab them the ball, but they have to make the shot.

It is reasonable to expect that most of the visitors to this blog are well-experienced railroaders for technically-savvy, established railroads, but not likely that knowledgeable of either traffic control systems or enforcement methodologies (prevention of human errors in the handling of movement authorities) that may exist elsewhere. Personally, until 3 years ago, my experience was almost exclusively with traditional signaling systems as well as non-signaled traffic control as used across 50% of the U.S. trackage – what is generically referred to as “dark territory”. With 40+ years of experience, including being the architect for the first overlay PTC system that provided the foundation for the PTC systems being deployed in the U.S. to meet a Federal mandate, my level of railroad basics had not been truly tested it turns out. It seems that I knew too much technically, but yet too little as to basic railroading. That is, I had a firm grip on understanding the pragmatic deployment of technologies to advance technologies for financially-successful, heavy density freight railroads. But, I really had never had to get to the basics of what safe railroading is when it comes to those railroads that have neither the internal resources (financial and technical) nor the support of suppliers who only deal with modern railroads thereby promoting only traditional signaling or advance systems such as ETCS.  How foolish, if not arrogant – I confess, on my part. But, again, that all changed 3 years ago when I became the Project Leader for a study funded by the U.S. Trade Development Agency (TDA) to study the safety and efficiency of the Egyptian National Railways (ENR).

ENR is the 2^nd oldest railroad on our planet, the once-shining, now tarnished, star of the Middle East. I say tarnished for reasons primarily due to the raping of the Egyptian economy by the now-defunct Mubarek regime over the last several decades. ENR has deteriorated to a pathetic operation which is both highly inefficient and horrendously unsafe due to the reliance on human involvement in the generation and handling of movement authorities. Specifically, 2 points make the case. The traffic control systems across 82% of the trackage, Staff (token) and TYER (token-less), are block-by-block authority systems that stem from the middle of the 19^th century.  Such inefficient traffic control systems have contributed substantially to the inability of ENR to handle freight operations that is critical for advancing Egypt’s economy. More tragically, the Egyptian people have been subjected to an amazing number of horrific train accidents resulting in fatalities. Specifically, within the last 2 months alone, there were two accidents that resulted in 55 fatalities due to errors by a mechanical interlocking operator and a level crossing guard.

Our study to address the safety and efficiency of ENR began 3 years ago, but was greatly hampered, if not threatened, by the politics and questionable ethics by key individuals that existed prior to Egypt’s revolution. Following the revolution, the project was assigned to ENR, and the professional railroaders at both MOT and ENR provided the means for the study to progress. The study is now complete, and the Prime Minister has directed ENR to immediately move forward with the study’s recommendation to implement our innovative traffic control, traffic management, and enforcement approach that is based upon proven concepts that until now have not been integrated to meet the unique requirements of ENR, and most likely many other railroads across Africa, the Middle East, and elsewhere.  I have labeled this approach as Virtual CTC (V-CTC) + Enforcement. This approach required myself and my team members to challenge our understanding of the basics of safe and efficient railroading. Simply stated, those basics fall into two categories. First, there is the point of functional vitality (i.e., how are authorities generated) across this most antiquated railroad – and how does one minimize the capital investment to complement or replace those processes. Second, to what extent and by what means can enforcement be provided to prevent human errors in the handling of the movement authorities, again both generation and adherence?

Functional Vitality:

The primary purpose of a traffic control system is to prevent overlapping authorities, i.e., to authorize only one train to occupy a portion of track for a given portion of time. However, as is the case in the U.S. with Employees in Charge (EICs) for work gangs, there can exist a nesting of authorities. That is, a train can have an authority for a segment of track (multiple blocks) within which there is a second level of authority that must be obtained at some point. In the case of ENR, this was a critical consideration in that it deploys hundreds and thousands of mechanical interlocking operators and level crossing guards, respectively, that have the responsibility to provide a nested authority for a train to advance through their individual portion of control. In fact, the two accidents that I mentioned above where the result of the failure of these “vital employees” (see a previous posting on this blog with that title) to perform their responsibilities.

Enforcement:

To provide enforcement means being able to obtain the parameters (time / distance / speed) of the movement authorities that are generated, including the nested authorities. We all understand how that works in signaled territory, and some of us understand how that works in dark territory. But very few of us have had to deal with the nested authority process. Without going into depth here, our solution for ENR presented a very pragmatic solution that minimizes the use of wayside infrastructure. This is important not only to the direct capital investment requirement and ongoing maintenance, but also due to the consideration of extreme weather and theft issues in Egypt that readily compromise the safety of any approach so dependent.

The bottom line to the above discussion is that dealing with railroads that are without the financial or technical resources, for whatever reason, to advance their operations, there are solutions that they can deploy that are not offered by major suppliers that sell major systems for major railroad operations, whether freight and/or passenger.  However, to develop such solutions means getting to the basics of railroad operations as to the generation of authorities and the means to provide enforcement. Our solution for ENR prevents accidents due to errors by dispatchers and train drivers, but also those errors by vital employees such as EICs, mechanical interlocking operators and level crossing guards. Such systems, to my knowledge, do not exist elsewhere  – that is prior to what we have designed for ENR.

If you wish to explore the above points further, then please contact me at comarch@aol.com or 904 386 3082 in the U.S. My team of seasoned railroaders can address functional, technical (including wireless), financial (business case), and mathematics-based (OR) traffic density from both a tactical and strategic standpoint.

The concept of 6 degrees of separation was initially introduced in a play written by John Guare in the early part of the 20^th century declaring that each of us is only six steps of introduction from any person in the world. In current terms, this concept is readily acceptable given the advancement in communications and travel that has shrunk the world as to providing such connectivity. In fact, with the predominance of social networks available via the world wide conduit of the internet, one could argue that the six degrees of separation is now substantially less, if not just one. Arguably, the most dramatic example is that of the Arab Spring that has brought the citizens of suppressed countries, including their expatriates, to the point of uniting against their respective governmental tyrants.  One would like to think that our individual connectivity has no boundaries at this point as long as the paths of internet communications can be provided to the masses via wireless. However, as well demonstrated by the recent U.S. Presidential election, this same advancement in connectivity also provides the ability for those individuals that don’t have a rational understanding of facts to present their self-serving prejudices to misdirect those that solely place their faith in the written word, as to what can be achieved. To that point, only but the most uninformed or self-serving individuals would be quickly reminded by the Republican campaign for the recent U.S. President election which overwhelmingly (compared to that of Democrat’s campaign), consisted of a constant stream of a substantially misrepresentation of facts to present a phenomenally irrational, non-compromising  right wing perspective that serviced those most-selfish individuals that have benefitted from the benefits of a capitalistic  society, but without the recognition of the masses that have made their accomplishments achievable. Fortunately, for the benefit of the majority of the U.S. populace, President Obama was re-elected. With that stated, onward to railroads.

Playing on this concept of how technologies, most specifically wireless communications linked with Internet, have brought the world closer today, it also true the degree of train separation can also benefit from the introduction of technologies, again wireless data, and the use of advanced traffic management systems that can provide a substantial increase in traffic density for any given corridor by simply knowing the position AND speed of trains. With the availability of both position AND speed data, that doesn’t  exist for the majority of railroads across the globe, a railroad’s operations can project  and prevent conflicts that may occur even within fixed-block operations as determined by traditional electronic signaling operations that depend upon traditional wayside technologies that provide block-size positioning at best. I refer to this capability as Proactive Traffic Management (PTM) as is described in greater detail in  various other postings on this blog.

The deployment of PTM is quite inexpensive  both absolutely and especially relative to its value in that it can be provided as an overlay to a railroad’s choice of traffic control, whether it be signaled or non-signaled, WITHOUT replacing the dispatching platform. This is true because PTM is only a management decision tool and not an execution platform such as CTC or Track Warrant. As a decision tool, PTM can dramatically complement, if not replace in many cases, the skill set of the dispatcher who is a manager of the execution platform. This means that PTM is not functionally vital, i.e., it does not generate authorities that provides for the integrity of train movements. The ultimate deployment of PTM is when it is tightly integrated with traffic control thereby becoming some level of moving block – a vital system. But only a few high speed / high density railroads can benefit from a moving block capability. In fact, in the U.S. there are a number of operations-savy individuals that will note that moving block for the most dense freight traffic corridors would provide little benefit until the yard operations are optimized concurrently. So! As an overlay to traffic control, short of making a transition to moving block, what is holding back the deployment of PTM across the majority of globe? I believe the primary reasons differ between public and private railroads.

PUBLIC: Outside of the Americas, the predominance of rail operations are owned / controlled by the governments of the countries in which they operate.  Again, in general, these are passenger operations without a clear responsibility for addressing financial bottom line, i.e., providing cost effective solutions that have to pass the threshold business test as to making a profit, or else it is out of business. In these environments it seems that the suppliers often rule the roost in designing the traffic control solutions that aren’t necessarily cost-justified. Technicians thrive on promoting systems in this environment; they believe that they are justified in delivering solutions without restrictions as to costs. However, for those countries that are confronted with growing their economies internally, as well as integrating with the world economy, they are being presented with technologies that they simply cannot be justified.

PRIVATE: In the Americas, the freight railroads are competing with road, barge, and pipeline transport and therefore have to maintain a for-profit operation to stay in business … or they are out of business. Indeed, in the U.S. there have been tens if not hundreds of railroad bankruptcies in the last century. The Penn Central bankruptcy in the 70s (which the largest bankruptcy up to that time for all industries and for which I was the lead financial analyst for the Trustee Staff, is the ultimate example. This railroad lost its understanding of what it was, and eventually went under. That railroad went into a downward spiral as it reduced maintenance expenditures . . . which resulted in reduced traffic speed . . . which resulted in the loss of revenue . . . which resulted in further reduction in maintenance expenditures … and the downward spiral continued to the point of bankruptcy.  Conrail was the Phoenix rising from the ashes of the Penn Central. OK, back to the issue of separation.

The separation between trains, a.k.a. headway, is THE key issue in determining the type of traffic control that should be in place, whether it be freight or passenger operations. Those European suppliers that service the high speed, high density operations in place across that continent have developed sophisticated systems that provide for both safe and efficient operations. BUT, what about those countries in Africa, the Middle East, and elsewhere that need cost-effective solutions to bring basic rail infrastructure to grow their GNP, both internally and relative to the world market?  They cannot afford the likes of traditional signaling, yet alone ETCS 1,2,3. These railroads need cost-effective solutions ; they need traffic control solutions generically referred to as dark territory that are used by railroads in the Americas that have a clear vision to the bottom line. They also need enforcement systems to prevent accidents due to human errors.  I speak with experience on this point given my assignment as Project Leader to address the safety and efficiency of the Egyptian National Railways (ENR) that still uses token and token-less traffic control across 82% of its operations.  With detail to be provide in the next posting on this blog, my team of independent consultants  (we don’t represent suppliers and we don’t accept commissions) have designed a traffic control, traffic management, and enforcement system that greatly improves both the safety and efficiency of ENR’s operation at a mere fraction of the cost to deploy ETCS.  This is a proven system as to the individual components that we have integrated. We have done so recognizing the true nature of ENR as to what they are and will be in the foreseeable future along with the realization of the capital investment that they can support. The approach I have titled as Virtual CTC (V-CTC) + Enforcement,  provides CTC functionality with the ability to prevent accidents due to drivers AS WELL as mechanical interlocking operators and level crossing guards, as well as the loss of train integrity. For example, two horrific accidents in Egypt in November, 2012 resulted in 54 fatalities that could have been prevented with V-CTC + Enforcement due to errors by mechanical interlocking operators and level crossing guards. Both of these accidents would not have occurred in the U.S., but in Egypt with their antiquated traffic control systems dependent upon “vital employees” (see the previous posting on this blog), there were human errors for which there was no enforcement system in place to prevent. But, through the efforts of my team in performing our study there, we recognized and modified the enforcement concept of PTC to handle. Specifically, we have designed an approach that monitors the traffic control activities of these vital employees to ensure that they have performed in providing valid movement authorities.  Most importantly, Virtual CTC + Enforcement minimizes the capital requirements to operate the railroad both safely and efficiently, versus slamming in signaling infrastructure and/or ETCS that would be 30 to 50 times more expensive by my rough estimate.

I can’t over emphasized the need for pragmatic, cost-effective solutions for traffic control, traffic management, and enforcement that traditional suppliers have refused to address for the majority of railroad operations across the globe.  Shame on them. Enough said. The next posting here will present V-CTC + Enforcement for those railroads and suppliers that are looking for solutions that support the majority of railroads across the globe that don’t provide high speed / high density operation – both passenger and freight. Please contact me at comarch@aol.com if you which to discuss your particular interests. My team of seasoned railroad professionals can address the functional, technical, financial, and mathematical throughput analysis of considering V-CTC + Enforcement from both a tactical and strategic perspective relative to expanding the safety and efficiency of a railroad’s operation, especially when integrating freight and passenger operations.

The bottom line here is that I warn railroads from being fooled by the written and stated words of suppliers that have solutions that are not appropriate for their operations. There may be pragmatic, cost effective solutions of which they may not be aware.

With the introduction of overlay PTC just over a decade ago, the concept of vitality needed to be expanded at that point beyond the mantra of signaling engineers as to a vital component or system being one that fails in a safe manner, i.e., failure without introducing any additional risk.  In addition to this design vitality, it was necessary to introduce a concept of functional vitality to prove that PTC was and remains not vital. That is, a functionally vital entity is one that generates the movement authorities for trains, thereby providing for the integrity of train movements. For signal engineers the two concepts are inseparable, and in their viewpoint, anything associated with traffic control must by vital. Such fatuous rationalization can be quite unfortunate for the deployment of advancing technologies in railroads, including PTC. Two current examples here are ITC’s efforts in designing the wireless and positioning platforms for PTC that are way beyond what is required for a non-vital system, if even a vital one.

In anticipation of such design tangents by railroad technicians ( as demonstrated in the past by UP with it Precision Train Control project that died from overdesign), I introduced the functionally vital perspective a decade ago to demonstrate that overlay PTC is not vital and therefore not subject to the design and regulatory complexities associated with vital systems. Stated otherwise, PTC’s ability to enhance the safety of rail operations is substantially less critical than that of the traffic control systems that provide for the integrity of train movements. PTC only addresses human errors whereas traffic control systems are absolute.

Being the architect of the first overlay PTC system, I was continuously challenged during the early years by labor, FRA, suppliers, and even my counterparts on other railroads, to explain why PTC is not vital. The forum for these discussions was primarily that of the Rail Safety Advisory Committee (RSAC) for PTC that was charged with defining the core objectives of PTC. Understandably, RSAC-PTC was primarily manned by signal engineers who live and breathe vitality with their natural inclination being that everything is vital. Again, for them PTC had to be vital, I assume, because it addresses safety, and it is related to vital traffic control systems. At the same time, signal engineers when asked during the courses I teach on PTC and railroad operations “What is vital in dark territory?”, will respond that there is nothing vital since there is no wayside equipment. The solution for addressing both of these ill-structured mind-sets of signal engineers as to PTC and dark territory was to provide the functional definition of vitality that really goes to the core of running a safe railroad, i.e., the generation of authorities.

In parallel with the functional vitality effort was the extraordinary task of convincing the masses that PTC did not deliver those business benefits that continue to be so widely and wildly proclaimed by FRA and suppliers as to increasing traffic density and the efficiency of the key operating assets, e.g., crews, locomotives, and even maintenance crews. I quote the FRA’s website “In addition to providing a greater level of safety and security, PTC systems also enable a railroad to run scheduled operations and provide improved running time, greater running time reliability, higher asset utilization, and greater track capacity.” Here is the simple, and one would think very obvious, logic as to why overlay PTC can’t provide such business benefits. To increase traffic density means that the generation of movement authorities need to be done more efficiently … and since PTC does not generate movement authorities (nor deliver them as the FRA website proclaims – that is the purpose of digital authorities – not PTC), then it cannot provide those benefits.  Actually, if not properly designed, PTC can actually decrease both the traffic density and safety by making unnecessary enforcements. What the FRA and others who flaunt PTC business benefits refuse to understand is that it is the wireless data path required by PTC that also permits train tracking status data to be delivered to back office management systems.  As demonstrated by NS and BNSF at least, a railroad doesn’t need PTC to obtain the stated business benefits; a railroad only needs a wireless data platform, whether it be cellular, satellite, and/or private. In any event, the bottom line remains, i.e., PTC is not vital in any sense.

OK, at this point you may be thinking about VPTC (where V means vital) which is one title given to the PTC systems being pursued by the freight and commuter railroads. Clearly such a title suggests that PTC is vital, but it isn’t. VPTC means that the platforms upon which those PTC systems are deployed are design vital so as to reduce the failure of the PTC system, but PTC is still not functionally vital. The purpose of VPTC is to provide a pragmatic economical solution to regulatory issues that requires a restricted speed for a train should its PTC platform fail. In heavy density corridors, the application of restricted speed could result in significant business costs.

With the distinction between design and functional vitality now established above, I introduce a new vitality phrase: “Vital Employee”. Simply stated, a vital employee is one that generates a movement authority. For U.S. railroads, the primary example is the Employee-In-Charge (EIC) that provides the authority to a train to move through a work zone, a work zone that is encapsulated (nested) within an authority generated by a traffic control system. Handling the enforcement of the nested EIC authority was a major design issue that I had to provide for the first overlay PTC system … and is now used by the PTC systems being deployed by the freight railroads.  Again this was done in a non-vital way by not affecting the underlying Method of Operations, thereby avoiding regulatory complexities.

The vital employee perspective has proven to be particularly challenging in my assignment as Project Leader for a consulting effort in Egypt to advance both the safety and efficiency of the majority of the Egyptian National Railways (ENR) operations that use token block and TYER, a.k.a. British Absolute Block, traffic control systems. In the case of ENR, their operations have mechanical interlockings that are handled by operators independent of the central movement office. Instead of a centralized dispatcher, ENR uses block/interlocking operators to generate block-by-block authorities thereby compromising the efficiency and safety of train movements compared to that which railroads around the world achieve with dark and signaled operations. For this engagement, a “virtual” CTC (V-CTC) system is being designed that will provide for multiple block authorities subjected to nested, manual interlocking authorities. This solution provides for enforcement for the authorities generated by both V-CTC as well as the interlocking operator.

As a closing point, I wish to remind all that the Book of Rules provides the underlying threshold of vitality for all rail systems. In my 40+ years in the industry, I find that too many tend to ignore this point – just as signal engineers tend to ignore dark territory.

In the previous 2 posts of this set of 3 regarding Industry INTRAoperability (not Railroad INTERoperability for PTC) I addressed both the opportunity and the rail executive education that are required for the unprecedented opportunity to advance the railroads’ operations, both individually and as an industry. The underlying logic is that rail executives are motivated by their bonus plans to optimize the handling of their responsibilities. Hence, a strategic perspective that is beyond the horizon of their bonus program requires that top management be so educated to provide the incentive to think strategically as to the deployment of technologies to satisfy a strategic business plan, a.k.a. Strategic Railroading™. In this posting I discuss a well-proven process that provides the structure to do so.

In other postings on this blog I have referenced IBM’s efforts in the 70s and 80s to introduce the usage of computers across industries to replace manual business processes as well as to re-engineer business processes given the integration of computers with telecommunications, thereby establishing new flows of information within and between enterprises.  In addition to the prestigious executive sessions that IBM provided for its clients back then, IBM developed a very formal process for identifying the information flow architecture that would support the advancement of computers. Referred to as Business System Processing (BSP), the Wikipedia description properly identifies the primary objectives, i.e.,

• understand the issues and opportunities with the current applications and technical architecture,
• develop a future state and migration path for the technology that supports the enterprise,
• provide business executives with a direction and decision making framework for IT capital expenditures,
• provide information system (IS) with a blueprint for development.

Why BSP can be of great value to the railroads in particular at this point is the opportunity of developing “a future state and migration path” given the proliferation of wireless networks, both private and commercial. Even more to the point is the tremendous effort and investment that the railroads are making to lay in a 220 MHz network in the name of PTC. And, as noted in other postings on this blog, this decision by the railroads to deploy 220 MHz is really pathetic in two primary ways.  First, the railroads have failed to justify the need for additional 220 MHz as evidenced by FCC’s rejection of the railroads’ request for such spectrum in addition to what they already own. Second, there is no strategic business plan associated with any strategic technology plan (other than to just install 220 MHz) to cost-effectively use all of the spectrum that the railroads now possess. It is in support of both of these points that a BSP could lay the foundation of how wireless can benefit not only the individual railroads, but also the industry overall. In fact, had the railroads already performed a BSP for the industry, one that was truly understood and accepted by senior management, then the 220 MHz sham by the railroads’ technicians would have never gained any ground in my opinion.

So! It’s agreed then. A BSP can be greatly beneficial. But how is such a process performed?

BSP Process

There are 8 primary, structured & well-proven steps in performing a BSP, as follows:

1. Gain Executive Authority: This is often the most critical part of a BSP. Without the proper level of commitment to support the need for incorporating multiple departments of an organization within the study, the effort will fail with the first major disagreement between the departments, a disagreement that is inevitable;

2. Define the Business Strategy: This steps sounds difficult perhaps, but it actually is quite simple if the participants can be honest about the successes and failings of the organization and their individual departments;

3.Define the Business Processes: This is the most creative part of the BSP in that it requires visionaries that can look beyond the current processes and recognize the possible changes due to advancing technologies. For railroads it is the focus on wireless data that can provide for more timely and accurate management of the vast sets of mobile assets;

4. Define the Business Classes: Defining data classes (aggregates of related data elements) is very straightforward once the business processes have been defined.  (Note the very simplified example below of which business processes create / use the various business classes.);

5. Validate Finds with Management: This process establishes a line in sand with the management team that demonstrates the study is meeting the objectives of the study so as to ensure on-going commitment.

6. Define the Information Architecture: Ah Yes! This is the most fantastic step where the BSP effort really clicks and all participants and management can see what they have been missing as to information flow between the primary entities, and processes. (Note below a simplified example of a BSP that I performed for the intermodal industry. The arrows indicate the flow of specific data classes (descriptions not included) between operational entities and/or data bases. The black objects and arrows are current, the red objects and arrows are new relative to the changes in the business processes, and blue objects are hardware that need to be developed;

7. Establish Information System Priorities: The appropriateness and credibility of the information architecture developed via the BSP is first tested here as each player pulls for particular interests in establishing the priorities of the future information systems. Using the above diagram as an example, the order in which the red blocks are developed, either individually or collectively, can greatly affect the actual success of reaching the desired overall objective.

8. Make the Business Case for Management: YES! The most important business case. If nothing else, the BSP process takes the control of technology investment out of the hands of the technicians who seemingly have the desire to deliver the optimum system as to capability, whether it is required or not.  Again, the most current, and capital-wasting example of this is that of PTC deployment where the technologists are out of control as to wireless (220 MHz), a train positioning platform, and the use of wayside interface units to interface with Intermediary Signals ( see the previous posting on this block “IS … Not”).

Voila!  I have managed or participated in 4 BSPs … and this is really good stuff.

In the forthcoming April, 2012  issue of Railway Age, I expose the tremendous over-design of PTC by the railroad’s technicians.  Specifically I refer to the issues of 220 MHz for a wireless network that is totally unjustified given the railroads current available wireless bands that are being ignored  (which the FCC shot down as to the request for additional 220 spectrum), as well as their pursuit of a Positive Train Location (PTL) component that is far beyond that which is really required. What I purposely left out of the article was the railroads’ pursuit of incorporating Intermediary Signals (ISs) into the functionality of PTC.  I did so because I thought this was a bridge too far for even Railway Age (what I consider to be the most daring and honest of railroad periodicals) to take on this subject. But, the short is that the railroads’ technicians have once again ignored the actual requirements by developing solutions that are, again, totally unjustified as to both functional and technical perspectives. If you dig deeply enough into this blog you will find a posting YOY WIUs where I introduced my thoughts with an explanation meant for the non-technicians.  What you read below, is a well-qualified operator’s perspective of this very point. The author is Dave Schanoes and his blog is www.ten90solutions.com.

********************************************************************************************************************************

PTC–Everybody, at least in the US, is talking about PTC.  I’m no different.  I talk about it.  I think about it.  I do some work on it.  And let’s be clear– I welcomed the mandate for it… although let’s be completely clear: the Chatsworth collision that moved the US Congress to act could have been prevented by the decades old cab signal/ATC systems in use on many railroads.

So maybe PTC wasn’t needed there, but even with ATC something more is needed; actually a few something mores, given the mixture of signalled and non-signalled territory in the US.

I was talking to my friend, Ron Lindsey, of Communication Architecture about end of train, restricted speed, intermediate signals and his questions made me think, and my thoughts made him question me some more, and we agree on this:

Why This? And why not This?

March 26, 2012

236.1005 (a) (2) of the famous subpart I of the regulations governing train control reads:

“[Each PTC system required to be installed under this subpart shall] include safety-critical integration of all authorities and indications of a wayside or cab signal system, or other similar appliance, method, device, or system of equivalent safety, in a manner by which the PTC system shall provide associated warning and enforcement to the extent, and except as, described and justified in the FRA approved PTCDEP or PTCSP…”

which means, or has been interpreted to mean,  intermediate block signal indications of a fixed block system, utilizing either wayside or cab signals or both, must be displayed [that’s the authority part, because in rule 251 or 261 territory, signal indications are the authority for movement] and enforced [that’s the indications part, as the fixed wayside, or cab displayed, block signals are speed indications].

There’s a “limited cab” in your system that means passenger trains must not exceed 45 mph?  Guess what? PTC has to display and enforce that limited cab and speed.

So here’s my question…”why?”  I’m serious, why?  What is gained by PTC enforcing the intermediate signals rather than calculating the braking curve and enforcing the braking curve to the point of restriction?

Well, someone’s going to say, because the point of restriction is a train somewhere ahead of the train receiving the “limited” indication, and the point of restriction is the restriced speed indication protecting the block in which that train is, and any block signal can be a signal displaying restricted speed, and therefore, PTC must monitor the intermediate signal aspects and enforce the intermediate signal indications.

Before we go any further– no, I’m not going to advocate we do away with fixed blocks [although I heartily recommend doing away with wayside signals except at interlockings in favor of cab signal systems.  And no, I’m not going to make an argument for CBTC or dynamic block or moving block, because I do not think CBTC or its variants are required for either passenger or freight movements in the US, given the density of the traffic.  And, no I’m not going to advocate doing away with the “restricted speed” indication— I think the restricted speed indication has a very important role to play in terminals, yards, stations, and for broken rail protection.

I just don’t think “restricted speed” (1) can actually be enforced by PTC  (2) is an effective and “positive” method of safe train separation.

Far be it from me to opportunistically cite the recent spate of restricted speed collisions as supporting evidence, but I refer to the recent spate of restricted speed collisions as establishing the point that we need to do just a bit better.

First, enforcing intermediate signal indications, even the restricted speed indication, is not necessary to PTC accomplishing its core functions: preventing train-to-train collision; derailment due to overspeed through permanent or temporary speed restriction; unauthorized incursion into a work zone;  operation through a switch not properly lined for the train’s intended route.

Train-to-train collisions can still occur at restricted speed; overspeed derailment can, and is prevented without resorting to signal indication; unauthorized incursion into a work zone is eliminated through enforcement of a  positive stop ; an improperly lined switch should also be protected through enforcement of a positive stop.

And… PTC is not enforcing restricted speed.   It is only enforcing the numerical magnitude, the “not to exceed,” tacked on to the rear end of the definitiion.  The meaning of restricted speed does not reside in the speed value.  The authorization for continued movement upon receiving the restricted speed signal is not an authorization to proceed at a certain speed.  The authority for movement is based on crew responsibility, upon the crew observing the rule.  Of course, this simply reintroduces the possibility for human error, which PTC is supposed to prevent in the first place.

The “guts” of the restricted speed indication is that “movement must be made at a speed that allows stopping within half the range of vision short of….” ( you know the rest).  PTC can’t enforce that.

Would you like to know something else about intermediate signals and the enforcement of their indications?  Railroads don’t do it.  Cab signal/automatic speed control systems do not do it… or aren’t required to do it.

You wanna bet?  Yeah, I wanna bet.

Back in the day when I was person with a bit of authority on a major commuter railroad in a major metropolitan area, I took out my trusty pencil and paper and did some calculations.

We used a 4 aspect, fixed block, cab signal/speed control system.  The aspects and associated indications were:  “normal”= MAS; “limited”= for passenger trains, not to exceed 45 mph; “medium”=for passenger trains, not to exceed 30 mph; “restricted”– prepared to stop within half the range of vision etc. etc. not to exceed 15 mph.

On a rather busy portion of our railroad, the MAS was 80 mph.  A train receiving a downgrade to “limited cab” was theoretically required to be at limited speed before entering the next block, particularly if the signal indication at that block was “medium cab.”

With our four aspect system, our signal design distance for deceleration from 80 mph to zero was approximately 9600 feet.  Our required rate of deceleration was 1.28 ft/sec/sec  or  (-).84 g.

But because we do things evenly, each block was approximately 2400 feet long.  Our signal design distance showed a required distance for decelerating from 80 mph to limited speed [45 mph] of 4611 feet, including the 8 second free-run time.

So what gives, here?  What gives is that our on-board speed control systems did not monitor the target speed of  the train in accordance with the speed transmitted by the signal protecting that block, but by the required braking rate to achieve zero velocity.

Certainly, if the engineer released the brakes before the target speed was achieved, a penalty brake application would ensue, but that again was based on not achieving a required rate of deceleration.

PTC does that.  It enforces that.  What it needs is not the signal data per se, but the location of the speed restriction, the target to which it calculates and enforces the required braking curve to comply with the limit to authority.

Cab signal/ATC systems  convey authority to the following train  enforcing  the numerical magnitude of the speed, rather than enforcing the limitation to the authority.  And that limitation is strictly a function of the technology the signal systems were built upon.

Why restricted speed?  Why intermediate signals?  Because we had NO WAY of determining, in the field, by the field apparatus, the location of the rear end of the leading train.

And today?  Today, we definitely have that technology.  We have GPS to locate the head end of the train.  On passenger trains, we know how many cars are in the consist and the exact length of each car.

And for freight trains?  Freight trains in the US operate with EOTs– end-of-train devices that utilize radio telemetry to convey the brake pipe pressure, airflow, etc. at the very rear of the train to the head end of the train.  There is no reason that signal cannot be enhanced, and processed to confirm train integrity to the GPS system and to measure train length.

Conveying the train length to the Back Office System and using that length to enforce a positive stop, to withdraw a following train’s authority for movement at a point to the rear,  then becomes part of our algorithm, adjusting for grade (slack on the lead train, braking on the following) for safe train separation.  This is not “moving block”– but certainly could become so in existing dark territory– but rather limit to the authority for movement in a fixed block system.

And if you ask me, it would be a shame to let the limitations of an older technology hobble that of the new, forcing us to repeat the same old, same old, same old failures.

You did ask me, right?

Copyright 3/26/2012 by Dave Schanoes

This is the 2^nd of 3 postings that address Industry INTRAoperability (I/I), i.e. the development of systems that support the business interest of the entire rail industry, versus the advances in technologies and systems made by each individual railroad for its singular purposes.  I/I is not the same as Railroad INTERoperability, as is required to deploy Positive Train Control (PTC) as a safety enhancement to the traffic control systems that provide for the integrity of movement operations. Rather, I/I addresses the business perspective of the advantages to the industry by the improved management of key resources subject to the interchange of trains between railroads. The assets that I am referring include the full array: track time, train crews, yards, locomotives, rolling stock, and shipments of high value and/or involving security issues.

Yes! I did state track time, train crews, and yards even those assets don’t cross borders. The reason for doing so is that the use of those assets increases in efficiency as the degree of scheduled operations increases . . . And, the ability of an individual railroad to run to scheduled operations is partially dependent upon the schedule reliability of the railroads with which it interconnects . . . And, since most railroads have yet to demonstrate their ability to run to schedule to a significant extent, contrary to their claims, then a valuable opportunity of pursuing I/I is that of providing timely data of train movements, both position and speed, across all interconnecting railroads so as line-ups can be adjusted in a timely fashion.  Unfortunately, even with such data, a number of roads are incapable of using it to any great extent given their lack of Proactive Traffic Management techniques that I introduced 6 years or so ago in my quarterly publication, Full Spectrum. However, it is encouraging that at least NS and BNSF have made such advancements via the deployment of pragmatic wireless solutions that can report the speed and position of their own trains on their respective properties.

As to the locomotives, rolling stock, and shipments that do cross railroad borders I identified a number of I/I applications in the FRA-funded study I performed in 2008: A Demand and Supply Analysis of the Opportunities for Wireless Technologies in Passenger and Freight Rail Operations, (www.fra.dot.gov/downloads/Research/ord0802.pdf). As the result of that study, I decided shortly thereafter to take the same approach that IBM used in the 60s and 70s to bring about major changes in the traditional business processes of a full range of industries with the introduction of main frame computers. That is, IBM established major executive education facilities and curriculums across the U.S. to expose their prospective clients’ top management teams to what could be done with computers. As noted in the previous posting, the initial efforts focused on replacing manual data handling processes, e.g., payroll, accounts receivables / payables, with computerized data processing. However, with the introduction of affordable disk storage and the integration of telecommunications with computers, the curriculums expanded in scope by identifying how to change the traditional business processes given the opportunities to rethink the flow of information within and between enterprises (The process of structuring a strategic information flow architecture will be discussed in the next posting: It Takes an Industry: Process).

So, following IBM’s lead I put together an Strategic Railroading Symposium for top railroad executives that would be sponsored by the supplier community overall to remove even the perception of bias. The symposium schedule (presented below) that I put together consisted of 2 tracks, Operations & Engineering, with two categories of topics each, that addressed I/I opportunities as well as other possible applications that I believed at that time would be valuable exposure for railroad top management. Actually, this effort was progressing well with the expression of key suppliers to participate . . . that is until the ramifications of the just-ordered PTC mandate took effect. At that point, rail’s management teams withdrew into their caves rejecting the consideration of anything other than the challenges of implementing PTC. The suppliers, hence, backed away from the opportunity given their inability to market even their current products and services, yet alone the challenges and risks of developing a long-term strategic perspective.

As you will see in the agenda below, several of those applications have had sporadic initiations across the industry in the last several years.

When rail management surfaces from the PTC abyss, then perhaps there will be an opportunity to reconsider some version of the Strategic Railroading Symposium.