April

Multi-sample input for Yes/No checklist tasks

Multi-sample checklists extend to Yes/No task types. Operators record multiple pass/fail checks within a single task, with the system tracking completed samples against the required count.

The required sample count is configured per task in checklist settings, following the same setup as measurement-type multi-sample tasks.

Multi-value task 1.png

Usability improvements

March

AI-powered analysis for downtime extra notes

Extra notes AI.png

Reading through hundreds of operator notes to find the root cause of a recurring issue is time-consuming and often results in missed patterns. While individual notes provide clues, the "big picture" usually stays hidden in the notes.

The new AI extra notes analysis turns raw text into actionable insights. By using AI, Evocon now analyzes your downtime notes to identify common themes, calculate their impact, and highlight statistical outliers, all delivered straight to your e-mail inbox as text summary and full .xlsx report.

Once the patterns are uncovered, you can streamline your process by adjusting the granularity of your stop reasons to be more accurate or take actions on the shop floor.

To get started, head to the Reports and ensure your x-axis is set to "Stop Reason." Look for the green AI badge next to stop reasons in the table that have enough data collected for a station (at least 50 notes) to generate a meaningful analysis (per station), delivered to your e-mail.

<aside> 💡

Learn more about how the AI notes feature works from our documentation.

</aside>

<aside> ⚠️

AI extra notes insights is currently in Beta and subject to improvements, gradually rolling out for tenants on Pro and Enterprise plans during this pilot phase. At the moment, there is no extra cost in using this feature but this might change in the future.

</aside>

Multi-sample checklist task for quality measurements

Multi-value task measurement.png

Checklist tasks now support multi-sample input for Measurement task types. Operators enter each sample as an individual value within the same task, and the system tracks how many have been recorded against the required count. A running average is calculated as values are entered, giving immediate feedback on whether the batch is trending within range.