The Reporting Database
In the Reporting database, the hierarchy of data entities are displayed as views with a V_ prefix. The Equipment hierarchy, for example, comprises three views: V_EquipmentFunction, V_EquipmentModel, and V_Equipment.
There is a correlation between the views in the Reporting database and the reference groups configured in Reference Edit.
Data Entities and Items
Reference Data is configured by defining data entities such as equipment, locations, and personnel. Each instance of an entity is an item of data, for example Truck1, LocA, John Smith, etc.
A data entity can be an attribute of another entity in a hierarchical structure. For example, an attribute of equipment is equipment model, and an attribute of equipment model is equipment function.
Active Lists
Active lists are the selection lists used by Pitram applications such as Data Acquisition and the Event Editor, or by Pitram Portal services such as Reporting, Drill and Blast and Grade Control. You can think of them as subsets of the records in a reference group table.
Drills, Dumps, Trucks, Loaders and Service Equipment active lists may be derived from the same Equipment table, for example.
In Data Acquisition, active lists can be used to identify which breakdown states apply to which equipment units, or which dump locations are valid for a particular source location, etc.
Mandatory Column Set
Every data item must have a Code, Description and Abbreviation that uniquely defines that item in its reference data group. The following mandatory columns are common to all views in the Reporting database:
| Column | Description |
|---|---|
| [ViewName]Code* | This column is provided for backwards compatibility with Micromine Pitram 2 sites. See "Source_Code" below. |
| [ViewName]_Code* | The numeric value in this column is generated automatically by the system and uniquely identifies a location. |
| If the location is a sublocation, then the Source_Code has a prefix = s, followed by the numeric. | |
| [ViewName]_Description | This is the name of the location as it is known on site. The suffix of the code may be edited. |
| [ViewName]_Description_Code* | The value in this column is generated automatically by the system. It is a copy of the Source_Code. |
| [ViewName]_Abbreviation | This is an abbreviation of the name of the location as it is known on site. Often the same value as the Source_Description, this value may be edited. |
* Columns that cannot be edited in Reference Edit.
Columns defined by the system.
Each column in a view is usually prefixed by the view name. However there are exceptions to this naming convention. Each view includes the Mandatory Column Set (described above) plus additional columns.