Skip to main content
Solved

How do we use Analytics and View separately?

  • October 26, 2022
  • 2 replies
  • 26 views
J
Level 7
Forum|alt.badge.img+4

Hi expert,

​

I have a question about Celonis Analytics and View in what case I'm better to use view.

I have already understand below post and understand basic difference however I don't think there is dicisive difference between each other...

 

Does anybody explain what business case I need to use view and analytics properly?

​

https://www.celopeers.com/s/question/0D50700000GC71TCAT/what-is-the-basic-difference-between-view-and-analysis-in-studio?language=en_US

 

Thanks in advance,

Best answer by guillermo.gost12

My take on that:

 

I see Analysis as suited for the "exploratory" phase, when you need to create new tables, graphs, etc... to identify insights, execution gaps, etc... or when you are validating the new data you are ingesting.

 

And I see Views for the second phase, when customer wants more to control the process, the evolution, the compliance, the implementation of the improvements... and/or when you need to provide a "tool" to execute

 

So, in a first project with a customer with average process maturity, I will show the results with Analysis. Then after identifying the improvements I will implement Views to control and manage the implementation of those improvements in the process.

 

Agree with Mateusz that looks like Celonis is putting more effort in evolving Views... looking forward for the Celosphere to get more info about Celonis roadmap in this and other aspects.

 

 

    2 replies

    D
    Level 0

    Hi,

     

    If you want to quickly build something to visualize data - analysis may be better as they are way easier to debug and fix the problems. However Buisness Views provide more features that are not available in Analysis, so if you want to use them - build business view.

     

    AS a rule of thumb, the best is to focus on one of them, business views are also receiving new components and updates so it's best option for now.

     

    Best Regards,

    Mateusz Dudek

    G
    Level 12

    My take on that:

     

    I see Analysis as suited for the "exploratory" phase, when you need to create new tables, graphs, etc... to identify insights, execution gaps, etc... or when you are validating the new data you are ingesting.

     

    And I see Views for the second phase, when customer wants more to control the process, the evolution, the compliance, the implementation of the improvements... and/or when you need to provide a "tool" to execute

     

    So, in a first project with a customer with average process maturity, I will show the results with Analysis. Then after identifying the improvements I will implement Views to control and manage the implementation of those improvements in the process.

     

    Agree with Mateusz that looks like Celonis is putting more effort in evolving Views... looking forward for the Celosphere to get more info about Celonis roadmap in this and other aspects.

     

     

    Community Code of ConductAccessibility statement