[Work_Item] Add guidance for how to incorporate non-cloud (on-prem) assets

[ahullah]

Problem Statement

Practitioners moving from a datacentre environment currently need to track the success of cloud migrations and identify dual-run cost (post migration) for effective business case calculation and cost optimization. Additionally allocation of 'all' it cost is a recurring issue that currently has to be handled by separate on-premise and cloud allocation models.

Objective

Provide some initial guidance on how practitioners should use FOCUS fields if they wish to import on-premise (CMDB) type data into the format.

Supporting Documentation

Include links to supporting documentation, if applicable.

Proposed Solution / Approach

In this initial approach, I would hope we can add some supporting content / guidance that explains how specific FOCUS fields might relate to non-cloud data sets, also include considerations around data update frequency to allow for public cloud style usage trending and analysis.

Epic or Theme Association

Provide the rational for the Epic or Theme.

Stakeholders

Provide names and roles of key stakeholders.

[kk09v]

I was originally the Horizontal Squad owner for on-prem/private cloud for 0.5, but we ended up folding that squad due to lack of people with interest/experience in that area combined with the need for more hands elsewhere on the spec. Happy to help work on this some more as I do have some of experience in this area.

[ThavronNan]

This is a big item for one of our clients. They have a very large investment in the on-prem cloud and only experimental use of the Public Cloud. We have shifted them to Focus for public cloud and are attempting to navigate mapping onPrem datasets into the Focus format over the next 4 months

[jpradocueva]

Action Items TF-1 call on Oct 22:

• [#613] Alex @ahullah : Prepare use cases for non-cloud asset guidance and follow up with Karl for insights into prior work on on-prem perspectives.

[shawnalpay]

@ahullah (cc @robmartin33) Had some conversations with TAC/GB practitioners today; based on that, question for you. Do you believe this topic handles for what you might call "private cloud", as opposed to what you've called "on-prem" / "non-cloud" here?

• If yes, can/should we expand this topic to handle for that?
• If not, can/should we craft a separate Work Item for that?

[shawnalpay]

Discussed in Oct 31 Members call. Will assign to a TF for further discussion.

[jpradocueva]

Comments from Members' call on Oct 31:

Analysis: Proposed guidance on non-cloud/on-prem assets. There’s ongoing debate on whether this should include private cloud, creating overlap with other specifications.
Agreements: Shawn will assign this topic to a task force for further discussion to clarify scope and applicability.

[jpradocueva]

Notes from the Maintainers' call on November 4:

Context: This work item addresses the growing need to include on-premises data within the FinOps framework, particularly for hybrid cloud environments. Including on-prem data allows practitioners to track costs in a consistent manner across different environments.
Level of Effort Required: High — Adding on-prem guidance is complex due to variability in on-prem data sources and requires detailed guidance on data integration and reporting.