Levels

A Parameters database will tend to have a fairly simple structure, with one, two or maybe three levels. If they have more levels than this, they tend to become too complicated and therefore lose one of their main benefits.

The levels will commonly be the same as specific levels in the Main database. For example, consider a Main database that has the levels Pit, Strip, Block and Seam. A Parameters database is required to store the coal loss thickness for the seam roof and seam floor. These parameters are different for each seam in the deposit and also for each pit. Since the parameters vary by pit and seam, these will be the levels required in the Parameters database.

The levels may also be a combination of Main database levels and some classification. For example, consider a Main database that has the levels Pit, Block, Bench. A Parameters database is required to store the loading unit productivity which varies according to the bench and the waste dump to which the block waste has been assigned. In this example, the Parameter database levels will be bench and waste dump.

In summary, the Parameters database levels will be defined by how the parameter varies.

Level Order

Since Parameters databases tend to have so few levels, the order of the levels is not usually critical. The decision will normally come down to which is the easiest format to enter, view and report on the parameters.

In the first example described above, if it is easier to enter all the seam data for one pit and then all the seam data for the next pit, etc, then pit should be the highest level. Conversely, if it is easier to enter all the pit data for one seam, and then all the pit data for the next seam, then seam should be the highest level. The following structure trees show how XPAC would display each level: