[Work_Item] Add normalized recommendations dataset

[shawnalpay]

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.

Practitioners consume recommendations from both providers and vendors. These represent an algorithmically-generated list of actions the practitioner should perform in order to optimize the resources and services under their control. Examples include rightsizing, modernization, deactivation, and commitment discount purchases.

Practitioners often consume this information from multiple providers, each of whom generates this information in a different format. Ideally, FOCUS would defined a normalized dataset that could accommodate these recommendations and allow them to be combined across providers and vendors, similar to how FOCUS facilitates combining cost and usage datasets across providers.

Use cases:

• Analyze recommendations across providers
• Analyze changes in recommendations (and potential savings) over time

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).

A new dataset with a set of columns facilitating the normalization of recommendations across providers.

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]

TBD

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)?

TBD

5. Epic or Theme Association

This section will be completed by the Maintainers.

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

TBD

6. Stakeholders *

List the main stakeholders for this issue.

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

Erik Marke (Swiss Post)
Sushil Gulati (Electrolux)
Julian Radu (European Parliament)
Tom Cross (Aer Lingus)
Kaz Szczebiot (JP Morgan Chase)

[jpradocueva]

Summary from the Maintainers' call on Nov 25

This PR proposes standardized recommendations for integrating FOCUS specifications into financial and operational systems. These recommendations aim to streamline adoption, reduce implementation complexity, and ensure consistency in interpreting and applying the specifications.