CBM (Condition Based Maintenance)
- Last UpdatedDec 02, 2024
- 4 minute read
Condition-based maintenance is a maintenance strategy according to which maintenance is carried out based on a specified condition of the technical system (inspection). To be able to determine the condition, there must be a failure-forecasting variable. A failure-forecasting variable is the measurable physical property of the system, from which indications are obtained over time relating to the level of condition. Examples of condition monitoring techniques include oil analyses and vibration measurements. It only makes sense to apply CBM if the technical system shows a steady and predictable decline in condition (linear or progressive) and if the failure-forecasting variable can be measured. Standards also must be set on the basis of which decisions can be made on maintenance actions to be taken and the period within which these actions have to be executed.
CBM and CBM Follow-up
Within CBM, a distinction is made between the inspection to be carried out and (any) subsequent maintenance actions. The inspection is referred to in Asset Strategy Optimization as CBM and the follow-up action as CBM follow-up. Adding an inspection is done in the same way as adding a corrective action (the FBM). Again, there are three sections that can be filled: General, Preventive and Costs. The General and Costs sections are completed in the same way as with an FBM action. The Preventive maintenance section is filled in differently and will be described here. The CBM Follow-up can be defined as a child object of the CBM or can be copied from an existing FBM by dragging the FBM and dropping it onto the CBM object. In that case, the copied FBM will be automatically converted into a child CBM-follow object.
Clustered Maintenance linked CBM action 
A CBM action which is linked to a CLM action has a different icon in the tree-view
( versus 
), to inform the user that the UBM action is linked to a CLM action.
Creating an FBM action
Creating an FBM object is similar to the steps in Create an FMECA system.
|
FIELD |
DESCRIPTION |
|
Description |
Users are free to enter any description for the object. The logical option is to describe the action performed when repairing or replacing the component, for instance "Repair spray head", where the component is the spray head. |
|
Number |
A maintenance action can be numbered. When configured, the number will be listed in the tree with the Description of the FBM. |
|
Maintenance time/unit |
Duration of the maintenance action. Select an appropriate unit of time. |
|
Mandatory |
This field can be set to indicate that the modeled maintenance is mandatory, for example
because of legislation. Marking it as mandatory is a signal that the maintenance should
not be changed or removed without careful consideration. This is highlighted by the
object icon |
|
Costs |
Costs can contain different sections: Maintenance category, Cost categories, and Total Costs. |
|
Maintenance category |
Select here from Minor maintenance, Major maintenance, and Renewal. |
|
Cost categories |
The options to enter in this field are predefined. Categories can be defined in the desktop version. Examples of cost categories include personnel, material, and equipment. |
|
Total costs |
This field has a dual function: If Cost categories are not used, the user may enter a cost value directly in this field. If costs have been specified using the cost categories, then this field will automatically show the sum of these values; in this case the field will be read-only; only when all the values in the cost categories have been reset to 0, will the field Total costs become editable again. |
|
Environmental Impact |
Based on the categories configured in System Options, the impact categories appear. In the field, enter the category value to calculate the Total CO2e. To know about this option, see the topic Environmental Impact. |
|
Free fields |
If Free fields are enabled in the desktop version, each of the fields will be shown here and can be edited dependent on the user rights. |
.