Gaining access to the switch list output format is from the trainlist screen. Switch lists are added to the output format menu as an option. Once selected, click the Generate Trainlist button. A thumbnail of the generated switch is displayed. Click the Print button to print the switch list.

Required fields​

ModuOps switch lists use 2 fields that typically have not been used in the past. Both of these fields must have data in them or the switch list will not display any information for the items when printed.

Equipment AAR code​

On the equipment screen, be sure that all equipment has a value for the AAR code field. This is the field that is displayed on the switch list when printing.

If you are not sure how to determine the AAR code for a piece of equipment, the Opsig group has a handy reference for AAR codes that you can see by clicking here.

Drop zone reference​

On the drop zone screen, be sure that all drop zones have a value in the Zone reference field. This field is displayed on the switch list when printing.

Switch list form details​

A switch list is printed in 2 columns. The first column is the ModuOps switch list form. The second column contains information about the work the crew will perform. The printed sheet is intended to be folded in half lengthwise.

Switch list header​

The switch list header displays the layout name. This is the name field on the Layout screen.

The header has a blank space to enter the date of the train's operation. Below this the train symbol is added to the switch list along with a space to write the time the train starts the job.

Switch list fields​

Each row of a switch list contains fields needed for the crew to perform the job. When a new module/town is on the train's route, the module/town name is displayed in the middle of the row. All the entries below this are intended for the module/town specified.

When a car is to be switched, the yard crew will have written in the reporting marks in the first column. The reporting marks should be entered such that the road name initials is entered in the left section of the column with the equipment number entered in the right of the column.

The column labeled Kind details the equipment needed. The equipment is specified as the AAR code followed by the length (ie. XM-50 for a 50' Box car).

The From column indicates where the equipment originates from. Currently this will only be the originating yard of the train. The Switchlist indicates a repeated previous value in this column with the text '' indicating that the previous value remains unchanged.

The Dest column indicates the drop zone the equipment is to be set out at.

Crew instructions and reference​

The 2nd column of the switch list provides crew with information about the work they need to perform. The header details the train information including the name and symbol as well as the number of cars and length.

Any special crew instructions are added to assist the crew in performing their job. This is information taken from the train's crew instructions as well as remarks for the module/towns and consignees they are working.

A handy reference is provided for the equipment on the train. This is a cross reference of the AAR Code to the equipment's description.

Crew will also find a reference for the drop zones they will be working to assist in setting out equipment to the correct zone.

Crew convenience​

To make it easier to carry a switch list around a layout, fold the switch list in half vertically. We find that the narrow sheet of paper is easier to manage when operating a train than having a full sheet.

Switch list FAQ​

When I print a switch list there are no equipment or drop zones listed​

Switch list uses 2 fields that previously have not been used. If a switch list prints and there is no information displayed then you must enter in the required data for the switch list to render properly.

If the Kind column is blank, return to the Equipment edit screen and add AAR codes to equipment.

If the From or Dest column is blank, return to the Drop Zone edit screen and enter a drop zone abbreviation in the Zone reference field.

Where can I find AAR codes?​

The Opsig group has a handy reference for AAR codes. You can find the reference by clicking here

Another option that we find works quite well is to use an online AI tool such as ChatGPT or Microsoft Bing Copilot. Simply type in something to the effect of "I have a model railroad that I need AAR codes for operations. What is the AAR code for an insulated box car?"

Is it possible to print more than 1 page of a switch list?​

Currently switch lists will print only 1 page. You will need to modify either the length of the train or limit the number of modules/towns a train services until the work fits on a single page.

Printing a switch list as an option on the trainlist screen. The switch list format is ModuOps spin on a prototypical switch list that leverages key information within ModuOps to assist operators.

A switch list details car type and where a car is moving from and to. Yard crew enter reporting marks on the switch list when the train is assembled in the yard.

The switch list displays information for the crew including remarks for the modules/towns and consignees they are working. The switch list also provides a handy reference of AAR codes and drop zone references to assist while working the switch list.

There is a new Layout screen, the Modules/Towns screen is redesigned, ability to easily add and save modules/towns, bug fixes and ui fixes. Check out the release notes for details.

Release Notes

Along with this release I've also spent a lot of time updating the online documentation. Finally the docs are at a point where they are a useful resource. There are still some things that I would like to add but overall we now have something that I hope can be used to answer many questions.

Read the new ModuOps Documentation!

And one more thing...

ModuOps is a bit cumbersome when it comes to setting up new modular layouts. Most of us kept a large reference file with all possible modules already in the file. This posed a problem because it was impossible to tell what equipment was needed for a layout and when setting up routes on trains, having every module as a selection made it difficult to find and remember only the modules needed for a layout.

ModuOps version 5.4.0 addresses this with the addition of an Add button on the modules/towns screen. Modules can easily be added to a layout. Now you can have only the modules you need in a layout file.

But we are missing one last piece to the puzzle. A central place to go to where you can find the latest version of modules to include in a layout you need to setup. Sure you could keep all the layout files on your local hard drive. But you'll miss out on any updates made and will not have any of the new modules created since your last setup.

I'd like to introduce the ModuOps Xchange, an online global storage repository of modules. The Xchange is intended to be the resource where you can turn to find any module you need for a layout, hopefully any where in the world. A lofty goal but I hope we can make this happen.

The Xchange is a resource that I hope makes setting up new layouts a breeze. Now Ops Chiefs can simply add modules needed for a layout from the ModuOps Xchange. With only the modules needed for a layout in the file, you can easily see the equipment needed as well as easily create train routes selecting from only the modules that will be in the layout.

Right now the ModuOps Xchange is a shared Google Drive. You can mount the share to your Google Drive and have access to the all the modules in the Xchange. If you'd like to add/update modules in the Xchange, save each module on the Modules/Towns screen and email the module files to me. I'll get the modules added into the Xchange ASAP.

For details on how to add the ModuOps Xchange to your Google Drive, see the docs on the ModuOps Xchange!

Wow! Like I said, the biggest minor update EVER in the history of ModuOps!

Worldwide Module Repository​

The Xchange adheres to international conventions for locating geographical regions worldwide. My vision is to create a global community where ModuOps users can seamlessly share their modules.

As an Ops Chief, you can effortlessly integrate modules from the Xchange into your layouts.

Easy Access​

The Xchange significantly reduces the administrative overhead required to set up a modular layout. By mounting the Module Xchange to your desktop file system, accessing modules becomes effortless. Adding a module to a layout is now as simple as incorporating it from the local file system into ModuOps.

Get more information on the ModuOps Xchange in the ModuOps documentation.

New data layer​

The User Interface looks the same as it has in the past. The under-pinnings of the app have been completely renovated. A brand new data layer is slid in on top of a sqlLite database. As a result you will see that opening a data file is significantly faster. When you use the app now everything you do is read/written directly to the database.

The notion of "saving" your data file has gone away. As you use the app, your data is updated as you go along. This takes a bit to get used to for sure.

NEW FILE FORMAT​

The data file is now the actual database for the app. Which unfortunately means that old data files are not compatible with the new version. There was no way to make the file formats compatible and for that I am sorry.

Not to worry. Files created with older versions of ModoOps (v2017+) can be converted to the new file format. The process is as easy as I could think of.

• select "Convert..." in the file menu
• step 1 will have you create a a new blank file in the new format, give the file a name and save it in a location where you'll be able to find it again
• step 2 is to locate your old .mop file on your hard drive and select it
• Viola! The old data is converted to the new format and is ready to use in the new version of ModuOps

If you have any issues converting your data file PLEASE REACH OUT TO ME. Email me the data file that you are having issues with and I'll see if I am able to convert it for you.

Trainlist screen updates​

Renaming schedule engines​

I decided to update the Trainlist screen a bit as well. As the app has gained more wide-spread use the scheduling engine naming is confusing. Very few of us know what it means to schedule like the Mad River and Big Timber software did.

You will see the Trainlist screen calls out the options for what they are, "Random" and "Use Cars/Week". The random option is just that, completely random based on the equipment needs all having a factor of 1 -- ie. all equipment needs are weighted as 1 unit. If a train has 10 potential requests, each item has a 10% chance of being selected no matter what the cars per week value is. Of course that changes if drop zones are full and cars can not be scheduled to a specific drop zone.

The "Use Cars/Week" option looks at the cars per week (CPW) defined for each equipment request resulting in a weighted random selection. This has the effect of statistically higher rates of selection for equipment needs with higher CPW values.

Drop zone favoring​

On the Trainlist screen is a new slider labeled "Drop Zone Favoring". The intention of this is to be able to increase the probability that the currently selected drop zone is re-selected for the next item of work going on the train.

The slider has "notches" from 0% to 100% in 25% increments. The default is set so there is a 50% chance of re-selecting the current drop zone again.

Why do you need this? Ops Chiefs will have the option to send larger cuts of cars to drop zones. If the slider is at "Never", trains will tend to have drops for more consignees with drop zone capacity trending toward less full.

On the other end of the scale if you select "Always", trains will tend to service fewer Consignees, have larger cuts per drop zone resulting in drop zones being near capacity.

Remember the system is using random generation for all this so your mileage will vary. In general you should see the trends described above. You'll have to play around with this for your setups to see what the right balance is.

New version numbers going forward​

I've decided to ditch version numbers that started with the year in favor of following a more traditional version numbering scheme. As a result this new version you'll find is v5.1.1. Why 5? Well I went back and looked at how many "major" prior versions we had. I came up with 4. So I made this version 5.

Speed​

Not that the app was all that slow in the past but I did put some effort into optimizing lots of things across the app. I'm hoping there's a sense the app is a little zippier.

Export module files now standard JSON​

I've changed the format of the export files to now be standard JSON. I won't go into what JSON is but let's just say it's a standard for storing/transmitting data that is relatively easy to figure out and can be edited with any text editor.

You do need to be a little careful about editing the files by hand so you do not create either a syntax error or some data that may not be valid. But, this should allow for easier exchange of modules between Ops Chiefs.

This change paves the way for an integrated, online module library.

Online module library​

If you have ever taken on the role of Ops Chief for a setup you know that getting the initial modules into the application can be quite a chore if you have nothing to start from. I know that many of the "regulars" have a data file that they start from that already has most if not all of the modules they will need in it.

I do have plans to bring a true online module library to ModuOps but for now we have our first step in getting there.

I have created an online open repository on Github. Github is a service that allows you to store text files (usually programming code) online and provides version control of the files. The service has a very generous free tier. While it is mostly used by programmers, it's not too difficult to download files from the service if you are not a programmer.

If you are familiar with Github, please jump on in and get the repo cloned to your local drive. If you have a data file and would like to have the modules available but are not familiar with Github, no worries. Send me the file and I'll do the work to get the modules posted online.

Feel free to head on over to the ModuOps Module Repository. The files are completely viewable from the website (for free). Of course when you open one of the module files it may look like Greek if you're not familiar with JSON.

Feel free to suggest module changes via email or if you already have a Github account go ahead and open up an issue. I will open issues as I do work with modules. Everyone should feel free to click on the "Issues" tab and see what's in the pipeline for changes to the public modules repository. If you have thoughts on the structure let me know. I took a first swing at setting things up but it is not set in stone.

We'll see how this goes. It's not ideal but it is better than trying to find modules for a setup when you know that someone already has used the module. I hope this start makes things a little easier when planning a new Ops session.

I'm working on a new section in the online manual detailing how to download and import modules from the public repository.

Mac updates​

Apple Silicon native​

This version natively runs on Apple Silicon hardware! The binary is dual-purposed supporting Intel macs as well.

macOS app signed​

The Mac version of ModuOps is now officially code signed. This means that you should not have to jump through hoops to install ModuOps on your Mac. If you have any issues with this let me know.

Download​

ModuOps is free software available on macOS and Windows. Head back to the ModuOps website home page where there is a download button near the bottom of the page.

Bug reports​

While some effort was made to find issues before the release, I'm sure there are bugs out there. If you have any issues with the new version either post to the groups.io email list or a note to bhall underscore 2001 at yahoo dot com.

There are a lot of changes here at the website as you can see. The hosting provider of the old site went belly up leaving me high and dry. Luckily I had a backup of the old content. However I decided to start over.

The new site uses Docusaurus for the engine. I've gone with simplicity for this site. I find the layout and navigation are easy to pickup and for those wanting to help out everything on the site is markdown files (with a little React thrown in).

I've also gone serverless! That's right, there isn't a server running this site. The website is made up of static html files that live on Amazon Web Services. This gives the site a nice performance boost, will be cheaper to operate and I'm hoping that Amazon will not go out of business during the rest of my tenure.

Downloading ModuOps is super easy with buttons on the home page for Mac and Windows. I'm busy adding documentation which was sorely needed. Since you're reading this you'll also notice I'm starting the Blog (again).

Some are aware of a new version in the works. I hope to have the work on that wrapped up soon. Look for a post here with the details of the new release.

Let me know what you think of the new site. I'm hoping you find it as nice to use as I've found it to develop.

-Bob