Resource Planning

If you have licensed the resource planning module and have the necessary user User Rights , the resource planning icon is available to you in the Navigation View :

This is active when resource planning is potentially possible for the up-to-date selected object.

Clicking on it opens the resource planning:

1	Button : Bar to call up the different views that are defined. Here in the example they are grouped into three groups. How the views are defined and grouped is explained further down .
2	The Period Picker : This allows the selection of the displayed time period in the following ways: Direct selection of start and end interval via date picker Move the displayed period to the left or right Extend the displayed period to the left or right by an interval The default display is based on the System Settings > Resource Planning : Start of the planning period Quantity of planning intervals If the period is changed, it will remain the same when switching to other views until Vertec is closed. Exception: Views that are already open in other tabs will keep their period. When restarting, the period is displayed again according to the system settings. Pivot tables are treated separately from timesheets and charts. A period change in the pivot table does not affect timesheets and vice versa.
3	The actual resource view for planning and evaluating resource planning data. The different types of views are explained further down . On all views, the corresponding numbers can be displayed with the button Als Excel exportieren exported to Excel.

Basic settings

In the System settings in the Resource planning section, you can make basic settings for resource planning. In particular, you can define whether you plan for projects or project phases and set the planning interval (day, week, month). Detailed information is described in the article System Settings Resource Planning .

The different types of views

The buttons open the different Resource Planning Views . These are defined and can be called up here.

Depending on the type of view, the button receives a corresponding icon.

Timetable	In this view, the planning data can be entered: Using the Star Line it is possible to add new projects (or phases or users, depending on the list) for planning. To ensure that a planning list that starts on a new interval (e.g. up-to-date month) is not completely empty, row objects that have planning data in the interval before the specified start date are also displayed. The timesheet has its own list settings, which can also be configured as usual. These settings have also been extensively expanded with List Controllers and Custom Renderers . Set or remove budgeted values In each (writable) row of the timesheet there is a button with which planned values can be set or removed: This allows budgeted values to be set for a combination of user – project/phase: User and project (or project phase) are automatically calculated from the corresponding resource list. The time period applies the values of the up-to-date list, but can still be adjusted. Percentage of free capacity This allows the user’s available time to be distributed linearly over the time period. The available time is the remaining availability, i.e. all the user’s not yet scheduled times. At 100%, the total available time is used, otherwise the corresponding percentage is used. Set Value Here a value can be entered manually. The value must be entered in relation to the planning interval, i.e. per day, week or month. The specified value is entered once for each interval in the selected period. The fixed value is entered regardless of how much standard time is available. This can lead to overbooking, which can be desired for special operations such as weekends. In addition, overbooking is an important benefit of resource planning – overbooking indicates bottlenecks that need to be resolved in a management process. Remove budgeted values Removes all planning data of this user-project/phase combination in the specified time period.
Pivot table	Based on a list of entries (user, project, or phase), a resource planning pivot table can be displayed. The pivot table shows the entries as rows and the planned opposite entries as columns. The PivotTable can also be mirrored, in which case it shows the entries as columns and the planned opposite entries as rows. The advantage of the mirrored pivot table is that new entries can be added via Star Line in order to capture planning data on them: A single planning interval is always set as the interval for pivot tables. Like the time table, the pivot table has its own list settings, which can be configured as usual.
Capacity graph	The capacity graph is a simplified graphical representation of the planned data with focus on the detection of free capacity or overbooking. The details of the planning (projects, phases) are not displayed. A capacity graph is only useful on the basis of users or lists of users, since it is based on the capacity data (standard hours). Again, if you hover the mouse over a segment, the detailed quantity of hours is shown:  The capacities of users are calculated as follows: Gross capacity: Available working time before taking into account absences (vacation, sickness, compensation), but including taking into account absences of type Frei(e.g. holidays). Net Capacity: Available working time after accounting for all absences. If a Adjusted net capacity is specified in the resource planning system settings, this percentage is used to calculate.
Utilization graph	A utilization graph displays planning data as a stacked bar graph: A bar is displayed for each time interval. If you hover the mouse over a segment, additional values are shown in a tooltip: User-based utilization graphs also show the capacity of the displayed user or team as a line. Starting with version 6.7.0.5, a third line with Adjusted net capacity net capacity can be displayed next to the gross and net capacity line. The individual segments of a bar typically correspond to the objects on which it was planned, but this view can be further configured by defining Utilization Dimensions .

Sum tables (read-only)

Time tables and pivot tables can also be shown as total tables. This is useful on a team container, for example, to show an overview of all planned totals of projects.

In this case, the tables are not writable, since the value in the cell is composed of several objects, i.e. summed.

Sum tables can be identified in the resource view by the fact that they have a sum symbol in the icon and are grouped separately:

A number of summary tables are included by default. For the complete list, see the included resource planning views section. For creating custom summary tables, there are a number of included List Controllers .

The planning editor

Since Vertec 6.6 there is a planning editor (PlanningWorker This can be used in resource planning like a user and serves as a placeholder for planning on a skill, a not yet employed or defined employee, etc.

Scheduling editors have a capacity (standard hour) of 0 and have a name, an abbreviation and the ability to be set to inactive:

Planning editors are entered under root data > planning editors.

Example

For example, a project leader in a civil engineering office plans not individual draftsmen directly, but a draftsman/team planning editor. The team leader then allocates the draftsmen to the respective projects and posts the planned values from the team planning editor to the respective user.

Since scheduling agents have a standard time = 0, for example, capacity and utilization can be compared in a team, even if it has assigned scheduling agents.

Show planning editors and project editors in the same lists

The basic class of project editors and planning editors is the AbstractWorker. If you want to be able to enter both in the same folder, make sure that you only show list columns that apply to both types. These are the members:

• Name (name)
• Active (aktiv)
• Abbreviations (kuerzel)
• Remarks (bemerkung)
• Icon Index (iconindex)

URL Support for resource planning views

The Vertec Breadcrumb url is also available in the resource planning views:

It can be copied and sent using the usual buttons.

The path of a resource planning URL begins with res-view. It represents the object selected in the tree and has the following parameters:

• viewtype=<id> for the Resource Planning Views
• dimension=<id> for the Utilization Dimensions

Resource planning views as favorites

The resource planning views can also be saved as Favorites . These are displayed when invoked with all parameters (see above). Resource planning views saved as favorites are given a designation according to the pattern Node (RP): Displayname, i.e. for example Projekt (RP): Bearbeiter. To identify the resource planning views favorites at a glance:

Resource planning views in history

On the other hand, no parameters are saved in the History . Therefore, it is only possible to navigate to the specific resource planning view. The corresponding button for the view must then be manually pressed again.

User rights for resource planning

The following user rights are relevant for querying resource planning data:

It became a new right type Ressourcenplanung introduced:

This is added to the Standard User group by default when the resource planning module is licensed and controls whether the resource planning navigation button is visible to the logged-in user.

In the resource planning itself, the access authorization to a plan data cell is based on the read and write rights on the attributes of the resource planning entries (Resourcelinks) of the participating business objects (user, project, phase), that is the actual planning data of these combinations. The access rights of both sides are linked with OR, i.e. the access right to one page is sufficient.

The default user rights are as follows:

• Users have read and write access to Resourcelinks of itself.
• Users usually do not have access to Resourcelinks by other users, except:
  • All users have access to Planning Editor and thus also to their Resourcelinks.
  • Team leaders with Team Leader Right have read and write access to Resourcelinks from users on their team.
  • Project leaders have read and write access to the projects on which they have Project Leader Legal .
  • Project supervisors have general read and write access.

The resource planning table views implement authorization checking according to the logic described above as follows:

• If only read permission exists, the cell is displayed but is not writable.
• If read and write permission exists, the cell is writable.
• If not read right on ALL Resourcelinks members of projects or phases in the list, then the resource planning view is not shown (as otherwise conclusions could still be drawn about the planning).

Graphic Art (utilization and capacity graphs) are only displayed if the logged-in user has access to the displayed planning data. Otherwise, instead of the graph, a display “No read permission to budgeted value. To read the budgeted values, you need read permission for at least one linked user, project or phase object”.

In the planning mode, Editor Phase Link , analogous logic is applied based on the project and user. Instead of Resourcelink Attributes, in this case, the user’s right on the attributes bearbeiterPhasen checked by project user and project phase.

Plan for Editor-Phase Assignments

As an alternative to normal resource planning, it is also possible to plan for the assignment of users to the phases (so-called Editor Phase Links ). To do this, the Plug-in: resource planning with worker assignments must be imported.

Python methods for resource planning

The following Python methods are available for resource planning, with which resource plan values can be set via Python code:

• On AbstractWorker, project user and Planningworker there is the method setresourceplanvalue(project_or_phase, date, value)
• On project and phase there is the method setresourceplanvalue(worker, date, value)

For more information about the new Python methods, see Vertec Python Features .

OCL variables for resource planning

For resource planning, in addition to the available Ocl variables , the following are also available:

These are available in Resource Planning Views and the corresponding List Controllers as well as in the Custom Renderers .

To make it easy to use OCL variables in list controllers and custom renderers, both have the self.evalocl() method available, which uses this specific OCL evaluator. The mentioned OCL variables are defined only in this evaluator (i.e. vtcapp.evalocl() does not know them).

The existing container variables varContainer and varParent contain in the case of a single object null.