Glossary of Terms
Some of the terms used in the application will be familiar to you, others you may know as other things from different software. Some of the key terms are Processes, Tasks, Equipment, Custom Fields, Dependencies, Constraints and Paths.
-
Aggregation controls the wayin which field values are aggregated per-level.By default, the Aggregation property of a field is set to None. Most commonly-used aggregations are Average, Sum and Weighted Average.
-
Related to Path Commands: When Allow Advance is turned On it allows the schedule to look further down the path to find Released Tasks (or until Allow Advance is set to Off). Allow Advance will only have an effect when there are Dependencies or Constraints set and the default is Off.
-
The "Alternate" Solids Field is used when a Solid can't be found in the primary Field (material that may have changed Solid type during reserves processing).
-
Related to Paths and Dependencies: Arrays allow for multiple lines to be combined into one and are particularly useful for Dependencies. Arrays can either be indexed (numbered) or non-indexed and represent a powerful but potentially complex tool and careful reading of the Dependencies topic is recommended.
-
Related to Arrays: The ArraySpan (..) option replaces the use of individual semi-colon delimited objects to Span multiple Positions. For example {D..G} is the same as {D;E;F;G}
-
ASAP Range determines which unlevelled tasks should be completed AS SOON AS POSSIBLE. If a task is not in the ASAP range, then it will be completed AS LATE AS POSSIBLE instead, without delaying any ASAP tasks.
-
Attribute Fields are a special group of fields which are imported into the Data Table. These Attribute Fields are Design Attributes that are imported from Development Network and Stope layers linked to the Data Table. During the Tunnel and Stope generation processes, Table Solids Fields are populated with the data from the design centrelines and the stope solids. These attributes are essential for building and running the schedule.
-
The definition of Availability varies from site to site but generally refers to the mechanical availability of a piece of equipment. No matter the definition, Availability, Utilisation and Equipment Count multiply to create an effective factor which converts Calendar Hours to Operating Hours.
-
Calculated Fields allow for Field Values to be based on an Expression as opposed to being imported or based on a script. Calculated Fields can reference other Fields within the same Leaf, and can be based on the current Levels and Positions. You can also reference values on other Tables using the TableValue Function, but it's important to know that you cannot currently reference other Positions within the current Table.
-
Calendar Hours refers to the actual amount of time that passes as opposed to Operating Hours. Calendar Hours will always be equal to or more than Operating Hours unless an Equipment Count of >1 is used.
-
A Calendar is a type of Table that is designed to allow parameters to change over the duration of your Scenarios. A Calendar requires a Start Date that is before the start date of the related Scenario, and any other Field values that are referenced are effective until the next Start Date (no End Date is required).
-
A Capacity Constraint applies a limit to either Quantities (Source and/or Destination) or Operating Hours over a certain period of time. The period of time is set either by the Scenario Calendar or manually.
-
Suppose you have a piece of Equipment named Blasting, but you also have a process called Blasting. You can't use Blasting as the name for each as they have to be unique, so the application places their location before the name, so the piece of Equipment called Blasting has the Code Name EquipmentBlasting (no spaces) and the Process called Blasting has the Code Name ProcessBlasting (no spaces). To see the full range of Code Names available to you scroll through the drop-down in the Expression Editor.
-
Related to the Expression Editor. Constants can be considered to be all of the possible options defined as part of the project and are usually compared to Variables. Examples include Scenario Settings such as Equipment or Processes, as well as Table Positions and Fields.
-
Data which does not change when running a mine schedule and/or haulage analysis.
-
Constraints allow conditions broader than Dependencies to be applied to Tasks and can be defined by multiple criteria such as location, time, Equipment, Process or historical events. There are three types of Constraints available by default: Capacity, Proximity and Time.
-
A Custom Field is a user-defined custom result that is built with a formula in the Expression Editor. Custom Fields can be either numeric or text values and range from simple to complex so a thorough understanding of the documentation is recommended.
-
The DateTime Field type refers to an absolute point in time. Calendar tables make use of this for various dates (e.g start and end dates).
-
The Default Task Rate determines the rate that should be used by equipment if none is specified - this is also used by unlevelled equipment to determine what their rate should be.
-
A Dependency is the requirement of one Task (a Predecessor) to be completed before another Task (a Successor) can begin and can apply to both Source and Destination Tasks (and between them). Dependencies set an Unreleased state to Tasks they apply to and once all Predecessors are completed this reverts to a Released State.
-
Every productive process has a value that is linked to a Field in the Deposit Table. Source scheduling is based on "working" this value, which is called the Source Quantity. Any Leaf in the Deposit Table that has a Source Quantity greater than zero can be worked. The most work that can be done on any Source Quantity is 100%.
-
Destination Paths are the primary instructions for destination scheduling and control the order in which Destination Quantity Fields are attempted to be "filled".
-
Double Precision Floats refer to any number including decimal places. Common examples include physical properties (Area, Thickness, Volume, Tonnes etc.) and equipment rates.
-
Equipment is anything that might "work" a Productive Process. Each piece of Equipment has a set of parameters that determines the rate it works each Source Quantity, how it is displayed in the Animation and how delays/downtime are applied and reported. Each Scenario will require at least one piece of Equipment.
-
The ETI (Ensemble Transport Interface) Stream file format was developed by the Communications Research Centre Canada. An ETI file contains a standardised output stream from a DAB/DAB+/T-DMB multiplexer and consists of a 2Mbit/s synchronous stream.
-
Fields define the types, behaviour and display properties of each piece of data that is held within a Leaf. Each Leaf on a Table shares the same Fields but not every Field in a Leaf requires data. Example Fields include Waste Volumes, Initial State Percentages and Solids.
-
A Leaf is defined as the overall data container at the lowest Level in our Level/Position tree structure. Each of these Leaves can contain anywhere from one to a great many number of individual pieces of data, but each Leaf in a Table shares a common structure with the rest. This is needed because different types of data are stored in different ways (for example dates & percentages are stored and reported differently) and this structure is made up of Fields.
-
The Format String controls the way data appears, but does not affect the actual data storage (you can display a number 0.532 as 0.53 but the number stored remains 0.532). Nomenclature is based on C# standards
-
Z angle. Line grade, for example, is the Z angle between two points.
-
Haulage Rules used to filter the Output Schedule are saved as a Haul Profile.
-
Haulage Logic comprises Haulage Rules which filter the Output Schedule. These filters are applied to create Haul Profiles.
-
Each Scenario has it's own Haulage Network. A Haulage Network has one to many network layers which are used to assist planning and those layers can be connected to each other. Layers themselves do not have properties, however the Network Shapes inside each layer do.
-
The Index (as opposed to Name) of an item refers to its actual location in the project database. Most relevant with Positions as it affects the behaviour of Spans, Arrays and Wildcards. Indices (plural) are 0-based meaning the first entry is Index 0 rather than 1.
-
Initial State allows you to set a pre-mined or pre-scheduled state using the sameText Range style as Source and Destination Paths.
-
Inline Ranges are similar to Text Ranges, except they are specific to the context in which they are used (for example, the Source and Destination Ranges in an Animation) and are not stored. However, some Inline Ranges are persisted to the project database, such as the Source and Destination prefilter ranges specified in General case settings
-
To complete a Destination Schedule or Haulage analysis when Source Scheduling is not being run, an Input Schedule is required. An Input Schedule is simply the resultant Schedule that has been created by whichever Scheduling solution is required. It defines the Source and (optional) Destination of the Schedule which allows the user to complete Haulage.
-
Joiner lines can be connected to each other to create a Joiner Web. Distinct from a network, Joiner Webs only consider the connectedness of Centrelines and have no concept of direction, entrances or exits. All Centrelines connected to the same Joiner Web are considered to be connected by the point at which they are connected to the Joiner Web. The Joiner Lines in a Joiner Web are differentiated from Centrelines by being drawn as dashed lines.
-
Related to Arrays: Use the Jump (#) option in conjunction with an ArraySpan to Jump more than one Position at a time. For example {D..H#2} is the same as {D;F;H}.
-
At the lowest Level in the tree-oriented data layout of a Table, the data itself is contained in Leaves. Leaves share a common Field structure. (Core)
-
At the lowest Level in the tree-oriented data layout of a Table, the data itself is contained in Leaves. Leaves share a common Field structure. (Core)
-
A Level Filter is an optional component of a Picked Range. Once a Level is ticked on, each Position selected is an inclusive type filter, meaning Positions that aren't selected are excluded from the Picked Range.
-
A Data Table can contain as many Levels as defined by the user. Advance allows for two sets of unique branches to be formed; one for development and one for stoping. It is important to note that each will have the same number of Levels. Each Level structure must contain unique full nodes or leaves.
-
The Name (as opposed to the Index) of an item refers to its description in the project database. Names are the most common form of reference. If Names have a logical order such as numbers (e.g. 1-20) or letters (e.g. A-F) then their related Indices should usually be in the same logical order.
-
A Node Filter is a required component of a Picked Range. Each Node selected is an inclusive type filter, meaning Nodes that aren't selected are excluded from the Picked Range.
-
Nodes represent the progressive Position within a Table Structure. A key concept to remember is that in a tree oriented table structure, a Node can have many Nodes underneath it (Child Nodes) but only one Node above it (Parent Node).The bottom Node in a Table is also referred to as a Leaf.
-
A Nonproductive Process represents a pause in activity such as a public holiday or maintenance. Nonproductive Processes are referenced in Delays, Paths and Equipment Setup.
-
Operating Hours refers to the effective time Equipment is used as opposed to Calendar Hours. Operating Hours are a result calculated from Calendar Hours multiplied by an effective factor (Availability * Utilisation * Equipment Count).
-
Related to Path Commands: The Order command controls the way the group of Leaves within an individual Path line is sorted. Order works in a similar way to the Sort tool in Excel and when not specified the default Order is from the Level Index 0 to the last.
-
The Output Schedule is the line-by-line representation of every single result you can get out of your Source and Destination Scheduling, as well as various (but not all) Haulage results.
-
To backfill underground mine stopes
-
A Percentage Field type refers to any number that is stored as a percentage. Common examples include qualities, Initial States and availability/utilisation.
-
Related to Path Commands and Initial State: Percentages define the portion of a task to be scheduled. When not written the default is 100% for both Paths and Initial State.
-
A Picked Range visually filters a Table using a tickbox for inclusion. Requires at least one Node Filter turned on to be effective.
-
A Pivot Table is a data summarisation tool that can automatically sort, provide totals or give the average of the data stored.
-
Point3D Field types refer to an XYZ position in real world coordinates.
-
Each Level in a Table Structure has one to many Positions which can be considered to be the Level's options. For example, in a Level called Zone, its Positions might be North, South, East, West.
-
Related to Dependencies: A Predecessor is a Task that is required to be completed before a Successor Task can be Released for scheduling.
-
An inclusive range that limits the amount of data available to the Scenario which is useful for large datasets where you are only working with a particular section.
-
Related to Path Commands: A Prefix applies to all subsequent Path lines that describe a node or nodes. There is no default Prefix.
-
A Process is any process or activity a piece of equipment may undertake that should be scheduled and reported separately from others. Processes are either productive (linked to a data value such as volume or metres) or non-productive (representing a pause in activity such as a public holiday or maintenance).
-
A Productive Process is linked to a data value such as volume or metres. Source Scheduling is based on "working" this linked value, which for each Productive Process is known as the Source Quantity. Productive Processes can be represented in an Animation by an associated Solid.
-
A Proximity Constraint applies a limit to the number of Equipment that can be present at a set location at any one moment in the Schedule. This location is set through the Range(s) and the Grouping but by default applies at the individual Leaf level (no Grouping). The Value sets the weight each piece of Equipment has and the Maximum sets the maximum sum of Values that can be present on any Group at one time.
-
Post Schedule Tasks (PSTs) can be setup as part of your Scenario Settings and occur immediately following Results generation.
-
Ranges group Leaves of data into groups. There are two types of Ranges (Text and Picked). Ranges are used in several places, including Table View, Destination Paths, Animation, Haulage Logic and Constraints.
-
A Return Air Raise (RAR) is a shaft or opening in an underground mine that allows return air to escape and which forms part of a mine's ventilation system.
-
Related to Path Commands (Source Path Only): A Rate Factor "[x%]" overrides the rate of a piece of equipment and by default is set to 100%.
-
Related to Tasks and the Snapshot Viewer: A Task that is Released has no Dependencies preventing it from being worked by a piece of Equipment. Note that it's possible for a Released Task to still be Constrained.
-
A Reporting Period defines the timeframes that your Scheduling and Haulage results are split into, sorted by and reported on. For example you would use a Reporting Period to define weeks, months or financial years.
-
Reporting Periods set your definitions of weeks, months, financial years or other periods of time relevant to your site. There are no reporting periods as a default.
-
Retard Curves handle the speed going up and down ramps in lieu of the restrictions from Ramp Codes.
-
Rimpull is the force available between the tyre and the ground to propel the machine (limited by traction) and it is measured at the wheel so includes all transmission losses.
-
Rimpull curves are used to determine the maximum speed attainable, gear range and available rimpull when machine weight and effective grade are known.
-
Rolling Resistance is the force that resists the rolling of a wheel or other circular object along a surface caused by deformations in the object and/or the surface.
-
A Scenario is the container of everything the application will use to schedule your Data, including but not limited to types of mining processes, equipment settings and paths. Each Scenario is distinct from every other and examples of different Scenarios might include different equipment types or dig strategies.
-
During haulage, rolling resistance is controlled by Segment Codes which get applied to each segment along a haul profile.
-
Simulation payloads relate to how much weight the truck carries under a normal load and is used to calculate travel times.
-
In an underground mine, skips act as shaft conveyors for transporting ore and waste masterial to the surface.
-
The Snapshot Viewer allows you to see at any one point in your Schedule the state and order of your Tasks, Equipment Paths, Dependencies, Constraints and more. It should be your primary tool for troubleshooting your scheduling.
-
Solids can be defined as the 3D data files used to represent both source and destination locations in the Animation and Preview window. Examples include Vulcan triangulations and Surpac DTMs. Solids will only be displayed in an Animation if there is an associated Source/Destination Quantity.
-
A Source Path is the primary set of source scheduling instructions for a particular piece of Equipment. Technically a Source Path defines the order in which Source Tasks are completed as well as controlling the behaviour of Equipment when it is unable to complete the defined instructions.
-
Every productive process has a value that is linked to a Field in the Deposit Table. Source scheduling is based on "working" this value, which is called the Source Quantity. Note that two or more different processes may use the same Field for their Source Quantity, however the value is duplicated, not shared.
-
The Span (-) character is used to define a range of positions in a Text Range or Path. If used in a Path the Span also sets the order in which the range will be processed for example 1-10 is a different order than 10-1. It is important to note that the resulting range is between the two Indices of the positions.
-
Speed Restrictions refer to conditional speed limits depending on the properties (angle and direction) of a Haul Profile Segment.
-
Related to Dependencies: A Successor is a Task that is Unreleased (cannot be worked) until all of it's Predecessors are completed.
-
The Summary window provides note taking for each Scenario to record any assumptions or information relevant to understanding it. Any Summary can be exported to a variety of output file formats including Rich Text (rtf) and Word (doc and docx).
-
Each project has one to many Data Tables, which hold site-wide information such as Deposit, Destination and Calendar data. Each Table has a unique tree-oriented data structure made of Levels, Positions & Fields. Extended applications of Tables include Rise-Run Matrices and Equipment Maintenance Databases.
-
A Task is either a Source or Destination work unit of the movement or processing of material. Scheduling can be considered to be the assignment of each of these Tasks to one or many pieces of Equipment and are broken up into Source and Destination Tasks.
-
The combination of a Process (including it's assigned Source Quantity) and each workable Leaf is known as a Task. Scheduling can be considered to be the assignment of each of these Tasks to one or many pieces of Equipment.
-
A Text Range filters a Table using a written system similar to a Source or Destination Path but simplified. Uses Wildcards, Spans and Commas.
-
A Text String Field type can contain any data (as a string) but no mathematical operations can be performed. Commonly used to preserve data for reporting/auditing purposes or to identify groups within a Table.
-
A Time Constraint applies a limit to the times that a Source or Destination Task is available to be worked.
-
Tonne kilometre per hour (TKPH) is the measurement of the work load of a tyre and is based on the weight and speed that the tyre can handle without overheating and causing it to deteriorate prematurely. A TKPH rating for a tyre is the theoretical maximum workload it can take (average weight on the tyre * average speed of the truck OR more specifically, tonnes * km/h).
-
Truck Payloads relates to how much source quantity you can move on a single truck pass. This might be in tonnes, CM or some other unit that you are scheduling in.
-
Unlevelled tasks do not get worked on by conventional equipment. Instead, it is guaranteed that they will always be worked on as soon as they are ready.
-
The definition of Utilisation varies from site to site but generally refers to the usage of a piece of Equipment when it is mechanically available. For example Utilisation may (but not necessarily) take into account shift changes, average rain delays and lunch breaks. No matter the definition, Availability, Utilisation and Equipment Count multiply to create an effective factor which converts Calendar Hours to Operating Hours.
-
Related to the Expression Editor. Variables are dynamic values or results that are usually compared to Constants. Examples include results that might appear on an Output Schedule line such as the Equipment/Process used or the Start Date.
-
Calculated or user-defined data which changes dynamically, for example, the quantity of material moved in a month or the distance of a truck haul.
-
The Wildcard (*) character is used to define all Positions within a Level. In a Path, the order in which the Positions are processed is from Index 0 to the last Index. A reverse Wildcard (-*) conversely runs from the last Index to Index 0. Additionally, any time a Path is incomplete (not all Levels are represented) the remaining Levels can considered to be Wildcards as well.
A
C
D
E
F
G
H
I
J
L
N
O
P
R
S
T
U
V
W