Tabsters Help Center

Point of attention : Access to the Budget tab of the various elements in Tabsters is based on access rights to the module granted by key users in your environment, from the Administration tab tab of Tabsters.
If you do not have access rights to this module, you will not be able to access project budget data.

‍

The Tabsters Budget tab is accessible from the global project portfolio , project portfolio, global project, project, global workpackage , workpackage, entity and some custom field maps.

‍

3 types of views are available in the budget tab:

• The table view, to enable you to enter and arbitrate your budget data.
  The table view of the budget tab is divided into two parts.
  
  On the left of the screen you'll find a graphic indicator, the budget donut, which is a graphic element enabling you to see the budget amount, overallburned and overallworkload .
  
  On the right-hand side of the screen, you'll find the various columns available in the budget tab, which can be configured by choosing the columns.
  ‍
  Also at the top of the tab, you'll find the usual icons allowing you to apply sorting & filters, but also an additional icon in the form of a list, allowing you to choose whether you want the budget donut to be displayed or not.
  This setting can also be saved in your view.
  ‍
• The pivot view, and the graphical view to enable you to set up customized graphs relating to your budget data for your Dashboard or PPT exports.

In the table section of your budget tab, your budget data is grouped by year, like a TCD.

This display gives you a quick & annualized view of your budgets.

The budget data for a budget line can thus be entered for several years without having to break down your budget envelope into different lines for each year.
‍

All native fields corresponding to numerical budget data(Budget amount, Budget in MD, workload / burned additional €, etc.) are only positioned below the years displayed in the view.
‍
The other fields native to the budget tab, such as Name, Validated, Project, entityetc. are positioned outside the year groupings in the table.

The order in which fields are displayed in the view is also affected by the order in which you display numerical budget fields.
Numerical budget fields will always be grouped together regardless of the presence of other non-numerical fields in the column selection order, as they are automatically positioned below the years.

The choice of years displayed in your table is manual & user-configurable.

To choose which years to display, simply go to the column selection.

In the column selection pop-up, you'll find a list of the different years available on the right-hand side of the pop-up.
To add a year to your view, simply click on the empty box to the left of its label.
If you wish to hide one of the years displayed, uncheck its box by clicking on its blue tick.

A Global option is also available in the list.

This option allows you to obtain the global sum of your various budget data, by summing the values for each year (even those not displayed in the view) for each budget field.

Once you have completed your settings, click on validate to apply your changes to the view.

The different years you have chosen to display will then appear in your view.

The global part is grayed out because its fields cannot be edited directly.

To modify your budget values, edit the values for the various years.
The sum of the global values will then be updated automatically.

‍‍TheBudget in Tabsters is divided around 3 pieces of data, the Budget, the workload (or forecast) and the burned.

Numerous fields are available by default on the budget tab in Tabsters, in addition to custom fields that you can create and position at budget level.

‍

Budget fields :

‍

• Budget amount:
  
  Defines the budget amount in € for the budget line.
  ‍Thisvalue can be edited by the user.
  ‍
• Budget in MD :
  
  Defines the amount of the budget envelope in MD for the budget line, if monitoring is carried out in number of days.
  This value can be edited by the user.

• Budget [Reference]:
  
  Keeps a 'snapshot' of the initial budget amount in €, this value is initialized with the first entry made in the Budget Amount field.
  This value can be edited by the user.‍
  ‍
• MD [Reference]:
  
  Keeps a picture of your initial MD budget, this value is initialized with the first entry made in the MD Budget field.
  This value can be edited by the user.
  ‍
• ‍Allocated(MD):
  
  Corresponds to the sum of the MD budgets of child lines N-1, aggregated at level N within the framework of a budget hierarchy.
  In the absence of a budget hierarchy, this value corresponds to the value of the line's MD budget.
  This value cannot be edited by the user.
  ‍

• Allocated € :
  
  Corresponds to the sum of the budget Amounts of child lines N-1, aggregated at level N within the framework of a budget hierarchy.
  In the absence of a budget hierarchy, this value corresponds to the value of the budget amount of the line.
  This value is not editable by the user.
  ‍
• Unallocated MD :
  
  Corresponds to the delta of the sum of the MD Budget of child lines N-1 in relation to the MD Budget defined at level N within a hierarchical budget structure.
  This value is not editable by the user.
  ‍
• Unallocated €:
  
  Corresponds to the delta of the sum of the Budget Amounts of child lines N-1 in relation to the Budget Amount defined at level N within a hierarchical budget structure.
  ‍Thisvalue is editable by the user.

‍

workload fields :

‍

• workload :
  
  Corresponds to the sum of the MD Expenses defined in the roadmap, and automatically uploaded to the corresponding budget line.
  This field is bottom-up aggregated within a hierarchical budget structure.
  This value cannot be edited by the user.
  ‍
• workload € :
  
  Corresponds to the sum of the MD charges defined in the roadmap, multiplied by the daily cost of the resource assigned to the corresponding workload .
  This field is aggregated bottom-up within a hierarchical budget structure.
  This value is not editable by the user.
  ‍

• additionalworkload € :
  
  Corresponds to a workload in € entered directly in the budget screen. This field allows you to add additional workload to be taken into account in budget calculations, in the event that an additional workload outside your Roadmap needs to be added.
  This field aggregates bottom-up within a hierarchical budget structure.
  This value can be edited by the user.
  ‍
• globalworkload € :
  
  Corresponds to the sum of the workload € and additional workload € values.
  This field is bottom-up aggregated within a hierarchical budget structure.
  This value is not editable by the user.
  ‍
• % workload :
  
  Corresponds to the ratio of the workload field and the Budget field in MD.
  This value cannot be edited by the user.
  ‍
• % workload €:
  
  Corresponds to the contribution of the global workload € field and the Budget amount field.
  ‍Thisvalue is not editable by the user.

‍

Fields related to burned :

‍

• burned :
  
  Corresponds to the sum of MD consumables defined in the roadmap and automatically brought up to the level of the corresponding budget line.
  This field is aggregated bottom-up within the framework of a hierarchical budget structure.
  This value cannot be edited by the user.
  ‍
• burned € :
  
  Corresponds to the sum of the consumables defined in the roadmap, multiplied by the daily cost of the resource assigned to the corresponding burned .
  This field is aggregated bottom-up within a hierarchical budget structure.
  This value is not editable by the user.
  ‍
• burned additional € :
  
  Corresponds to a burned in € directly entered in the budget screen. This field allows you to add additional burned to be taken into account in budget calculations, in the event that an additional expense outside your Roadmap is to be added.
  This value can be edited by the user.
  ‍
• globalburned € :
  
  Corresponds to the sum of the burned € and workload additionnelle € values.
  This field is bottom-up aggregated as part of a hierarchical budget structure.
  This value cannot be modified by the user.
  ‍
• % burned :
  
  Corresponds to the ratio of the burned field to the Budget field in MD.
  This value cannot be edited by the user.
  ‍
• % burned € :
  
  Corresponds to the ratio of the burned global € field to the Budget amount field.
  This value cannot be edited by the user.

In the Tableau display of your budget tab, you'll find the donut budget visual indicator on the left-hand side of your screen.

This visual indicator gives you a quick, visual overview of your overall budget data on the tab.

1. The budget donut is made up of the various budget values that are aggregated at the level of your budget tab.
   ‍
   The donut display is made up of the donut itself, as well as the numerical indicator of the percentage of overall budget that has been burned for the moment.
   
   The display and its percentage are updated in real time, based on modifications impacting your budget lines.
   ‍
2. Below the donut, you'll find the different budget values on which the donut display is based.
   
   The entire donut (gray area) is thus based on theoverall € budget for the level you're at.
   
   The light blue area of the donut corresponds to theoverall € budget workload that has been assigned.
   
   Finally, the dark blue part corresponds to the overall € amount that has been consumed so far (the amount on which the donut's percentage of the budget is based, compared with the overall budget).
   
   Below, indicators of total € amounts allocated & not allocated are also available.
   ‍
3. This icon allows you to show or hide the budget donut to adapt the display to your needs;
   This setting is saved in your view parameters when you save your view.
   ‍
4. The jogwheel allows you to configure the display of your budget donut.
   
   By default, the budget donut displays data for budget €, burned €, workload €, Allocated & Non-allocated €.
   
   By clicking on the jogwheel, you can access the donut configuration pop-up, which allows you to define the fields on which you wish to base the display of the budget donut.

‍

In the budgets section, you'll find the possibility of using the various custom fields that have been added to the application.

‍

• Classic' custom fields, such as Axis, Date, Resource, etc., work in the same way as the other Tabsters tabs.
  Adding a custom field to your view will allow you to fill in the required information on each line, regardless of the multiperiodicity chosen.
  ‍
• Vector custom fields are used to create numerical custom fields that are positioned at the selected multi-periodicity level (i.e. one cell per year present in the view for this field).
  This allows you to define different numerical values for each year, with the total value automatically aggregated at the 'global' level.

To facilitate access to budget data and to enable data centralization, some budget data is also available outside the Budget tab.
‍

Roadmap :

‍

Several budget fields are available in the Roadmap tab, such as Budget amount, Budget in MD, % workload € and % burned €.

These fields will be automatically consolidated from the budget data entered in the budget tab, in the corresponding Roadmap lines.

In addition to the budget tab fields mentioned above, the fields Current value €, Earned value € & Cost variance are also available in the Roadmap.
‍

• The Earned Value € field, corresponds to the sum of MD consumptionof tasks with Completed status, multiplied by the daily rate of the resource assigned to the corresponding task.
  This field is aggregated bottom-up within a hierarchical project structure.
  ‍
• The Current value € field corresponds to the sum of