Project Hierarchy Visualization

[engineering-issue-sync-app[bot]]

Value Proposition Statement

Automation leads can visualize the end-to-end process through a hierarchical view of all related processes, enabling better decision-making and strategic alignment.

User Problem

Organizational complexity:

BFSI and telco processes are intricate, involving multiple departments, regulatory requirements, and customer touchpoints. This complexity makes it challenging for automation leads to understand the full scope of processes and their interdependencies, leading to inefficiencies and potential compliance issues.

Top-down obscurity:

Leadership struggles to get a clear, comprehensive view of their organization's processes. This lack of visibility hinders their ability to make informed decisions, identify bottlenecks, and drive strategic improvements across the organization.

Bottom-up misalignment:

Isolated process automation projects often fail to consider the broader organizational context. This can result in siloed improvements that don't align with overall business objectives or may even conflict with other processes, reducing the overall impact of automation efforts.

Release Notes

Our MVP process architecture solution addresses these challenges by providing a comprehensive, hierarchical view of all related processes. This release enables automation leads to:

• Visualize the entire process architecture in a single, interactive interface

• Drill down from high-level processes to detailed sub-processes and activities

By providing this holistic view, our solution empowers automation leads to make more informed decisions, ensures top-down visibility for leadership, and helps align bottom-up automation projects with the big picture. This release lays the foundation for more strategic, impactful process improvements across the organization.

User Stories (MosCoW priority)

• [ ] (M) [Diagram] As an automation lead, I want to view a diagram of interrelated processes so I can see how multiple levels of processes relate to each other.
• [ ] (S) [Project Scope] When viewing a diagram, I want to view all linked BPMN diagrams within the project so I can see the relationships
• [ ] (C) [Ordering] When I view the diagram of interrelated processes, I want sub-processes to be in the right approximate order so I can visualize dependencies
• [ ] (M) [Autogen] As an automation lead, I want the process architecture to be automatically generated from my Web Modeler files so I don't have to maintain it
• [ ] (M) [Drilldown] When I view the process architecture, I want to drill down into specific processes to see their sub-processes and activities so that I can identify areas for potential automation.
• [ ] (C) [Info] When I view the process architecture, I want to see a brief explanation of a given BPMN diagram so I can gain context

Potential Improvements Central Process Management

• (W) [Publish] As a privileged user, I want to publish my process to the organization's process architecture so it can be part of the larger context

Automation Status

• (W) [Cluster Integration] As an admin, I want to integrate my process architecture with a cluster so I can view the most recently deployed process on production

Process Metrics

• (W) [Heatmap Overlay] As an admin, I want to view a heatmap overlay so I can see the frequency of use or duration of steps of a given process
• (W) [Incidents Overlay] As an admin, I want to view the technical health of my E2E processes and its subprocesses so I know it's working as expected

Business KPIs

• (W) [Optimize Integration] As an admin, I want to view the production dashboard of a given process so I can see how well it's performing
• (W) [KPI Overlay] As an admin, I want to see whether my business KPIs are being met for my E2E processes and its subprocesses so I know we're going to be successful

Implementation Notes

• This could be experimental, using existing functionality as much as possible to validate a potential product offering
  • An API is out of scope, as this would be harder to change over time
  • Access control changes are out of scope
  • Scalability is not yet important
• Web Modeler offers links to parent and child processes. It should be possible to recursively travel these links to generate a diagram
  • There should be an appropriate open-source diagram generator that could create the process architecture
  • The nodes on the diagram should link to the processes
  • The DMN viewer shows hierarchical diagrams- we could use similar styling
• In the long run, this belongs in a CoE context with a subset of all processes across the Web Modeler and deployed clusters
• The latest version of the process is appropriate
• In the exploratory stage, we should not make deep changes to page structure. A button and modal are appropriate
• Exploring ALL files in the entire org would likely provide a bad UX and performance. Exploring related files to a given process should be acceptable
• In the future, integrating with process application READMEs could be interesting

^{:robot: This issue is automatically synced from: source}

[HanselIdes]

Here is a rough concept explaining this first iteration The visualization is still a rough wireframe