Giving feedback¶
Your answer on a finding is the most useful thing you can give Artekis. It decides what Artekis reports next time, and your answer stays on record with your name and the time.
The four answers on a finding¶
| Answer | Use it when | What happens |
|---|---|---|
| Confirm | The problem is real and worth acting on. | The finding stays open until the readings return to normal. |
| Known issue | It is real, but you already know about it (a repair is planned, it is waiting on parts). | Artekis stops reporting this pattern for a while (30 days by default), so it does not keep raising what you already know. |
| Dismiss | It is not a problem for your plant. | Artekis stops reporting this pattern for longer (90 days by default). |
| Wrong | Artekis misread the data, or the explanation does not hold up. | The finding is closed and the pattern is not reported for 90 days, as with Dismiss. It is also kept as a test case for tuning the check, so add a note saying what Artekis got wrong. |
You can add a note to any answer. Your plant's administrator can change the 30 and 90 days.
In the Anomaly Watch queue¶
Unusual readings in the Anomaly Watch queue take three answers: Real issue, Known and Not an issue.
A Real issue on an unusual reading does more than record your answer: Artekis proposes an alarm rule for it (a detector) and replays that rule over the last weeks of history to show how often it would have fired, how many of those were real and how many would have been false alarms. An engineer reviews the rule and, if it is good, imports it into Ignition as an ordinary tag alarm. From then on Ignition itself alarms on it, live, without Artekis.
Who can answer¶
Who may record an answer is set by your administrator. If you cannot see the answer buttons, your sign-in can read findings but not judge them.