- Industry
- Oil & Gas
- Department
- Engineering
- Team
- Platform and Reliability
- Kind
- Decision-maker
- Approver
- FinOps Lead
- Code
- ENG-13
It finds wasted cloud and data centre spend across the company's estate, such as idle analytics clusters left from a reservoir study, oversized historian replicas and unattached storage, and estimates the monthly saving of each fix. It schedules safe clean-up in non-production and holds anything that serves operations, regulatory reporting or seismic data retention.
How it works
7 steps, and a person signs off before step 7.
- 01Looks it up
Finds the record the request is about in the cloud billing and usage export: costs and usage by resource..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Forecasts, when it decides
Projects what each option will cost or return before it recommends one.
- 05Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 06Asks a person
Hands the work to FinOps Lead with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the infrastructure pipeline: it schedules the rightsizing and clean-up. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The cost policy: tags, the data retention rules for seismic, well and production data, protected workloads, and commitment rules.
Reads from
the cloud billing and usage export: costs and usage by resource.
Acts in
the infrastructure pipeline: it schedules the rightsizing and clean-up.
Hands back
A list of savings, each with resource, issue, fix, monthly_saving_usd, risk and act_now (true or false).
Asks a person when
A saving touches production, a protected tag, retained data or a commitment purchase.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Idle below CPU (%) | 5 | Average CPU. |
| Lookback (days) | 30 | Usage window. |
| Smallest saving (USD a month) | 50 | Below this it is ignored. |
| Acts itself in | non_production_only | Where it may act. |
| Protected tags | do-not-stop, production-critical, regulatory-retention, seismic-archive | Comma-separated. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Act only in non_production_only.
- Never touch resources tagged do-not-stop, production-critical, regulatory-retention, seismic-archive, and never delete seismic, well or production data inside its retention period.
- Ignore savings under 50 USD a month.
- Mark resources idle below 5 percent CPU over 30 days.
See the Cloud Cost Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.