Skip to main content
Early beta
ModuOps version 6 is in early beta. Anything you do in it may be lost or may not be compatible with the final version. Don't rely on it for anything you can't afford to redo.
Version: Version 6 (preview)

Getting to Know ModuOps

ModuOps (pronounced 'mod-you-ops') was initially developed with Free-mo Operators in mind, but it’s evolved to meet the needs of all types of modular layouts. It’s been shaped by feedback from clubs and home layout enthusiasts alike, making it a versatile tool for anyone interested in adding operations to their model railroad.

A modular Free-mo layout stands out in several ways:

  • Each setup is completely unique.
  • The layout only exists for a day or two.
  • It will never be recreated in the exact same way.
  • The starting state of the layout is unknown.
  • Crew mistakes happen but should fix themselves as operations progress.
  • Managing rolling stock can be tricky and prone to errors.
  • ModuOps is built based on the characteristics of the Mad River and Big Timber (MRBT) software, and this guide explains some of the design choices behind the app. Many of its features stem from experience with MRBT and New England Free-mo, shaped by the challenges these setups face.

The ModuOps Difference​

ModuOps is a random car type generator. The software essentially takes a list of car types and randomly assigns them to locations on the layout. Using car types IS the significant difference ModuOps offers.

The strict rules associated with reporting marks adds significant effort to an Operating Session. The administrative overhead to maintain car reporting marks takes a tremendous amount of time. In fact, the time invested in this task alone typically exceeds the life-span of the layout by many factors.

Best Practices​

ModuOps requires a sourcing yard sending cars to Consignees. Large layouts can be split into Districts with regional yards acting as the source of cars for an area of the Layout. It is even possible to simulate transfers between yards by making the yard itself a Consignee.

ModuOps currently offers 3 scheduling engines, the original MRBT random engine (each request has a 1/n chance of selection), a weighted selection engine and the new Pull & Drop Ops engine.

The weighted selection uses a demand number given to requests. In addition to the weighted selection, it is possible to skew selections to facilitate car blocking.

The random and weighted selection engines are Stateless. That means that the system does not store any information about the past, present or future state of the layout. These engines are based on MRBT's original flow where all traffic originates at a yard and travels to a consignee. It is important to remember this sequence when creating operating plans.

Pull & Drop Ops​

Version 6 introduces the Pull & Drop Ops engine. For the first time, ModuOps is no longer Stateless. The engine remembers what car types have been dropped at each drop zone and schedules those cars to be picked up on a later train. Consignees can be marked as a producer or a consumer, so the engine also tracks loads and empties. Think of it as a car card system using car types, with no cards to manage.

Pull & Drop Ops still does not need the layout to be setup in any particular manner. The first time a drop zone is worked, the crew is instructed to "PICKUP ALL" which puts the drop zone in a known state. It repeats every few visits, so mistakes don't build up. Mistakes still fix themselves as operations progress.

Trains leave the yard at their target length. When the usual pickups wouldn't leave room for enough set-outs, the engine adds pickups, oldest car first, until the train is full. A whole day of runs can be generated and printed in one batch. See Trainlists.

The trade off is a bit more overhead. Trainlists are numbered and need to be run in sequence. See Trainlists for the details.

Home Layouts​

ModuOps works GREAT with home layouts. In fact, there are quite a few home layouts switching from car cards to ModuOps for formal Operating Sessions. Many of the concerns that Free-mo Ops Chiefs have transfer directly to operations on a home layout.

In fact, a home layout is the perfect place to start before diving in as a Free-mo layout Ops Chief. Most home layouts are smaller than Modular Layouts. Starting with a small layout allows you to learn how ModuOps works.

Club Layouts​

ModuOps is an excellent choice for static club layouts. A great benefit of ModuOps is there is no setup required for an ops session. This gives clubs the flexibility to have host formal operating sessions as well as open "free running" sessions intermixed. ModuOps does not care what state the layout starts at or is left in. An operating session can start at any time no matter where cars are on the layout.

Contacts​

ModuOps has an email list hosted on groups.io.

There is also a group on Facebook.

If you need to reach me directly best way is bhall underscore 2001 at yahoo dot com. Hopefully you can figure that out ;-)

How Much?​

Good question. Developing a software such as this does incur costs. I've invested time in training, development tools, the website and time in writing and maintaining the application.

ModuOps is Donation-ware. If you feel compelled to donate, please contact Bob Hall for details on how to make a donation. Thank you!