Performance Formulas screen - HxGN EAM - 11.07.01 - Feature Briefs - Hexagon

HxGN EAM Asset Performance Management

Language
English
Product
HxGN EAM
Search by Category
Feature Briefs
HxGN EAM Version
11.7.1

Asset Performance is defined as a function of condition, operational capacity, reliability, and maintainability. On the Performance Formulas screen, these four variables are associated with a weight. Six additional variables and weight combinations can be defined for the formula. These ten variables combined, make up the equipment "overall" performance number, which is the sum of the weight multiplied by the variable rating of each of the ten variables. Note that it is not necessary to use all ten variables.

The Performance Formulas screen displays these important attributes:

  • Performance Formula: The unique identifier for the formula.

  • Organization: Organization of the formula. Can be common.

  • Description: Short description of the formula.

  • Status: System Codes of type entity "PFST." Select one of these options:

    • Unfinished (U): Formula data can be changed.

    • Request Approval (RA): Formula data is protected.

    • Approved (A): Formula data is protected and can be used for performance calculations.

  • Class: If you have many different formulas you may want to use the Class field to group formulas together. Like other screens in HxGN EAM, this field is also used to determine the relevant custom fields.

  • Date Approved: This date gets populated automatically at the time of approval of the formula. It plays an important role in determining the equipment that should be included in the aggregation of performance numbers to equipment class and category levels. But more on that later in the section on calculating performance on category and class level.

Condition and Capacity Details section:

  • Condition Rating Weight: Specify the weight that must be assigned to the Condition Rating of the equipment when calculating the equipment performance. Enter a value between 0 and 1. If the condition rating of the equipment should not be included in the performance calculation, you can enter 0 or leave this field blank.

  • Capacity Rating Weight: Specify the weight that must be assigned to the Capacity Rating of the equipment. For more details on weights see Condition Rating Weight.

  • Capacity Code: Specify the capacity code that will be used for this formula. On the System Codes screen, use the code entity "CACO." This code must also be used on the corresponding equipment when defining capacities on the Capacities tab.

MTBF and MTTR Details section:

  • MTBF Rating Weight: Specify the weight that must be assigned to the MTBF Rating of the equipment. For more details on weights see Condition Rating Weight.

  • Maximum Allowable Failures per Year: Specify the number of failures at which the MTBF Rating should be set at 0. If you specify 10 here, the system will assign 0 to the rating if it finds 10 or more failures. If, for example, the system finds 5 failures, the rating will be set at 50. And with 0 failures, the equipment will get the maximum rating of 100.

  • Include Children: If you select this option, the system will include the failures associated to children of the equipment in the failure count as well.

  • Usage Based: If you select this option, the system will also calculate the number of failures relative to the usage of the equipment. For example, for a bus it may be more relevant to know that there are 10 failures per 10000 miles than 10 failures per year.

  • At Usage Per Day: For the usage-based calculations, you also need to specify the usage of the equipment per day. That way the system can convert the allowable failures per year to a number per miles or kilometers. For example, at 150 miles per day, 10 failures per year would be the equivalent of 365 * 150 / 10 = 5475 miles per failure.

  • MTTR Rating Weight: Specify the weight that must be assigned to the MTTR Rating of the equipment. For more details on weights see Condition Rating Weight.

  • Maximum Allowable Repair Hours: Specify the number of repair hours at which the MTTR Rating should be set at 0. This serves the same purpose as Maximum Allowable Failures per Year.

  • Repair Time Calculation: You can select one of two options:

    • Daily Maximum Booked Hours: Repair time is determined by adding the maximum hours booked against the work order for each day a booking is recorded. To avoid double counting, the system only includes the maximum hours of one of the employees. For example, if there are 5 booking records against the work order and Employee A booked 2 hours on day 1 and 4 on day 2 and Employee B booked 7 hours on day 2 and 1 on day 3, the repair time will be 6 (Employee A: 4 and 2) plus 7 (Employee B: 7) plus 1 (Employee B: 1) is 14 hours.

    • WO Closed / Reported: Repair time is the difference between the work order Date Completed and the Date/Time Reported (time component is relevant for both).

  • Use Downtime Hours if Present: If you select this option, the system will use Downtime Hours from the work order to determine repair time. If this field is blank, the system will revert to the calculation based on the selection you made for Repair Time Calculation.

  • Variable Details section:

In this section of the performance formula, you can setup the use of 6 additional configurable parameters and weights to include in the performance calculations. Since all variables work the same way, we will only describe variable 1.

  • Variable 1 Rating Weight: Specify the weight that must be assigned to the Variable 1 Rating of the equipment. For more details on weights see Condition Rating Weight.

  • Variable 1 Query: Create a query on the Queries screen in HxGN EAM. These queries should be compatible with an inbox or KPI query but will likely be setup as an Equipment Ranking query because that query allows searching for data related to the equipment because it makes use of the :OBJECT and :OBJECTORG parameters in the where clause.

  • Best Acceptable Result 1: The query that you select for variable 1 must return a number. The system does not know which numbers to expect, so for that reason you must also specify the significance of these numbers and identify whether they are good or bad. Note that a good number may not always be the lower number, like it is for failures. It may be that the good number is the high number. For that reason, you need to specify what is best and what is worst.

    Example: If Best Acceptable Result 1 is set to 50 and Worst Acceptable Result 1 is set at 25, then:

    • 50 and higher will be good and will be assigned a rating of 100

    • 25 and lower will be bad and will be assigned a rating of 0

    • any number between 25 and 50 will get a rating relative to its position between 0 and 100. For higher numbers, the rating will be closer to 100.

      With the same query you can also swap the 25 and the 50. In that case 50 is bad and therefore 50 and higher will be assigned a rating of 0, 25 and lower a rating of 100. Numbers between 50 and 25 will get their rating assigned the same way, but now the lower numbers will get a rating closer to 100.

  • Worst Acceptable Result 1: See the explanation of Best Acceptable Result 1.