Passenger Trains > Metra acknowledges PTC impact on flipping trains

https://metrarail.com/about-metra/newsroom/new-rock-island-line-schedule-finalized-meet-demands-positive-train-control
Note the sixth paragraph, which speaks of additional time added to schedules in instances when there is a quick equipment turn.
Their honesty is refreshing!
Andy

I'm sure they applied the lessons learned from the BNSF implementation. 

High marks for METRA. This has to be one of, if not the, best-written and most informative public release regarding PTC and its impact on operations that I have seen.  Good job.

Gordon

Entering the next trip PTC safety data AS A TASK should not take more than two to three minutes if using an IT template with a fast reboot computer druve.  
A full ten minutes assigned to the computer’s PTC respecifucation suggests they need a better IT tech department.

Time for walking between train ends, and a crew safety briefing is NOT an added PTC tim3callocation task.

I know first-hand that Metra can turn a train in 8.5 minutes if they have to:
https://www.trainorders.com/discussion/read.php?4,4691994

Posted from iPhone

gbmott Wrote:
-------------------------------------------------------
> High marks for METRA. This has to be one of, if
> not the, best-written and most informative public
> release regarding PTC and its impact on operations
> that I have seen.  Good job.
>
> Gordon

I agree. For a complex topic for the general public, it's direct but not "in your face", factual, concise and well stated. There can be discussion about whether it should take so long to perform these tasks, and that may be valid. But until those issues are resolved, this is a good explanation for the general public.

Jimblaze Wrote:
-------------------------------------------------------
> Entering the next trip PTC safety data AS A TASK
> should not take more than two to three minutes if
> using an IT template with a fast reboot computer
> druve.  
> A full ten minutes assigned to the computer’s
> PTC respecifucation suggests they need a better IT
> tech department.

I don't have / haven't had direct involvement, but while developing the Eugene OR - Vancouver BC passenger services operating plan and attempting to establish times for such events, the information that I had was that the weak link of changing direction was the data communications rate and reliability.

TAW

Jimblaze Wrote:
-------------------------------------------------------
> Entering the next trip PTC safety data AS A TASK
> should not take more than two to three minutes if
> using an IT template with a fast reboot computer
> druve.  
> A full ten minutes assigned to the computer’s
> PTC respecifucation suggests they need a better IT
> tech department.

If the article is read correctly it states "=16pxWith the added task of initializing the PTC system, these “flips” are expected to take more than 10 minutes," it doea not say it takes 10 minutes for PTC input.

Correct on the above.

I don’t run passenger, and I’m not a 100% sure how it works in these cases but...

Trains going in the same direction and just having a crew change, takes about 5min on average to init PTC.

If the train is at its initial terminal or the system prompts is, a departure test is required. This test - tests the airbrake system so it knows it can stop the train. With a passenger train, it would go quick.

In swapping ends, I’m not sure if it would be required or how the system reacts to it. On something small like a commuter train should only add a couple of minutes.

METRA operates a pretty uniform fleet of equipment that has a clearly defined minimum stopping rate regardless of trainset size.  There should be no need to input trainset details.  I'm pretty sure Amtrak just has a switch in the cab to select the various speed profiles that a train is set to run (Class A through Class D or E with A being a high speed trainset).

The laughable part is that it takes Waze about 10 seconds to start up and download all the traffic information nearby including the speed limit on pretty much every road. 

At some point someone will adapt computer vision system from a self-driving car that can just decipher the signals temporary speed limit signs along the right of way.  Problem solved.

You would trust your life to Waze?
I would not.

mbrotzman Wrote:
-------------------------------------------------------
> METRA operates a pretty uniform fleet of equipment
> that has a clearly defined minimum stopping rate
> regardless of trainset size.  

So you think the six-car train I ride in almost every day has the same stopping distance as the 11-car trains from Naperville and Route 59?

mbrotzman Wrote:
-------------------------------------------------------
> METRA operates a pretty uniform fleet of equipment
> that has a clearly defined minimum stopping rate
> regardless of trainset size.  There should be no
> need to input trainset details.  I'm pretty sure
> Amtrak just has a switch in the cab to select the
> various speed profiles that a train is set to run
> (Class A through Class D or E with A being a high
> speed trainset).
>
> The laughable part is that it takes Waze about 10
> seconds to start up and download all the traffic
> information nearby including the speed limit on
> pretty much every road. 
>
> At some point someone will adapt computer vision
> system from a self-driving car that can just
> decipher the signals temporary speed limit signs
> along the right of way.  Problem solved.


Crews don't input stopping distances.