MineMarket Alias1 Values
Note: Words in coloured text refer to node names in the XML file. Words in bold refer to field names or data in MineMarket, or required text strings. Words in italics refer to field values in MineMarket.
Alias1 Configuration
The NotifyOperationsScheduled, NotifyWorkExecuted and NotifyWorkReconciled messages, used to import mine sources, require that to store the current product of the mine source, that there are products with the Alias1 of "Insitu Ore", "Insitu Waste" and "Overburden".
The NotifyPerformanceTracked message, used to export stockpile states, requires that, for exporting any despatch stockpile, there is one product with an Alias1 of "Product On Rail", "Product On Ship" or "Product On Barge", as applicable to the despatch type. ("Bauxite Shipped" is an accepted alternative to "Product On Ship" for backwards compatibility.)
Hierarchy Scope
B2MML includes a concept called hierarchy scope, which is related to the MineMarket supply chain, but has many more levels than the MineMarket supply chain.
The following table summarises the relationship between the B2MML hierarchy scope and MineMarket supply chain.
| B2MML Level | MineMarket Class |
|---|---|
| Enterprise | Business Area |
| Site | Business Area |
| Area | Location |
| ProcessCell | [Not supported] |
| Unit | [Not supported] |
| ProductionLine | [Not supported] |
| WorkCell | [Not supported] |
| ProductionUnit | [Not supported] |
| StorageZone | [Previously used for Location. Deprecated from MineMarket 5.6.0 and IMS Integration Hub 2.14.] |
| StorageUnit |
Stockpile Category [Supported for exported data only. Deprecated for imported data from MineMarket 5.6.0 and IMS Integration Hub 2.14. Replaced by MaterialActual»StorageLocation.] |
| WorkCenter | [Not supported] |
| WorkUnit | [Not supported] |
| EquipmentModule | [Not supported] |
| ControlModule | [Not supported] |
| Other | [Not supported] |
Assumptions
The ID of each object in B2MML is unique for a given level in a given hierarchy, but it might not be unique globally. The Alias1 of a MineMarket location, for example, must be unique among all locations.
Alias1 Convention
The following convention is important for supply chain configuration in MineMarket:
To guarantee the uniqueness of Alias1 values of business areas, locations and stockpile categories, prefix the Alias1 with the Alias1 of the object immediately above it in the hierarchy.
For example:
- A business area with an Alias1 of ABC (represented in B2MML as an enterprise with an ID of ABC)
- A child business area with an Alias1 of ABC_DEF (represented in B2MML as a site with an ID of DEF)
- A location with an Alias1 of ABC_DEF_GHI (represented in B2MML as an area with an ID of GHI).
Datamine recommends configuring the MineMarket supply chain with the same hierarchy as the B2MML model.
Topics for Agreement with an Integration Partner
For an implementation of MineMarket in which B2MML is to be used, there must be agreement with the integration partner about which hierarchy scope levels will be used in messages to and from MineMarket, and how, before the MineMarket supply chain is defined.
If messages that include unsupported hierarchy scope levels are sent to MineMarket, the messages may not be processed correctly. However, if those hierarchy scopes occur in parts of the messages that MineMarket does not use, the messages may still be processed correctly.
