开云体育

Hi,

I am a novice user of OperationsPro (OP) and an intermediate user of CATS.? I?have used the latter to dispatch several operating sessions now, but I am just in the process bringing OP into the mix.? I have sorted out how CATS and OP can communicate session progress at run time (OP reports train data to CATS and CATS reports train progress to OP) and I would like to use that capability during a session to manage progress.

As I prepare for my next session, I am looking for recommendations on how to manage the building of trains in OP while being able to exploit the run time capability noted above.? My preference would be to have all the trains built in OP in advance, print the necessary switch lists, then reset OP to the beginning of the session so that it can communicate the proper real-time info to CATS (such as train length at departure).? I feel it would be too hectic to try and build trains & print paperwork in real time.? One complication is that some trains in the session depend on earlier trains having completed their work, so they cannot be built until the earlier trains have terminated (if I understand OP correctly).

One idea I've had is to take a pre-session snapshot as a backup, build, print, and terminate trains for the session, then reset with the backup.? I think I would still have to re-build the trains as the session progresses, but having gone through a "virtual" session beforehand, and having the lists printed in advance, I think that would be manageable.? I welcome any suggestions, as I may be missing an obvious and better solution, for example using Save Builds, but I'm not seeing it now.

Thanks in advance,
Gary

What about using automation to automatically build trains and print out the necessary paperwork? One thing I’ve been experimenting with of late is starting with just four trains built and, as the op session progresses (I use web server to view the switch lists, move, and terminate trains) the automation will automatically build trains. Some trains are only built after one train terminates and other require multiple trains to terminate before building. One of the automations handles cars into and out of staging as well.?

Sam

Oh, I like the idea of automating the dependent builds.? What I really want to avoid is for a human to have to manually manage too many support tasks during a session, since things can get pretty hectic, and we don't always have enough people to manage support roles like that (and we keep our dispatcher pretty busy with lots of through traffic).

During a session, we have numerous through trains that simply run staging to staging (with lots of meets en route).? Those can be built ahead of time with no issues, and CATS can communicate their progress to OP (but OP rejects those messages if I terminate them ahead of time).

For the modest number of trains with online work, terminating one can trigger an automatic build/print of all dependent trains with minimal human intervention.? I'll give that a try.? Thanks for the suggestion. :)

Gary

I'm responsible for my layout as well as 3 others. I've incorporated automations into all of them so there is less "human" input when the JMRI input is needed. But remember, if train 1234 is at your main class yard, the cars are not available for another train until train 1234 leaves. I've added a lot of things into the other layouts so the building of trains and the creation of the paperwork is all choreographed with the movement of the JMRI train icons on the JMRI dispatchers panel. Using CATS is only done here on my layout. But the automations are still the same. The need to think how the program sees the availability of cars is a must for great car movements. When a train arrives into a class yard, just have the automation move that train and the next automation can now create a new one with the cars in that class yard made available for the build.

later

Dave
Trempealeau WI

Thanks for the input Dave.? I do think automation will accomplish what I'm after, though I have yet to implement it.

We had a session yesterday where I ran through the lineup in advance in simulator mode and printed out all the manifests, then reset the layout to the pre-session state for the actual session.? During the session itself, I did not manage to keep up with the real-time builds very well (without automation) but since we had the paperwork in advance, it was not much of an issue.? I think I see how to get where I want to go though, and it seems like a fun journey.? :)