Transaction Editors
Production transactions are a record of the movement of bulk material through the supply chain across predefined process flows that link the locations together, from the mine sources to the run of mine (ROM) stockpiles, and from there through the various production processes to the final product stockpiles.
The material movement is undertaken by some mechanical means (for example, conveyor), or by truck, in which case, various trucking factors can be recorded.
Transaction Editors
The parameters of the transaction are set up beforehand in a transaction editor. This is a transaction template that defines what information is to be recorded for the transaction.
There are three types of transactions:
- Standard—incorporate no truck movements, but can apply to stock movement; for example, by conveyor belt
- Truck—allow a number of individual trucks to be selected
- Truck type—allow for all of a group of trucks under a particular truck type to be selected
For transaction editors in 3D Stockpile Modelling, use the standard transaction type.
The movement product, that is, the product moved in the transaction, can be predefined for the transaction. This is usually done when one explicit product cannot be deduced from the process flow.
Transaction editors are used for transaction data entry. Existing transaction editors can be edited.
For transaction security, each transaction row in the transaction group can be edit-enabled or edit-disabled once transaction data is entered. This means that the source and destination stockpiles or mine sources and tonnages can be made non-editable. Note that sample editing is controlled by the sample template configuration set for each transaction template.
Sites are usually configured to have the transaction editors around processes, rather than just one process flow. For example, if there were a few process flows for transactions from the mine to the crusher, all of those process flows would be included in a single transaction editor. A logical grouping might also be if the data entry of transactions for a group of process flows were done at the same time (that is, the entry of the trucking data for one shift).
When a transaction editor for transactions by truck type is configured, and a waste process flow added to it, only mine sources that have waste products added to them are possible source locations when entering transactions using the transaction editor.
A transaction editor must belong to a transaction editor category or sub-category.
Standard Conveyor Movements
Standard conveyor movements differ from truck or truck type movements, in that the total quantity moved is always entered, instead of a calculation based on truck factors.
Truck Movements
Truck movements allow for the total quantity of material transacted over a period (for example, a shift) to be calculated based on the number of truck trips and their typical tonnage or volume.
Truck movements differ from truck type movements in that a specific truck is selected, with its defined tonnage or volume, instead of a generic truck type with a standard tonnage or volume.
Truck Type Movements
The truck type movements allow for the total quantity of material transacted over a period (for example, a shift) to be calculated based on the number of truck trips and their typical tonnage or volume.
Truck type movements differ from truck movements in that a specific truck type is selected, with a standard tonnage volume used instead of that of a specific truck.
Generally, truck or truck type transactions are used when the truck moves material within one business area, and truck despatches are used when the truck moves material between business areas.
Example: Business Area 1: Mine Site, Business Area 2: Port
All trucking between locations at the mine site is performed using truck or truck type transactions. All trucking between locations at the mine site and locations at the port is performed using truck despatches.
Video
A Datamine consultant recorded this video about transaction editors in MineMarket.
