Ownership Cost vs. Capability Cost

The technical layers are dominated by a single category of links, which are * Ownership* links. For example:

Even though the links have various names, they all indicate "ownership", which is why they are treated equally in Cost Propagation.

However, the Cost Propagation mechanism in Txture is not limited to the technical layers, it also encompasses the business layers of your model. In those layers, we encounter another category of links which also requires Cost Propagation but is different from ownership:

In the example above, we still encounter ownership links (in blue) which eventually lead to the Organizational Units. However, we also see links that eventually lead to Business Capabilities (in red). Note in particular that the application has two paths to Business Capability (the arrows below indicate the cost flow direction, not the link direction):

• App 1 (owner) Stakeholder 1 (part of) Org. Unit 1 (supported by) Business Capability 1
• App 1 (supported by) Business Capability 1

Here, associating the cost of App 1 twice to Business Capability 1 would be a mistake. As the image shows, even though there are two paths, and both App 1 and Org. Unit 1 hold the full costs, Business Capability 1 receives these costs only once.

The key concepts to achieve this are:

• Cost Propagation computes the ownership tree (blue) and the support tree (red) separately.
• The per-asset costs resulting from the support tree are written only into the Business Capabilities. All other assets receive the costs resulting from the ownership tree.
• The link [Business Capability] supported by [Organizational Unit] is special in that it propagates only the direct costs of the Organizational Unit to the Business Capability, avoiding accounting for Applications twice.