Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| 262:prepareprocessforagenticai [2026/11/18 16:42] – [How it works] Iseler, Marc | 262:prepareprocessforagenticai [2026/11/18 17:07] (current) – [Prepare your Process for Agentic AI] Iseler, Marc | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Prepare your Process for Agentic AI ====== | ====== Prepare your Process for Agentic AI ====== | ||
| - | - define collection | + | Ensure that collections are properly defined so that the agent can identify the correct project based on the available context. |
| - | - define exposure | + | |
| + | Also ensure that users have access | ||
| ===== How it works ===== | ===== How it works ===== | ||
| The Agent governance MCP toolset consists of 3 tools: | The Agent governance MCP toolset consists of 3 tools: | ||
| - | < | + | * Stages projects list: lists all available collections |
| - | Stages projects list | + | |
| - | Stages usecases list | + | |
| - | Stages usecases get | + | |
| - | </ | + | |
| ===== Use-case modelling ===== | ===== Use-case modelling ===== | ||
| + | A Use Case is a subtype of the Phases and Milestones element type. It is intended to serve as a top-level element in the process element tree. As a container element, it comprises Phases and Milestones and defines the scope of a use-case package. | ||
| + | |||
| + | From a methodological perspective, | ||
| + | |||
| + | When generating a use-case package, the following modeling patterns are taken into account: | ||
| + | |||
| + | * **Sections**: | ||
| + | * **Milestone gates**: For each Milestone, the applicable gates are included. These comprise the required Work Products and Quality Levels, including their criteria presented as a checklist. | ||
| + | * **Activities and flow**: For each section, the Activities of the associated Workflows are included in the order defined by their sequence associations. This also includes Decisions and their alternative branches. | ||
| + | * **Roles and work products**: For each Activity, the Responsible Role and other RASIC Roles are included, together with the input and output Work Products and the applicable agent policy regarding roles that may only be performed by humans. | ||
| + | * **Supporting process elements**: All Practices, Tools, and Checklists associated with the Use Case, its subordinate Phases and Milestones, and the associated Quality Levels, Activities, and Work Products are included. Templates, Trainings, and other Guidance elements are excluded from the generated package. | ||
| + | * **Association comments**: Comments attached to associations are included as notes on the respective process element. | ||
| - | ===== Example ===== | ||