Optimisation
Track every savings opportunity with an owner, an effort score, evidence, and a ticket. Replaces v1 Recommendations.
Atlas → Optimisation lists every way you can save, sized and assigned. Each opportunity has an owner, an effort score, a risk rating, evidence, and a link to its ticket.
Coming from v1? Recommendations are now opportunities. Each saving now has an owner, an effort score, and a ticket.
Savings are priced at the provider catalog and shown net of commitments, so an instance already covered by a Savings Plan doesn't show a saving it can't deliver.
Optimisation score
The score, out of 100, measures how optimised your estate is. The change this quarter is shown under it; select it to see what got done. Four pillars make up the score:
| Pillar | Measures |
|---|---|
| Right-sized | Compute and databases sized to what they use |
| Attached | Storage, IPs, and gateways that are attached to something and in use |
| Right tier | Storage and services on the right tier for how they're accessed |
| Commitments | Steady usage covered by Savings Plans, reservations, or CUDs |
Iris names the pillar holding the score back and what fixing it is worth, for example Right tier is holding the score back — $7.6K in right tier moves would lift it ~5.
Headline numbers
| Tile | Shows |
|---|---|
| Potential savings | Monthly savings across open opportunities, as a share of spend |
| Realised this quarter | Savings verified in billing this quarter, against your target |
| Blocked on people | Savings with no owner, and decisions due soon |
How to get there
A matrix breaks potential savings down by kind of change (rows) and effort (columns). Select any cell to filter the tracker to it.
| Effort | Meaning |
|---|---|
| Quick wins | High value, low effort. Do these first. |
| Big projects | High value, needs planning or engineering time |
| Housekeeping | Small, low effort, and safe. Batch them. |
| Park | Low value for the effort, or blocked. Revisit later. |
The tracker
The tracker lists every opportunity, grouped by Type by default.
| Column | Meaning |
|---|---|
| Key | The opportunity ID, such as REC-4501 |
| Opportunity | What to change |
| Resource | The resource or group in scope, such as payments-worker-7 +23 |
| Type | Opportunity type |
| Team | The owning team |
| Saves | Monthly saving, net of commitments |
| Evidence | strong, fair, or low |
| Owner | The person responsible, or Assign |
| Status | Where the finding is. Select to change it. |
| Ticket | The linked ticket and its state, or + Ticket |
Rows also carry badges such as realised (saving verified) or clawed back (a saving that reversed).
Status vs ticket
Status is what OpsLyft knows about the finding. The ticket is the work. The Work from this page is tracked in Tickets bar shows ticket counts; select Open board in Tickets to see them.
| Status | Meaning |
|---|---|
| Open | Found, not yet assigned |
| Assigned | Has an owner |
| In progress | Work has started |
| Verifying | The change is made; OpsLyft is waiting for billing to confirm the saving |
| Done | Saving verified in billing |
| Clawed back | The saving reversed after it was verified, for example the resource was scaled back up |
Evidence
| Evidence | Meaning |
|---|---|
| strong | A full lookback of metrics and billing supports the saving |
| fair | Most data is present; check before acting |
| low | Limited data; validate with the owner first |
Filter and add
- Use the Ask bar, for example low-risk savings over $5K/mo that nobody owns.
- Use Filters and Group to slice the tracker.
- Select + Opportunity to add one by hand, for example from a resource in Live inventory.
Export
Select Export at the top right.