Fixed and unified embedding of graphics within the whole kit

- Every graphic gets a subline (Figure: bla bla)
- Ensured correct alignment

docs-kits/kits/Demand and Capacity Management Kit/adoption-view/overview.md

@@ -103,6 +103,8 @@ deactivate s
 end
 ```
 
+Figure: *Core business process*
+
 ## Business Process
 
 ### Business Architecture

docs-kits/kits/Demand and Capacity Management Kit/adoption-view/use-case/business-process.md

@@ -104,7 +104,9 @@ The supplier on the other hand has more options to solve problems. They can not
 ## Material Demand
 
 ![Guide Demand](./resources/business-process_guide_demand.svg)
+
 Figure: *Basic DCM process with demand part highlighted*
+
 <!--
 ```mermaid
 block-beta
@@ -260,6 +262,7 @@ Figure: *Visualizing demand quantities as bars*
 ## Capacity Group
 
 ![Guide Capacity](./resources/business-process_guide_capacity.svg)
+
 Figure: *Basic DCM process with capacity part highlighted*
 <!--
 ```mermaid
@@ -484,6 +487,7 @@ config:
 -->
 
 ![Capacity Example](./resources/business-process_capacity-types_example_legend.svg)
+
 <!--
 ```mermaid
 ---
@@ -661,7 +665,6 @@ config:
 ```
 -->
 ![Capacity Example](./resources/business-process_capacity-types_example4a.svg)
-
 ![Capacity Example](./resources/business-process_capacity-types_example_legend.svg)
 
 Figure: *Visualizing capacity and demand in a case of bottleneck*
@@ -710,7 +713,6 @@ config:
 ```
 -->
 ![Capacity Example](./resources/business-process_capacity-types_example4b.svg)
-
 ![Capacity Example](./resources/business-process_capacity-types_example_legend.svg)
 
 Figure: *Visualizing capacity and demand*
@@ -952,6 +954,7 @@ block-beta
 ## Match and Comparison of Demand and Capacity
 
 ![Guide Match](./resources/business-process_guide_match.svg)
+
 Figure: *Basic DCM process with match and comparison part highlighted*
 <!--
 ```mermaid
@@ -1079,7 +1082,9 @@ F["Agreed Capacity"] style F fill:#219dd4,color:#000000
 ## Collaboration
 
 ![Guide Collaboration ](./resources/business-process_guide_collab.svg)
-*Basic DCM process with collaboration part highlighted*
+
+Figure: *Basic DCM process with collaboration part highlighted*
+
 <!--
 
 ```mermaid

docs-kits/kits/Demand and Capacity Management Kit/adoption-view/use-case/comments.md

@@ -40,6 +40,8 @@ s->>c: I updated the capacity data to include pre production, lets discuss this
 end
 ```
 
+Figure: *Utilizing comments to solve a production problem*
+
 ## Details
 
 Collaboration is a critical element in Demand and Capacity Management. It enables alignment and cooperation between customers and suppliers within their respective business relationships. This interaction is facilitated by the exchange of comments, which are messages or texts related to data objects – either Material Demand or Capacity Group. These objects are identified by an "ObjectID," which matches the UUID of either a WeekBasedMaterialDemand or a WeekBasedCapacityGroup.

docs-kits/kits/Demand and Capacity Management Kit/adoption-view/use-case/delta-production.md

@@ -37,6 +37,8 @@ Simulated Delta-Production enables suppliers to add extra detail to their capaci
 ![DCM_DeltaProduction](./resources/business-process_DeltaProduction_functional.svg)
 ![DCM_DeltaProduction_Legend](./resources/business-process_DeltaProduction_functional_legend.svg)
 
+Figure: *Capacity group structure with linked material demand including simulated Delta-Production Result*
+
 <!--
 block-beta
 columns 10
@@ -81,8 +83,6 @@ C["Capacity data (MUST)"] style C fill:#B3CB2D,color:#F4F2F3
 D["Capacity data (optional)"] style D fill:#617000,color:#F4F2F3
 -->
 
-Figure: *Capacity group structure with linked material demand including simulated Delta-Production Result*
-
 Simulated Delta-Production may be used within a capacity group to indicate how production can be adjusted to meet demand. It helps cover potential shortfalls by showing where goods could be produced earlier or later than currently demanded. Therefore simulated Delta-Production covers both pre-production and post-production activities.
 
 Suppliers can provide these values on a weekly basis alongside their regular capacity data via parameter:
@@ -124,7 +124,7 @@ s->>c: 50 each in weeks 48 und 49 are pre-produced to cover the demand in week 5
 end
 ```
 
-Figure: *Sequence Diagram for simulated Delta-Production*
+Figure: *Utilizing simualted delta-production to solve a production problem*
 
 ![DCM_DeltaProduction](./resources/business-process_DeltaProduction_example_diagram.svg)
 

docs-kits/kits/Demand and Capacity Management Kit/adoption-view/use-case/demand-volatility.md

@@ -83,7 +83,7 @@ B["Capacity data (optional)"] style B fill:#617000,color:#F4F2F3
 ![Demand Volatility CG](./resources/business-process_demand_volatility_CG.svg)
 ![Demand Volatility CG Legend](./resources/business-process_demand_volatility_CG_legend.svg)
 
-Figure 1: *Demand Volatility within capacity group*
+Figure: *Demand Volatility within capacity group*
 
 Feature Demand Volatility is to be used optional but if it is used certain parameters are required to be filled.
 
@@ -128,9 +128,10 @@ s-->>c: Increase limited to max. 20% in subhorizon 3
 s-->>c: Decrease limited to max. -20% in subhorizon 3
 s-->>c: Measurement starts in week 0, using 4 subhorizons of length (2,11,39,52) 
 end
-
 ```
 
+Figure: *Utilizing demand volatility metrics to address data consistency issues*
+
 For further details, please refer to [CX-0128 Demand and Capacity Management Data Exchange][StandardLibrary].
 
 ## Notice

docs-kits/kits/Demand and Capacity Management Kit/adoption-view/use-case/disruption-notification.md

@@ -32,7 +32,9 @@ c->>s: The disruption (strike) has ended
 end
 ```
 
-For further details, please refer to [CX-0128 Demand and Capacity Management Data Exchange][StandardLibrary].
+Figure: *Utilizing supply chain disruption notification*
+
+For further details, please refer to [CX-0146 Supply Chain Disruption Notifications][StandardLibrary].
 
 ## Notice
 
@@ -50,4 +52,4 @@ This work is licensed under the [CC-BY-4.0](https://creativecommons.org/licenses
 - SPDX-FileCopyrightText: 2023-2024 ZF Friedrichshafen AG
 - SPDX-FileCopyrightText: 2023-2024 Contributors to the Eclipse Foundation
 
-[StandardLibrary]: https://catenax-ev.github.io/docs/next/standards/CX-0128-DemandandCapacityManagementDataExchange
+[StandardLibrary]: https://catenax-ev.github.io/docs/next/standards/CX-0146-SupplyChainDisruptionNotifications

docs-kits/kits/Demand and Capacity Management Kit/adoption-view/use-case/load-factors.md

@@ -97,7 +97,7 @@ c->>c: Their capacity for both toys is 250 cycles
 c->>c: Reduce demand for chrome toys to 75 so total demand equals 250 cycles
 ```
 
-Figure: *Sequence diagram example for application of Load Factor*
+Figure: *Utilizing load factors*
 
 The supplier has created a capacity group "Red and Chrome Toys" with the unit “cycle” (unit:cycle). A processing time per piece of 1 cycle is set for red toys and 2 cycles for chrome toys. The maximum available process time is set to 250 cycles.
 
@@ -108,6 +108,7 @@ Without the Load Factor applied, it would not have been transparent for the cust
 One possible solution would be to reduce the chrome toys by 25 pieces to 75 pieces. New required process time would add up to 100(red)\*1 + 75(chrome)\*2 = 100 + 150 = 250 cycles.
 
 ![Loadfactor](./resources/business-process_LoadFactor_example_diagram.svg)
+
 Figure: *Example for application of Load Factor within WeekBasedCapacityGroup*
 
 For further details, please refer to [CX-0128 Demand and Capacity Management Data Exchange][StandardLibrary].

docs-kits/kits/Demand and Capacity Management Kit/adoption-view/use-case/nesting.md

@@ -107,6 +107,7 @@ Capacity Group 3 is the result of the indirect way of linking Material Demand, t
 If a linked Capacity Group contains further linked Capacity Groups (dark green in figure below), the Nesting is recurrent and must go further until referenced Capacity Groups contain only linked demand series (orange in figure below) ("domino effect").
 
 ![Recurrent nested Capacity Groups](./resources/business-process_nesting_example-recurrent.svg)
+
 Figure: *Recurrent nested Capacity Groups*
 
 ### Considerations
@@ -146,7 +147,7 @@ end
 c->>c: My demands for all 5 toys are interlinked and transparent that they affect same capacity together
 ```
 
-Figure: *Sequence diagram for Nesting*
+Figure: *Utilizing nesting to structure demand and capacity data*
 
 For further details, please refer to [CX-0128 Demand and Capacity Management Data Exchange][StandardLibrary].
 

docs-kits/kits/Demand and Capacity Management Kit/adoption-view/use-case/rfu.md

@@ -40,6 +40,8 @@ end
 c->>c: Show user how old the data is and when was the last time it got synchronized.
 ```
 
+Figure: *Utilizing request for update*
+
 For further details, please refer to [CX-0128 Demand and Capacity Management Data Exchange][StandardLibrary].
 
 ## Notice

docs-kits/kits/Demand and Capacity Management Kit/architecture-view/dependencies.md

@@ -22,6 +22,8 @@ In order to keep things orderly some restrictions to this graph apply:
 
 ![Dependency Graph](./resources/dependencies_dependency-graph.svg)
 
+Figure: *Dependencies*
+
 <!--
 ```mermaid
 mindmap

docs-kits/kits/Demand and Capacity Management Kit/architecture-view/overview.md

@@ -177,6 +177,8 @@ sequenceDiagram
     end
 ```
 
+Figure: *Core business process*
+
 Note that the supplier does not need to immediately reply with capacity group after receiving demand information, although a timely reply is appreciated, there can be a considerable time in between instead.
 
 Digital Twins can also be used to reference parts, but are not shown in the sequence diagram for simplicity.

docs-kits/kits/Demand and Capacity Management Kit/development-view/api-capacity-group.md

@@ -47,6 +47,8 @@ sequenceDiagram
   
 ```
 
+Figure: *Exchanging WeekBasedCapacityGroup via API*
+
 ### Open API documentation
 
 |API|Link|

docs-kits/kits/Demand and Capacity Management Kit/development-view/api-comment.md

@@ -69,6 +69,8 @@ sequenceDiagram
   
 ```
 
+Figure: *Exchanging IdBasedComment via API*
+
 ### Open API documentation
 
 |API|Link|

docs-kits/kits/Demand and Capacity Management Kit/development-view/api-material-demand.md

@@ -46,6 +46,8 @@ sequenceDiagram
     end
 ```
 
+Figure: *Exchanging WeekBasedMaterialDemand via API*
+
 ### Open API documentation
 
 |API|Link|

docs-kits/kits/Demand and Capacity Management Kit/development-view/api-rfu.md

@@ -69,6 +69,8 @@ sequenceDiagram
   
 ```
 
+Figure: *Exchanging IdBasedRequestForUpdate via API*
+
 ### Open API documentation
 
 |API|Link|

docs-kits/kits/Demand and Capacity Management Kit/development-view/model-capacity-group.md

@@ -22,6 +22,8 @@ Suppliers provide customers capacity data as `WeekBasedCapacityGroup` aspect mod
 ![WeekBasedCapacityGroup Structure](./resources/model-capacity-group_structure.svg)
 ![WeekBasedCapacityGroup Structure Legend](./resources/model-capacity-group_legend.svg)
 
+Figure: *WeekBasedCapacityGroup structure*
+
 <!--
 ```mermaid
 block-beta

docs-kits/kits/Demand and Capacity Management Kit/development-view/model-comment.md

@@ -22,6 +22,8 @@ Customer and suppliers provide each other `IdBasedComment` aspect models in orde
 ![IdBasedComment Structure](./resources/model-comment_structure.svg)
 ![IdBasedComment Structure Legend](./resources/model-comment_legend.svg)
 
+Figure: *IdBasedComment structure*
+
 <!--
 ```mermaid
 block-beta

docs-kits/kits/Demand and Capacity Management Kit/development-view/model-material-demand.md

@@ -22,6 +22,8 @@ Customer provide suppliers demand data as `WeekBasedMaterialDemand` aspect model
 ![WeekBasedMaterialDemand Structure](./resources/model-material-demand_structure.svg)
 ![WeekBasedMaterialDemand Structure Legend](./resources/model-material-demand_legend.svg)
 
+Figure: *WeekBasedMaterialDemand structure*
+
 <!--
 ```mermaid
 block-beta

docs-kits/kits/Demand and Capacity Management Kit/development-view/model-rfu.md

@@ -22,6 +22,8 @@ Customer and suppliers provide each other `IdBasedRequestForUpdate` aspect model
 ![IdBasedRequestForUpdate Structure](./resources/model-rfu_structure.svg)
 ![IdBasedRequestForUpdate Structure Legend](./resources/model-rfu_legend.svg)
 
+Figure: *IdBasedRequestForUpdate structure*
+
 <!--
 ```mermaid
 block-beta