AgentaaS OS
IFO4 PLAYGROUND
P1
1
Savings Plan Coverage Report2
Analyze Existing SP UtilizationP2
3
Layered Commitment Strategy4
Tranche Purchase PlanP3
5
Track SP Utilization Post-Purchase6
Optimize EC2 Instance Savings Plans vs Compute Savings PlansP4
7
Integrate SP Commitments into Annual BudgetP5
8
Implement SP Amortization in Cost ReportsP6
9
Identify EC2 RI vs SP Arbitrage10
Set Commitment Expiry Management SystemP7
11
Present SP Optimization Results to Finance12
Build the Commitment Health DashboardInitiatives11
Capital Under Change$19.2M
Health Score74/100
Waste %16.8%
Value at Risk$10.4M
Phase 1: Coverage Analysis
Savings Plan Coverage Report
ANALYTICS15 pts
Spend Trend
SITUATION
Run the Savings Plan coverage analysis in AgentaaS OS. Current state: $109,000/month in Compute Savings Plans (34% coverage). Uncovered on-demand spend: $209,000/month. Savings Plan utilization: 94% - the existing commitments are well-used. The opportunity is in buying more coverage, not fixing existing commitments.
Health
74/100
Waste
16.8%
Spend
$318K/mo
Savings
$32K
AGENT INSIGHT
Cost Optimizer: moving from 34% to 70% SP coverage saves $864,000/year. Recommend tranche purchasing: $38K/month additional commitment over 3 months to reach 70% coverage.
DECISION REQUIRED
What Savings Plan coverage target should you set for the additional commitments?
Hint: FinOps SP coverage target: 70% of baseline compute spend. The 30% buffer is for variable and experimental workloads.