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

[Work_Item] Support for recognising contractual commitment events as billing records (i.e. burn-up, negotiated rates) #666

Open
ahullah opened this issue Dec 13, 2024 · 3 comments
Assignees
Labels
1.2 consideration To be considered for release 1.2 discussion topic Item or question to be discussed by the community saas SaaS-centric concepts work item Issues to be considered for spec development

Comments

@ahullah
Copy link
Contributor

ahullah commented Dec 13, 2024

Problem Statement

Currently we support macro (contract negotiation) and micro (ad hoc / resource or product level) commitments for the micro commitments we provide all records required to fully account for the commitment (purchase, usage, wastage) however we do not provide the same capability for macro (contractual) commitments, where we typically only account for usage (and potentially wastage) the initial purchase is not well supported.

Objective

Define a mechanism for incorporation of contractual / negotiated commitment terms to be represented as billing records

Supporting Documentation

See 616

Proposed Solution / Approach

Incorporate changes to charge type, charge category (or others?) and an appendix for specific record types to provide a way for macro commitments to be represented as a 'purchase' type record to support longer term / contractual commitment mechanisms

Epic or Theme Association

616

Stakeholders

Chris, Irena, Riley, Larry

@ahullah ahullah added the work item Issues to be considered for spec development label Dec 13, 2024
@github-project-automation github-project-automation bot moved this to Triage in FOCUS WG Dec 13, 2024
@ahullah ahullah added 1.2 consideration To be considered for release 1.2 discussion topic Item or question to be discussed by the community saas SaaS-centric concepts labels Dec 13, 2024
@ahullah
Copy link
Contributor Author

ahullah commented Dec 13, 2024

this was raised off the back of TF-3 13/12/24 --- further investigation required on impact on existing CSPs as this is concept is not well supported today

@ahullah
Copy link
Contributor Author

ahullah commented Dec 13, 2024

NOTE: USE CASE: this allows practitioners to track their 'performance' / usage against larger scale commitments that may span multiple years to avoid financial penalties / usage true-ups

@jpradocueva
Copy link
Contributor

Action Items from the Maintainers' call on December 16:

  • [#666] Irena @ijurica : Prepare a high-level overview document outlining the scope, potential impact, and examples of contractual commitments.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1.2 consideration To be considered for release 1.2 discussion topic Item or question to be discussed by the community saas SaaS-centric concepts work item Issues to be considered for spec development
Projects
Status: Triage
Development

No branches or pull requests

7 participants