Collecting and Preparing Data for Task Definition and Process Analysis
To ensure the greatest success with ABBYY Timeline’s task mining feature it is important to plan ahead. The following tips will help you record a "clean" sequence of user actions which will greatly improve your ability to easily identify tasks and, as a result, obtain a more accurate insight into your business processes the tasks that support them.
1. Encourage users to focus on the task(s) of interest. Record only those user actions that are related to the business processes you are interested in. Redundant or unrelated actions will clutter the logs collected and slow down task definition and analysis.
For more accurate analysis, encourage users to record only actions in those applications that are directly related to your business processes and tasks of interest. This makes the resulting logs easier to analyze and facilitates task identification. See the "Avoid Recording Work outside of Tasks" section for details.
2. Encourage users to perform one task at a time. During the recording phase instruct users to perform a single task at a time without switching to any other tasks until the previous task is completed (also, see below for instructions on handling overlapping tasks)
To improve process analysis and to facilitate task markup in your Timeline project, we recommend loading and marking up logs of consecutive tasks, i.e. logs of processes where a user has completed the current task before switching to another.
If a user switches to another task without completing the current task, such tasks are said to be "overlapping."
- For more information about logging consecutive and overlapping tasks, see the "Action Sequences and Logs" section.
- If a user whose actions are being recorded switches to another task, different Timeline projects must be used for log markup and task definition. For more information, see "What do I do if a user switches between tasks while logging?"
3. Log same-type tasks performed multiple times
For the automatic task identification feature to be able to define tasks correctly, actions performed as part of one task should be logged multiple times representing multiple task instances of the same task type. For more information, see "Defining Tasks Automatically."
9/22/2023 8:59:47 AM