Differences

This shows you the differences between two versions of the page.

--- 261:metamodelstrategy [2026/04/15 00:53] – created Meier, Erich
+++ 261:metamodelstrategy [2026/04/15 01:03] (current) – Meier, Erich
@@ Line 3: / Line 3: @@
 With the goal of supporting new process modeling best practices faster than before, while still keeping the number of metamodel variants low, we will support two standard metamodels going forward.
-====== Unified Configuration Best Practice ======
+This new strategy will be implemented with the **next Stages release 26.2**. We share this strategy already with this release to enable our customers to adjust accordingly in a timely manner.
+===== Unified Configuration Best Practice =====
 The **Unified Configuration Best Practice** will represent a clearly structured and consistent version of the Unified Configuration that reflects our best methodological recommendations for process modeling.
@@ Line 24: / Line 26: @@
 Please discuss further details with your Product Consultant.
+===== What we will already deliver with this release =====
+With **Stages 26.1**, a first version of the **Unified Configuration Best Practice** is being provided.
+==== Changes compared to Unified Configuration 3 ====
+  * To better support the modeling and tailoring of different process lifecycles, **Quality Levels will be modeled at milestones** instead of at work products.
+  * The **Responsible association between Workflow and Role** will no longer be available, ensuring a more consistent and unambiguous process modeling. Instead, the **Accountable** association should be used.
+  * Comments on the input/output relationships between activities and work products are no longer converted into work product states, but are displayed as normal comments.
+This metamodel can be used for productive process modelling and will be the foundation for process frameworks distributed by the Stages team, e.g. the **[[https://www.ul.com/sis/stages/stages-automotive-process-framework|Automotive Process Framework]]**.
+For existing processes modeled with Unified Configuration 2 or 3, a migration will be required.
+Manual migration is already possible; automated migration support is planned for one of the next releases.