Guide: Enterprise Resource Planning - Revision history

As1844 at 15:02, 3 March 2026

2026-03-03T15:02:17Z

← Older revision		Revision as of 15:02, 3 March 2026
Line 13:		Line 13:
	* Entitlements are automatically evaluated during registration.		* Entitlements are automatically evaluated during registration.
	* Users receive immediate access and resources ([[Projects and Quota\|project quota]]) once their entitlement is confirmed. No manual activation is required.		* Users receive immediate access and resources ([[Projects and Quota\|project quota]]) once their entitlement is confirmed. No manual activation is required.

			=== Shared resources ===
			All resources in the bwCloud-OS are shared between all users. Since everyone should be able to access them, project quota limits are set. However, not every user group (e.g., teacher and student) requires the same [[Guide: Project and Quota#List of quota flavors\|quota flavor]].

	=== Charging ===		=== Charging ===

As1844 at 09:05, 2 March 2026

2026-03-02T09:05:53Z

← Older revision		Revision as of 09:05, 2 March 2026
Line 7:		Line 7:

	== Motivation ==		== Motivation ==
	The bwCloud-OS [[Guide: Enterprise Resource Planning#Contract relationship bwCloud-OS\|negotiated only contracts with institutions (customers)]] but not with individual members (users). This is a crucial [[Guide: Enterprise Resource Planning#Contract relationship bwCloud-OS\|difference compared to other known cloud providers]]. Further, there are several different types of sponsors (e.g., faculties, research projects) located at the institutes that need to be enhanced to manage the resources of sub-groups of their members (e.g., students of a faculty).		The bwCloud-OS [[Guide: Enterprise Resource Planning#Contract relationship bwCloud-OS\|negotiated only contracts with institutions (customers)]] but not with individual members (users). This is a crucial [[Guide: Enterprise Resource Planning#Contract relationship bwCloud-OS\|difference compared to other known cloud providers]].

	=== Automated resource provisioning ===		=== Automated resource provisioning ===
Line 18:		Line 18:

	=== Delegating resposibility ===		=== Delegating resposibility ===
	The institutes can define an internal process so their members can set entitlements in the home IdP.		The institutes can define an internal process so their members can set entitlements in the home IdP. There are several different types of sponsors (e.g., faculties, research projects) located at the institutes that should be enhanced to manage the resources of sub-groups of their members (e.g., students of a faculty). With access to their internal data (e.g., from the local IdP), different eligibilities can be assigned.

	=== Reimbursement ===		=== Reimbursement ===
Line 26:		Line 26:
	* bwCloud-OS will generate aggregated usage reports and invoices per institution—no individual billing.		* bwCloud-OS will generate aggregated usage reports and invoices per institution—no individual billing.

	=== Budget ===		=== Budget (Not supported yet) ===
	Sometimes resources should only be consumed up to a certain level or amount of time.		Sometimes resources should only be consumed up to a certain level or amount of time.

	* [[Guide: Entitlement & Eligibility#Constraints\|Constraints]] can be used to manage the valid period for eligibility.		* [[Guide: Entitlement & Eligibility#Constraints\|Constraints]] can be used to manage the valid period for the eligibility.
	* After reaching an eligibility constraint, no more costs can be produced within the associated project.		* After reaching an eligibility constraint, no more costs can be produced within the associated project.

			==== Paidafter ====
			This may be seen as a 'paidafter' credit (analog to 'prepaid'). Institutes grant their members an amount of BEH to consume. Members can freely choose how to consume those, but not more. After the [[Guide: Charging\|payment period]], the institute will only be charged for the consumed BEH.

	=== Central eligibility platform ===		=== Central eligibility platform ===

As1844 at 08:51, 2 March 2026

2026-03-02T08:51:49Z

← Older revision		Revision as of 08:51, 2 March 2026
Line 7:		Line 7:

	== Motivation ==		== Motivation ==
	The bwCloud-OS [[Guide: Enterprise Resource Planning#Contract relationship bwCloud-OS\|negotiated only contracts with institutions (customers)]] but not with individual members (users). This is a crucial [[Guide: ~~Charging~~\|difference compared to other known cloud providers]]. Further, there are several different types of sponsors (e.g., faculties, research projects) located at the institutes that need to be enhanced to manage the resources of sub-groups of their members (e.g., students of a faculty).		The bwCloud-OS [[Guide: Enterprise Resource Planning#Contract relationship bwCloud-OS\|negotiated only contracts with institutions (customers)]] but not with individual members (users). This is a crucial [[Guide: Enterprise Resource Planning#Contract relationship bwCloud-OS\|difference compared to other known cloud providers]]. Further, there are several different types of sponsors (e.g., faculties, research projects) located at the institutes that need to be enhanced to manage the resources of sub-groups of their members (e.g., students of a faculty).

	=== Automated resource provisioning ===		=== Automated resource provisioning ===

As1844 at 15:56, 27 February 2026

2026-02-27T15:56:01Z

← Older revision		Revision as of 15:56, 27 February 2026
Line 2:		Line 2:
	➡️ '''To the''' '''[[Guide: ERP-API\|ERP-API]].'''		➡️ '''To the''' '''[[Guide: ERP-API\|ERP-API]].'''

	The bwCloud-OS provides an [[Guide: ERP-API\|ERP with a RESTful API]] ~~that allows our customers to~~ overview and ~~manage~~ the ~~accounting data and resources of their members. Mainly, this means to manage~~ [[Guide: Entitlement & Eligibility\|entitlements and eligibilities]].		The bwCloud-OS provides an [[Guide: ERP-API\|ERP with a RESTful API]] for overview and management of the [[Guide: Entitlement & Eligibility\|entitlements and eligibilities]]. Hence, for managing accounting data and resources of members.

	__TOC__		__TOC__

As1844 at 15:52, 27 February 2026

2026-02-27T15:52:09Z

← Older revision		Revision as of 15:52, 27 February 2026
Line 8:		Line 8:
	== Motivation ==		== Motivation ==
	The bwCloud-OS [[Guide: Enterprise Resource Planning#Contract relationship bwCloud-OS\|negotiated only contracts with institutions (customers)]] but not with individual members (users). This is a crucial [[Guide: Charging\|difference compared to other known cloud providers]]. Further, there are several different types of sponsors (e.g., faculties, research projects) located at the institutes that need to be enhanced to manage the resources of sub-groups of their members (e.g., students of a faculty).		The bwCloud-OS [[Guide: Enterprise Resource Planning#Contract relationship bwCloud-OS\|negotiated only contracts with institutions (customers)]] but not with individual members (users). This is a crucial [[Guide: Charging\|difference compared to other known cloud providers]]. Further, there are several different types of sponsors (e.g., faculties, research projects) located at the institutes that need to be enhanced to manage the resources of sub-groups of their members (e.g., students of a faculty).

	~~=== Access Control ===~~
	For [[registration]] to the bwCloud-OS several [[Guide: Conditions of use\|Condition of use]] need to be fulfilled. By rolling out the [[Guide: Entitlement & Eligibility#Access Control\|access entitlement]] home organizations can manage by themselves who is allowed to access the bwCloud-OS.

	=== Automated resource provisioning ===		=== Automated resource provisioning ===
Line 18:		Line 15:

	=== Charging ===		=== Charging ===
	All ~~consumptions~~ within the bwCloud-OS, within projects, are [[Guide: Charging\|charged]]. ~~Hence, for each project, a customer is required, which differs from the user or owner.~~		All consumption within the bwCloud-OS, within projects, are [[Guide: Charging\|charged]]. Charging will be based on the projects [[Booking Units\|booking units]] (BEH) and will be addressed to the [[Projects and Quota\|project owner]]'s home organization.

	Charging will be based on the projects [[Booking Units\|booking units]] (BEH) and will be addressed to the [[Projects and Quota\|project owner]]'s home organization.

	=== Delegating resposibility ===		=== Delegating resposibility ===
Line 27:		Line 22:
	=== Reimbursement ===		=== Reimbursement ===
	Entitlements also help define who is financially responsible for producing BEH.		Entitlements also help define who is financially responsible for producing BEH.
	* Defining [[Guide: Entitlement & Eligibility#Cost centers\|cost centers]] to separate costs into [[Guide: Entitlement & Eligibility#Example eligibility 1\|different cost positions]], allowing institutions to reimburse the costs internally.		* Defining [[Guide: Entitlement & Eligibility#Cost centers\|cost centers]] to separate costs into [[Guide: Entitlement & Eligibility#Example eligibility 1\|different cost positions]], allowing institutions to reimburse the costs internally. With access to their internal data (e.g., from the local IdP), different eligibilities (e.g., with different cost centers) can be assigned.

	* bwCloud-OS will generate aggregated usage reports and invoices per institution—no individual billing.		* bwCloud-OS will generate aggregated usage reports and invoices per institution—no individual billing.

As1844 at 15:40, 27 February 2026

2026-02-27T15:40:25Z

← Older revision		Revision as of 15:40, 27 February 2026
Line 41:		Line 41:

	== Contract relationship bwCloud-OS ==		== 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.[[File:Compare cloud provider contracts v3.drawio.png\|thumb\|Contract relationship compared between bwCloud-OS and other IaaS providers\|center]]
	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.

As1844 at 15:39, 27 February 2026

2026-02-27T15:39:26Z

← Older revision		Revision as of 15:39, 27 February 2026
Line 7:		Line 7:

	== Motivation ==		== Motivation ==
	The bwCloud-OS negotiated only contracts with institutions (customers) but not with individual members (users). This is a crucial [[Guide: Charging\|difference compared to other known cloud providers]]. Further, there are several different types of sponsors (e.g., faculties, research projects) located at the institutes that need to be enhanced to manage the resources of sub-groups of their members (e.g., students of a faculty).		The bwCloud-OS [[Guide: Enterprise Resource Planning#Contract relationship bwCloud-OS\|negotiated only contracts with institutions (customers)]] but not with individual members (users). This is a crucial [[Guide: Charging\|difference compared to other known cloud providers]]. Further, there are several different types of sponsors (e.g., faculties, research projects) located at the institutes that need to be enhanced to manage the resources of sub-groups of their members (e.g., students of a faculty).

	=== Access Control ===		=== Access Control ===

As1844 at 15:22, 27 February 2026

2026-02-27T15:22:22Z

← Older revision		Revision as of 15:22, 27 February 2026
Line 39:		Line 39:
	=== Central eligibility platform ===		=== Central eligibility platform ===
	The gimmic with the eligibility enhances (later) the bwCloud-OS local support to manage quota privileges within the bwCloud-OS environment. Such a [[Guide: REST-API for accounting and resource management#Eligibility rules\|central service]] could simplify local processes within the customers.		The gimmic with the eligibility enhances (later) the bwCloud-OS local support to manage quota privileges within the bwCloud-OS environment. Such a [[Guide: REST-API for accounting and resource management#Eligibility rules\|central service]] could simplify local processes within the customers.

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

As1844 at 15:21, 27 February 2026

2026-02-27T15:21:04Z

← Older revision		Revision as of 15:21, 27 February 2026
Line 1:		Line 1:
	~~__TOC__~~

	➡️ '''To the''' '''[[Guide: ERP-API\|ERP-API]].'''		➡️ '''To the''' '''[[Guide: ERP-API\|ERP-API]].'''

As1844 at 15:20, 27 February 2026

2026-02-27T15:20:49Z

← Older revision		Revision as of 15:20, 27 February 2026
Line 1:		Line 1:
			__TOC__

			➡️ '''To the''' '''[[Guide: ERP-API\|ERP-API]].'''

	The bwCloud-OS provides an [[Guide: ERP-API\|ERP with a RESTful API]] that allows our customers to overview and manage the accounting data and resources of their members. Mainly, this means to manage [[Guide: Entitlement & Eligibility\|entitlements and eligibilities]].		The bwCloud-OS provides an [[Guide: ERP-API\|ERP with a RESTful API]] that allows our customers to overview and manage the accounting data and resources of their members. Mainly, this means to manage [[Guide: Entitlement & Eligibility\|entitlements and eligibilities]].

	__TOC__		__TOC__

	~~➡️ '''To the''' '''[[Guide: ERP-API\|ERP-API]].'''~~

	== Motivation ==		== Motivation ==