Back to Details

finops-analyst

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

FinOps Analyst

FinOps分析师

When to Use

适用场景

  • Analyze cloud bills and usage (CUR, Cost Explorer, billing export, Cost Management)
  • Design tagging and allocation keys for showback or chargeback
  • Find waste — idle compute, unattached storage, orphaned IPs, over-provisioned SKUs
  • Recommend commitments — RIs, Savings Plans, CUDs, reservations (usage-based)
  • Build budgets, forecasts, and variance explanations for leadership
  • Detect anomalies and investigate spend spikes
  • Report unit economics — cost per tenant, API, feature, or environment
  • Run FinOps reviews with service owners (monthly optimization cadence)
  • Model what-if scenarios (region move, architecture change, commit purchase)
  • 分析云账单与使用情况（CUR、Cost Explorer、账单导出、成本管理工具）
  • 设计用于展示或收费的标签与分配规则
  • 排查资源浪费——闲置计算资源、未挂载存储、孤立IP、过度配置的SKU
  • 推荐承诺型购买方案——RI、Savings Plans、CUD、基于使用量的预留方案
  • 为管理层制定预算、预测及差异说明
  • 检测异常情况并调查支出激增原因
  • 汇报单位经济效益——按租户、API、功能或环境统计的成本
  • 与服务负责人开展FinOps评审（月度优化节奏）
  • 模拟假设场景（区域迁移、架构变更、承诺型购买）

When NOT to Use

不适用场景

  • Map cloud spend to GL, amortize prepaids, fixed assets → 
    compute-accounting-manager
  • Enterprise agreement strategy and org-wide CCoE FinOps program → 
    enterprise-cloud-architect
  • Provision VPC, fix IAM, implement infra → 
    cloud-engineer
  • Execute access tickets and patch windows → 
    cloud-system-administrator
  • Rack/GPU utilization and stranded kW → 
    data-center-compute-supply-efficiency
  • Capex policy and board asset governance → 
    director-infrastructure-capex-accounting
  • Generic BI without cloud cost domain → 
    bi-analyst
  • SOC 2 cloud evidence → 
    cloud-compliance-specialist
  • TCO/NPV business cases, commit portfolio economics, CFO scenarios → 
    cloud-economist
  • Cloud program strategy, migration portfolio, EA sign-off → 
    vp-of-cloud
  • Infrastructure org strategy, portfolio budget, board narratives → 
    vp-of-infrastructure
  • 将云支出映射至总账、摊销预付款、固定资产核算 → 
    compute-accounting-manager
  • 企业协议策略及全组织CCoE FinOps项目 → 
    enterprise-cloud-architect
  • 配置VPC、修复IAM、实施基础设施 → 
    cloud-engineer
  • 执行访问工单与补丁窗口 → 
    cloud-system-administrator
  • 机架/GPU利用率与闲置千瓦数管理 → 
    data-center-compute-supply-efficiency
  • 资本支出政策及董事会资产治理 → 
    director-infrastructure-capex-accounting
  • 无云成本领域聚焦的通用BI分析 → 
    bi-analyst
  • SOC 2云合规证据收集 → 
    cloud-compliance-specialist
  • TCO/NPV业务案例、承诺型购买组合经济效益、CFO场景模拟 → 
    cloud-economist
  • 云项目策略、迁移组合、EA审批 → 
    vp-of-cloud
  • 基础设施组织策略、组合预算、董事会汇报 → 
    vp-of-infrastructure

Related skills

相关技能

NeedSkill
VP cloud envelope and executive FinOps accountability
vp-of-cloud
TCO, NPV, migration and commit business cases
cloud-economist
Ledger, capex/OpEx, month-end close
compute-accounting-manager
Enterprise EA and org chargeback model
enterprise-cloud-architect
Tag enforcement and cost runbooks in ops
cloud-engineer
Hygiene execution (delete idle resources)
cloud-system-administrator
K8s cluster cost and rightsizing
cluster-deployment-engineer
LLM/token cost programs
ai-token-improvement-plan-engineer
AI ops cost and capacity
ai-lead-ops
Well-Architected cost pillar at design
cloud-architect
Business requirements for finance tools
business-analyst
VP infrastructure leadership
vp-of-infrastructure
需求技能
VP级云支出管控与FinOps高管问责
vp-of-cloud
TCO、NPV、迁移及承诺型购买业务案例
cloud-economist
分类账、资本支出/运营支出、月末结账
compute-accounting-manager
企业EA与全组织收费模型
enterprise-cloud-architect
运维中的标签强制执行与成本运行手册
cloud-engineer
资源清理执行（删除闲置资源）
cloud-system-administrator
K8s集群成本与合理配置
cluster-deployment-engineer
LLM/Token成本优化方案
ai-token-improvement-plan-engineer
AI运维成本与容量管理
ai-lead-ops
设计阶段的Well-Architected成本支柱
cloud-architect
财务工具的业务需求梳理
business-analyst
VP级基础设施领导力
vp-of-infrastructure

Core Workflows

核心工作流

1. Scope and FinOps principles

1. 范围与FinOps原则

Inform, optimize, operate; boundaries with accounting.
See 
references/finops_scope_and_principles.md
.
告知、优化、运营；与会计职能的边界界定。
详见 
references/finops_scope_and_principles.md
。

2. Cost visibility and allocation

2. 成本可见性与分配

Tags, CUR, dashboards, allocation rules.
See 
references/cost_visibility_allocation.md
.
标签、CUR、仪表板、分配规则。
详见 
references/cost_visibility_allocation.md
。

3. Optimization and rightsizing

3. 优化与资源合理配置

Waste, SKUs, commitments, engineering tickets.
See 
references/optimization_rightsizing.md
.
资源浪费、SKU、承诺型购买、工程工单。
详见 
references/optimization_rightsizing.md
。

4. Budgeting and forecasting

4. 预算与预测

Budgets, forecasts, anomalies.
See 
references/budgeting_forecasting.md
.
预算、预测、异常检测。
详见 
references/budgeting_forecasting.md
。

5. Unit economics and reporting

5. 单位经济效益与汇报

Cost per unit, executive narratives.
See 
references/unit_economics_reporting.md
.
单位成本、高管汇报内容。
详见 
references/unit_economics_reporting.md
。

6. FinOps governance

6. FinOps治理

Policies, RACI, review cadence.
See 
references/finops_governance.md
.
政策、RACI矩阵、评审节奏。
详见 
references/finops_governance.md
。

Outputs

产出物

  • Cost breakdown — by account, service, tag, trend vs prior period
  • Optimization backlog — savings estimate, owner, risk, effort
  • Commitment recommendation — coverage %, term, break-even, risk
  • Allocation model — keys, untagged %, disputed splits
  • Forecast — baseline, growth drivers, confidence range
  • Anomaly report — root cause, one-time vs recurring
  • 成本细分报告 — 按账户、服务、标签、与往期趋势对比
  • 优化待办清单 — 预估节省金额、负责人、风险、工作量
  • 承诺型购买建议 — 覆盖比例、期限、收支平衡点、风险
  • 分配模型 — 规则、未打标签占比、有争议的拆分方式
  • 预测报告 — 基线、增长驱动因素、置信区间
  • 异常报告 — 根本原因、一次性/经常性判断

Principles

原则

  • Everyone owns their spend — FinOps enables; engineering decides trade-offs
  • Unit economics over totals — tie cost to business drivers
  • Measure then commit — stabilize usage before multi-year RIs
  • Same tags as finance — align with 
    compute-accounting-manager
    keys where possible
  • Fast feedback — weekly visibility beats quarterly surprises
  • 人人对自身支出负责 — FinOps提供支持；由工程团队决定权衡方案
  • 优先关注单位经济效益而非总额 — 将成本与业务驱动因素关联
  • 先衡量再承诺 — 在签订多年期RI前稳定使用量
  • 使用与财务一致的标签 — 尽可能与
    compute-accounting-manager
    的规则对齐
  • 快速反馈 — 周度可见性优于季度意外