开云体育

I want to send a train of loaded coal hoppers from staging to a classification yard. Then, move those cars on a yard local to various industries. I want the yard local to pick up empty coal hoppers at those same industries and bring them back to the classification yard. Finally, send those empty coal hoppers on a third train from the classification yard back to the staging yard. All in the same operating session.?

?

I tried it this past week at an operating session by building the first train, printing the manifest, and then moving and terminating the train.? Then I built the yard local and repeated the same build/print/move/terminate process. Then I built the third train and printed that manifest. I put the three manifest copies in the stack of manifests used for the session, in the proper sequence.?

?

I also printed the switch lists after each build to give to the two yard masters.? ??

?

It's a lot to do and can be confusing to the yard masters. Is their a more elegant way to accomplish all this through Operation Settings, or thr Cars or Locations tables?

?

John P.? ??

John, for the SwitchList, at the Club, I always reset my Switchlists at the beginning of a session, then each build will add to it.? Only after all trains are built do I printout the Switchlist. So, each Yard has just one SwitchList and all the trains through the Yard are listed with all the cars.

?

I use Automation in my building of trains, and with 28 trains to be run in an Ops Session, I separate them into four lines (actually 5, but the first is just to build and reset some trains to eliminate all Waits).? Arbitrarily named group A is the first group where I build 12 trains, update my SwitchLists (four Yards), then terminate seven of the trains that have been built.? In group B (second group), I build seven trains then update the SwitchLists, then terminate eight trains (some from group A, and some from group B).? My third step builds seven trains then updates the SwitchLists, then terminates? 11 (all unterminated trains from group A, group B, and group C).? The last step builds two and terminates them (of course, after updating the SwitchLists).? I do this to carefully control when cars are available for the next train, which is as soon as the train that they are assigned to gets terminated.? So for example, if I want a train in group B to pick up a car from a group A train, I have to terminate the A train before building the B train.? However, if I do not want a B train to pick up a car assigned to an A train (usually because the A train wouldn't yet be at the Yard where B is being built), I build B before terminating A.

?

Incidentally, after an astute YardMaster showed me how he planned his Yard moves by looking through the SwitchList for any car that is on more than one train, I came up with a tool to use.? I designed an Excel spreadsheet that takes the SwitchList and sorts it by car number, time and train, then sorts it back to train order with notes ("Out on #45", and "From #89") to help the YardMaster be more responsive to cars that need to be sorted out of an incoming train to go out on another train.? I included three macros to do those steps. The screenshot below is from one Yard so the YardMaster can see that train 72 has four cars that will need to be shuffled immediately and the others can go to a storage area for next session

?

Phil