Solutions represent the service and business-facing view of IT spend. While Towers explain where technology costs are incurred, Solutions explain what IT delivers to the organization.
Solution allocation connects technology and asset costs to Solution Offerings, and ultimately to the Solution Type, Solution Category, and Solution Name.
Where Solutions fit in the cost flow
Yarken follows a layered cost distribution model:
Spend → Cost Pools → Towers → Solutions → Consumers
At the Solutions stage:
-
Spend has already been normalized (Cost Pools)
-
Positioned by technology domain (Towers)
-
Consolidated at the asset level (Applications, Products, Services)
Solutions translate this consolidated spend into service offerings that can be consumed and charged.
How Solution allocation works
Solution allocation begins after Tower allocation is complete.
There are two sources of spend that flow into Solutions:
1. Direct allocation from Towers
Spend can be directly allocated from Towers to Solution Offerings when the spend does not need to flow through assets.
2. Asset-based allocation
Asset spend represents costs consolidated into:
-
Applications
-
Products
-
Services
Spend from these primary assets is allocated to Solution Offerings using Solution rules or Solution mappings.
Once spend reaches Solutions, it is automatically transferred to Consumers based on downstream consumption logic.
Prerequisites for Solution allocation
Before configuring Solution allocation, ensure the following prerequisites are met:
-
Spend must be allocated to Towers for the selected month.
-
Spend from non-primary assets must be consolidated into Applications, Products, or Services at Tower-level.
-
Solution Offerings must already defined in Master Data before you can allocate spend to them.
Related content