Been working with OpsPro to learn the finer points of combining locations, routes and trains to get the car movements I want. As a single operator, I wanted to make sure I have a structure to operate my layout while giving me flexibility in how I complete a cycle that includes interaction between multiple trains to serve all locations on my layout. I am looking for feedback on ways to improve my strategy and to correct any errors I have in my game plan. Sorry that this is rather lengthy but it was necessary to describe this in a way I hope others can understand.
My layout has a mainline plus multiple locations (with spurs) where each location has a separate nearby location (siding) to support the exchange of cars with a mainline train. Mainline locos do not go beyond the sidings¡. only switchers operate beyond the sidings. This means that I need multiple trains and routes to move cars to the various locations like I want. After reading the OpsPro documentation and several tutorials I have found on the web, I think the following is what I need to achieve the car movement I want.
Assume I have a mainline with a mainline train (Train-B with Route-B) that is attempting to pick up and deliver cars to a location (City-C) that is a set of spurs on a lead departing from a siding (Siding-S with a C/I track) on the mainline. The mainline siding is a named location (Siding-S with a C/I track) where the car exchange (pick up & drop as needed) is made between the mainline train and the location City-C. The locations City-C and Siding-S are served by a switcher loco (Train-A with Route-A) which will move all the cars as needed from the Siding-S to the correct spur at the location at City-C. To make sure all cars are moved and tracked by OpsPro so their locations are properly documented, I think I need to configure routes and trains as follows.
Step 1) ¡°Build¡± Train-A which uses a switcher to pick up appropriate cars at City-C and position the cars at Siding-S for Train-B to pick up. Train-A only serves locations Siding-S and City-C. Train-A would visit each City-C spur to pick up cars that need to move to Siding-S so that the cars are available for the mainline Train-B to pick up when it arrives at Siding-S. ?When all Train-A ¡°moves¡± are done and train is terminated, the appropriate cars that Train-B needs to pick up will be ready and sitting at Siding-S.
Step 2) ¡°Build¡± Train-B to include a visit to Siding-S to pick up and drop off cars as needed to/from City-C. When Train-B ¡°moves¡± from location Siding-S, Train-B will contain all the cars it was supposed to pick up from City-C and the Siding-S will contain all the cars Train-B dropped which are destined for City-C.
Step 3) ¡°Build¡± Train-C which uses a switcher to start at Siding-S and move the cars (dropped by Train-B) to their appropriate location at City-C. When all Train-C ¡°moves¡± are done and train is terminated, all the cars destined for City-C will be positioned at their proper spur and OpsPro will know where they are.
As I understand it, I need to ¡°build¡± and then execute (move) the trains in the following sequence. Since I have multiple siding and locations that are served by the mainline train. Here is how I would expect to deal with that.
1)???? Build a Train-A for each siding/city location. Must build a train for all locations served by the mainline BEFORE step 2 below. This will ensure that all cars to be picked up by the mainline train will be in place at the appropriate siding when OpsPro builds the train for the mainline.
2)???? Build the mainline Train-B (OpsPro will assume that all the Train-A¡¯s have made their moves and cars are waiting for Train-B at Siding-S)
3)???? Build a Train-C for each siding/city location to move cars from Siding-S to correct spurs at City-C (OpsPro will assume the Train-B is done and has delivered cars to Siding-S)
4)???? Execute (move) all Train-A movements for each siding/city location. Can be done in any operational sequence desired but car movements to each siding must be completed BEFORE mainline Train-B departs (moves) from the Siding-S. Operations approaches could include combinations of the following:
a.????? Operator makes all Train-A moves at each siding/city before Train-B even starts. No further action required until Train-B arrives at Siding-S
b.????? Operator make Train-A movements ¡°just-in-time¡±. When Train B arrives at siding, the Train-A makes all its moves to bring cars to the siding. Then all the pick up & drop action would occur and Train-B is free to ¡°move¡± from the Siding-S.
5)???? Execute (move) Train-B along its route from siding to siding. Pick up and drop cars per manifest then move to next siding on route.
6)???? Execute (move) Train-C whenever I am ready but must be before another session which would cause me to ¡°build¡± Train-A again. ?Cannot build another Train-A until Train-C has finished moving and properly placing all cars in Train-C. This creates a new starting point to build the next Train-A.
I think it could easily take several hours for me as a single operator to make a complete cycle. I think the above 6 steps will allow me to suspend my session at any place in the actual operations portion.
If you read this far, thanks and I welcome any feedback on what I stated out above.
Paul Davidson