Appendix #6: Glossary of Terms

Click to Print
Term Description
@Position Related to Arrays: Uses the Index (rather than the Name) of a Position. @0 indicates the first item (zero indexed) and @-1 indicates the last (@-2 second last etc)
Aggregation Aggregation controls the way a collection of data is displayed. Most commonly Sum or Weighted Average, Aggregation can also be None, Minimum, Maximum or Average.
Allow Advance 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.
Array 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 section of the documentation is recommended.
ArraySpan 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}
Availability 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.
Calendar Hours 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.
Calendar Table 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).
Capacity Constraint 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.
Constant Related to the Expression Editor. Constants can be considered to be all of the possible options defined in Spry and are usually compared to Variables. Examples include Scenario Settings such as Equipment or Processes, as well as Table Positions and Fields.
Constraint 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 in Spry: Capacity, Proximity and Time.
Custom Field 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.
DateTime 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).
Dependency 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.
Double Precision Float Double Precision Floats refer to any number including decimal places. Common examples include physical properties (Area, Thickness, Volume, Tonnes etc.) and equipment rates.
Equipment 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.
Field 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.
Format String 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 available in Appendix 1 of the documentation.
Index The Index (as opposed to Name) of an item refers to its actual location in the Spry database. Most relevant with Positions as it affects the behaviour of Spans, Arrays and Wildcards. Indices (plural) in Spry are 0-based meaning the first entry is Index 0 rather than 1.
Initial State Initial State allows you to set a pre-mined or pre-scheduled state using the same text range style as Source and Destination Paths
Jump 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}
Leaf 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)
Leaves 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)
Level Each Table in Spry has one to many Levels. Each Level contains at least one Position within it and together these form the Table’s hierarchical structure. For example if your deposit had a structure with pit, strip and block the Table would have 3 Levels.
Level Filter 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.
Name The Name (as opposed to the Index) of an item refers to its description in the Spry database. Names are the most common form of reference in most elements of Spry. 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.
Node A Node refers to the progressive Position within the tree-oriented data structure of a Table. The bottom Node in a Table is also referred to as a Leaf. (Advanced – Scripting)
Node Filter A Node Filter is an 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.
Nonproductive Process 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 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).
Order 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.
Output Schedule 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.
Percentage A Percentage Field type refers to any number that is stored as a percentage. Common examples include qualities, Initial States and availability/utilisation.
Percentage 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.
Picked Range A Picked Range visually filters a Table using a tickbox for inclusion. Requires at least one Node Filter turned on to be effective.
Pivot Table A Pivot Table is a data summarisation tool that can automatically sort, provide totals or give the average of the data stored.
Point3D Point3D Field types refer to an XYZ position in real world coordinates.
Position Each Level in Spry has one to many Positions which can be considered to be the Level’s options. For example, in a Level called Month your Positions would be January through to December.
Predecessor Related to Dependencies: A Predecessor is a Task that is required to be completed before a Successor Task can be Released for scheduling.
Prefilter Range 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.
Prefix Related to Path Commands: A Prefix applies to all subsequent Path lines that describe a node or nodes. There is no default Prefix.
Process 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).
Productive Process 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.
Proximity Constraint 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.
Range Ranges group Leaves of data into groups. There are two types of Ranges (Text and Picked). Ranges are used in several places in Spry including Table View, Destination Paths, Animation, Haulage Logic and Constraints.
Rate Factor 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%.
Released 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.
Reporting Period 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.
Scenario A Scenario is the container of everything that Spry 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.
Snapshot Viewer The Snapshot Viewer displays the current and future behaviour of Equipment at a particular point in time and is a powerful troubleshooting tool for Source and Destination Scheduling. It can be used to diagnose the behaviour of Paths, Dependencies and Constraints and a thorough understanding of the relevant documentation is recommended.
Solid 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.
Source Path 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.
Source Quantity A Source Quantity is (generally) the property of a Productive Process or Task and represents the quantity or value that can be “worked”. Example Source Quantities are Volumes, Metres or Tonnes and the most work that can be done on any Source Quantity is 100%.
Span 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.
Successor Related to Dependencies: A Successor is a Task that is Unreleased (cannot be worked) until all of it’s Predecessors are completed.
Table Each Spry project has one to many 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.
Task A Task is either a Source or Destination work unit of the movement or processing of material. Scheduling in Spry 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.
Text Range A Text Range filters a Table using a written system similar to a Source or Destination Path but simplified. Uses Wildcards, Spans and Commas.
Text String 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.
Time Constraint A Time Constraint applies a limit to the times that a Source or Destination Task is available to be worked.
TKPH Ton 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. If the calculated TKPH is higher than the tyre’s rating, TKPH becomes a limiting factor. This will result in the Adjusted Cycle Time being increased until TKPH is equal to the Tyre Rating.
Utilisation 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.
Variable 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.
Wildcard 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.