Utilization dimensions

Utilization Graphs are shown broken down according to different dimensions. These are the criteria according to which the bars (or values) are divided.

This can be, for example, by project leader, by industry, by project type, etc. But you can also define any of your own dimensions, such as Verkauft/Offeriert,  Produktiv/Unproduktiv etc.

Utilization dimensions are defined in the folder Settings > Resource planning > Utilization dimensions:

Own class / opposite side

The load dimensions are always shown for the opposite side. This means:

A resource planning entry (so-called resource planning entry) ResourceLinks) always contains on one side a user (project user, PlanningWorker, AbstractWorker) and on the other side a project or a project phase, depending on the Planning Level .

The other side is always the other side. So if a utilization dimension is defined for the class project, it appears as a utilization graph on the user and vice versa.

By setting the check mark “Show in same class,” the utilization graph is also shown on the own class, which can be useful on lists of objects (e.g. the utilization dimension Bearbeiter on a team list).

Caution is advised when calculating the dimensions via Python if the option “Show on same class” is activated: a case distinction must be made here, so that a utilization dimension works on both the own and the counterclass.

Example Utilization dimension by keyword folder

In Vertec it is possible to define your own categories using keyword folders and to assign entries to these categories. These can be e.g. locations, industries, skills etc.

The resource planning data can be grouped and summarized according to these categories by defining a utilization dimension.

In this example, we would like to evaluate the resource planning data by industry. For this purpose, there is a keyword folder projects by industry:

Now we create a new utilization dimension in the folder Settings > Resource planning > Utilization dimensions:

As calculation method we select Ordner.

A field keyword folder appears below, where buttons with the three dots can be used to select the desired keyword folder.

As a class we choose Projekt, because the folder keyword evaluates projects.

If we do not want to show the folder only on users (by default, the load dimension is shown on the opposite side, in our example, users (AbstractWorker)), we put a check mark on Show on same class.

Now the evaluation will appear automatically on users and, because we have checked the box, on projects:

For the absolute numbers, the graph can also be exported to Excel.

Calculation of load dimensions via Python

The most extensive control over the calculation of a load graph allows the calculation method via Python.

The calculation is carried out by a UtilizationProvider Class that defines the following methods:

Example of a provider that generates a utilization graph according to productive/unproductive (Planning Level Project ):

class ProdInternalUtilizationProvider(object):
    productive_label_text = vtcapp.translate('label_productive')
    internal_label_text = vtcapp.translate('label_internal')

    def initialize(self, entries, start, end, subscriber):
        self.provider = vtcplanningcore.ResourcePlanningProvider(
            entries, start, end)
        self.entries_are_workers = vtcplanning.is_abstractworker(entries)

        if self.entries_are_workers:
            self.projects = self.provider.get_otherside_entries(subscriber)
        else:
            self.projects = entries

    def get_series_properties(self):
        prod_series = {
            'caption': self.productive_label_text,
            'orderIdx': 1,
            'color': 'clDarkRed',
        }
        internal_series = {
            'caption': self.internal_label_text,
            'orderIdx': 2,
            'color': 'clLightRed',
        }
        return [internal_series, prod_series]

    def generate(self, startdate, enddate, subscriber):
        """ Generates a list of series. Each series is identified by
        its name in the return value """
        for project in self.projects:
            if self.entries_are_workers:
                planned_minutes = self.provider.get_planned_minutes_aggregated(
                    None, project, startdate, None, subscriber)
            else:
                planned_minutes = self.provider.get_planned_minutes_aggregated(
                    project, None, startdate, None, subscriber)

            # self.evalocl subscribes implicitly
            if self.evalocl("typ.produktiv", project):
                yield (self.productive_label_text, planned_minutes)
            else:
                yield (self.internal_label_text, planned_minutes)

The class must be defined in a script module. On the definition of the load dimension, it is then <Modulname>.<Klassenname> referenced.

Supplied load dimensions

The following load dimensions are supplied by Vertec as standard:

• Projects (for class) Projekt)
• Project types (for class Projekt)
• User (for class Projektbearbeiter)
• User levels (for class Projektbearbeiter)
• Project phase status (for class Projektphase)