Minor changes are by default collapsed in the page history.
No changes
The page does not exist yet.
Failed to load changes
Version by on
Leave Collaboration
Are you sure you want to leave the realtime collaboration and continue editing alone? The changes you save while editing alone will lead to merge conflicts with the changes auto-saved by the realtime editing session.
Information
This site will undergo a brief period of maintenance on Friday, 18 December at 12:30 AM Central/12:00 PM IST. During a 30 minute window, site availability may be intermittent.
Information
This documentation supports the 20.02 version of Remedy Service Desk.To view an earlier version, select the version from the Product version menu.
Establishing the root cause
When performing a root cause analysis, you try to establish the problem's root cause. Even if the problem investigation was triggered proactively by your organization's capacity management system, you must determine why the service infrastructure is running out of capacity.
After you determine the root cause, take the following steps:
Look at the Workaround field to review any previously proposed workarounds. With the root cause now known, if necessary, propose a better workaround and describe how to implement it. For information about how to do this, see Proposing-a-temporary-workaround.
If you cannot determine the root cause, you must record this also in a work information note on the Work Detail tab. Ensure that you record why a root cause cannot be found, and be sure to record the activities that you performed to determine that a root cause cannot be determined.
If the root cause analysis is temporarily unable to progress (for example, if you are waiting for information from a supplier), make sure you set the problem investigation's Status field to Pending, and then specify why in a work information note on the Work Detail tab. See Creating-work-information-entries for information about how to do this.