Best practices "Folder Structure" (Workspaces, Tags,..) in the IBC

Hi Celonis Community,

I really appreciate ideas / best practices how to “organize” our analyses in the IBC as we are moving from on-premise to the cloud.

Our corrent “folder structure” on-premise

  • Purchase-to-Pay

    • Division I
      • _archive
      • _dev
    • Division II
      • _archive
      • _dev
  • Order-to-Cash

    • Division I
      • _archive
      • _dev
    • Division II
      • _archive
      • _dev

To sum up

  • We have currently two active processes: P2P and O2C
  • Our company is subdivided into four divisions each having their own analysis and a subfolder for development and archived analysis

In the IBC afaik there are “workspaces” and “tags” for organizing the “analysis ecosystem”.
Does anybody have ideas / best practices how the set it up in the IBC?

1 Like

Hello Stefan,

thank you for engaging in our community!

Yes as there are no cascading workspaces on the IBC the structure for the analyses needs to be adapted for your organization.

First I would suggest having all the workspaces that are not production such as “archive” and “dev” in your test environment aka your Sandbox team. Each production IBC team is entitled to a Sandbox team.

As for the divisions and their individual processes we recommend organizing it like this:

  • P2P - DIV 1
  • P2P - DIV 2
  • O2C - DIV 1
  • O2C - DIV3

We recommend using tags to quickly filter for specific use cases such as automation across all processes and divisions.

Best regards,
Alex

2 Likes