Name: Introducing Condition-Based Maintenance in SAP S/4HANA Cloud Maintenance Management
Uploaded: 2023-9-21
Duration: 226 s
Description: Learn about condition-based maintenance in SAP S/4HANA Cloud. Discover how CBM helps prevent equipment failure by monitoring asset conditions and triggering maintenance activities. Watch now!

Share feedback

Planned maintenance of Practice Systems

Planned maintenance of Practice Systems

Why create an SAP account?

Enhance your learning experience

SAP Learning

Choose your subscription

Manage your subscription

Live Sessions

Hands-on Practice

Certification

My Learning

Ready to start learning?

Learn about condition-based maintenance in SAP S/4HANA Cloud. Discover how CBM helps prevent equipment failure by monitoring asset conditions and triggering maintenance activities. Watch now!

Introducing Condition-Based Maintenance in SAP S/4HANA Cloud Maintenance Management

Welcome to this microlearning video where we will be discussing Condition-Based Maintenance in SAP S/4HANA Cloud. First, let's define what Condition-Based Maintenance, CBM, is. CBM means that based on the condition of the asset, a maintenance activity is executed. The end goal is to listen to the various parameters of an equipment and catch the anomaly before it leads to the failure of a machine. The condition of an asset is determined by how efficiently it is performing and fulfilling its purpose. In simple terms, condition-based maintenance means that if a measurement reading crosses a limit, it triggers an activity that will bring the parameter back within limits. In S/4HANA Cloud, the CBM process begins by creating a measuring point for a technical object. In this example, our asset will be a cooling water circulation pump, and we will monitor the inflow temperature. On the initial screen, the measuring point category also has to be selected. CBM needs to be enabled through a few customizing steps, which are described on our Help portal. Next, we maintain the details of the measuring point, such as its description or the characteristic, which determines the unit of measure, number of characters and decimal places. To monitor the inflow temperature of the pump, we set target and define the limits and tolerance in the additional data tab. In this demo, the target temperature is 35 degrees Celsius with an upper limit of 70 and a lower limit of 25. However, you might not want to wait till the measurement crosses these limits: The tolerance can be defined in the unit of measure or in percentage. These values represent less critical limits where you may want to be notified when thresholds are reached. The next step is to enable conditions and define the maintenance object to be created. In this demo, we will create a reactive maintenance request. We also fill in the details of the notification, such as priority and description. Don't forget to activate the used conditions. In this example, we've set conditions for both the lower and upper limits, but you can also set these rules for tolerance limits. By clicking on Save, the measuring point creation process is complete. To see what happens when the threshold is reached, we need to create a measurement document. Since the upper limit is set at 70 degrees Celsius, recording a value of 82 should trigger the creation of a notification with the defined details. Saving this new value generates the measurement document. By opening this document in the Change Measurement Document app, we can see the maintenance request number. By clicking on it, the details of this object can be displayed. To proceed with the condition-based maintenance, this notification can be reviewed. In this example, we will go ahead and accept it. With this, we jump into the planning phase, where we can continue the 9-phase maintenance process, for example with a work order creation.