Name: Assessing Priority of a Maintenance Request Based on Consequences and Likelihood in SAP S/4HANA Maintenance Management
Uploaded: 2023-10-2
Duration: 330 s
Description: Learn about event prioritization of a maintenance request in SAP S/4HANA Maintenance Management!

Share feedback

Planned maintenance of Practice Systems

Planned maintenance of Practice Systems

Why create an SAP account?

Enhance your learning experience

SAP Learning

Subscribe now

Learn more

Live Sessions

Hands-on Practice

Certification

My Learning

Ready to start learning?

Learn about event prioritization of a maintenance request in SAP S/4HANA Maintenance Management!

Assessing Priority of a Maintenance Request Based on Consequences and Likelihood in SAP S/4HANA Maintenance Management

Welcome to this Microlearning video where we will be discussing event prioritization, assessing the priority of a maintenance request in SAP S/4HANA Maintenance Management. A notification is used to request and document a maintenance activity. To initiate the corrective maintenance of a technical object whenever a breakdown or failure occurs, you can create a notification, a maintenance request. In SAP S/4HANA Cloud and since SAP S/4HANA version 2021, the Maintenance Management solution provides a feature for event prioritization, which enables you to define consequences and likelihoods to assess priorities for a maintenance request in a structured and flexible way. Defining the correct priority while reporting a functional failure of an asset is extremely important in terms of speeding up repair time, reducing the impact on the environment, ensuring personal safety, and managing the financial impact. You can use the Create Maintenance Request app to easily request the maintenance work or repairs to be done on a technical object. While creating a maintenance request, the app helps you provide all the relevant information required to solve the problem as soon as possible. You can use the Help Guide to get further details about the available fields. For instance, let's say a maintenance worker sees oil leaking from a pump in maintenance plant 1010 and wants to report it. They would select the pump, note down its location, the failure mode group, the failure mode, the detection method, what the effect is, and whether it is a breakdown. They would then write a brief description and provide more details in the long text with answering questions based on a template. While the selection of a priority can be as simple as selecting from a list of priorities, adding more context to why that priority was selected helps planners, reliability engineers, and maintenance supervisors in assessing the criticality of the job. The event prioritization process consists of three main dimensions. Consequence categories such as safety impact, financial impact, environmental impact, or regulatory impact. Possible consequences for each consequence category. Possible likelihoods for all consequences. You may configure as many consequence categories as you want depending on your business needs. The consequence defines the specific dimension of impact if the failure is not fixed. Likelihood defines the probable occurrence of the selected consequence. The mapping between consequence, likelihood of occurrence and the calculated priority is configured and assigned to a notification type for a given maintenance plant. All these dimensions can be customized based on business needs. At each consequence category level, you can enter the consequence and its likelihood, and based upon the customizing settings, the priority for the respective consequence category is derived by the system. You can delete the selection and reselect them, or you can change each of these aspects and see how it influences the overall priority for the category. Upon pressing the Assess button, the system calculates the overall priority for this maintenance request. The standard logic used to derive the final priority is to pick the highest priority among all the consequence categories. The highest priority in this example is high, so the same will be selected as the final priority in the notification. After the assessment, despite being able to modify the priority manually, the system will give you a warning message. Once the Priority Assessment has been completed and the details are filled, you can submit the notification. With this, the system automatically jumps to the My Maintenance Request app, where you can see the actual status of your notifications. As a next step of the 9-phase maintenance process, this notification can be reviewed. At this stage the reviewer can check the assessment and - in this example - change it. Appropriate assessment can lead to reduced downtime that may affect the overall production process. A well-defined priority also helps a maintenance supervisor or operations maintenance coordinator to group-related issues for subsequent execution by the appropriate engineers. After that, we proceed with accepting the maintenance request. With this, we jump into the planning phase, where we can continue the 9-phase maintenance process, for example, with a work order creation.