search

FinOps-Open-Cost-and-Usage-Spec / FOCUS_Spec

The Unifying Specification for Cloud Billing Data
https://focus.finops.org
Other
184 stars 39 forks source link

[Work_Item] Cloud Sustainability #637

Open bndshrm opened 3 weeks ago

bndshrm commented 3 weeks ago

1. Problem Statement *

Describe the problem, issue, use case, or opportunity that this work item addresses. Include practitioner quotes illustrating real examples a) of questions being asked by practitioners and b) value unlocked by answering these questions, if available.

  • What is the problem?: Explain the context and why it needs resolution.
  • Impact: Describe how the problem affects users, systems, or the project.

The FOCUS Spec should • We need to be able to understand the carbon equivalent (CO2e) of our cloud usage down to the resource level • Normalize the carbon equivalent data from different sources (CSPs, SaaS vendors and regulators)

Use cases:

• Visibility into the carbon footprints • Allow decision making including cost and carbon equivalent • Helps make decision on the power source (renewables, nuclear)

2. Objective *

State the objective of this work item. What outcome is expected?

  • Success Criteria: Define how success will be measured (e.g. metrics and KPIs).

Promote, advance, and socialize Cloud Computing Sustainability Best Practices to reduce the environmental impact of public cloud. Forge partnerships with ESG leaders, practitioners, and vendors, establishing unified operational standards and processes that advance Cloud Sustainability, seamlessly integrating it into broader enterprise Sustainability practices.

3. Supporting Documentation *

Include links to supporting documents such as:

  • Data Examples: [Link to data or relevant files; DO NOT share proprietary information]
  • Related Use Cases or Discussion Documents: [Link to discussion]
  • PRs or Other References: [Link to relevant references]

KPIs are listed in below document https://docs.google.com/document/d/12Qkw1ZXxskNKTwzi5eQxAFn-9o1uuEFUo8Zu243dYHg/edit?tab=t.0

4. Proposed Solution / Approach

Outline any proposed solutions, approaches, or potential paths forward. Do not submit detailed solutions; please keep suggestions high-level.

  • Initial Ideas: Describe potential solution paths, tools, or technologies.
  • Considerations: Include any constraints, dependencies, or risks.
  • Feasibility: Include any information that helps quantify feasibility, such as perceived level of effort to augment the spec, or existing fields in current data generator exports.
  • Benchmarks: Are there established best practices for solving this problem available to practitioners today (e.g. mappings from existing CSP exports that are widely used)?

n/a

5. Epic or Theme Association

This section will be completed by the Maintainers.

  • Epic: [Epic Name]
  • Theme: [Theme Name, if applicable]

Sustainability

6. Stakeholders *

List the main stakeholders for this issue.

  • Primary Stakeholder: [Name/Role]
  • Other Involved Parties: [Names/Roles]

Bindu Sharma (Teradata)

jpradocueva commented 2 weeks ago

Action Items from the Members' call on November 7:

shawnalpay commented 1 week ago

@bndshrm Thank you for authoring this issue! I have converted it into the Work Item format in order to consider it formally for a future release. All the guidance you shared in your original post should still be there; feel free to edit and add more if you see fit.

jpradocueva commented 2 days ago

Action Items from TF-1 call on November 19:

Kbjng commented 2 days ago

@shawnalpay do we a research group yet? Thanks

shawnalpay commented 1 day ago

@Kbjng Not yet! I shall be proposing the creation of a Research Group to the FOCUS Steering Committee this week, and pending that outcome, we will decide on next steps. I'll circle back!

Kbjng commented 1 day ago

@shawnalpay That’s awesome. Thanks for the good work.

jpradocueva commented 4 hours ago

Action Items from the Members' call on November 21: