Create an Issue

Create an Issue when a task reveals an abnormal condition that needs investigation or follow-up after the round.

Create an Issue directly from a round task or from the Issues screen.

  1. Open the Create Issue screen.
    • From a round task: Use this when you notice an abnormality while executing a Round task. For example, if the vibration reading for P-204 approaches the alert threshold, tap Issue below the task. The screen is prefilled from the task — asset or functional location, troubleshooting details, issue type, and priority.
    • From the Issues screen (independently): Use this when the finding is not related to the task you are completing. Tap the Add Issue icon at the top, then select the asset and location. For example, if you notice a problem with P-210 while completing a task for P-204, you can create an Issue for P-210 even if it is not on your assigned route.

    If the condition has already been reported: mRounds checks for existing Issues on the same asset or location before you complete the form, and shows them to you. From a round task the check runs when the screen opens; from the Issues screen it runs once you have selected the asset and location. The check covers ERP notifications as well as mRounds Issues, and resolved Issues can be filtered out. The check helps you avoid reporting a condition someone has already raised.

  2. Fill in the Create Issue screen.

    Title, Description, and a photo describe the condition. Category and Priority decide what happens to the Issue next. Read these two rules before you fill the form.

    Category changes where the Issue goes. Choosing Maintenance sets Convert to ERP Notification to Yes, and the Issue is converted to a notification automatically. It leaves mRounds and lands in the maintenance system.

    The other categories — Observation, Incident, Near Miss, Hazard — keep the Issue in mRounds, where it is tracked and closed by your team.

    Priority — check the risk matrix first. Tap the help icon next to Priority to see the instructions for determining risk-matrix-based Priority. Do this before you select a value.

    For Shutdown and Turnaround priorities, selecting the consequence makes Impact, Likelihood and Spare availability available, and those are carried into SAP.

    Table 1. Issue fields
    Field What it does
    Title and Description What the condition is and where the equipment is.
    Photo Evidence of the condition. Photos are stamped with the time and location they were captured.
    Event Execution Shutdown, Turnaround, or General — the work context the Issue belongs to.
    Plant, Unit, Location, Asset Where the condition is. Prefilled when you create the Issue from a round task.
    Assigned To The user or user group that owns the follow-up.
    Start and Due date and time When the follow-up should begin and when it is needed by.
    Status Open, In-Progress, or Resolved.
    Figure 1. Create Issue


  3. Expand More Details and complete the location, ownership, and dates.
    1. Select the Plant, Unit, Location, and Asset.
      Note:
      Plant and Unit auto-populate from your User Preferences.

      When you scan an asset, these details are added instantly.

    2. Select an operator from Assign to, then tap Save.
    3. Select the Start Date and Time and the Due Date and Time.
    4. Select the Status.
    Figure 2. Fill More Details


  4. Switch on Convert to ERP Notification if the Issue belongs in the maintenance system.

    Already on if you chose the Maintenance category.

  5. Tap the Create button in the top-right corner.

The Issue is created and appears in Open Issues. If it is assigned to you, it also appears in My Issues.

Next: If you are responsible for the investigation, assign the Issue to yourself. Return to the round and continue the remaining tasks.