The tables behind Cloud Cost Management

Represents a single line of cloud spend for a day, the core record the team uses to analyze costs.

Represents a cloud provider account the company pays for, tracked for ownership and contract renewal.

Defines how spend on a cloud account is allocated to a cost center, and how often that's reviewed.

A record of an asset being assigned to a cost center, used to track who pays for what and for how long.

Represents a service problem being worked, tracked from open to resolution by whoever's assigned.

Represents a cloud provider account the company pays for, tracked for ownership and contract renewal.

Tracks a request to bring a new cloud account under cost management, from ask to approval.

Defines a reusable cost allocation model, so new accounts can be set up consistently.

Defines how spend on a cloud account is allocated to a cost center, and how often that's reviewed.

A record of an asset being assigned to a cost center, used to track who pays for what and for how long.

A piece of IT equipment or cloud resource, used to track its status, location, and the service it supports.

A rule that flags unusual spending patterns, used to catch cost overruns as they happen.

Flags an unusual spike in spend on an account, so the team can investigate and clear it.

Represents a service problem being worked, tracked from open to resolution by whoever's assigned.

A status note logged during an incident, used to keep everyone informed as the situation develops.

Captures a notable cost-related event tied to an incident, so analysts can trace what happened and when.

Schedules an analyst to watch cost alerts for a service during a shift, so someone is always on point.

Represents a single line of cloud spend for a day, the core record the team uses to analyze costs.

Suggests a way to cut spend on a resource, letting the team review, apply, and verify the savings.

Defines a repeatable cost-saving program for a service, so owners can enable or configure it consistently.

Records how widely a savings program has been rolled out, so the team can track coverage and approval.

Checks whether a savings change on a workload actually delivered the promised savings.

Captures a snapshot of how busy an asset is, helping the team spot underused resources to trim.

Represents a purchased commitment like reserved instances, tracked for quantity and expiry.

Links a purchased commitment to the resource using it, tracking coverage and release when freed.

A planned change to a service, used to schedule and coordinate work with a clear rollback plan.

Records a reviewer's decision on a proposed change, so approvals and reasons are kept on file.

Records a cost-saving change applied to a service, so the team can track rollouts and reversals.

Compares expected versus actual cost after a change, catching savings that got reversed unexpectedly.

Represents an IT service the team supports, tracked for criticality, status, and ownership.

Logs one run of a cost data pipeline, so the team can see if it started, finished, or failed.

Confirms whether a cost data source loaded on time, helping the team catch stale or broken feeds.

Logs an event received from an external integration, so the team can confirm delivery and dedupe replays.

Documents an API endpoint a service uses to pull billing data, so owners know what's being called.

Summarizes usage traffic through an endpoint over a window, flagging volume and rejected records.

Logs one export of cost data out of a store, so the team can confirm size, validity, and completion.

Defines a live feed of cost data flowing from a source, used to configure retention and origin.

Represents a database or warehouse holding cost data, tracked for platform and ownership.

Connects two billing data feeds together, helping the team trace how cost data flows between systems.

A time window when a cost center is open for spending, used to control when charges are allowed to post.

Records a cost-related notice sent to a group, so the team can see what was communicated and when.

A how-to guide for managing costs, used by the team to standardize cost-saving practices across services.

Represents a Kubernetes cluster the team pays to run, tracked for ownership and version.

A cloud resource under active cost oversight, used to track ownership, spend, and review deadlines.

Represents a team member involved in cloud cost work, used to assign ownership and responsibility.

A known issue behind one or more incidents that the IT team is tracking down to its root cause.

Tracks an attempt to fix a flagged resource using a playbook, so the team can follow it to completion.

Lists an available fix playbook for a vendor product, so the team knows what remediation options exist.

Marks a block of prepaid capacity reserved on an asset, so the team can see what's committed versus free.

A record of an asset being decommissioned, used to prove it was shut down and wiped properly.

A confirmed link between an asset and the service it supports, used to map dependencies before changes.

Captures a user's rating and comment on a runbook, helping the team keep guides useful.

Represents a paid software subscription, used to track renewal dates, seat counts, and cost by owner.

Tracks a person's use of a SaaS license, helping the team spot unused seats worth reclaiming.

Tracks a request for service work, from submission through due date to completion.

Defines a cost item shared across services, used to organize and display it consistently in reports.

Users

A note on how badly a workload is affected by an incident, used to prioritize response and recovery.