Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEEDBACK]: Support for a forecast dataset #650

Open
tfcross opened this issue Nov 20, 2024 · 1 comment
Open

[FEEDBACK]: Support for a forecast dataset #650

tfcross opened this issue Nov 20, 2024 · 1 comment
Assignees
Labels
forecasting Related to budgets and forecasts use case Feature Request & Use Case Feedback

Comments

@tfcross
Copy link

tfcross commented Nov 20, 2024

Summary

The existing FOCUS dataset is purely for historical spend, but it could be also be useful to have predicted, or forecast costs in the same format. This can be aggregated from multiple sources, in much the same way as the historical FOCUS data, to provide a rolled up forecast, and easily visualised alongside historical data.

Which area does this issue relate to?

A: Missing FinOps feature, use case, or scenario

Detailed Description

If we imagine a time when all of yout provider cost data is in FOCUS, pulled in from various sources into a common platform for analysis and visualisation, that gives you a single pane of glass for historical spend. If I wanted to see that alongside forecasted spend, I would either have to rely on a single source for forecasting, based on my FOCUS data, or I could source forecast data from many providers and normalize those forecasts just the same as we do for historical spend with the current FOCUS standard. In this scenario, having a common schema for forecasted spend would unlock some really nice capabilities.

What use cases, FinOps or others, can't be performed with the existing specification unless this issue is addressed?

The two immediate use cases that spring to mind:

  • Allowing teams designing new services to use FOCUS as an output for cost estimation, which could then be aggregated into more accurate forecasts and compared against actuals post deployment.
  • Allowing teams to use a FOCUS-based forecast to indicate when a recommendation will be acted upon, allowing you to aggregate the future execution of recommendations and combine that with your existing FOCUS-forecast data to further improve forecast accuracy and hold teams accountable, driving conversations like: "You had this rightsizing on your forecast, but it didn't materialize when you thought it did, can you adjust your forecast and replan this optimization?".

Which FinOps personas does this issue relate to?

Practitioner, Engineering, Finance, Leadership

Which provider groups or specific providers does this issue relate to?

All providers

On a scale of 1 - 4, how critical is this for your organization?

4: Suggestion, not planning to use FOCUS soon

Objective

No response

Data Examples

No response

Issues, PRs, or Other References

No response

@github-project-automation github-project-automation bot moved this to Triage in FOCUS WG Nov 20, 2024
@shawnalpay shawnalpay added use case Feature Request & Use Case Feedback forecasting Related to budgets and forecasts labels Nov 20, 2024
@jpradocueva
Copy link
Contributor

Summary from the Maintainers' call on Nov 25

Context:
This issue focuses on introducing standardized methodologies and data fields for forecasting within the FOCUS specification. It aims to support consistent predictive analysis for cost management, enabling users to leverage the specification for budgeting and planning purposes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
forecasting Related to budgets and forecasts use case Feature Request & Use Case Feedback
Projects
Status: Triage
Development

No branches or pull requests

3 participants