The Studio Survey Database

Studio Survey relies on a database structure to understand the data that is stored within it.

You can set up a new database, or link to an existing one using Database Settings.

Each new database includes a default hierarchical structure that denotes the pit, area, ROM and corresponding data. The folder structure is used to specify the type of data that is being input or output, and the date to which the survey data relates.

The database is used to store both the inputs to survey reporting (data is added using the Add to Database task for either open pit or underground scenarios) and the outputs from each reporting function. Support is provided for storage of open pit and underground survey campaign data.

For example, for an open pit scenario, each pit in the database is represented by a corresponding folder in the local database's "Pits" sub-folder. Within each pit folder, an "Areas" sub-folder contains other folders representing major areas of pit operations (or, in fact, any survey data that needs to be distinguished from other data at a secondary level). Within each area folder, a set of folders exists that represents each of the fundamental data types associated with survey reporting, e.g. "Pit Excavation Boundaries". Within each data type folder, folders are created by the reporting functions and are named using a standard date format.

In general:

Inputs to a Studio Survey reporting function are added to the database using the Add to Database task.
Outputs from a Studio Survey reporting function are generated in an automatically-created date-indexed folder.
These outputs are used to publish reports for a given survey date.
Excel reports are formatted according to the selected reporting template.

This approach ensures that the context to which survey data relates, that is; location and time, is clearly accessible to the Studio Survey reporting functions and is easy to understand when accessed outside of the application.

In addition to collected survey data, the database also includes:

Survey reports and the 3D data to which each report belongs, segregated by survey date (the "Publications" folder)
Excel and Studio plot templates, typically customized to match your reporting and legal entity requirements (the "Settings" folder)
Information relating to the Surveyors you use to perform the survey reporting (the "Surveyors" folder).

You can view files that have been added to the active database using the Project Data control bar or the Browse Database tool.

Database Structure

Your Studio Survey database adheres to the following default schemas, although survey data folders can appear at multiple levels within the tree, depending on their assigned data scope. There are different folder structures for open pit and underground scenarios:

Open Pit Database Structure...

Underground Database Structure...

Data Scope

The Add to Database screen is used to configure data scope, when it is added to the database.

By default, when you add to the Survey Database, data represents the state of the mine at a given date, and applies to a particular data context, such as a pit and area for open pit surveys (or decline, area, level and stope for underground operations). You can also create data at a more general level.

For example, you may have a string file containing all excavation boundaries for all areas of a pit. In this scenario, you could add the boundary string file to the [Current Pit] level, meaning it will be selectable in all EOM pit reports for the current pit, regardless of the area designation. Similarly, if your project encompassed multiple pits, and the string data contained all boundaries for all pits, it could be added at the [Global] level.

An underground example could be a set of planned design strings representing developments related to the same decline, and applying to multiple areas. In this case, the [Development Design Strings] would be added to the [Current Area]

If you are adding open pit data for a Pit Actual, Design Compliance or Plan Compliance report, you can add data at one of three levels:

Current Area: data added at this level relates to a specific area and pit and will always be used in a report if it exists, otherwise, data for the same Survey date at the Pit or Global level will be used.
Current Pit: data added at this level is accessible to any EOM pit report, regardless of the Area for which the report is being generated, providing area-specific data (see above) for the same Survey date does not exist.
Global: data added at this level is accessible to any EOM pit report, regardless of pit or area reporting context, providing data does not exist at a lower level.

If you are adding data for an open pit ROM report, you can add data at one of two levels:

Current ROM: the ROM data will be specific to a ROM. When a ROM report is run for the given Survey date, this data will be used in preference to any global data that may exist (for the same Survey date).
Global: data added at this level will be (potentially) available to any ROM report for the same Survey date, providing more specific data isn't available (i.e. hasn't been added at the Current ROM level - see above).

Database Location and Access

A Studio Survey database can be created inside your current Studio Survey project or externally, including network locations.

Where local or network folder paths are synchronized to a cloud system, a globally accessible system is possible, This is simple to set up - just point Studio Survey at the synchronized folder using the Database Settings dialog.

Note: You cannot overwrite an existing Studio Survey database.

Database Customization

Configuring your database is as straightforward as editing or adding folders based on template structure. Assuming you have the necessary modification rights for the database folder, you can set up new database areas by creating new folders. Setting up and editing existing database folders is explained in more detail here.

Other folders will be added by Studio Survey as report data and publications are created. These system-generated folders will normally be described by the current survey date, and will generally be stored under the "Publications" parent folder, in a suitable date-described sub-folder (see above for an overview of a typical database structure).

Templates are an important aspect of your reporting, and whilst a series of default reporting templates are provided, you can use Studio Survey to create your own plot templates, and Microsoft Excel to modify workbook templates, or create new ones. Swapping between Excel templates, once added, is a case of changing a selection using the Database Settings dialog.