Linted for Whitespaces

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

@@ -15,7 +15,7 @@ description: Glossary
 |API|Application Programming Interface is a set of rules, protocols, and tools for building software and applications. Examples for DCM can be found here: [Development View - APIs utilized by a DCM application](../development-view/overview.md#apis-utilized-by-a-dcm-application)|
 |Aspect Model|See: [CX-0002 Digital Twins in Catena-X][StandardLibrary]|
 |Bottleneck|A facility, function, department, or resource whose capacity is less than the demand placed upon it. For example, a bottleneck machine or work center exists where jobs are processed at a slower rate than they are demanded (Source: ASCM Supply Chain Dictionary, 17th edition).|
-|Business Application Provider|Typically, it is a third party that offers tools to data consumers and data providers for demand and capacity management purposes that conform to the core business logic, data models and APIs described in the Catena-X DCM  standard.|
+|Business Application Provider|Typically, it is a third party that offers tools to data consumers and data providers for demand and capacity management purposes that conform to the core business logic, data models and APIs described in the Catena-X DCM standard.|
 |Business Partner Number Legal Entity (BPNL)|See: [CX-0010 Business Partner Number][StandardLibrary]|
 |Business Partner Number Site (BPNS)|See: [CX-0010 Business Partner Number][StandardLibrary]|
 |Calendar Week|A week consisting of seven days, typically numbered according to the week containing the year’s first Thursday. For example, if the first Thursday of the year is on January 1st, that week is considered Week 1.|
@@ -32,7 +32,7 @@ description: Glossary
 |Flexible Capacity|The difference between maximum and Actual Capacity, which represents the measures to potentially increase capacity without further agreements between partners, such as extending the utilization of production resources within a week.|
 |JSON|The JavaScript Object Notation (JSON) is a standard text-based format for representing structured data based on JavaScript object syntax. It is commonly used for transmitting data in web applications (e.g. sending some data from the server to the client, so it can be displayed on a web page, or vice versa).|
 |Linking Material Demand|Material demands can be linked directly to a capacity group or indirectly through another capacity group, which is known as “Nesting.”|
-|Load Factor|An optional feature of a capacity group that adds individual numerical material load factors to WeekBasedMaterialDemand linked by the WeekBasedCapacityGroup. It  adds flexibility to the unit of measure of the capacity group.|
+|Load Factor|An optional feature of a capacity group that adds individual numerical material load factors to WeekBasedMaterialDemand linked by the WeekBasedCapacityGroup. It adds flexibility to the unit of measure of the capacity group.|
 |Material|The elements, constituents, or substances of which something is composed or can be made of. Usually referred to by a material number.|
 |(Material) Demand|A need for a particular product or component. The demand could come from any number of sources (e.g. a customer order or forecast, an interplant requirement, a branch warehouse request for a service part, or the manufacturing of another product). At the finished goods level, demand data is usually different from sales data, because demand does not necessarily result in sales (e.g. if there is no stock, there will be no sale (Source: ASCM Supply Chain Dictionary, 17th edition)). Material demand may comprise multiple demand series by location and demand categories. When the term is written as one word (WeekBasedMaterialDemand), the term refers specifically to the respective aspect model.|
 |Maximum Capacity|This is the highest achievable production capacity of a supplier within a given calendar week, in a certain unit of measure, for a specific customer. The Maximum Capacity is equal or higher than the Actual Capacity. It considers further capacity-increasing measures that have been planned upfront between the parties involved and can be activated whenever needed. Capacity-increasing measures can be, e.g. a longer utilization of the available production resources, a shift extension or additional shifts. Secondarily, additional resources can also be activated.|

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

@@ -63,7 +63,7 @@ Of course, by realizing efficiency through improved collaboration all involved p
 
 | Semantic Model | Link to GitHub Repository |
 | ------------- | ------------- |
-| WeekBasedCapacityGroup  | <https://github.com/eclipse-tractusx/sldt-semantic-models/blob/main/io.catenax.week_based_capacity_group/3.0.0/WeekBasedCapacityGroup.ttl> |
+| WeekBasedCapacityGroup | <https://github.com/eclipse-tractusx/sldt-semantic-models/blob/main/io.catenax.week_based_capacity_group/3.0.0/WeekBasedCapacityGroup.ttl> |
 | WeekBasedMaterialDemand | <https://github.com/eclipse-tractusx/sldt-semantic-models/blob/main/io.catenax.week_based_material_demand/3.0.0/WeekBasedMaterialDemand.ttl> |
 | IdBasedRequestForUpdate | <https://github.com/eclipse-tractusx/sldt-semantic-models/blob/main/io.catenax.id_based_request_for_update/3.0.0/IdBasedRequestForUpdate.ttl> |
 | IdBasedComment | <https://github.com/eclipse-tractusx/sldt-semantic-models/blob/main/io.catenax.id_based_comment/1.0.0/IdBasedComment.ttl> |

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

@@ -18,7 +18,7 @@ sidebar_position: 1
 
 ## Business Roles and Functions
 
-The core DCM business process is executed by two roles and uses two APIs as well as  two aspect models. The customer is responsible for `WeekBasedMaterialDemand`, the supplier for `WeekBasedCapacityGroup`. Within `WeekBasedCapacityGroup` the supplier has to link material demands.
+The core DCM business process is executed by two roles and uses two APIs as well as two aspect models. The customer is responsible for `WeekBasedMaterialDemand`, the supplier for `WeekBasedCapacityGroup`. Within `WeekBasedCapacityGroup` the supplier has to link material demands.
 
 |Function / Role|Customer|Supplier|
 |-|-|-|
@@ -149,7 +149,7 @@ classDef Demand fill:#FFA600,stroke:#FFFFFF,color:#000000
 classDef Capacity fill:#B3CB2D,stroke:#FFFFFF,color:#000000
 classDef DemCap fill:#D9B917,stroke:#FFFFFF,color:#000000
 classDef Frame fill:#979797,stroke:#EAEAEA,color:#000000
-classDef Highlite  stroke:#FF0000,stroke-width:4px
+classDef Highlite stroke:#FF0000,stroke-width:4px
 class A1,C1 Demand
 class A3,C4 Capacity
 class E2,G2 DemCap
@@ -306,7 +306,7 @@ classDef Demand fill:#FFA600,stroke:#FFFFFF,color:#000000
 classDef Capacity fill:#B3CB2D,stroke:#FFFFFF,color:#000000
 classDef DemCap fill:#D9B917,stroke:#FFFFFF,color:#000000
 classDef Frame fill:#979797,stroke:#EAEAEA,color:#000000
-classDef Highlite  stroke:#FF0000,stroke-width:4px
+classDef Highlite stroke:#FF0000,stroke-width:4px
 class A1,C1 Demand
 class A3,C4 Capacity
 class E2,G2 DemCap
@@ -330,9 +330,9 @@ The customer must have the capability to consume the capacity group data from th
 
 ### Capacity Group Structure
 
-The capacity group is the entity where material demand and capacity information are matched and compared for the purpose of a collaborative DCM. Thereby, the capacity group builds the common view on the data exchanged between a customer and a supplier.  
+The capacity group is the entity where material demand and capacity information are matched and compared for the purpose of a collaborative DCM. Thereby, the capacity group builds the common view on the data exchanged between a customer and a supplier.
 
-The entity capacity group may be used, i.e. to combine capacities related to one or more machines, facilities or plants.  
+The entity capacity group may be used, i.e. to combine capacities related to one or more machines, facilities or plants.
 
 ![Capacity Group Structure](./resources/business-process_CGstructure.svg)
 ![Capacity Group Structure Legend](./resources/business-process_CGstructure_Legend.svg)
@@ -431,9 +431,9 @@ D["Agreed Capacity"] style D fill:#219dd4,color:#F4F2F3
 
 Embedded into the WeekBasedCapacityGroup are
 
-- **Actual Capacity** as the  planned available capacity of a supplier
+- **Actual Capacity** as the planned available capacity of a supplier
 - **Maximum Capacity** as the maximum releasable capacity of a supplier
-- **Agreed Capacity**  as the understanding between Customer and supplier, regardless of contractual obligations. It is optional.
+- **Agreed Capacity** as the understanding between Customer and supplier, regardless of contractual obligations. It is optional.
 
 In addition the difference between actual capacity and maximum capacity is commonly understood as flexible capacity.
 
@@ -572,7 +572,7 @@ On supplier side: Supplier should detect that actual capacity is insufficient, u
 
 On customer side: when validating its own production plan, customer may consider utilizing the supplier’s flexibility up to the maximum capacity and conclude that feasibility is given.
 
-#### Example 3:  No Flexible Capacity
+#### Example 3: No Flexible Capacity
 
 ![Capacity Example](./resources/business-process_capacity-types_example3.svg)
 <!--
@@ -621,7 +621,7 @@ config:
 Figure: *Visualizing capacity and demand in case without flexible capacity*
 
 Actual capacity is equal to maximum capacity, and demand is very close.
-Though no proper imbalance  is detected, even a slight increase of demand could not be managed.  Both, supplier and customer, can conclude, that it may be relevant to collaborate to identify measures to mitigate risk.
+Though no proper imbalance is detected, even a slight increase of demand could not be managed. Both, supplier and customer, can conclude, that it may be relevant to collaborate to identify measures to mitigate risk.
 
 #### Example 4: Solving a Capacity Bottleneck
 
@@ -747,7 +747,7 @@ Further properties are added at lower level below the “Capacities” property.
 
 For a functional capacity group, the supplier must link it directly or indirectly to a material demand:
 
-- **Direct linking** means that the capacity group links at least one material demand.  
+- **Direct linking** means that the capacity group links at least one material demand.
 - **Indirect linking** means that the capacity group links to another capacity group which links at least one material demand. This is also referred to as **nesting**.
 
 #### Direct Linking
@@ -804,27 +804,27 @@ D["Capacity data (optional)"] style D fill:#617000,color:#F4F2F3
 
 ```
 -->
-For the technical representation of a capacity group the aspect model WeekBasedCapacityGroup is utilized.  
+For the technical representation of a capacity group the aspect model WeekBasedCapacityGroup is utilized.
 
-The aspect model WeekBasedCapacityGroup must be used by a supplier to provide capacity information to the Customer.  
+The aspect model WeekBasedCapacityGroup must be used by a supplier to provide capacity information to the Customer.
 
-For further details refer to the semantic model in Chapter 3.2 and to the APIs in Chapter 4.2.  
+For further details refer to the semantic model in Chapter 3.2 and to the APIs in Chapter 4.2.
 
-A partner acting as a supplier sends a capacity group to its customer. In order to link demand series in the capacity group between customer and supplier, the following properties must be filled-in:  
+A partner acting as a supplier sends a capacity group to its customer. In order to link demand series in the capacity group between customer and supplier, the following properties must be filled-in:
 
 - Supplier
 - Customer
-- materialNumberCustomer  
-- CustomerLocation  
-- demandCategory  
+- materialNumberCustomer
+- CustomerLocation
+- demandCategory
 
 If there’s no complete match between supplier and customer data, it’s recommended to initiate collaboration (i.e. see chapter “Comments”)
 
 The supplier has the option to mark a WeekBasedCapacityGroup as inactive (i.e. the capacity is obsolete), in this case the capacity will not be considered in the demand-capacity matching. However, the WeekBasedCapacityGroup can be reactivated again.
 
 ### Building N-Tier Chains via Capacity Groups
 
-Building supply chain via capacity groups is crucial to improve resiliency, transparency and efficiency along the value chain. Using the individual one-to-one capacity groups between one-ups and one-downs step by step builds the whole supply network. This enables all partners to collaborate along the whole value chain and navigate through complex and dynamic market conditions.  
+Building supply chain via capacity groups is crucial to improve resiliency, transparency and efficiency along the value chain. Using the individual one-to-one capacity groups between one-ups and one-downs step by step builds the whole supply network. This enables all partners to collaborate along the whole value chain and navigate through complex and dynamic market conditions.
 
 The following figure illustrates how plastic granulate ends up being used in the housing of a control unit and how this would be viewed from a birds eye perspective.
 
@@ -935,7 +935,7 @@ class t2pzc,t1c CG5
 class car Car
 ```
 
-![N-Tier  Linking Legend Legend](./resources/business-process_nTierLinking_Legend.svg)
+![N-Tier Linking Legend Legend](./resources/business-process_nTierLinking_Legend.svg)
 
 Figure: *A small supply network built by seven capacity groups*
 
@@ -998,7 +998,7 @@ classDef Demand fill:#FFA600,stroke:#FFFFFF,color:#000000
 classDef Capacity fill:#B3CB2D,stroke:#FFFFFF,color:#000000
 classDef DemCap fill:#D9B917,stroke:#FFFFFF,color:#000000
 classDef Frame fill:#979797,stroke:#EAEAEA,color:#000000
-classDef Highlite  stroke:#FF0000,stroke-width:4px
+classDef Highlite stroke:#FF0000,stroke-width:4px
 class A1,C1 Demand
 class A3,C4 Capacity
 class E2,G2 DemCap
@@ -1128,7 +1128,7 @@ classDef Demand fill:#FFA600,stroke:#FFFFFF,color:#000000
 classDef Capacity fill:#B3CB2D,stroke:#FFFFFF,color:#000000
 classDef DemCap fill:#D9B917,stroke:#FFFFFF,color:#000000
 classDef Frame fill:#979797,stroke:#EAEAEA,color:#000000
-classDef Highlite  stroke:#FF0000,stroke-width:4px
+classDef Highlite stroke:#FF0000,stroke-width:4px
 class A1,C1 Demand
 class A3,C4 Capacity
 class E2,G2 DemCap

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

@@ -117,7 +117,7 @@ rect rgb(157,93,00)
 end
 s->>s: Manage Capacities
 s->>s: There is a bottleneck in week 50
-s->>s: It is solvable via pre-production in weeks 48 and 49  
+s->>s: It is solvable via pre-production in weeks 48 and 49
 rect rgb(4,107,153)
     s-->>c: I can produce 100 in week 47, 0 in week 50 and 150 in weeks 48 and 49
     autonumber off

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

@@ -33,7 +33,7 @@ The exchange of measurements of the demand deviation metric between business par
 - improving the balance between demands and capacity
 - reducing the costs of supply chain operations
 
-## Functional Description Demand Volatility  
+## Functional Description Demand Volatility
 
 Supply chains in the automotive industry are characterized by a dynamic operating environment that manifests itself in regular changes in delivery and production requirements. This leads to varying degrees of Demand Volatility that customers communicate to their suppliers, in short term as well as long term planning horizons.
 
@@ -68,7 +68,7 @@ classDef Capacity_must fill:#B3CB2D,stroke:#FFFFFF,color:#000000
 classDef Demand_optional fill:#BF7100,stroke:#FFFFFF,color:#000000
 classDef Capacity_optional fill:#617000,stroke:#FFFFFF,color:#000000
 class A,B1,B2,B3,B4,B5,C1,C2,C4,C5,C6,D1,D5,D6 Capacity_must
-class C1,C2,D4,C7,D7 Capacity_optional  
+class C1,C2,D4,C7,D7 Capacity_optional
 
 style C3 fill:#617000,stroke:#d91e18,stroke-width:2px,color:#000000
 ```
@@ -93,12 +93,12 @@ __Parameters of the Demand Volatility metric are as follows:__
 |-|-|-|-|
 | Start Reference Date Time | Yes | Point in time when the measurement is initiated on suppliers side. It needs to be a point in time after receiving the active flag. It also marks the beginning of the first reporting interval/subhorizon| A value of 2024-08-01 indicates the measurement will start as of August 1st 2024. |
 | Measurement Interval | Yes | Indicates the length in weeks between two measurements. First interval start with the *Start Reference Date Time*. Second interval starts the mentioned weeks after this date and so on | A value of 4 indicates a measurement will be taken each 4 weeks, starting with the *Start Reference Date Time*. |
-| Sequence Number | Yes | Sequence Number of the respective subhorizon. The time frame can be divided into any positive number of individual subhorizons | A value of 2 indicates that this specific subhorizon is subhorizon number 2.  |
+| Sequence Number | Yes | Sequence Number of the respective subhorizon. The time frame can be divided into any positive number of individual subhorizons | A value of 2 indicates that this specific subhorizon is subhorizon number 2.|
 | Subhorizon Lengths | Yes | Length of an individual subhorizon. Minimum length is always one week per individual subhorizon due to the DCM granularity | In the example having a *Sequence Number* set as 2, a value of 6 indicates that subhorizon 2 has a length of 6 weeks. |
 | Absolute Negative Deviation | No | Absolute negative deviation threshold which triggers an alert | E.g. -100 units (value 100) means an alert is triggered if the absolute negative deviation between two measurement intervals for a respective calendar week decrease by 100 or more units. |
 | Absolute Positive Deviation | No | Absolute positive deviation threshold which triggers an alert | E.g. 100 units (value 100) means an alert is triggered if the absolute positive deviation between two measurement intervals for a respective calendar week increases by 100 or more units. |
-| Relative Negative Deviation | No | Relative negative deviation threshold which triggers an alert | E.g. -30% (value 0,3)  means an alert is triggered if the relative negative deviation between two measurement intervals for a respective calendar week decrease by 30% or more. Value can be set between 0 and 1. |
-| Relative Positive Deviation | No | Absolute negative deviation threshold which triggers an alert | E.g. 20% (value 0,2)  means an alert is triggered if the relative positive deviation between two measurement intervals for a respective calendar week increase by 20% or more. Value can be set between 0 and 1. |
+| Relative Negative Deviation | No | Relative negative deviation threshold which triggers an alert | E.g. -30% (value 0,3) means an alert is triggered if the relative negative deviation between two measurement intervals for a respective calendar week decrease by 30% or more. Value can be set between 0 and 1. |
+| Relative Positive Deviation | No | Absolute negative deviation threshold which triggers an alert | E.g. 20% (value 0,2) means an alert is triggered if the relative positive deviation between two measurement intervals for a respective calendar week increase by 20% or more. Value can be set between 0 and 1. |
 
 For further details please refer to [Aspect Model WeekBasedCapacityGroup](../../development-view/model-capacity-group.md).
 

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

@@ -9,7 +9,7 @@ sidebar_position: 7
 
 ## Business Roles and Functions
 
-Supply chain disruption notifications  use their own aspect model and API. Supply chain disruption notifications are provided and consumed by both customer and supplier.
+Supply chain disruption notifications use their own aspect model and API. Supply chain disruption notifications are provided and consumed by both customer and supplier.
 
 |Function / Role|Customer|Supplier|
 |-|-|-|