Monitor credit consumption to prevent over usage

[AxelGrille1]

SAP BTP Credits

Early Warning

Introduction:

Many BTP customers have negotiated contracts with SAP for their BTP credits. To prevent credit overconsumption, an usage predictor can be very helpful. Therefore, we propose implementing a detailed tracker with a usage prediction feature.

Usage Prediction Model:

Since business operations are often cyclical, we base our predictions on the usage from the previous two months. This approach could also account for seasonal variations.

Steps to Implement the Tracker:

1. Data Retrieval:

    We will use the Usage Data Management Service API to gather consumption data for each global account and its associated subaccounts.

2. Data Processing:

    The daily usage data for each subaccount will be classified and filtered to retain only the data from the last two months.

    We will then compute the sliding means for each subaccount. This involves averaging the daily usage over the past two months.

3. Prediction Calculation:

    The computed sliding means will be multiplied by the number of days remaining in the current month to predict future usage.

    This prediction accounts for seasonality, providing a more accurate forecast shifted by two months..

4. Alert System:

    Based on the predictions, an alert will be sent to the account owner if they are likely to over consume their credits. The alert will provide a detailed view of the credit usage with charts and tables associated with a prevention message like ‘We recommend you to review your credit consumption or contact SAP for a renewal of your contract’. This allows them to take preventative action or renegotiate their credit contract with SAP.

Technical Implementation:

•  We will deploy a Python-based microservice on SAP BTP Cloud Foundry.
•  This microservice will:
•   Scrape usage data via the API endpoint.
•   Generate time series for analysis.
•    Present the data in an easy to understand chart format.
•    Provide recommendations based on the usage predictions.

Conclusion:

This usage tracker will help BTP customers manage their credit consumption more effectively, avoiding overconsumption and potential cost overruns.

[Wallace]

I see this in the post: We will deploy a Python-based microservice on SAP BTP Cloud Foundry.

this brings two questions:

1.  If we have Neo based subaccounts/non Cloud Foundry items?

2.  Will this microservice then be active in all subaccounts?

And a bonus question - "free" services - will they appear in the use?  

[i0337818]

Who will and by when?