Defining cost constraints
We now need to apply what we have learned to our company's organization, for costs to be clear and split across all departments and for technical constraints to be correctly implemented and configured for our cost governance model.
Depending on your cloud usage and how your organization works, you must create a conceptual map on how a chargeback (albeit theoretical) should work for each cloud service. If your organization is made up of many separate departments, each holding its own authority over cloud costs, these suggestions will still work, although you might have to duplicate all your efforts.
For example, in a company where a central information technology (IT) department is providing services to other departments, these could be the criteria:
- Application usage:
- Each application has a unique and dedicated set of cloud services that can be charged back to users (one-to-one relationship app/department/cost), as illustrated in the following...
