Hello @Guillermo Gost , are you trying to define scope of work? I think it is depend on how do you want to position and approach Celonis itself. My past experience was:

• Use Case for specific tools function or area to be improve (eg. planning for tools function or on time delivery for use case)
• I also use process / value stream when describing the scope

Hope that help and let me know your thought.

Well, trying to clarify... let's imagine I say in a scope of work:

• one process
• one system
• 2-3 use cases

"process" and "system" are clear the meaning, and it is straightforward to define. But... "use case" ?

What's a "use case"? How to define it in a scope of work?

Hi, do you want specific use cases within a process like O2C or P2P ? 

For example like, "how many deliveries are late?" or "do our VIP customers get the goodies we promise them?" --> here times on O2C 

"How many price changes do we have in order type XY?" --> P2P

Or the shared service center question "how many invoices does a division post per employee?"

Nope, I am trying to find or imagine a "standar" definition. Something that could be applicable to any process, industry, etc...

Hi Guillermo,

Perhaps you could associate the term "use cases" with the "number of execution gaps" you can address within the scope?

I hope that doesn't sound far-fetched.

Hmmmm.... not a bad idea... at the end, a use-case is to resolve one or several execution gaps....

BTW after holidays I will try to ask some Celonis ppl I am working with.

Each use case, as I understand it, could be said to be equal to a seperate project, because each use case sets out to solve a separate problem statement or give visibility on a certain issue.

Hi Guillermo,

Besides the number of Execution Gaps, maybe also add the number of KPI's and Action Engine Skills or Action Flows. E.g a use case is at least:

• An Analysis to identify 1 Execution Gap in the process
• 1 KPI for the Execution Gap
• 1 Action Engine/Action Flow to resolve the Execution Gap