Guide: Enterprise Resource Planning: Difference between revisions
No edit summary |
No edit summary |
||
| 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). | ||
=== Automated resource provisioning === | === Automated resource provisioning === | ||
| Line 18: | Line 15: | ||
=== Charging === | === Charging === | ||
All | 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. | ||
Revision as of 15:52, 27 February 2026
➡️ To the ERP-API.
The bwCloud-OS provides an 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 entitlements and eligibilities.
Motivation
The bwCloud-OS negotiated only contracts with institutions (customers) but not with individual members (users). This is a crucial 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
Registration is streamlined through entitlements:
- Entitlements are automatically evaluated during registration.
- Users receive immediate access and resources (project quota) once their entitlement is confirmed. No manual activation is required.
Charging
All consumption within the bwCloud-OS, within projects, are charged. Charging will be based on the projects booking units (BEH) and will be addressed to the project owner's home organization.
Delegating resposibility
The institutes can define an internal process so their members can set entitlements in the home IdP.
Reimbursement
Entitlements also help define who is financially responsible for producing BEH.
- Defining cost centers to separate costs into 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.
Budget
Sometimes resources should only be consumed up to a certain level or amount of time.
- Constraints can be used to manage the valid period for eligibility.
- After reaching an eligibility constraint, no more costs can be produced within the associated project.
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 central service could simplify local processes within the customers.
Contract relationship bwCloud-OS
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.
