# The US personnel office runs cloud-spend anomaly detection and routes rightsizing, commitment and budget decisions through a named FinOps team

Page: https://flyvolo.ai/en/changes/ev-20240331-devops-engineer-7
Date: 2024-03-31 · Stage: Deployment
Can this record move a task judgement? yes
Occupation: https://flyvolo.ai/en/careers/devops-engineer

## Scope

One US federal agency. The case study, published by the General Services Administration with OPM's deputy CIO as contact, says OPM's Azure cloud spend grew over 2,000% since 2021, which led it to a dedicated team for monitoring and managing cloud costs; that its anomaly detection establishes dashboards to detect, identify and act on unexpected increases in cloud spend; that it uses a decision matrix for each bucket of decisions; and that the team tracks decisions such as reserved-instance commitments, rightsizing, budget management and forecasting. It does not say whether the detection uses AI or simple thresholds. Progress is reported as of March 2024; dated to the end of that month.

## Source

- U.S. Office of Personnel Management — 'FinOps – Agency Case Study', published by GSA's Office of Government-wide Policy (progress as of March 2024) — https://itvmo.gsa.gov/assets/files/OPM-FinOps-Case-Study.pdf (primary source)

## What this means

In one public agency, spotting the cost spike is a dashboard's job, while what to do about it is decided by named people under a written decision matrix.

## What it does not show yet

One agency's own account, published by another agency; it does not say whether the detection is AI, and measures nothing about engineers' time.

## How to verify it yourself

Open the GSA-published 'OPM FinOps – Agency Case Study' and find "act upon potentially unexpected increases in cloud spend".


More: https://flyvolo.ai/llms.txt