Wishlist

In deployment planning, the display of the workload should be freely adjustable by the user — either in FTE or in hours. When choosing the hour display, the actual available hours per employee should be displayed, automatically calculated correctly on the basis of full-time or part-time. This eliminates the need to manually convert FTE into hours and makes deployment planning much clearer and faster.

If an MA hasn't written any hours in a project for a certain period of time (e.g. 3-6 months), then it should be automatically removed. The option would be great.

It should be possible to eject deployment planning and/or deployment planning views (projects, employees, next week, project employees) like the rest of the lists.

After the deployment planning has been updated, the time periods can no longer be edited in the Projects—Employees view. This is a central function for our team, as we use this view in weekly capacity meetings and adjust the time periods there. In this context, it must be possible to enter and edit time periods quickly. We ask that this be made possible again.

A direct link from “Own projects” in the personal area to the deployment planning of the respective projects in the office sector would make our work significantly easier. In our office, the team contributes the capacities themselves in coordination with the project management. This supports your own organization and reduces coordination costs! Ideally, the periods and capacities could be entered and processed directly in the “Own Projects” overview.

In the overviews of (new) deployment planning (e.g. projects/employee deployment plan), the workload of the MA is displayed using a color code. This is even more important with the new EPL, as the planned capacity is shown here in FTE. Here, even 0.5 FTE for a part-time person can mean 100% utilization. projo colors a load of 100% as green. Omissions below 100% remain green but become brighter/less saturated. Low utilization above 100% is colored yellow. Size replans red. Very large dark red. We have the following comments about this: • Legend Introduction of a legend on all pages in which projo uses colored backgrounds to transport information • Tolerance (maybe adjustable) when Projo changes the color from green (100% planned) to yellow. (It seems that this is already happening at 100.01% in the new EP. In sharpness, however, Projo cannot automatically adjust deployment planning at all and even manual adjustment will hardly be successful with performance-specific planning) • Color/color spectrum. This may be a very personal perception, but planned workloads of 90%-100% are unproblematical in my opinion/can happen. However, lower workloads (certainly below 75%) are problematic. I personally find blue colors quite appropriate there (air...;))

In Projo, contract deadlines can be defined in the overview tab. It would be very helpful for planning if these were displayed in deployment planning.

In the New EP, it should also be possible, as before, to plan capacities in services whose order amount has already been used up. As before, personnel costs should be distributed in proportion to the order amounts for parallel services (unless MA is planned with different sub-FTEs per service). Example in the appendix: January-June, the costs for special services (with previous budget), but not to LP5 (with used up order amount), although capacity is planned there. Starting in July, after the end of the special services, costs will be planned in the LP5. This distorts planning/controlling of individual services. As with the old EP, we ask you to enable capacity planning regardless of remaining order amounts. This is necessary for planning and controlling. Thank you!

Would you please add a 2nd decimal place to the unit “FTE” and correctly represent roundings or additions (see screenshots: FTE_1 sum of FTEs from Katja and Vanessa wrong and Vanessa (planned with 0.9 FTE on 2 parallel work phases)) actually only planned with 0.45 FTE, not 0.5 FTE///FTE_2: Frank 10 hours/week = 0.25 FTE, but presented with 0.3 FTE - > both raise unnecessary questions...).

In deployment planning, it is easiest for me to be able to distribute the resource 100% of employee A and 100% of employee B to my projects. The fact that employee A works 40 hours a week and employee B 32 hours a week is important during evaluation, but leads to arithmetic acrobatics when entering data. It would be nice if you could change the percentages based on working time from relative (to individual working time) to absolute (relative to full time) with a counter and always see in deployment planning what an employee's working time is in general and in the respective week (due to vacation, illness...).