Process findings and SOP conformance in Duaer

What the findings say

Under Process findings on the process sources page, each finding comes with its number of cases and the median time:

• Waiting: for example “Received → Test started: 15% took over 5 d”, and now “12 waiting at Received over 5 d”.
• Rework: for example “Reviewed done more than once: 8%”.
• Likely late: for example “18 at Assigned likely to go over 2 d (100% did)”. The cases are not late yet, but at least half of the cases that waited that long at the step went over its limit. The limit is the same as for waiting. It can propose a card rule too; once adopted, the cards reach the owners before the limit. The employee portal’s case timeline and Cases by level mark a case that is likely late.
• Cause: for example “Mostly lab B”, from the attributes chosen in the mapping.
• Waiting on a lower level: where sources have levels (such as orders and order lines), for example “7 waiting on Order line Packed over 4 d”: the order is not finished and its slowest line has sat at that step longer than usual. It can propose a card rule too; once adopted, the cards go to the orders’ owners.
• Causes across levels: an order’s cause may come from its lines, such as “Mostly Order line at Packed” or “Mostly Order line·sku SKU-107”; a line’s may come from its order, such as “Mostly Order·customer East Build”.

Only patterns in at least 20 cases and at least 10% of them count as findings. Duaer recomputes them daily and after every read; select Check now to do it at once.

Turn a finding into a card rule

1. On a finding, select Propose card rule. The proposal becomes a card rule waiting for approval, shown as Waiting for approval.
2. Once an owner or admin approves it, it shows Adopted and matching cases start getting cards in the employee portal.
3. Open Value: how many cases ran over in the 30 days before adoption and in the latest 30 days, the change in points, and how many cards were decided. With too little data it says Not enough data since adoption yet.

Dismiss a finding you do not need; Restore brings it back. For how card rules write cards, refer to the Duaer tasks table.

Compare with your SOP

1. On the source, select SOP, find your SOP with Search the knowledge base for the SOP and tick one or more items. Duaer reads only documents you are allowed to open.
2. Select Read the steps. Duaer reads each step’s name, whether it is required and its time limit where the SOP words one (“within 24 hours”), and matches each step to a step in your data. Without a usable answer it reads the numbered lines.
3. Check each name, activity, Required and Time limit, then Save SOP.

How the cases follow the SOP shows the fitness and how many cases follow it fully, which step is skipped by how many cases, which two steps happen in the reverse order, which step runs over its limit, and steps the SOP does not have. With findings on, these also appear as findings, without a card rule to propose.

Performance spectrum and cases on the employee portal

Above the process map on the employee portal there are Map, Performance spectrum and Cases. All three show the same cases: those the person may see, narrowed by the map’s filters.

• Performance spectrum: pick a connection, such as Assigned → Resolved. The top line is when cases reached the first step, the bottom line when they reached the second; each case is one line, and the more it slants, the longer it took. Lines are coloured in three bands: up to the median, up to the limit, over the limit, with the same limit as findings. Point at a line to see the case and its time; select it to open the timeline.
• Cases: one row per case with its id, object type, current step, since when, elapsed time and status (Open, Finished, Likely late). Find a case by id, filter by object type or current step, show only open or only likely-late cases, sort by any column, and select an id to open its timeline. A case at an end step of its process counts as finished; steps dated after now are left out.

Simulate a change

Before changing how work is done, see what it would bring, computed from the cases already recorded. It only calculates: nothing is changed or saved.

• Employee portal: Simulation above the process map. Choose A connection gets faster (by a share, or at most so many days), A step is no longer redone (the loop back to it and its time go) or A step is dropped (the step and the wait for it go). It uses the cases the map’s filters keep.
• Process findings: Simulate on a bottleneck, waiting, likely-late or rework finding works on the finding’s connection or step, 30% faster to start; change it to another share or a number of days.
• Results compare now and after: cycle time median and P90 (finished cases, first step to an end step), late cases and on time (with the same limits as findings), and the time saved across all cases and how many cases change. A step recorded twice at the same moment counts once, not as rework.