TTTO: OS-ing

 I ran a large TTTO layout for ten years in So. Cal. That layout was AIR1.  Initially I installed a fairly flexible phone system, you could call anywhere on the layout from  anywhere on the layout, and I intended that crews would call in with their OS*

What happened, from the very first instant, was a non-stop cacophony of phone calls in the DS office that was completely unmanageable. 

Within minutes of the end of that session I started beating the bushes for a solution. A friend from Illinois suggested I do what he did, use post-it note OS’s. When trains reached a point where they were supposed to OS, crews would write on the post-it note their train, location, and the time. The crew member then walked over to the operators desk, and dropped the post-it note in the OS box. The operator would then transmit these OS’s to the DS during a lull in the session.

Here’s an important, and apparently secret note about OS’s. They are not as VITALLY important to the DS as everyone makes them out to be. The DS NEEDS an OS from each train at the following three places, AND THATS ALL:

1) When the train initially departs its originating station.

2) When the train ends its run.

3) At any register stations.

Otherwise it’s most efficient to leave the trains, and crews, to their own devices. Generally at meets an OS is not important**.

In any case, within minutes of using this post-it note system, I knew we had solved that problem. On AIR1 we never had another problem with OS’s, with regard to transmitting them to the DS. I put some lipstick on this pig by printing small slips called “OS Reports” with the vital information requested,  pre-printed on the slip:

1) Train Name

2) Location

3) Time

All crews had to do was fill in the blanks. SIMPLE!

You’d be surprised how many operators think none of that is necessary! (We got tons of slips with just the train name written on them, or even better just a time, but no name or location.)

Additionally OS-ing is a bug-a-boo on a lot of layouts. Most often trains do not OS leaving dispatchers in the dark.  Other times they OS to often.

On AIR 2 I hope to slay the biggest demon on TTTO layouts, IN MY OPINION, the Operator position. Unfortunately like the hydra, you cut off one head, another pops up. Without an operator who will transmit the OS’s to the DS?

Currently my simplest solution is to have the DS walk the twenty feet from his desk to a point where a OS Slip collection box will be located. 

The most expensive solution is RFID scanners at T.O. Stations***. The computer geeks out there really like this idea. An RFID tag on the engine and caboose can establish direction of travel as well as identity. Me, I’m not so sure. 

I will concede that NEARLY any cost is worth it to me to get rid of the operator position, and those mind-numbingly wasteful, and traffic slowing,  Train order dictations and read-backs! 

Whenever would-be dispatchers suggest I add a SECOND operator position I become apoplectic!

Initially when AIR2 does start operations, it will be a OS’s slip in a box that we begin with. It works really well.

How do you transmit OS reports to your dispatcher? Are you experiencing a bottleneck because of too many os’s for the DS to handle at times?



*An OS is, to oversimplify, a report from the train crew to the dispatcher of their position. Dispatchers like to know where you are ALL the time, so they can micro-manage the traffic flow!

**Dispatchers who require an OS for a meet are actually doing a poor job IN MY OPINION. And every dispatcher who REQUIRES these OS’s will argue ad nauseam how import these OS’s are. 

***T.O. Station is short for “Train Order Station” where orders are transmitted to train crews, and OS’s are generated and transmitted to Dispatchers.

Comments

Popular posts from this blog

Wingedfoot Paper Part 2: Pulpwood

Freight House Operations: LCL and Freight Houses

Freight House Operations: LCL from Foreign Road Freight Houses