General Recommendations for Processing

Scenario Constraints

The best way to constrain a scenario in Quantm is:

1. Start with constraining the templates needed in a scenario.

2. Enter the costing information for the scenario.

3. Enter the geometric parameters for the scenario.

4. Constrain feature data within the scenario.

Options

High-priority avoid zones should be placed to block out undesirable corridors and areas where alignments are running to shift alignments into a more desirable location in the next submission.

Tip:  As the alignments are geometric, they can be easily converted to editable allowing for tweaks along the way with the shift from the seed seen in previous versions. Also, as the results are geometric, they will not lose the IP locations.

When moving to seeded submissions use the editable function regularly, especially between each processing step, to put seeds into a more desirable location to help the results coming out of the system to be positioned in a desired location. 

Tip:  Unless otherwise desired, all seeded submissions should have the spread set to Loose to give IP more room to move.

Note:  It is important to remember that changing the number of IP will change the costs, just because an alignment is the cheapest does not necessarily mean it is the best or has the desired number of IP.

Tip:  In cases where there is an imported geometric seed that is close to final, it may be desirable to bypass the exploration step and go straight to the refinement.

Once this step is done, the alignment should be edited to make sure the horizontal location is desired before moving on. It is important here to address any major horizontal issues to help reduce their impact moving forward.

First off, an exploration submission should be done with vertical only selected. This should be done to get the IP into the best location and to identify the optimal number of IPs when looking at the horizontal alignment.