Index
A
- abstraction, Abstraction Assists Understanding-Abstraction Assists Understanding
- accessibility
- data, Core Principles of FinOps
- reports, Accessibility
- color, Color
- color, consistency of, Consistency of Color and Visual Representation
- consistency, Usability and Consistency
- language, Language
- recognition versus recall, Recognition Versus Recall
- usability, Usability and Consistency
- visual hierarchy, Visual Hierarchy
- visual representation, consistency of, Consistency of Color and Visual Representation
- account strategy, inform phase, Inform
- account-based attribution, Who Pays for Commitments?
- accounts
- cost allocation and, Tag- and Hierarchy-Based Approaches
- folders and, Comparing Accounts and Folders Versus Tags and Labels-Comparing Accounts and Folders Versus Tags and Labels
- hierarchies, Accounts, Tagging, Account Organization Hierarchies
- naming, Accounts, Tagging, Account Organization Hierarchies
- shared costs, Accounts, Tagging, Account Organization Hierarchies
- tagging, Accounts, Tagging, Account Organization Hierarchies
- versus tags, Comparing Accounts and Folders Versus Tags and Labels-Comparing Accounts and Folders Versus Tags and Labels
- accrual basis accounting, Amortization: It’s Accrual World
- accuracy in reporting, Perfect Is the Enemy of Good
- action
- action, processes and, Action-Action
- activity-based costing, Activity-Based Costing-Activity-Based Costing
- actual costs, chargeback, Chargeback and Showback Considerations
- advancing pitch, Advancing Pitch
- All upfront commitment, Components of the commitment break-even point
- allocation
- amortization and, Amortization: It’s Accrual World-Amortization: It’s Accrual World
- AWS accounts, Comparing Accounts and Folders Versus Tags and Labels
- chargeback, Chargeback Versus Showback
- cloud cost, Tags, Labels, and Accounts, Oh My!
- importance of, Why Allocation Matters-Why Allocation Matters
- service provider comparison, Comparing the Allocation Options of the Big Three-Comparing the Allocation Options of the Big Three
- shared costs and, Spreading Out Shared Costs-Spreading Out Shared Costs
- showback, Chargeback Versus Showback
- spend panic and, The “Spend Panic” Tipping Point-The “Spend Panic” Tipping Point
- Amazon Web Services (AWS) (see AWS (Amazon Web Services))
- amortization, A Dollar Is Not a Dollar, Inform, Amortization: It’s Accrual World-Amortization: It’s Accrual World, Step 6: Allocate Up-Front Commitment Costs Appropriately
- amortized costs, Defining the Basic Terms
- analytics, usage optimization and, Usage Reduction by Resizing (Rightsizing)
- anchoring bias, reporting and, Anchoring Bias
- anomaly detection, Basic Format of Billing Data
- audience consideration, pitches, Playing to Your Audience
- automated forecasts, Manual Versus Automated Forecasts
- automated rightsizing, Advanced Workflow: Automated Opt-Out Rightsizing-Advanced Workflow: Automated Opt-Out Rightsizing
- automation
- deciding to, Automating Cost Management
- implementing, How to Start-How to Start
- measurement, MDCO and, Automated Measurement
- outcomes, What Is the Outcome You Want to Achieve?
- scheduled resource start/stop, Scheduled Resource Start/Stop
- security, Safety and Security-Safety and Security
- tag governance, Tag Governance
- tools, Automation Tools
- usage reduction, Usage Reduction
- when to automate, Automated Versus Manual Tasks-Automated Versus Manual Tasks
- AWS (Amazon Web Services)
- Azure
- resource groups, Tags, Labels, and Accounts, Oh My!
- RIs (Reserved Instances), Overview of Usage Commitments Offered by the Big Three, Azure Reservations-Instance Size Flexibility
- SPs (Savings Plans), Azure Savings Plans-Azure Savings Plans
- subscriptions, Tags, Labels, and Accounts, Oh My!
B
- benchmarking, Benchmarking and Gamification
- benchmarks
- billing, tags and, Using Tags for Billing
- blended amortization, Who Pays for Commitments?
- blended rates, Defining the Basic Terms
- block storage, cost control and, Block Storage
- bottom-up forecasting, Granularity
- break-even point, commitment-based discount program, Step 1: Learn the Fundamentals of Each Program-The commitment waterline
- budget management, Advancing Pitch
- budgets
- business language versus cloud language, Cloud Language Versus Business Language-Cloud Language Versus Business Language
- business teams, Product or Business Teams
- business value of cloud, decision making and, #2: Decisions Are Driven by the Business Value of Cloud
- BYOL (“bring your own license”), rate optimization and, BYOL Considerations
C
- cadence-driven cost optimization, Metric-Driven Versus Cadence-Driven Processes-Metric-Driven Versus Cadence-Driven Processes
- cancellations, Conversions and Cancellations
- capabilities
- CAR (Cost Allocation Report), A Brief History of Cloud Billing Data
- carbon emissions, What Are Cloud Carbon Emissions?
- carrot versus stick approach to teams, Carrot Versus Stick Approach-Carrot Versus Stick Approach
- cash basis accounting, Amortization: It’s Accrual World
- cash flow break-even point, Components of the commitment break-even point
- CCoE (Cloud Center of Excellence), The Role of Each Team in FinOps, Indirect Collaboration
- central enablement team, Who Does FinOps?
- centralized FinOps teams, Why a Centralized Team?-Why a Centralized Team?
- centralized rate reduction, Centralizing Rate Reduction-Centralizing Rate Reduction
- centralized systems
- centralized teams, Core Principles of FinOps, Type of Alignment to the Organization, #5: A Centralized Team Drives FinOps
- CEOs, influencing, CEO Persona
- Certified Service Providers, Full Time, Part Time, Borrowed Time: A Note on Resources
- CFOs, influencing, CFO Persona
- chargeback, Chargeback Versus Showback
- charges, time and, Time, Why Do You Punish Me?-Time, Why Do You Punish Me?
- cloud
- cloud billing
- anomaly detection, Basic Format of Billing Data
- CAR (Cost Allocation Report), A Brief History of Cloud Billing Data
- charges, time and, Time, Why Do You Punish Me?-Time, Why Do You Punish Me?
- complexity, Cloud Billing Complexity-Cloud Billing Complexity
- consolidated billing, A Brief History of Cloud Billing Data
- cost avoidance, responsibility, Who Should Avoid Costs and Who Should Reduce Rates?
- CSV (comma-separated values), A Brief History of Cloud Billing Data
- CUR (Cost and Usage Report), A Brief History of Cloud Billing Data
- data
- DBR (Detailed Billing Report), A Brief History of Cloud Billing Data
- DBR-RT (Detailed Billing Report with Resources and Tags), A Brief History of Cloud Billing Data
- detailed billing data, Types of Cloud Bill
- hourly data, The Importance of Hourly Data
- in-house tooling, Basic Format of Billing Data
- invoices, Types of Cloud Bill
- native cost tools, Types of Cloud Bill
- rate reduction
- rates, Two Levers to Affect Your Bill-Two Levers to Affect Your Bill
- spending formula, Basic Format of Billing Data
- time, A Month Is Not a Month
- usage, Two Levers to Affect Your Bill-Two Levers to Affect Your Bill
- usage reduction, decentralized, Why You Should Decentralize Usage Reduction-Why You Should Decentralize Usage Reduction
- usage row, Basic Format of Billing Data
- vendor platform, Basic Format of Billing Data
- cloud chaos, The Impact of Not Adopting FinOps
- cloud cost management, Defining the Term “FinOps”, Where Did FinOps Come From?
- cloud cost optimization, Where Did FinOps Come From?
- cloud cost, allocation and, Tags, Labels, and Accounts, Oh My!
- cloud financial engineering, Defining the Term “FinOps”
- cloud financial management, Defining the Term “FinOps”, Where Did FinOps Come From?
- Cloud FinOps term, Defining the Term “FinOps”
- cloud forecasting, The State of Cloud Forecasting
- cloud gridlock, The Impact of Not Adopting FinOps
- cloud language versus business language, Cloud Language Versus Business Language-Cloud Language Versus Business Language
- cloud native automation tools, Tooling Deployment Options
- cloud optimization, Defining the Term “FinOps”
- cloud providers
- cloud spending acceleration, Cloud Spend Keeps Accelerating-Cloud Spend Keeps Accelerating
- cloud usage, Core Principles of FinOps
- cloud value proposition, Use Cloud for the Right Reasons
- Cloudability, A Brief History of Cloud Billing Data
- clusters, Containers 101
- CM (Configuration Management) framework, Connectivity to Other Frameworks
- CO2e, What Are Cloud Carbon Emissions?
- cognitive bias, reporting and, Anchoring Bias, Confirmation Bias
- COGS (cost of goods sold), Defining Finance Terms for Cloud Professionals
- collaboration, Core Principles of FinOps, #1: Teams Need to Collaborate
- color in reports, Color
- commitment coverage, MDCO, Achievable Goals-Commitment coverage
- commitment waste, Defining the Basic Terms
- commitment waterline, The commitment waterline-The commitment waterline
- commitment-based discounts, Introduction to Commitment-Based Discounts, Commitment-Based Discount Basics-Commitment-Based Discount Basics
- AWS (Amazon Web Services), Overview of Usage Commitments Offered by the Big Three
- Azure RIs, Azure Reservations-Instance Size Flexibility
- cancellations, Conversions and Cancellations
- centralized, Chargeback and Showback Considerations
- commitment level to provider, Step 2: Understand Your Level of Commitment to Your Cloud Service Provider
- conversions, Conversions and Cancellations-Conversions and Cancellations
- Google Cloud CUDs, Google Committed Use Discounts-Google Flexible Committed Use Discounts
- ISF (instance size flexibility), Compute Instance Size Flexibility-Compute Instance Size Flexibility
- iteration, Step 5: Measure and Iterate-Step 5: Measure and Iterate
- just-in-time purchasing, Step 4: Purchase Regularly and Often, Purchasing Commitments Just-in-Time-Purchasing Commitments Just-in-Time
- measuring, Step 5: Measure and Iterate-Step 5: Measure and Iterate
- mistakes, Common Mistakes
- over purchasing, Step 5: Measure and Iterate-Step 5: Measure and Iterate
- payments, Who Pays for Commitments?
- process repeatability, Step 3: Build a Repeatable Commitment-Based Discount Process-Step 3: Build a Repeatable Commitment-Based Discount Process
- program break-even point, Step 1: Learn the Fundamentals of Each Program-The commitment waterline
- program fundamentals, Step 1: Learn the Fundamentals of Each Program-The commitment waterline
- rate optimization and, Commitment-Based Discounts
- strategy building, Steps to Building a Commitment-Based Discount Strategy-Step 6: Allocate Up-Front Commitment Costs Appropriately
- strategy management, How to Manage the Commitment Strategy-How to Manage the Commitment Strategy
- strategy tips, Strategy Tips-Strategy Tips
- term use, Defining the Basic Terms
- up-front cost allocation, Step 6: Allocate Up-Front Commitment Costs Appropriately-Step 6: Allocate Up-Front Commitment Costs Appropriately
- versus rightsizing, When to Rightsize Versus Commit-Strategy Tips
- zone approach, The Zone Approach
- commitments unused/unutilized term, Defining the Basic Terms
- communication
- complexity in system design, A Complex System Designed from Scratch Never Works
- composite forecasts, Forecasting Models
- compute pricing, Compute Pricing
- confirmation bias, reporting and, Confirmation Bias
- consistency in reports, Usability and Consistency
- consolidated billing, A Brief History of Cloud Billing Data
- constraints, engineers and, Constraints and the Solving of Hard Problems-Constraints and the Solving of Hard Problems
- containers, Containers 101
- clusters, Containers 101
- cost allocation, Cost Allocation
- FinOps lifecycle and, The Container FinOps Lifecycle
- images, Containers 101
- labels and, Tags, Labels, and Namespaces
- namespaces, Containers 101, Tags, Labels, and Namespaces
- optimization phase, Container Optimize Phase-Server Instance Rate Optimization
- orchestration, Containers 101, The Move to Container Orchestration-The Move to Container Orchestration
- pods, Containers 101
- proportions, Container Proportions
- server instance node, Containers 101
- server instance rate optimization, Server Instance Rate Optimization
- serverless, Serverless Containers
- tags and, Tags, Labels, and Namespaces
- usage optimization, rightsizing, Centralize the rightsizing of clusters-Decentralize the rightsizing of containers/pods
- contributors to action, Contributors to Action
- conversions, Conversions and Cancellations-Conversions and Cancellations
- cost allocation, Advancing Pitch
- Cost Allocation Report (CAR), A Brief History of Cloud Billing Data
- Cost and Usage Report (CUR), A Brief History of Cloud Billing Data
- cost as efficiency metric, Data in the Path of Engineers
- cost avoidance, Defining the Basic Terms, Tracking Savings
- (see also usage optimization)
- cost center/business unit tags, Picking the Right Number of Tags
- cost control
- cost drivers, Cloud Billing Complexity
- cost estimates, forecasting and, Cost Estimation-Cost Estimation
- cost of capital, Defining Finance Terms for Cloud Professionals
- cost of goods sold (COGS) (see COGS (cost of goods sold))
- cost optimization
- cost savings, Defining the Basic Terms
- coverable usage, Defining the Basic Terms
- covered usage, Defining the Basic Terms
- cross-functional teams, The Role of Each Team in FinOps
- crossover point, Components of the commitment break-even point
- CSV (comma-separated values), A Brief History of Cloud Billing Data
- CTO/CIO, influencing, CTO/CIO Persona
- CUDs (Committed Use Discounts), Defining the Basic Terms, Introduction to Commitment-Based Discounts, Google Committed Use Discounts
- (see also commitment-based discounts)
- applying, Applying Google CUDs in a Project
- billing, Google Billing and Sharing CUDs-Google Billing Account and Ownership
- cores, Paying for Cores, Not Hours, in Google
- Flexible CUDs, Defining the Basic Terms, Google Flexible Committed Use Discounts
- ownership, Google Billing Account and Ownership
- payment linkage, Google Billing Account and Ownership
- rate reduction and, Two Levers to Affect Your Bill
- sharing, Google Billing and Sharing CUDs-Google Billing Account and Ownership
- cultural changes, Operate
- culture
- CUR (Cost and Usage Report), A Brief History of Cloud Billing Data
- custom pricing, Custom Pricing
- custom rate calculation, Inform
D
- data
- data center, traditional processes and, Cloud Spend Keeps Accelerating
- data format, cloud billing, Basic Format of Billing Data-Basic Format of Billing Data
- data in the path of the engineer, Data in the Path of the Engineer-Data in the Path of the Engineer
- data retention policies
- data-driven decision making, Data-Driven Decision Making, Starting with the End in Mind: Data-Driven Decision Making-Starting with the End in Mind: Data-Driven Decision Making
- DBR (Detailed Billing Report), A Brief History of Cloud Billing Data
- DBR-RT (Detailed Billing Report with Resources and Tags), A Brief History of Cloud Billing Data
- decentralized teams, Type of Alignment to the Organization
- decentralized usage reduction, Why You Should Decentralize Usage Reduction-Why You Should Decentralize Usage Reduction
- decision making
- Deming, W. Edwards, Deming on Business Transformation-Deming on Business Transformation
- Detailed Billing Report (DBR), A Brief History of Cloud Billing Data
- Detailed Billing Report with Resources and Tags (DBR-RT), A Brief History of Cloud Billing Data
- developers, FinOps teams and, Engineering and Developers
- DevOps term, Where Did FinOps Come From?
- discounts
- domains, Foundation Framework, Domains and Capabilities
- driver-based forecasting, Forecasting Methodologies
E
- EBITDA (earnings before interest, taxes, depreciation, and amortization), Defining Finance Terms for Cloud Professionals
- EC2 (Elastic Compute Cloud), RIs (Reserved Instances), Standard Versus Convertible RIs
- efficiency, cost as metric, Data in the Path of Engineers
- Electricity Maps, FinOps and GreenOps Better Together?
- emissions
- ESG (environmental, social, and governance) initiatives, Sustainability: FinOps Partnering with GreenOps
- reporting, Are Cloud Providers Green?-Granularity
- scope 1, Scope 1, 2, and 3 Emissions
- scope 2, Scope 1, 2, and 3 Emissions
- scope 3, Scope 1, 2, and 3 Emissions
- engineering lead, influencing, Engineering Lead Persona
- engineers
- constraints and, Constraints and the Solving of Hard Problems-Constraints and the Solving of Hard Problems
- cost-efficiency, Principles for Enabling Cost-Efficient Engineering-#6: Leadership Support Isn’t Helpful, It Is Essential
- data in the path of the engineer, Data in the Path of the Engineer-Data in the Path of the Engineer
- FinOps teams and, Engineering and Developers
- motivation, What’s on the Mind of the Engineer?
- motivations, Engineers-Engineers
- partnering models
- reducing load, What’s on the Mind of the Engineer?
- reporting and, Data in the Path of Engineers
- us versus them, Integrating Us with Them
- environment tags, Picking the Right Number of Tags
- estimates, forecasting, Cost Estimation-Cost Estimation
- executive pitches, Different Executive Pitches for Different Levels
- executive sponsor pitches, Pitching the Executive Sponsor-Pitching the Executive Sponsor
- executive support, Who Does FinOps?
- executives
F
- feedback loops
- feedback, gathering, Gather team feedback
- finance people, motivations, Finance People
- finance team, Finance
- finance terms
- FinOps
- as cultural shift, When Should You Start FinOps?
- as light practice, A Confession
- core principles, Core Principles of FinOps-Core Principles of FinOps
- culture, FinOps Culture in Action-Tipping the Scales in Your Favor
- definition, Defining the Term “FinOps”
- GreenOps and, FinOps and GreenOps Better Together?-FinOps and GreenOps Better Together?
- hiring for, Hiring for FinOps-Hiring for FinOps
- history, Where Did FinOps Come From?-Where Did FinOps Come From?
- impact of not adopting, The Impact of Not Adopting FinOps-Informed Ignoring: Why Start Now?
- leader history example, The FinOps Hero’s Journey-The FinOps Hero’s Journey
- overview, What Is FinOps?
- planning for, Stage 1: Planning for FinOps in an Organization
- practitioners, FinOps Practitioners
- preparing for, Stage 3: Preparing the Organization for FinOps
- principles, The Six Principles of FinOps
- startup timing, When Should You Start FinOps?-When Should You Start FinOps?
- terminology, Where Did FinOps Come From?
- users, Who Does FinOps?-Who Does FinOps?
- FinOps automation (see automation)
- FinOps model, initial, Define initial FinOps model
- FinOps teams (see teams)
- FinOpsPod podcast, When to Build
- Flexible CUDs, Defining the Basic Terms, Introduction to Commitment-Based Discounts, Google Flexible Committed Use Discounts
- (see also commitment-based discounts)
- Flickr, Use Cloud for the Right Reasons
- flow, Data in the Path of the Engineer
- folders, Tags, Labels, and Accounts, Oh My!
- forecasting, Advancing Pitch, Accurate Forecasting
- automated, Manual Versus Automated Forecasts
- bottom-up, Granularity
- budgeting and, Forecast and Budgeting-Forecast and Budgeting
- cloud forecasting, The State of Cloud Forecasting, The State of Cloud Forecasting
- communication and, Communication
- composite, Forecasting Models
- cost estimates and, Cost Estimation-Cost Estimation
- cost optimization and, Impacts of Cost Optimization on Forecasts-Impacts of Cost Optimization on Forecasts
- driver-based, Forecasting Methodologies
- frequency of, Forecast Frequency-Forecast Frequency
- future projects, Future Projects
- granularity, Granularity-Granularity
- inaccuracies, Inaccuracies
- inform phase, Inform
- machine learning, Forecasting Models
- manual, Manual Versus Automated Forecasts
- middle-out, Granularity
- models, Forecasting Models
- multivarate, Forecasting Methodologies
- naive forecasting, Forecasting Methodologies
- rolling, Forecasting Models
- static, Forecasting Models
- tagging and, Creating Goodwill and Auditability with Accounting
- top-down, Granularity
- trend-based, Forecasting Methodologies
- univariate, Forecasting Methodologies
- Fortune 500 companies, Use Cloud for the Right Reasons
- Foundation Framework, The FinOps Foundation Framework
- frameworks, The FinOps Foundation Framework, Connectivity to Other Frameworks
- (see also Foundation Framework)
- CM (Configuration Management), Connectivity to Other Frameworks
- conflict avoidance, Working with Other Methodologies and Frameworks-Share Knowledge
- cybersecurity, Connectivity to Other Frameworks
- FinOps intersection, Advancing Pitch
- information security, Connectivity to Other Frameworks
- ITAM (IT Asset Management), Connectivity to Other Frameworks
- ITFM (IT Financial Management), Connectivity to Other Frameworks
- ITIL (IT Infrastructure Library), Connectivity to Other Frameworks
- ITSM (IT Service Management), Connectivity to Other Frameworks
- maturity assessment, Advancing Pitch
- SAM (Software Asset Management), Connectivity to Other Frameworks
- TBM (Technology Business Management), Connectivity to Other Frameworks
- fully loaded costs, Defining the Basic Terms
- functional activities, Functional activities
G
- gamification, Benchmarking and Gamification
- GCE (Google Compute Engine), Paying for Cores, Not Hours, in Google
- goal setting
- budgets and, Budget Variances-Budget Variances
- cost allocation, The First Goal Is Good Cost Allocation
- goals as target line, Goals as Target Lines-Goals as Target Lines
- iron triangle, The Iron Triangle: Good, Fast, Cheap-The Iron Triangle: Good, Fast, Cheap
- OKRs (objectives and key results), Hitting Goals with OKRs-OKR Focus Area #3: Control
- reasons for, Why Do You Set Goals?
- savings and, Is Savings the Goal?-Is Savings the Goal?
- goals
- Google RIs (Reserved Instances), Overview of Usage Commitments Offered by the Big Three
- greenhouse gases, What Are Cloud Carbon Emissions?
- GreenOps, Partnering with Engineers on Sustainability
- greenwashing, Sustainability: FinOps Partnering with GreenOps
- groups
H
- headcount plan for FinOps teams, Sample Headcount Plan for Advancing a FinOps Team
- Hick's Law, reporting and, Hick’s Law
- hierarchies, Accounts, Tagging, Account Organization Hierarchies
- hierarchy structures, Tags, Labels, and Accounts, Oh My!
- hierarchy-based approaches, Tag- and Hierarchy-Based Approaches-Tag- and Hierarchy-Based Approaches
- hiring, Hiring for FinOps-Hiring for FinOps
- hiring plan, Sample Headcount Plan for Advancing a FinOps Team
- homegrown tooling, Build Versus Buy Versus Native
- horizontal rightsizing, Centralize the rightsizing of clusters
- hourly data, The Importance of Hourly Data
I
- IAM (Identity and Access Management) service, Google Billing Account and Ownership
- ICC (internal cost of capital), Defining Finance Terms for Cloud Professionals
- images, Containers 101
- inaction in teams, Handling Inaction-Handling Inaction
- inform phase of lifecycle, The FinOps Lifecycle, Inform-Inform
- informed ignoring, Informed Ignoring: Why Start Now?-Informed Ignoring: Why Start Now?, A Confession
- infrastructure sharing, Share Infrastructure
- instance size flexibility (ISF) (see ISF (instance size flexibility))
- instances
- integration, A New Way of Working Together
- internal cost of capital (ICC), Defining Finance Terms for Cloud Professionals
- invoices, Types of Cloud Bill
- IP addresses, unused, Clean up unused IP addresses
- Iron Triangle, The Iron Triangle: Good, Fast, Cheap
- Cheap, The Iron Triangle: Good, Fast, Cheap
- Fast, The Iron Triangle: Good, Fast, Cheap
- Good, The Iron Triangle: Good, Fast, Cheap
- unit economic metrics, Coming Back to the Iron Triangle-Coming Back to the Iron Triangle
- ISF (instance size flexibility), AWS RIs (Reserved Instances), Instance Size Flexibility-Instance Size Flexibility
- ITAM (IT Asset Management), Connection to Other Frameworks/Models, Connectivity to Other Frameworks
- iteration, commitment-based discount programs, Step 5: Measure and Iterate-Step 5: Measure and Iterate
- ITFM (IT Financial Management), Connectivity to Other Frameworks
- ITIL (IT Infrastructure Library), Connectivity to Other Frameworks
- ITSM (IT Service Management), Connection to Other Frameworks/Models, Connectivity to Other Frameworks
L
- labels, Tags, Labels, and Accounts, Oh My!
- language, Defining a Common Lexicon
- language in reports, Language
- leadership
- leadership team, reporting and, Data in the Path of Leadership
- lifecycle
- lift-and-shift, The Impact of Not Adopting FinOps
- LinkedIn, Where Did FinOps Come From?
M
- machine learning forecasts, Forecasting Models
- maintainability, OKRs, OKR Focus Area #2: Maintainable
- manual forecasts, Manual Versus Automated Forecasts
- matching principle, Defining Finance Terms for Cloud Professionals
- maturity assessment
- MDCO (metric-driven cost optimization), Metric-Driven Cost Optimization
- measurability, OSSM and, Cloud Spend Keeps Accelerating
- measurement
- metadata, Tags, Labels, and Accounts, Oh My!
- metric-driven cost optimization (MDOC) (see MDOC (metric-driven optimization))
- metrics (see unit economic metrics)
- middle-out forecasting, Granularity
- midstage maturity, Adopting FinOps
- months, A Month Is Not a Month
- motivating people, Difficulty Motivating People Is Not New-Difficulty Motivating People Is Not New
- motivations
- multicloud providers, reporting and, Multicloud
- multivariate forecasting, Forecasting Methodologies
N
- naive forecasting, Forecasting Methodologies
- names tag, Picking the Right Number of Tags
- namespaces, Containers 101
- native cost tools, Types of Cloud Bill, Cloud Billing Complexity
- native tooling, Build Versus Buy Versus Native
- negotiated discounts, centralized, Chargeback and Showback Considerations
- negotiated rates, Negotiated Rates
- net present value (NPV), Step 6: Allocate Up-Front Commitment Costs Appropriately
- net-zero emissions, What Are Cloud Carbon Emissions?
- networking, cost control and, Networking
- NFR (nonfunctional requirement), Partnering with Engineers on Sustainability
- No upfront commitment, Components of the commitment break-even point
- NPV (net present value), Step 6: Allocate Up-Front Commitment Costs Appropriately
O
- object storage, cost control and, Object Storage
- OKRs (objectives and key results), Hitting Goals with OKRs-OKR Focus Area #3: Control
- on-demand rate, Defining the Basic Terms
- on-demand, OSSM and, Cloud Spend Keeps Accelerating
- onboarding, Onboarding
- operate phase of lifecycle, The FinOps Lifecycle, Operate-Operate
- operations, scheduled, Scheduled Operations
- optimization, Metric-Driven Cost Optimization
- (see also MDOC (metric-driven optimization))
- costs
- optimize phase of lifecycle, The FinOps Lifecycle, Optimize-Optimize
- OSSM (on-demand, scalable, self-service, measurable), Cloud Spend Keeps Accelerating
- over purchasing, commitment-based discount programs, Step 5: Measure and Iterate-Step 5: Measure and Iterate
- overlapping goals, Make Friends and Share Goals
- oversized/undersized, Defining the Basic Terms
- overspend, effects of, Advancing Pitch
- ownership of cloud usage, #3: Everyone Takes Ownership of Their Cloud Usage
P
- payments, commitment-based discount programs, Who Pays for Commitments?
- performance simulation, rightsizing and, Not Simulating Performance Before Rightsizing
- personas
- phases, Foundation Framework, Phases
- pilot stall, The Impact of Not Adopting FinOps
- pitches
- pods, Containers 101
- practitioners, FinOps Practitioners
- principles, Foundation Framework, Principles
- Prius Effect, Real-Time Feedback (aka the “Prius Effect”)-Real-Time Feedback (aka the “Prius Effect”)
- private offers, Seller Private Offers
- processes, Processes
- procurement
- product teams, Product or Business Teams
- projects, Tags, Labels, and Accounts, Oh My!
- psychology of reporting, Psychological Concepts
R
- rate optimization
- rate reduction, Two Levers to Affect Your Bill
- real-time reporting, Real-Time Feedback (aka the “Prius Effect”)-Real-Time Feedback (aka the “Prius Effect”)
- redesign
- remediations, GreenOps and, GreenOps Remediations
- renewable energy, cloud providers and, Are Cloud Providers Green?
- reporting
- accessibility, Accessibility, #4: FinOps Reports Should Be Accessible and Timely
- color, Color
- color, consistency of, Consistency of Color and Visual Representation
- consistency, Usability and Consistency
- language, Language
- recognition versus recall, Recognition Versus Recall
- usability, Usability and Consistency
- visual hierarchy, Visual Hierarchy
- visual representation, consistency of, Consistency of Color and Visual Representation
- accuracy, Perfect Is the Enemy of Good
- changing, Rolling Out Changes
- consolidating, The Universal Report
- data quality, Data Quality-Data Quality
- engineers, Data in the Path of Engineers
- finance team, Data in the Path of Finance
- leadership, Data in the Path of Leadership
- maturity assessment and, Maturity
- multicloud providers, Multicloud
- personas and, Personas
- psychology , Psychological Concepts
- real-time reporting, Real-Time Feedback (aka the “Prius Effect”)-Real-Time Feedback (aka the “Prius Effect”)
- showback, Inform
- tag performance, Reporting on Tag Performance
- tiering, Report Tiering-Report Tiering
- timeliness, #4: FinOps Reports Should Be Accessible and Timely
- universal report, The Universal Report-The Universal Report
- research phase of planning, Do your research
- reserved instances (see RIs (Reserved Instances))
- resource allocation
- resource groups, Tags, Labels, and Accounts, Oh My!
- resource owner tag, Picking the Right Number of Tags
- resource-blended rate, Who Pays for Commitments?
- resources, Full Time, Part Time, Borrowed Time: A Note on Resources-Full Time, Part Time, Borrowed Time: A Note on Resources
- responsibility, processes and, Responsibility
- revenue, unit economics and, Unit Economics Don’t Have to Be About Revenue
- rightsizing
- automated, Advanced Workflow: Automated Opt-Out Rightsizing-Advanced Workflow: Automated Opt-Out Rightsizing
- averages, relying on, Relying on Recommendations That Use Only Averages or Peaks
- Azure managed disk, Failing to Rightsize Beyond Compute
- Cloud SQL and, Failing to Rightsize Beyond Compute
- clusters, centralized, Centralize the rightsizing of clusters
- communication and, Not All Waste Is Waste
- EBS (Elastic Block Store), Failing to Rightsize Beyond Compute
- extending, Failing to Rightsize Beyond Compute
- Google Cloud Persistent Disk, Failing to Rightsize Beyond Compute
- managed SQL, Failing to Rightsize Beyond Compute
- peaks, relying on, Relying on Recommendations That Use Only Averages or Peaks
- performance simulation and, Not Simulating Performance Before Rightsizing
- RDS (Relational Database Service), Failing to Rightsize Beyond Compute
- reserved instances, Hesitating Due to Reserved Instance Uncertainty
- resource shape and, Not Addressing Your Resource “Shape”
- term use, Defining the Basic Terms
- use reduction and, Usage Reduction by Resizing (Rightsizing)-Hesitating Due to Reserved Instance Uncertainty
- versus commitment-based discount programs , When to Rightsize Versus Commit-Strategy Tips
- RIs (Reserved Instances), Defining the Basic Terms, Introduction to Commitment-Based Discounts
- rolling forecasts, Forecasting Models
S
- SaaS (software-as-a-service), Build Versus Buy Versus Native
- SAM (Software Asset Management), Connectivity to Other Frameworks
- savings
- Savings Plans (SPs) (see SPs (Savings Plans))
- savings pools, Who Pays for Commitments?
- savings potential, Defining the Basic Terms
- savings realized, Defining the Basic Terms
- savings, goal setting and
- scalability, OSSM and, Cloud Spend Keeps Accelerating
- scaling, usage optimization and, Scaling
- schedule-driven cost optimization, Metric-Driven Versus Cadence-Driven Processes-Metric-Driven Versus Cadence-Driven Processes
- scheduled operations, usage optimization and, Scheduled Operations
- scope 1 emissions, Scope 1, 2, and 3 Emissions
- scope 2 emissions, Scope 1, 2, and 3 Emissions
- scope 3 emissions, Scope 1, 2, and 3 Emissions
- scorecards, Inform
- self-built automation tools, Tooling Deployment Options
- self-hosted third-party automation tools, Tooling Deployment Options
- self-service, OSSM and, Cloud Spend Keeps Accelerating
- seller private offers, Seller Private Offers
- server instance node, Containers 101
- serverless computing, usage optimization and, Serverless Computing-Serverless Computing
- serverless containers, Serverless Containers
- service providers, Foundation Framework, Structure of a Domain
- service/workload name tag, Picking the Right Number of Tags
- shared costs, Accounts, Tagging, Account Organization Hierarchies
- showback, Chargeback Versus Showback
- showback reporting, Inform
- Site Readability Engineers (SREs) (see SREs (Site Readability Engineers))
- skill sets requirements, Hiring for FinOps
- SME (subject matter experts), The FinOps Team Doesn’t Do FinOps
- socialization of FinOps for adoption, Stage 2: Socializing FinOps for Adoption in an Organization-Define initial FinOps model
- sourcing
- spend data, stakeholder info, Operate
- spend panic, The “Spend Panic” Tipping Point-The “Spend Panic” Tipping Point
- spending accountability, Spending Is Fine, Wasting Is Not-Spending Is Fine, Wasting Is Not
- spending data, mapping, Inform
- spending formula, cloud billing and, Basic Format of Billing Data
- spot resources, rate optimization and, Spot Resource Usage
- Spotify, Use Cloud for the Right Reasons
- SPs (Savings Plans), Defining the Basic Terms, Introduction to Commitment-Based Discounts
- SREs (Site Readability Engineers), Why to Buy
- staffing teams, Staffing and Augmenting Your FinOps Team
- stakeholders
- starting pitch, Starting Pitch
- static forecasts, Forecasting Models
- storage pricing, Storage Pricing-Storage Pricing
- subject matter experts (SMEs), The FinOps Team Doesn’t Do FinOps
- subscriptions, Tags, Labels, and Accounts, Oh My!
- support charges, Spreading Out Shared Costs
- sustainability, Sustainability: FinOps Partnering with GreenOps
T
- TAG (Technical Architecture Group), Indirect Collaboration
- tag strategy, Inform
- tag-based approaches, Tag- and Hierarchy-Based Approaches-Tag- and Hierarchy-Based Approaches
- tagging, Accounts, Tagging, Account Organization Hierarchies
- cost center/business unit, Picking the Right Number of Tags
- delaying activation, Getting Started Early with Tagging
- environment, Picking the Right Number of Tags
- governance, automating, Tag Governance
- names, Picking the Right Number of Tags
- number of tags, Picking the Right Number of Tags-Picking the Right Number of Tags
- reports, Reporting on Tag Performance
- resource owner, Picking the Right Number of Tags
- service/workload name, Picking the Right Number of Tags
- standard, implementing, Deciding When to Set Your Tagging Standard-Deciding When to Set Your Tagging Standard
- tag hygiene, Maintaining Tag Hygiene-Maintaining Tag Hygiene
- tags, Tags, Labels, and Accounts, Oh My!
- (see also labels)
- billing and, Using Tags for Billing
- consistency, Maintaining Tag Hygiene
- containers and, Tags, Labels, and Namespaces
- flexibility and, Tags and Labels: The Most Flexible Allocation Option-Getting Teams to Implement Tags
- implementing, onboarding teams, Getting Teams to Implement Tags
- restrictions, Working Within Tag/Label Restrictions-Working Within Tag/Label Restrictions
- versus accounts, Comparing Accounts and Folders Versus Tags and Labels-Comparing Accounts and Folders Versus Tags and Labels
- target lines, MDCO and, Targets
- target setting, Setting Targets
- TBM (Technology Business Management), Connection to Other Frameworks/Models, Connectivity to Other Frameworks
- TCO (total cost of ownership), Total Cost of Ownership
- teams
- budgeting and, The Importance of Managing Teams to Budgets-The Importance of Managing Teams to Budgets
- business teams, Product or Business Teams
- carrot versus stick approach, Carrot Versus Stick Approach-Carrot Versus Stick Approach
- central enablement team, Who Does FinOps?
- centralized, Core Principles of FinOps, Why a Centralized Team?-Why a Centralized Team?, Type of Alignment to the Organization, #5: A Centralized Team Drives FinOps
- cloud expertise, Who Does FinOps?
- cloud variable cost model, #6: Take Advantage of the Variable Cost Model of the Cloud
- collaboration, #1: Teams Need to Collaborate
- communication between, Who Does FinOps?
- cross-functional, The Role of Each Team in FinOps
- culture, Carrot Versus Stick Approach-Handling Inaction
- decentralized, Type of Alignment to the Organization
- decisions, business value of cloud, #2: Decisions Are Driven by the Business Value of Cloud
- Deming on, Deming on Business Transformation
- developers and, Engineering and Developers
- education, Tipping the Scales in Your Favor
- engineers and, Engineering and Developers
- executive support, Who Does FinOps?
- executives and, Executives and Leadership
- finance team and, Finance
- FinOps team as enablement team, The FinOps Team Doesn’t Do FinOps
- goals and, Achieving Goals
- headcount plan, Sample Headcount Plan for Advancing a FinOps Team
- inaction, Handling Inaction-Handling Inaction
- leadership and, Executives and Leadership
- ownership of cloud usage, #3: Everyone Takes Ownership of Their Cloud Usage
- procurement and, Procurement and Sourcing
- product teams, Product or Business Teams
- reporting, #4: FinOps Reports Should Be Accessible and Timely
- sharing among, Share Influence, Terminology, and Processes
- skills needed, Who Does FinOps?
- sourcing and, Procurement and Sourcing
- staffing, Staffing and Augmenting Your FinOps Team
- startup and, When Should You Start FinOps?
- technology leader and, Where Does Your FinOps Team Report?-Where Does Your FinOps Team Report?
- Technology Business Management (TBM), Connection to Other Frameworks/Models, Connectivity to Other Frameworks
- terminology, Defining a Common Lexicon
- amortized costs, Defining the Basic Terms
- blended rates, Defining the Basic Terms
- cloud language versus business language, Cloud Language Versus Business Language-Cloud Language Versus Business Language
- commitment waste, Defining the Basic Terms
- commitment-based discounts, Defining the Basic Terms
- commitments unused/unutilized, Defining the Basic Terms
- cost allocation, Defining the Basic Terms
- cost avoidance, Defining the Basic Terms
- cost savings, Defining the Basic Terms
- coverable usage, Defining the Basic Terms
- covered usage, Defining the Basic Terms
- finance terms
- fully loaded costs, Defining the Basic Terms
- on-demand rate, Defining the Basic Terms
- oversized/undersized, Defining the Basic Terms
- rate reduction, Defining the Basic Terms
- rightsizing, Defining the Basic Terms
- savings potential, Defining the Basic Terms
- savings realized, Defining the Basic Terms
- unblended rates, Defining the Basic Terms
- universal translator, Creating a Universal Translator Between Your DevOps and Finance Teams
- wasted usage, Defining the Basic Terms
- workload management, Defining the Basic Terms
- third-party automation tools
- time-based discounts, Time-Based-Time-Based
- tooling
- top-down forecasting, Granularity
- total committed cost break-even point, Components of the commitment break-even point
- total cost of ownership (TCO), Total Cost of Ownership
- training, Foundation Framework, Structure of a Domain
- trend-based forecasting, Forecasting Methodologies
U
- UI (user interface), The UI of FinOps
- unblended rates, Defining the Basic Terms
- unit costs, measuring, Advancing Pitch
- unit economic metrics, Unit Economics and Metrics-Unit Economics and Metrics
- unit economics, Considerations
- univariate forecasting, Forecasting Methodologies
- universal report, The Universal Report-The Universal Report
- universal translator, Creating a Universal Translator Between Your DevOps and Finance Teams
- unlimited storage, Object Storage
- (see also object storage)
- up-front cost allocation, Step 6: Allocate Up-Front Commitment Costs Appropriately-Step 6: Allocate Up-Front Commitment Costs Appropriately
- usability of reports, Usability and Consistency
- usage
- usage optimization
- automated analytics and, Usage Reduction by Resizing (Rightsizing)
- benefits, Benefit Versus Effort-Benefit Versus Effort
- containers, rightsizing, Centralize the rightsizing of clusters-Decentralize the rightsizing of containers/pods
- cost avoidance, Tracking Savings, Tracking Savings
- data retention policies, Usage Reduction by Removing/Moving
- lost or forgotten resources, Usage Reduction by Removing/Moving
- maturing, Maturing Usage Optimization-Maturing Usage Optimization
- redesign and
- rightsizing and, Usage Reduction by Resizing (Rightsizing)-Hesitating Due to Reserved Instance Uncertainty
- RIs (Reserved Instances) and, Effects on Reserved Instances-Effects on Reserved Instances
- savings tracking, Tracking Savings-Tracking Savings
- serverless computing and, Serverless Computing-Serverless Computing
- usage reduction workflows, The Cold Reality of Cloud Consumption
- waste, finding, Usage Reduction by Removing/Moving
- usage reduction
- usage-based discounts, Usage-Based-Usage-Based
- users of FinOps, Who Does FinOps?-Who Does FinOps?
- UX (user experience), The UI of FinOps
V
- values, communicating, Communicate value
- variable cost model, Core Principles of FinOps, #6: Take Advantage of the Variable Cost Model of the Cloud
- vendors
- vertical rightsizing, Centralize the rightsizing of clusters
- visibility, Visibility-Visibility
- visual hierarchy in reports, Visual Hierarchy
- volume/tiered discounts, Volume/Tiered Discounts
- Von Restorff effect, reporting and, The Von Restorff Effect
..................Content has been hidden....................
You can't read the all page of ebook, please click
here login for view all page.