Copilot for process discovery

Navigating across process mining visualizations to extract insights for improvement is often very time-consuming. To enable a faster and more convenient approach to process discovery, we have an AI-powered Copilot.

Copilot is a chat interface that allows us to ask process discovery questions in Process Discoverer. The chat conversation is based on the process map displayed in Process Discoverer and can answer quick questions about the process performance. So, rather than navigating the barrage of information in Process Discoverer, we can simply ask Apromore.

To use our AI Copilot, open an event log in Process Discoverer and click Copilot.

This opens the Copilot chat window. We see examples of questions we can ask.

In the chat input field, we can ask process discovery questions about the event log we have opened. For instance, we can ask: What is the most frequent activity in this process? Press Enter.

We see a progress bar indicating that Copilot is finding the answer to our question.

After a few seconds, Copilot returns the answer. For easy discovery, when Copilot returns answers that involve activities in the process map, Copilot highlights the activities involved.

Note

By default, Copilot is disabled in client instances. To turn on Copilot in your tenancy, please contact your account executive or customer support. Once enabled, Copilot enables the user to submit up to 50 prompts per calendar.

To enable us to easily identify answers, Copilot responds directly and concisely. We can however ask questions to dig deeper. For instance, we can ask why this activity is the most frequent.

The chatbot tells us it has the highest total frequency of 1108, which is correct.

Note

• AI models are non-deterministic. Hence, given the same prompt, the model may return a different response.

• Copilot understands the context based on the chat history in a session. Notice that we did not specify the activity in question in the second prompt, but Copilot correctly determined it from our earlier prompt. We can clear the chat history by closing and reopening Copilot or refreshing the Process Discoverer page.

Let’s ask Copilot to determine the bottlenecks in the process.

Copilot correctly identifies the activity and transition bottlenecks.

Note

When multiple activities are referenced, they are all highlighted.

As seen, all bottleneck activities are highlighted.

When a response contains multiple strings, we decide which elements to highlight using a two-step approach:

1. Exact Match: We first look for an element that exactly matches the response string.

   • Example: If the Copilot response is “Banker Manager” and a process map node with the same name exists, it will be highlighted.

2. Substring Match: If no exact match is found, we check for substrings of the response.

   • Example: If the Copilot response is “Banker Manager” and nodes named “Banker” and “Manager” exist, both will be highlighted.

In summary, we prioritize exact matches over substrings and longer phrases over shorter ones.

Note

When we apply a filter to the log, answers from Copilot will be based on the filtered process map. To demonstrate this, let us remove the most frequent activity, “Analyze Request for Quotation”.

Copilot detects that a filter has been applied and informs us that previous answers may no longer be valid.

Now, let us ask what the most frequent activity in the process is.

Copilot provided its answer based on the currently displayed filtered log.

Change Copilot window size

We can expand or contract Copilot’s window. We can choose to expand it horizontally or vertically. To expand horizontally, click the horizontal expand icon.

This increases the window width.

To expand vertically, click the vertical expand icon.

And this expands the Copilot window vertically.

Similarly, we can contract the window horizontally or vertically by clicking the respective contract icon.

We can close the Copilot window by clicking the close icon.

 

Note

When using Copilot, the chat history is retained even when the chat window is closed, or Process Discoverer is refreshed. To clear the chat history, reopen the event log.