You can create a multiRUNS project by either r-clicking on a .dat file under the projects view and then select New multiRUNS Project or you can go to File-->New Project and select the multiRUNS project.

As with all projects, you can have multiple workflows associated with a project. In other words, for the same input file you can create different templates that have different parameters allowing you scan a different range of solutions.

Once you have created a workflow node, follow the 5-steps accessible through a r-click on the workflow node:

1. Add Tags. Use this action to create the template by adding tags (variables) that can be associated with external include files.
2. Set Tags. Associate external include files with each tag.
3. Open Simulation Viewer. Create/run/delete the various 3DSL input files.
4. Create All Runs. Create all possible input files from the combination of include files. This action can also be performed from the Open Simulation Viewer action.
5. Run Simulations. Run all input files. A more selective choice of which input files to run and which not can be done from the Open Simulation Viewer action.

Post processing of results can be done in the usual manner by comparing field and well plots, comparing history matching errors, or ranking the various simulations. Look in the Tool Panel of the compare plots for controls to color results by tag-value or to look at the results via the ranking functionality.

Consider a case that has 3 different grids, 3 different pvt descriptions, and 3 different OWC for a total of 27 runs. You can download the data to construct this example from here. Displaying the oil and water production using different colors for each include file of each tag can show trends that might otherwise be difficult to recognize. See below for an example.

Red and blue dots are historical oil and water production respectively. Runs with grid01 are blue, grid02 are red, and grid03 are orange. Note that there does not seem to be an obvious trend in which grid is closer to history.

Here the runs are colored by their PVT file, with pvt01 being blue, pvt02 are red, and pvt03 are orange. Here the data seems to indicate that pvt01 is no likely to be a good fluid representation.

Finally, coloring by the OWC files (owc01=blue, owc02=red, and owc03=orange) shows the clearest trend, with the historical data clearly being best represented by the owc01 include file.