RCM++ and RBI allow users to define a variety of task types for scheduled maintenance, so that the available task types match their organization's terminology. In order for simulation and cost calculation results in RCM++ and RBI to be accurate, it is necessary to map these task types to the three scheduled task classes used in URDs (i.e., preventive, inspection or on condition). To define the available task types, including their task class association, choose File > Manage Repository > Task Types.
(In a secure database, this is available only to users with the "Manage other repository settings" permission.)
The table in the window displays a list of the existing task types defined for the database. For each task type, you must specify a name, an abbreviation of up to three characters, and a task class that it corresponds to. Click the cell in the Task Class column to choose one of the three scheduled task classes from the drop-down list. You can have multiple task types that use the same task class. This can be helpful in indicating to users which properties should be defined for a given task. For example, a service task and a failure finding task could both be classified as inspection tasks for the purposes of the simulation; however, for the service task, a user will want to define a restoration factor, whereas for the failure finding task, no restoration occurs.
To edit an existing task type, click inside the cell and either edit the text (in the Name and Abbreviation columns) or choose a new option from the drop-down list (in the Task Class column).
To add a new task type to the bottom of the list, click inside the last row and enter the data.
To delete a task type, select the row and click the Delete icon. There is no undo for delete.
To insert a new task type above an existing one, select the existing row and click Insert.
To move an existing option up or down in the list, select the row and click the Move Up or Move Down icon.
What's Changed? In previous versions of RCM++, task types and the cost calculation methods associated with them were defined via the task selection logic.
© 1992-2017. HBM Prenscia Inc. ALL RIGHTS RESERVED.
E-mail Link |