Manage business processes

  • Release version: Yokohama
  • Updated February 5, 2025
  • 1 minute to read
  • Business processes model how your organization performs work to achieve a business outcome. Use business processes in Enterprise Architecture Workspace to build a process hierarchy and to associate processes with supporting business applications.

    You can create business processes or modify an existing one to align it with your business requirements.

    Based on your requirements, model a business process hierarchy by creating parent‑child relationships between business process records using CI relationships.

    A business process or capability hierarchy is an ordered grouping of business processes in a hierarchical fashion.

    L0 and L1 business processes

    L0 signifies the high-level process encompassing all activities associated with that process. For example, in the IT service management business process, the L0 business process encompasses all activities related to managing IT services within the organization.

    L1 signifies the specific tasks within the L0 business process. For example, within the IT service management business process, incident management is an L1 business process which specifically deals with logging, categorizing, and resolving incidents.

    Business process hierarchies can include multiple levels (L0, L1, L2, and deeper). Use CI relationships to create parent‑child relationships between business process records and build the hierarchy over time.

    Business processes in Enterprise Architecture Workspace

    Use business processes to connect operational workflows to other enterprise architecture artifacts:
    • Associate business processes with business applications to show which applications support the workflow.
    • Associate architectural artifacts with business processes to link design decisions to execution.
    • Add business processes to process maps or diagrams to visualize relationships.
    • Link business processes to value streams to show how internal workflows support end‑to‑end value delivery.

    Use business processes to model internal workflows and relate them to supporting applications. Use business capabilities to describe what the organization does. Use value streams to describe end‑to‑end value delivery across functions.