Close this search box.

Optimizing Crew Assignment and Movement Decisions to Minimize Operational Costs

With Woodstock's Crew Movement feature you can account for movement costs between blocks to improve crew assignment and movement decisions and minimize costs. Learn how it works.

Remsoft’s 2020 Woodstock Scheduler release provided users with numerous improvements, fixes, and new features to the application. Among these is the new Crew Movement feature, which stands out in its ability to help organizations model and reduce their overall operational costs. This feature allows the cost of crews moving from one block to the next, or from one sequence of blocks to the next, to be represented in a model.   

The feature also provides the user with an automated approach for generating treatment sequences, based on a set of user-defined parameters. A sequence is a fixed and/or preset order of blocks and moves between these blocks, and treatment decisions are made by the solver for the entire sequence, not the individual blocks within. Thus, this new feature not only accounts for movements between individual blocks, but also for larger moves between entire sequences that may be spread quite far apart. 

Computer image of harvest blocks shown spatially
A group of harvest blocks shown spatially in the Scheduler Maps View.
Computer image of six separated sequences of harvest blocks
Six separated sequences of harvest blocks created using Scheduler’s Sequence Builder and a set of user defined parameters. If not created by the Sequence Builder, they can be manually declared by a user in the Attribute Input table. In this case, the sequences were created using the straight-line distance from one block to another.

A model can be configured to include movement costs between blocks and/or sequences in the matrix so they can then be considered by the solver. This facilitates better crew assignment and movement decisions to minimize costs, benefitting the overall solution and helping an organization’s bottom line and operational efficiency.

Finally, it is important to note that the Sequence Builder also allows users to manually edit sequences by adding and deleting individual movements. Users can also create or delete entire sequences manually in the maps view as well.

Now, let’s get into the weeds a little bit, and explain what data is needed and how to use this feature once configured.

Data Requirements

This feature relies on an already functional harvest crew scheduling Solution model and requires the following data to be configured properly.

  • Move costs: Costs triggered by moving from one block to the next. Blocks do not need to be in a sequence to trigger this cost. Anytime a crew moves from one block to the next, it will trigger a cost.
  • Big move costs: Cost triggered between the last block of a sequence and the first block of a new sequence (i.e., the cost of moving from sequence to sequence).
  • Road distances (optional but beneficial): The distance on roads from one block to the next. If this is not supplied, the model will use linear distance from the center of a block to the next.
Computer image of harvest blocks with distances via roads
This image shows the same blocks as those shown above. However, this time the Sequence Builder used an external file that contains the distances between each block via roads instead of straight-line distances. This is why the sequences look different.

Using the Sequences in your Solution

Now, you may be thinking, “It’s great that I can create view sequences in Scheduler, but how are they factored into an actual model run?” We’ve got that covered, too. Any model that uses the Crew Movement feature will also contain an additional custom internal procedure that imports the sequences from the maps into a data table, and then into the Woodstock model itself. These sequences, combined with the cost data outlined above, allow the model and solver create a solution that contains user-defined sequences and minimizes the costs of moving from one sequence to another.

Computer image of six separated sequences of harvest blocks
Remember the image above from earlier? After the sequences were generated, they were imported into the model to be used in its solution.
Computer image of crew sequences
These sequences were used in the model’s final solution, where “blue crew” began in the western sequence and worked their way east, and “brown crew” began in northwestern sequences (outside the image frame), and finished with the two sequences shown here. This is the power of using the sequence generator.
Computer image of crew movement sequences
Here they are on a larger scale, where all brown movements follow pre-defined sequences as well.
Computer image of two crew movement sequences
Here are the same two crews, in the same general area, without any predefined sequences for the model to work with. Note the large move for brown crew, which is negated when sequences used in the solution are initially generated using the Sequence Generator, taking advantage of maximum cost parameters.

As you can see, with the proper data and configuration of Scheduler’s new Crew Movement feature, a user can generate groups of harvest sequences that adhere to specific parameters easily and efficiently. They can then use these sequences, as well as movement costs, to generate a solution that takes into full account the cost of moving crews from one sequence to another.

Learn more about this powerful tool in Woodstock Scheduler and its ability to help organizations reduce forestry planning and harvest costs and improve overall bottom lines.

Share on 

Get our brief with articles on using analytics, AI and business intelligence for forest management planning.