Cloudability Business Mappings
Business Mappings are a series of “IF” statements with conditions that help FinOps teams organize their data. Each statement represents a set of conditions that help sort whether a cost should belong to one bucket or another.
There are 2 problems that business mappings help FinOps address when organizing Cloud spend— Cleaning up errors and creating custom cost buckets.
Cleaning up Errors
How many ways are there to write that something in a part of a production environment? Users could put all types of values like “Production”, “PRD”, and “Prod” that all mean the same environment. Business Mapping helps FinOps groups clean up these discrepancies and create one normalized set of terms.
For example, a Business Mapping can be a statement like:
If the environment tag has the value Production, PRD, and Prod, return Production instead
Using this clean up method enables FinOps team to make curated reports and dashboards that cater directly to the stakeholders who need to make timely, important decisions.
Creating Custom Cost Buckets
When organizations experience change, departments can get moved around, applications can become part of new products, teams can be renamed, and more. When these changes occur, the way the Cloud resources are organized don’t always reflect those changes quickly. Cloudability enables FinOps to take key pieces of data from the billing files and organize their own custom cost buckets.
For example, there could be a Business Mapping that organizes applications into products. A statement like this can be use in Cloudability:
If the Application tag equals 123, 555, or 321, then return Location Services
Using Business Mappings for this purpose will help FinOps organizations quickly adapt to changes so that timely and informed decisions can be made about Cloud spend.