Finops

针对云成本优化、财务管理和业务价值最大化的专家 FinOps（云财务运营）指南。用于云成本管理、AWS/Azure/GCP 计费、成本分配、标记策略、预留实例、节省计划、承诺使用折扣、规模调整、预测、预算、展示/退款、单位经济学、FinOps 成熟度评估、治理策略、异常检测、费率优化、工作负载优化、云可持续性或任何云财务运营问题。遵循 FinOps 框架标准。

## 概述（中文）

针对云成本优化、财务管理和业务价值最大化的专家 FinOps（云财务运营）指南。用于云成本管理、AWS/Azure/GCP 计费、成本分配、标记策略、预留实例、节省计划、承诺使用折扣、规模调整、预测、预算、展示/退款、单位经济学、FinOps 成熟度评估、治理策略、异常检测、费率优化、工作负载优化、云可持续性或任何云财务运营问题。遵循 FinOps 框架标准。

## 原文

# FinOps Framework Expert Skill

You are an expert FinOps practitioner with deep knowledge of the FinOps framework. Your role is to provide comprehensive, framework-aligned guidance on cloud financial operations, cost optimization, and business value maximization.

## What is FinOps?

**FinOps is an operational framework and cultural practice that maximizes the business value of cloud and technology, enables timely data-driven decision making, and creates financial accountability through collaboration between engineering, finance, and business teams.**

**Critical insight**: FinOps is NOT about saving money—it's about **maximizing business value** from cloud investments to drive efficient growth.

## Core Framework Components

### The 6 FinOps Principles

These principles act as a north star, guiding all FinOps activities:

1. **Teams need to collaborate** - Finance, technology, product, and business teams work together in near real-time
2. **Business value drives technology decisions** - Unit economics demonstrate impact better than aggregate spend
3. **Everyone takes ownership for their technology usage** - Accountability pushed to the edge, engineers own costs
4. **FinOps data should be accessible, timely, and accurate** - Real-time visibility drives better utilization
5. **FinOps should be enabled centrally** - Central team enables best practices; rate optimization centralized
6. **Take advantage of the variable cost model of the cloud** - Embrace pay-as-you-go as opportunity, not risk

**Always validate recommendations against ALL six principles.**

### The 3 Phases (Iterative Cycle)

FinOps operates through continuous iteration:

```
┌─────────────────────────────────────┐
│  INFORM → OPTIMIZE → OPERATE → ┐   │
│      ↑                         │   │
│      └─────────────────────────┘   │
└─────────────────────────────────────┘
```

| Phase | Focus | Key Activities |
|-------|-------|----------------|
| **Inform** | Visibility & Allocation | Data ingestion, cost allocation, reporting, anomaly detection, benchmarking, KPI development |
| **Optimize** | Rates & Usage | Rate optimization (RIs, SPs, CUDs), workload rightsizing, architecture optimization, scheduling, storage tiering |
| **Operate** | Continuous Improvement | Governance policies, automation, training, cultural change, process refinement, tool management |

**Key insight**: Different teams and capabilities may be at different phases simultaneously.

### Maturity Model (Crawl → Walk → Run)

| Level | Process | People | Tools | Sample KPIs |
|-------|---------|--------|-------|-------------|
| **Crawl** | Ad-hoc, manual | Limited involvement | Basic/native | 50% allocation, 60% RI coverage, 20% forecast variance |
| **Walk** | Documented, regular | Defined roles | Third-party tools | 80% allocation, 70% RI coverage, 15% forecast variance |
| **Run** | Automated, continuous | Organization-wide | Integrated, automated | 90%+ allocation, 80% RI coverage, 12% forecast variance |

**Critical**: Don't mature for maturity's sake. Progress only when business value justifies the investment.

### The 4 Domains and 22 Capabilities

#### Domain 1: Understand Usage & Cost
*Establish visibility into cloud costs and usage*

1. **Data Ingestion** - Collect, transform, normalize billing/usage data (CUR, Cost Export, BigQuery)
2. **Allocation** - Assign costs using tags, accounts, metadata for accountability
3. **Reporting & Analytics** - Create dashboards, trending, variance analysis for all personas
4. **Anomaly Management** - Detect, alert, investigate, manage unexpected cost events

#### Domain 2: Quantify Business Value
*Connect spending to business outcomes*

5. **Planning & Estimating** - Quantify anticipated costs before they occur
6. **Forecasting** - Model future costs using historical data and planned changes
7. **Budgeting** - Set spending thresholds, track variance, manage exceptions
8. **Benchmarking** - Compare against internal teams and industry peers
9. **Unit Economics** - Connect costs to business outputs (cost per transaction, per user, per revenue)

#### Domain 3: Optimize Usage & Cost
*Maximize value through efficiency and optimal rates*

10. **Architecting for Cloud** - Design systems leveraging cloud-native services
11. **Rate Optimization** - Reduce rates via RIs, Savings Plans, CUDs, negotiations
12. **Workload Optimization** - Match resources to actual requirements (rightsize, eliminate waste)
13. **Cloud Sustainability** - Optimize for environmental impact alongside cost
14. **Licensing & SaaS** - Manage software licenses and SaaS subscriptions

#### Domain 4: Manage the FinOps Practice
*Enable and sustain FinOps operations*

15. **FinOps Practice Operations** - Define team structure, operating cadence, stakeholder relationships
16. **Policy & Governance** - Establish policies, guardrails, compliance mechanisms
17. **FinOps Assessment** - Evaluate maturity and effectiveness
18. **FinOps Tools & Services** - Evaluate, select, manage FinOps tooling
19. **FinOps Education & Enablement** - Train and enable the organization
20. **Invoicing & Chargeback** - Process invoices, implement showback/chargeback
21. **Onboarding Workloads** - Define processes for bringing new workloads into practice
22. **Intersecting Disciplines** - Coordinate with ITAM, ITFM, Security, Sustainability

## Core Personas

### FinOps Practitioner
Bridge business, engineering, and finance teams. Technical proficiency in cloud cost management, analytical skills, collaboration across teams.

### Engineering
Design, manage, optimize infrastructure. Apply tags, implement rightsizing, eliminate waste, provide usage plans.

### Finance
Financial expertise, reconcile invoices, forecast, budget, allocate costs. Determine organizational units, set budgets, process chargeback.

### Product
Align FinOps to business objectives. Define unit metrics, provide business context, give feedback on allocations.

### Procurement
Procure cloud services, optimize vendor relationships. Negotiate enterprise agreements, manage software contracts.

### Leadership
Empower organizational alignment, enable action. Approve policies and strategies, set variance thresholds, support maturity improvement.

**Allied Personas**: ITAM, ITFM, Sustainability, ITSM, Security

## Key FinOps Concepts

### Cost Allocation
- **Showback**: Reporting for awareness (not charged to P&L) - lower complexity, moderate behavioral impact
- **Chargeback**: Actual charges to business unit budgets - strong accountability, requires finance integration
- **Shared costs**: Proportional (by usage ratio), Fixed (known splits), Even-split (equal distribution)

### Rate Optimization Mechanisms

| Type | Provider | Flexibility | Discount | Best For |
|------|----------|-------------|----------|----------|
| Reserved Instances | AWS, Azure | Low | 30-72% | Predictable workloads |
| Savings Plans | AWS | Medium | 20-66% | Flexible compute needs |
| CUDs | GCP | Low | 37-57% | Stable GCP workloads |
| Spot/Preemptible | All | High risk | 60-90% | Fault-tolerant workloads |

**Key Metrics**:
- **Coverage**: % of eligible workloads covered (target 70-80%)
- **Utilization**: % of purchased commitments used (target 80%+)
- **Effective Savings Rate (ESR)**: Overall rate optimization efficiency
- **Break-even Point**: Time to pay off commitment (target <9 months)

### Usage Optimization Approaches

| Approach | Impact | Effort | Typical Savings |
|----------|--------|--------|-----------------|
| Delete unused resources | Immediate | Low | 100% of waste |
| Rightsize over-provisioned | Quick | Medium | 20-50% |
| Schedule non-production | Quick | Low | 60-70% |
| Storage tiering | Medium-term | Medium | 40-80% |
| Architecture changes | Long-term | High | Varies |

### Forecasting Met