Import Stopes
In the Workflow Pane, you can also navigate to this function as part of your Scheduling Workflow. The Import process will cut out any development solids that intersect with the stopes and build development solid dependencies accordingly.
The Import Stopes dialog
Input Data
Select the Source of the data that will be used as input to the function:
| Selection | Design elements you have interactively selected in the Design Window. |
| Visible | Design elements that are visible in the loaded layer. Elements that have been specifically hidden are excluded. This a quick way of selecting all visible elements in a layer without having to explicitly select them. |
| Layer | One or more layers that you select. Names of layers currently loaded in the Design Window are shown in bold. |
|
|
|
For large datasets, for performance reasons you may prefer to select a layer rather than load that layer and select all of the elements in the layer.
Selecting a non-applicable layer will have no effect. In most cases, an error icon will indicate that the chosen input layer is not valid. Hover over the icon to view a validation hint. 
Settings
Output Layer
(Optional) Use the drop-down to select an Output Layer.Tip: In the Layer Selection pane, you can right-click on the Layers node (or a folder) to Add a new layer.
The Output Layer can be used to repair solids that failed to cut successfully.
Block Model Interrogation
Optionally, select one or more Block Model Interrogations to define what attributes should be populated with the values of a given block model field.
Block Model Interrogations allow you to generate quality values from one or more Block Models and assign aggregated values to fields in the Scheduling Data Table. A pre-requisite is that the quality fields you want to interrogate (Gold Grade and Density, for example) have already been setup in the target Data Table, alongside the calculated fields (Tonnes, Volume and Gold Grams, etc) populated as a result of the interrogation.
Cut devs out of stopes
When this check box is selected, the Import process will cut out any development solids that intersect with the stopes and build dependencies accordingly.
Dependencies in "Stope on dev Rule"
The Stope on dev Rule is determined by looking at the intersection between development and stopes. In the case of an intersection, a rule is created from stope to development to indicate that the stope will follow the completion of the development.
When this check box is selected, any stopes that do not have development network intersections are added to an "UNSET" range.
See: Stope on Dev Rule
Apply
Click Apply to import the stopes. Depending on the size of the dataset and the settings you have chosen, there may be a delay before the imported stopes appear in the Animation Window:
In the Properties pane, you can view the physical properties (volume and length) of the development cuts.