 Based on the provided data and processes, here are the main anomalies:

1. **Performance Discrepancies:**
   - The performance value for the process with frequency 16 is significantly higher (98982000.000) compared to other processes with similar frequencies. This could indicate an anomaly or an outlier.
   - The process with frequency 14 and performance 54709714.286 also has a relatively high performance value compared to other processes with the same frequency.

2. **Process Sequence Anomalies:**
   - Some processes have "Payment" steps occurring multiple times in succession, which might be unusual or unnecessary:
     - Frequency 14: Create Fine -> Send Fine -> Insert Fine Notification -> Payment -> Add penalty -> Payment -> Payment
     - Frequency 13: Create Fine -> Send Fine -> Insert Fine Notification -> Add penalty -> Payment -> Payment -> Payment -> Payment
   - In some processes, "Insert Date Appeal to Prefecture" comes before "Insert Fine Notification", which seems illogical as the fine notification should typically come first:
     - Frequency 10: Create Fine -> Insert Date Appeal to Prefecture -> Send Fine -> Insert Fine Notification -> Add penalty -> Send Appeal to Prefecture

3. **Incomplete Processes:**
   - Some processes do not end with a expected terminal step (like Payment, Send for Credit Collection, or Notify Result Appeal to Offender):
     - Frequency 12: Create Fine -> Payment -> Payment (stops at Payment)

4. **Unexpected Steps:**
   - The process with frequency 9 includes an "Appeal to Judge" step followed by "Payment", which might be unusual as typically after appealing to a judge, one would expect a result or further action before payment:
     - Frequency 9: Create Fine -> Send Fine -> Insert Fine Notification -> Insert Date Appeal to Prefecture -> Send Appeal to Prefecture -> Add penalty -> Receive Result Appeal from Prefecture -> Notify Result Appeal to Offender -> Appeal to Judge -> Payment