Feature of the week series #12 – Action Engine Signal History


#1

Dear Celonis Community!

Last week, we showed you how to work with OKR’s in the Transformation Center to transform your company.

This week, we want to introduce the Action Engine Signal History which provides transparency on how you have handled Action Engine recommendations in the past.

How does a Signal get into the Signal History?

When a Signal is created, it is shown in your Signal List as an open item. From here you can directly jump into the Signal Details, where you will find all information you need to take immediate action. As soon as the Signal is resolved, the Signal is automatically removed from the Signal List and put in the Signal History. Thus, the history provides each user an overview of the Signals he resolved.

Check it out in the following video:

The Signal History adds value especially for the following use cases:

Transparency: being able to understand how you handled previous Signals and getting overall transparency on the usage of Action Engine.

Documentation function: retrospectively demonstrate which action(s) you took for a specific Signal.

Periodic exchanges with business partners: e.g. when you have an exchange with a supplier, you can look up all historic Signals referring to this supplier, thereby get an impression for example on the frequency of duplicate invoices send by this supplier and instantly discuss this topic.

We hope that the Signal History helps you in your daily action handling! How do you like this feature?


#2

Dear Celonis,

I like the functionality and what you can do with it.
The examples which are setup in you movie are for me not the best since the functionality you show is standard SAP (centainly in S4HANA which has exactly these push functions within the UI).

Why not concentrate on actions you normally would not see in SAP like:

  • Warnings for Price Changes after a Invoice comes in.(= a compliance warning);
  • Warning is case a PO is put in after the Invoice comes in ( Maverick Buying);
  • Warnings if Touch Rate or Thi would have said “Digital Fitness rate” drops down;
  • Put on warning levels on all kind of other PPI to actively inform the responsible persons.
    Of course you could even think about a “appreciation” action in case a certain PPI has been reached or certain warning did not appear over a certain period.
    This would differentiate you completely from SAP and show an added value to your customers (beside what they already have within SAP).

Maybe other have some other ideas for this nice action engine.

Have :grinning:!
Hans


#3

Dear Hans,

thank you very much for the valuable feedback!

It is definitely a unique capability of Action Engine that we can leverage the power of process mining. We also take advantage of it in this example: taking into account actual cycle times for similar purchase orders in the past, Action Engine recommends to prioritize specific purchase requisitions to make sure important customer orders are delivered on-time.

It is great that you provided further valuable use cases how Action Engine can be used to:

  • identify specific process flows/patterns to act upon
  • detect frequent deviations/trends in KPIs proactively

We are excited to discuss further ideas and examples!


#4

Dear Celonis,

From a principle point of view the great thing of it that the action engine serves as “push” function to the desired action. In many Softwares is actually the other way around: first call up a Transaktion and then see what needs to be done.

What I would do is to combine your action engine with KPI dashboard. In this way you would very likely see the relationship between the “open action” and the PPI.

What do you think?

Have :grinning: !
Hans