Design Compliance Report

To access this screen:

Activate the Reports ribbon and select Reports >> Design Compliance.
Run the command "compliance-to-design".
Use the quick keys 'cde'

The main purpose of the Design Compliance report is to assess the correlation of ground data for a given period versus the designed/expected outcome for the same survey period. This is with respect to:

Material mined and planned.
Material mined but not planned.
Material planned but not mined.

As with other Studio Survey reports, the design and as-mined surface are selected according to date. This data will have been committed to the current database using the Add to Database tool.

For underground compliance reporting, see Drive Compliance Report.

Note: This tool supports batch processing: use Add to Batch to schedule processing at a later date, using the Run Batch task.

In the context of the Design Compliance command, a Design Surface represents a calculated surface indicating a target to be achieved at a given point in the future, potentially several reporting periods ahead. This is similar to the Plan Compliance report, although the "plan" in that report would normally be associated with an end-of-period surface, created for the month ahead. In short, it reports the difference between the actual mined surface versus the designed surface, and is typically used to validate how blasting has honoured the designed pit walls and to check for under- or overmining.

Any surveyed pit surface can be selected (by its survey date). The Design Surface must have been added to the current database as the Design Surfaces type for it to be selectable.

A boundary string can be specified if required. This will restrict the surface comparison and cut/fill volume calculation to the surface data falling within the perimeter. This boundary will be applied to both the Designed Pit Surface and Surveyed Pit Surface.

For example, in the image below, the Designed Pit Surface is shown on the left and the ground data for the same reporting period is shown on the right. The boundary string is shown in both views in red:

Whilst superficially similar, the two surfaces differ (within the boundary) in some areas. For example, a magnified view of an east/west profile shows examples of both planned/not mined and mined/not planned extraction:

Report Output File Naming Convention

Output files from Studio Survey's reporting processes follow the same file naming convention. This is adopted to make files more easily recognizable outside of Studio Survey, and to make searching for them easier.

The following conventions are used for reports:

Open pit scenarios:

Report_<pit>_<area>_<rom>_<date>.xlsx

For example:

Report_Pit_1_Area_1_ROM_1_2020-03-23.xlsx

The following conventions are used for output data:

Open pit scenarios:

<data type>_<pit>_<area>_<rom>_<date>.dm

For example:

NaturalSurface_Pit_1_Area_1_2020-03-24_tr.dm

The Compliance to Design Published Report

The Compliance to Design default published report contains undermine and overmine tonnages for the reporting period, plus the net calculation, according to the bench definition for the reporting scope.

This information is subdivided into per-elevation/bench data, which can be useful to see where net volume discrepancies have occurred, e.g.:

Report Output

Design Compliance report generation includes the following items:

A spreadsheet containing a Design Compliance worksheet. This worksheet is explained in more detail here.
A wireframe file pair representing the volume differences between the expected/designed surface and the surveyed data, e.g:

The default colouring represents areas that have been planned-not-mined (red) and mined-not-planned (green).
Compliance wireframe data includes a True_Thickness attribute that contains the true thickness of the solid at each location. This could be useful, for example, to highlight areas of concern, ignoring acceptable thickness tolerances, For example, if a 0.5m variation in toe position is acceptable, you may only be concerned with values above this threshold. For example, the image below shows output compliance solids coloured using a blue-red (thin-thick) legend, highlighting potential areas of concern in red:
A strings object containing outline strings for each overmine or undermine volume, e.g.:
A Datamine table containing volume calculations for each overmine/undermine volume, per bench. This table is used during publishing to create or update the output results spreadsheet.
A copy of any boundary strings used to constrain output volumes.

Using the Reporting Date Calendar

When you select a date for reporting, the calendar tool can be used to see previous report date(s). These are highlighted in red, e.g.:

You can regenerate EOM data for any date, including dates for which EOM output already exists but, in this scenario, you will need to confirm if you wish to overwrite existing data.

Previewing and Loading Report Data

EOM reporting panels offer functions to preview both your report input surfaces/strings and your output volumes and reports/tables.

Preview data: available for all report inputs represented by 3D data.
Load data: available for all report inputs represented by 3D data, including output data.

If results data is previewed, up to three separate displays will be created:

A PDF or .emf report: this is generated based on the current Plot Template that is associated with your project. Only displayed if it is possible to generate an output report in this format. Not seeing a PDF or .emf report? Check to see if your report has an associated plot template, using the Database Settings screen.
Wireframe Volume: this represents the cut & fill solids created by your reporting task. This is shown in Datamine's Table Previewer application. Only displayed if it is possible to construct a 3-dimensional volume from the input data of your report.
A Report Table: this table, in Datamine format, contains the volume assessment of your cut & fill volumes for the selected report. If it is not possible to construct a 3-dimensional volume, a table (nor any other output) will be displayed.

Compliance to Design Report Activity

To configure a Compliance to Design EOM report:

Select the Current Pit that relates to the report you plan to create. The pit associated with the current project is set using the Database Settings screen. You can either pick an existing pit or access the settings dialog to modify the pits of the current database.
Choose the Current Area to which the monthly report relates. This can also be changed using the Database Settings screen, accessible via the browse button. You can either pick an existing area or access the settings dialog to modify the areas of the current database.

Select the Surveyor for the current report. Surveyor names are configured using the Survey Database Settings task. The Surveyor is displayed in the output end-of-month results, and will appear in the generated spreadsheet report once published.
Choose the Report Date. This is the date to be associated with filing the report. By default, this will be the current date. This information is stored in the output wireframe triangles file generated by the reporting process (according to cut and fill calculations), and will be shown in the accompanying published spreadsheet.

Note: You can generate multiple reports on the same day if you need to; each report will be labelled according to the time it was generated.

Choose the Surveyed Pit Surface for your report. This is the ground data for a given reporting period. You can choose from any surface that was added to the current database with the data type Surveyed Pit Surfaces.
Choose Designed Pit Surface. This is the surface that represents the expected outcome of the reporting period. This surface will be used in comparison with the Current Surface to deduce whether material has been mined that wasn't planned, or planned but wasn't mined. Commonly this is used to determine the overall compliance of the extraction operations over the specified time period with the expected result, and will be used to drive downstream processes such as penalty calculations, regeneration of schedule information and so on.
Optionally, choose a Pit Excavation Boundary. A pit boundary can be used to constrain the context of volume generation/calculation. Any data item within the database (for the given pit/area) of the type Pit Excavation Boundaries can be selected, and will be applied to both the Surveyed Pit Surface and the Designed Pit Surface. If multiple string entities exist within the file, you can select an attribute-value pair to denote which entity to be used for your compliance report.
Choose your cut and fill Calculation Options. These determine how data fragments and noise are detected when calculating a cut and fill volume.
- Remove solids with volume below: by default, all cut and fill volumes that represent the difference between the specified surfaces (optionally constrained by a boundary) will contribute to the output EOM report. You can change this number to remove trivial fragments below a specified volume, with higher values leading to potentially greater volume removal where multiple small volumes are output.
- Trim solids with thickness below: reduce the number of thin data fragments result from near-coincident surfaces by increasing this value. Higher values will tend to increase the amount of data removed from the output cut and fill solids and resulting report.
- Decimate input surfaces to limit triangles to: ground data can be represented by very dense wireframe data, and this can lead to increased cut and fill calculation times. Enabled by default, input surfaces will be pre-decimated to reduce their data density and commit less dense/simplified data into the EOM volume calculation routine. This can increase the performance of the EOM reporting tool at the sacrifice of input surface detail.
Pick the Benches to include in your report. By default, all benches from the highest to lowest will be used for reporting, but you can constrain the reporting range using the From and To boxes. Benches are listed as defined in Database Settings.
Choose your cut and fill Calculation Options. These determine how data fragments and noise are detected when calculating a cut and fill volume.
- Remove solids with volume below: by default, all cut and fill volumes that represent the difference between the specified surfaces (optionally constrained by a boundary) will contribute to the output EOM report. You can change this number to remove trivial fragments below a specified volume, with higher values leading to potentially greater volume removal where multiple small volumes are output.
- Trim solids with thickness below: reduce the number of thin data fragments result from near-coincident surfaces by increasing this value. Higher values will tend to increase the amount of data removed from the output cut and fill solids and resulting report.
- Decimate input surfaces to limit triangles to: ground data can be represented by very dense wireframe data, and this can lead to increased cut and fill calculation times. Enabled by default, input surfaces will be pre-decimated to reduce their data density and commit less dense/simplified data into the EOM volume calculation routine. This can increase the performance of the EOM reporting tool at the sacrifice of input surface detail.
If you wish, you can Use a fixed plot scale. If checked, all plotted items will honour the scale set. This can be useful if projections on your report relate to the same data in different views, for example.
To generate evaluation results as part of your report (it's optional), you'll need to specify a suitable block model:
1. Enable Use block model for reporting.
2. Use the "..." button to display the Block Model Options popup.
3. Fill out the fields on the Block Model Options screen and click OK.
  
  See EOM Report Block Model Options.
You can also set up a batch run of reports:

Add to Batch: add the current report definition to a queue of batched tasks that can be run later using the Run Batch task. Data will not be processed until the batch is processed, meaning changes made to data between report specification and execution will be included.

Finally, review the results of the calculations:

Results: