Guide: Charging: Difference between revisions

Latest revision as of 09:00, 2 March 2026

⚠️ Please Note: This page is currently under development but kept up to date.

All consumptions within the bwCloud-OS will generate costs the home organizations need to play. The payment period is one year.

A registered user can generate costs like follwing:

A user brings a quota entitlement/ eligibility and requests a projects with quota.
The project will be created, quota set, and members added.
Every existing VM and volume will produce costs within this project.

The example in the image below demonstrates how costs can be accumulated based on cost centers.

@@ Line 5: / Line 5: @@
 |}
-All consumptions within the bwCloud-OS will generate costs the home organizations need to play.
+All consumptions within the bwCloud-OS will generate costs the home organizations need to play. The payment period is one year.
-== Contract relationship bwCloud-OS ==
-[[File:Compare cloud provider contracts v3.drawio.png|thumb|Contract relationship compared between bwCloud-OS and other IaaS providers]]
-The contract is closed between the bwCloud-OS and the institutes (customers), as illustrated in the picture. Due to this, one bill will be sent to the customer, including all generated costs from members/ projects related to this institute. Therefore, it is possible that an additional organizational or technical process within each institution may be necessary to manage the accounting relationship between the institution and its members.
 == Cost generation ==
@@ Line 17: / Line 13: @@
 # The project will be created, quota set, and members added.
 # Every existing VM and volume will produce costs within this project.
+=== Cost accumulation examples ===
+==== Example cost accumulation 1 ====
+The example in the image below demonstrates how costs can be accumulated based on cost centers.
+[[File:Example eligibiliy cost center.drawio.png|thumb|Example for eligibility cost centers|600x600px|left]]