The Filter column contains a filter for each row and defines what XPAC will display in the Result column for that row.
The following table lists all the valid components of a filter statement:
Component |
Meaning |
= |
Equal to |
> |
Greater Than |
< |
Less Than |
>= |
Greater Than or Equal to |
<= |
Less Than or Equal to |
n |
Numeric value for use in conditional statements, eg. M(mOre_Fe) > 62.0 |
"Text" |
Text from a classified field in the main database, used in a conditional statement. The text must be inside double quotes. eg. GetClass(mProd_Type) = "Bypass" |
M(mCode) |
Value in a main database data field for the record in each scheduling step. It is used in conditional statements. mCode must be a valid data field number or code in the main database. eg. M(mWst_Thk) < 0.5, M(50) < 0.5. |
And |
Logical And used with conditional statements. Both the conditional statement before and after the And must be valid or true for a scheduling step to pass the filter. eg. M(mAl2O3) < 2.6 And M(mSiO2) < 3.5 |
Or |
Logical Or used with conditional statements. Either the conditional statement before or after the Or must be valid or true for a scheduling step to pass the filter. eg. M(mCl_Thk) < 0.3 Or M(mCl_Ash) > 25.0 |
Not() |
Logical Inverse used with conditional statements. If the conditional statement is valid or true for the scheduling step, then it will not be passed by the filter. If it is invalid or not true, then it will be passed by the filter. eg. Not (GetClass(mOre_Type) = "Sulphide") |
Activity(number) |
The activity function can be used to over-ride the productive activity number associated with the data field(s) in the Result, eg. Activity(3) The activity function can also be used to report the duration, in calendar or operating hours, of non-productive activities, eg. Activity(102) The number in the brackets can be any valid productive or non-productive activity number. |
Resource(name) |
The resource function can be used to only pass steps scheduled by the specified resource. The name of the resource is exactly as it is in the tree structure in schedule setup and it should be inside double quotes. eg. Resource("Dragline107") |
Pil(level, position) |
This function is used to filter the scheduled steps according to their position in level numbers. The schedule steps that are passed by this filter will have the specified position number at the specified level of the database, eg. Pil(4,5) To filter a range of position numbers, use the GetApil function. |
GetApil(level) |
This function is used in a conditional statement to filter the scheduled steps according to their position in level numbers. The function will return the position in level number at the level specified inside the brackets. eg. GetApil(4) >= 5 |
StepType(number) |
The Step Type function is used to filter steps according to their activity types. The number in the brackets can be one of the following: 1 Productive Steps. 2 Non-Productive, Non-Operating Steps 3 Non-Productive, Operating Steps 4 Non-Productive, Extended Operations 5 Non-Rostered (Non-Operating) Steps IMPORTANT NOTE |
GetClass(mCode) |
This function is used in a conditional statement to filter the scheduled steps according to the value in a classified Main database data field. The function returns the value of the data field with the specified full code name or number in the brackets. eg. GetClass(mRamp_Name) = "16E", |
GetDestApil |
This function is used in a conditional statement to filter the schedule steps according to the position in level numbers for their destination. The function will return the position in level number at the level specified inside the brackets. The level number is passed as an integer. The value of the level number must be between 0 and the level of the output path records. The maximum level number possible in XPAC is 10. The function will return the absolute position in level (PIL) number as a long data type. If the level number is invalid, the function will return a zero. eg. GetDestApil(0) = 2, |
Destination(Destination Name) |
This function returns true if the current output steps destination is the same as the supplied destination. This filter works for Stockpiles and Dumps. Eg. Destination("OVERFLOW") |