Methods?

Have you chosen what methods you will use for train authority (what trains get to run when) and car forwarding?

Design for Operation - Track Plan

One of the primary goals of my model railroad is to have several friends over on a regular basis for an evening of enjoyable railroad operation.  I currently operate on another friend's railroad, and our operating crew has had a ton of fun over the past decade or so.  That layout is larger than mine and supports about 10 operators.  After many design changes and considerations, I hope to support about half of that, or 3-4 operators, plus me.

A review of my final track plan is probably in order here, since it changed several times during development.  The layout is basically a coal branch with three towns, Nicholas, Ashley Creek, and Angela's Landing.  Nicholas is the major town, and serves as the connection East to the C&O at Meadow Creek (staging) and west to the NYC via Swiss (staging).  West staging also serves as the "online" town of Jamestown WV.  Finally, a log branch extends from Angela's Landing to a logging scene on the second level.

Level 1 (staging beneath Nicholas)

Level 2 - logging branch

January 2018 progress (Nicholas with staging underneath)

Prototype Influence - NF&G and Greenbrier Subdivision

In designing my layout and planning my operations, I looked primarily at two prototype lines, the Nicholas, Fayette and Greenbrier in Nicholas County, WV, and the Greenbrier Subdivision of the C&O, serving Cass and Durbin.  Most of what I am freelance modeling comes from the NF&G.  On my railroad, Nicholas = Rainelle, WV., and the NF&G actually interchanged with Meadow Creek (C&O) and Swiss (NYC).  The NF&G was jointly owned and operated by these two railroads, with the C&O having the major presence.

However, I am not trying to model the NF&G, but rather use it's physical plant and operations as inspiration.  I studied the trains it ran, and also the trains run on the Greenbrier Sub, and used this to plan my own operations. A preliminary list of trains included coal turns, eastbound and westbound coal, eastbound and westbound freight, local freight, and local passenger, along with logging trains.  To this I can add through trains if necessary, but I doubt it will be. 

Here are a few inspirational shots of the NF&G in operation, courtesy of the C&O Historical Society, of which I am a member.  I highly encourage people to join their prototype historical society, if available.  I can't even begin to list what I've learned as a member of the C&OHS.

Methods - Switchlist

@Dave - excellent question.  I've been considering operating methods for many years now.  It started back with Tony Koester's articles in MR and I've been planning ever since.  In fact, I got so much in my head I could hardly make a decision, and I'm still riding the fence in many ways.  But . . . I finally decided to go in a solid direction and later I can always "choose to re-decide" as my Mother likes to say.  Thanks, Mom!

I've chosen a program called Switchlist for the Macintosh to design and run my operating sessions.   http://www.vasonabranch.com/railroad/switchlist.html  Why did I chose this over other options like car cards and waybills, TT&TO and CTC, or JMRI Ops?  For me, Switchlist is a good fit because:

1. It is simpler and easier to set up than JMRI Ops.
2. It generates car movements based on consignee/shipper information so it is realistic, not just random.
3. It is designed for a small to medium sized layout and matches how I want to operate.
4. The switchlists and reports are customizable.
5. If I ever choose to use Car Cards (my other choice) I can use the information from Switchlist to develop the cards.
6. Robert Bowdidge, the software's author, provides FANTASTIC support.

Here is a sample of a switchlist for the Westbound Freight

Methods - Sequence Operations

I've settled on a sequential operation scheme to control what trains run when.  I've split the defined trains into AM and PM.  I can run these by myself, one at a time.  Or, when I have more operators, I can start the day off with the first two or three trains.  As these finish, the dispatcher (probably me) will determine when the next trains run based on the pace of the operating session.  Or, if we want, we can add times and a fast clock to determine train start times.

Below is a list of the current trains listed on my train order board.  So far, this is working great.  I can go down to the train room and run a train or two at any time.  The board tells me what to run next, and the trains are purposeful, not just random roundy-roundy.  Switchlist tells me what needs to be done in each train.

you need a timetable

and it keeps the passenger trains out of the cornfields

Train ops

With the sequence operations you don't exactly need a timetable, but you might want to have one as a "handout" for visitors.  If you ever do have TT&TO ops, you'll need one.

If you have a head on collision between passenger trains, I'd like to see that since it looks like in each session you have a passenger turn, the WWD train becomes the EWD train back.

While I understand your list of AM-PM trains shows the "order" of the trains and so may be a "train order board", there is a real thing called a train order board and that might confuse people who know about TT&TO, a term for what you have is a "line up".  If you decide at some future time to revise that, you might want to consider calling the sequence board al "train lineup" or "line up of trains".  Minor point.

Looks like you have the operations pretty well set.

Now its time to throw in an extra or special train.

Following

Michael;

Without getting into my own influences I am keen to read your thought process and how you work with “Switchlist” for the Mac. The idea of a timetable appeals to me simply to plan meets and set priorities. Trains can always run 12 hours late and others proceed under the dispatcher authority. Since that is just you (or me in my case) there would be no need for any paperwork or verbal authority. Of course you can talk to yourself if you want ...

you still need a timetable

Sequence Operations

Much like your RR operations method, I've opted for sequence of trains on my Hawks Nest Subdivision RR (also a member of the C&OHS) with a mix of a few mainline trains and branch line trains.  I was able to setup JMRI ops to control car routing the way I wanted (it wasn't easy and took some time to find tricks to make it work right).  The switch lists were customized to look like the C&O conductor work orders and are easy fo follow.  A max of 3 operators can run the RR - usually its just me and the sequence approach works out very nicely.

I'm following your train of thought on this process as it has many parallels to my situation.

Rick G.

@Rick

Sounds like you are running very similar to me, which is neat to hear.  Do you have a sample of one of your switch lists?  I've not seen a C&O Conductor work order and I'd be very interested in that.  I hope you're having fun running your railroad!

More Responses

You are correct in your assessment of my passenger train.  Indeed, the WB becomes the EB becomes the WB.  That's how the NF&G ran it in my period, from Rainelle to Johnstown in the morning, then back through Rainelle south to Meadow Creek, then back to Rainelle in the evening.  I plan to include a run up the branch to Angela's Landing too, once I have that portion of the railroad built.  It's all still stick benchwork now.  Also, thanks for the "Line Up" suggestion.  I like that and may use it.

Thanks for your observations on timetables.  I agree with the need for the timetable, but maybe not for my operators.  I'll post some more paperwork here soon to show how I plan to handle that, although since I'm still running solo it's all just ideas for now.  As a preview, I'm currently thinking that the dispatcher (me) will decide when trains can leave stations, and he will be responsible for knowing what trains are on the railroad and giving clearance.  Later, if I have a regular, experienced crew, I might run a fastclock with a timetable, and have times that trains can leave stations.  But I don't want to get too complicated with the paperwork, because I think my operators wouldn't like it.  They're pretty relaxed guys, and they like the KISS principle.  We'll see as time goes on, and that's one of the main reasons I started this thread.

I'm glad to see you're following along.  Stay tuned, as I plan to describe how I set up and use Switchlist in some detail.   

Conductors reports

First a correction, the reports are actually called a Conductor's Work Report (sorry).  They are sort of a detailed time and activity report and focused on mine runs.  I found a collection of nearly 300 of these from September 1965 and used them for the basis of an article in the COHS magazine (September 2016 I think).  There is a lot of interesting information one these.  One thing I did find, is that foreign road cars handled are generally listed by number and sometimes car seal numbers.  C&O cars are shown only by load/empty, capacity and counts.  I also found info on cars heading to/from the NYC (NF&G).  A sample is shown here.  One day these will be transferred to the COHS archives in Clifton Forge.

I'll post a sample of one of my switch lists from JMRI when I can.

Rick G.

More Simple

Michael,

I too am a believer in the "Kiss" method...keeping things simple. Our layouts have a lot in common, but I see our operating paths is where we differ. 

I use sequence schedules on my layout, but have a separate one for the coal trains and the merchandise freights. That's not prototypical, but it sure works well on my layout! When I'm operating solo, I choose if I want to run a coal train or merchandise freight, then go to the appropriate sequence schedule to see which train will run next. That makes it very easy to pick up where I left off. This sequence schedule hasn't been been tested much with multiple operators yet, but I have a feeling the flexibility it allows will let me pick which trains I need/want to run next with crews. 

For dispatching, each train crew receives a simple train order at the beginning of their run telling them where their particular train goes and what it does. As dispatcher I keep an eye on things and let crews know if they need to hold at a siding, need to clear the main, speed up or slow down for a meet, etc. It's kind of like simple Track Warrant orders. Again, it's not strictly prototypical, but there's no paper work, and lets everyone have a lot a fun. 

Car movements are taken care of by simple car cards and waybills. No need for printing switch lists, manually staging cars, or updating software. Again, I just pick up where I left off from last session, and everything seems to run smoothly. 

Though I like to run in a prototypical fashion, I don't want the "work" the real railroads had to go through. That's not to say what you are planning is bad. It's not. It's just different. But it seems to suit you, so that's great! Enjoy your operating adventures!

Like the layout, your leading

Like the layout, your leading picture, too. Nice theme/era/etc.

I always find interesting things to glean when reading how other folks operate their layouts. This thread likewise.

Thanks for taking the time to share!

I'll be following along, too... IF I can find it again once it falls off the "Recent Blog Posts" menu!

Andre

Timetable and Line up

Here is the timetable I used in my last session.  It combines both a timetable and a train line up, plus special instructions, its on one page.  The trains that will NOT run on the op session are greyed out.  The portion between Trap Rock and Valley hasn't been built yet so no times are shown.  Reading and Birdsboro are represented by one staging yard.  Since I haven't had time to renumber all my engines, there are several NYC engine running around (they are black with yellow lettering, so they fit in nice).  The arrangement is based on a prototype P&R timetable page.

Updates

Glad to have you following along!  Now that you've posted on this thread, you can click on My Account and then the Track tab.  It will show you every thread you've posted in, and whether there are any new posts.  It was a while before I found that, but now I'll often just post a "I like this" entry on a thread I want to follow, so it shows up here.

I really like that timetable.  At first glance, it seems complicated, but after a couple of minutes it makes perfect sense.  I especially like how you incorporated the train Lineup and Tonnage Ratings.  I'm finding that's going to be important, especially if I send smaller engines through the helix. This is what I had in mind for later on with my railroad, so I may "borrow" from your design.  

Once again, our ideas are very similar.  I see my operating sessions going just as you describe, with me acting as "track warrant officer" telling people if they need to take the siding, or wait at the station until such-and-such train arrives, and deciding when to release trains to keep the pace right, especially extras. 

This is how we run on the Stinky Creek.  Westbounds are superior, and people just call out, "anyone coming westbound?  I need to go over the mountain."  It's not prototypical, but it works great and everyone has fun.  It's especially fun when someone forgets to ask and there's a mid-mountain meet, and we have to negotiate who backs up!  That's prototypical!  In the early days of railroading, it was often decided by a fistfight between engineers! 

N&AC Operations Map

Here's what I had developed to give my operators.  At the top is a map of the system, showing East and West, and all stations in between.  I used actual C&O Operating Rules, and listed only the ones I plan to use.  Basically East is superior to West, wait for clearance from the dispatcher (me) before leaving your originating station, re-align switches for the main, watch the signals and blow the whistle.  

Now I'm thinking I'd like to add to this a simple Timetable like Dave's, with the train lineup too.  I'd print that on cardstock in a foldable format like the C&O used, and it would fit in your pocket.

Conductor's Clipboard

I plan to give each operator a clipboard with the following:

1. A train card describing what their train will do
2. An engine card showing what engine they will use, and what function buttons do what (for sound)
3. The system map shown in the previous post
4. The switchlist for the train
5. A velcro spot to attach a throttle, if desired
6. An uncoupling pick
7. A pen for making notes on the switchlist

Here's the clipboard I'm using at the moment.  I hang it on hooks on the fascia.  You can see where the system map is in a big sleeve, so I can update and replace it as necesary.  The train and engine cards fit in smaller pockets.

Rules

A couple notes on the rules you have quoted because they affect operations.

The first three rules (71,72, 73) are generally called "superiority of trains".  In order to use them you will need a timetable because class and direction are conferred by the timetable.  Extra trains do not have "class" and have NO superiority by direction, rule 72 doesn't apply to extras (they don't have "class").  Normally superiority by direction is handled by a "special instruction" in the time table, not a rule.  That way you can vary it by subdivision.

As a side note, CTC supersedes the superiority of trains (they don't apply) and track warrants don't include it.

Rule 83 has been paraphrased which has changed its meaning from the way the prototype uses it.  Traditionally the rules say a train must obtain a clearance before leaving its initial station.  Subtle but significant difference.  Obtaining "a clearance" and obtaining "clearance" are not necessarily the same thing.  "A clearance" is a piece of paper, "clearance" is verbal authority.  The prototype says "initial station" (one station), your rule says "its station" (every station).  If I was operating with those rules I would talk to the dispatcher at Angelas Landing, then stop at Coal Creek and call the dispatcher, then stop at Ashley Creek and call the dispatcher, then stop at Charmco and call the dispatcher, then stop at AC Cabin and call the dispatcher, then stop at NC Cabin and call the dispatcher.  Even if I had a running order or a clear signal, I would still stop and call because rule 83 says so.  That may be what you intended, so its not wrong if it is.

On the prototype you need a clearance at the initial station to make sure you have all the proper orders starting out and then get a clearance any place there is a "stop" train order for the train's direction.  Under CTC you get a clearance at the initial station and only need to talk to the dispatcher if you want to do something different or have a question about a stop signal.  With track warrants you get the equivalent of a clearance at the initial station and then talk to the dispatcher when you get to the end of your limits.

Rule 30 might have a typo, "the bell must be run" vs "the bell must be rung".

Train and Engine Cards

To assist operators, I've developed train and engine cards. 

Engine Cards - The engine cards show the locomotive photo, and include information on the DCC Address, and what all the function keys do for that locomotive.  This is not as necessary for WiThrottle, as the buttons are labeled.  But for my traditional wireless throttles like the UT4R it's helpful.  The engine cards are placed in boxes for the roundhouse, yard tracks or staging tracks, based on their location.  There's also a spot at the top of the switchlist to indicate where to find your engine at the start of your run.

Train Cards - Train cards give basic instructions for how to run a train.  Looking at this example, they can be improved.  For example, they could say "Proceed Eastbound" to indicate what direction you are going.  Any other ideas?  This is definitely a work in progress, as most trains just come and go from staging right now.  Later, they might say something like "Proceed to Angela's Landing and switch industries.  Request clearance from dispatcher before returning to Nicholas."

Like What I See

Those cards are very nicely done and should greatly aid operations, especially for new operators!

Train cards

I have very similar cards.  The following isn't criticism, just discussion on options.

Since your rules mention "class" and "extras", you might want to add class or extra to the description.  Caveat, if you make them a regular train, then you should give them a schedule.  You don't need schedule times at all stations, just the junctions and passing sidings.  Passenger trains are usually first class, priority freights are 2nd or 3rd class, drag freights and locals (or scheduled coal turns) are 3rd or 4th class. Irregular coal runs are usually extras.  You can also run trains scheduled one way and extra back.  That's handy if you have irregular working times.  You can control when the yard starts it (scheduled train) but don't have to worry about when its done with its work to come back (extra train).

You can abbreviate direction as "xxxxward", EWD, WWD, NWD, SWD.

You can regionalize the terms set out vs drop, pick up vs. lift based on what your area used (you may have already done that).  You can always tweak brevity, "P/U EWD cars per Yardmaster". 

You say "Proceed to....", do I just go or do I have to talk to somebody or get some permission first?  Is the train card saying I can proceed authority to go?  You can also eliminate the "Proceed to..." line by just listing the next station or junction where the train works.  If you list Swiss, NY, Nicholas, WV, and Meadow Creek, then instructions to "proceed" or "continue" to those locations may be superfluous, since they are your next stop, its implied that you go there.  That can buy you a line that allows a comment on how you are to proceed.