### Feedback:

_Capacity planning is based on different layers and presupposes the ability to define and manage weekly working capacity per user_

Begin of the deletion Without claiming to be exhaustive, three levels are highlighted as examples:

End of the deletion * **Generic resources** similar to op’s placeholder users to visualize needed experts or non-human resources while planning Begin of the insertion

End of the insertion Begin of the deletion

End of the deletion * Begin of the insertionWhen it comes to non-human resources, it is essential to to have numerical limitations of every resource that can be assigned, analog to personal users.

* End of the insertion **Group resources** which are based on grouped users and their merged working capacity, to identify available capacity before assigning
Ideally based on user groups so that LDAP group synchronisation can be utilised

* **User resources** which are based on its individual working capacity per week, Begin of the insertionlineary or dynamicallyEnd of the insertion distributed over Begin of the insertiondays.End of the insertion Begin of the deletion daysEnd of the deletion

* Begin of the insertionRecurringEnd of the insertion Begin of the deletion RepetitiveEnd of the deletion tasks can build a „background noise“, project works cover the remaining capacity

* Unfavourable: Low or excessive utilisation

* Ideal: Medium to high utilisation Begin of the insertion



Scenario Planning ("Draft Mode" / "What-if" Mode):

* Introduction of a "Draft Mode" for resource planningEnd of the insertion Begin of the deletion


_When it comesEnd of the deletion to Begin of the insertionconduct simulations (e.g., planning scenarios without direct impact on ongoing projects) without real impact on productive data before role based approval



Visualization of Utilization:

* Visualization of utilization data, staggered by projects, based on current data or in case of "What if" scenarios (see above)



Resource requests vs. assignments

* Distinction between requested and assigned resources (e.g., use of placeholder users in resource management).

* Clearly defined process: One personEnd of the insertion Begin of the deletion non-human resources, itEnd of the deletion is Begin of the insertionresponsible for approving requests, another makes the request, it couldEnd of the insertion Begin of the deletion essential toEnd of the deletion be Begin of the insertionhelpfulEnd of the insertion Begin of the deletion ableEnd of the deletion to Begin of the insertionmap these information via LDAPEnd of the insertion Begin of the deletion take limitations into accountEnd of the deletion in Begin of the insertionbigger organisations



Resources on Parent Work Packages:

* Resource allocation on parent work packages (not just at the lowest level)



Daily Business and Availability Factor:

* Solution for resources in daily business: IntroductionEnd of the insertion Begin of the deletion planning. A machine cannot divide itself._


**ContextEnd of the deletion of Begin of the insertionan availability factor to map capacities.

* Short-term absences (vacation, sickness): Clarification on how to adjust existing project plans.



Extending baseline comparison:End of the insertion Begin of the deletion user:**End of the deletion

* Begin of the insertionMultiple data points for comparisons



Write Access for Custom Fields especially in case of estimated work:

* Restrict write access for custom fields, but make them available for specific roles.


<br>

Context of user:

* End of the insertion [ ] Non-user
* [ ] Uses Community Edition
* [x] Tests OpenProject Enterprise
* [ ] Existing customer
* [ ] Enterprise Cloud
* Begin of the insertion[x]End of the insertion Begin of the deletion [ ]End of the deletion Enterprise on-prem
* [ ] BIM Cloud
* [ ] BIM on-prem

**Link to Odoo (if applicable)**

* [https://helpdesk.openproject.org/web#id=29765&amp;menu\_id=200&amp;cids=1&amp;action=300&amp;model=crm.lead&amp;view\_type=form](https://helpdesk.openproject.org/web#id=29765&menu_id=200&cids=1&action=300&model=crm.lead&view_type=form) Begin of the deletion

* Decision maker has rated this priority as high and decisive (for that reason, I chose to set it as high)End of the deletion