Glossary: Project and portfolio management

You can record and view your own absences, as well as view the absences of your department colleagues.
See also:
Vacation and Absence,
Absence (Employee)
Absence of the Department
Absence (Department)
Absence (Resource)

In PLANTA, you can assign different permissions to users. There are two types of access rights, which are controlled independently of one another. Access rights for modules or menu items determine which modules or menu items a user is allowed to use. Access rights for objects (planning objects, resources, etc.) determine which objects a user can access.
See also:

Modification Rights
User Rights

Costs/effort, and budgets are imported from SAP to PLANTA and vice versa using account assignment elements.
See also:
Alternative Structures entry,
SAP WBS Elements entry,
SAP WBS module

Is the last released status report.
See also:
Status Report entry

In PLANTA, a distinction is made between actual, remaining, and total values for various objects (such as expenses, costs, etc.) and at multiple levels (project, task, etc.). The Actual value is the actually incurred value.
See also:
Actual, remaining, total values for costs and effort,
Actual, remaining, total values for project durations,
Actual, remaining, total values for task durations

Adaptive Cards are JSON-based, adjustable interfaces that are used in PLANTA for the exchange of data and information between the PLANTA system and external applications.
See also:
Adaptive Cards,
Configure Adaptive Cards,
Adaptive Cards Customizer

For agile planning, PLANTA offers the agile component pulse. It can be combined with the traditional PLANTA Project component and thus be used as PLANTA Hybrid for both agile and traditional project management.
See also:
Documentation for agile component,
Hybrid entry

In PLANTA, a project structure can be imported, edited, or created manually from an external system (e.g. SAP) via a PLANTA Standard interface.
See also:
Account Assignment Elements,
SAP WBS Elements,
PLANTA project Standard Integrations,
SAP WBS,

In PLANTA, the approval/release process is used in various areas, such as status reports, working with process models, budget planning, resource planning, etc.
See also:
Release Status Report,
Approve Phase in the Process Status module,
Release Budget (Period) in the Portfolio,
Approve Project Budgets
Cancel Approval per Budget Period

Resource Requests/Approval

A baseline is a status report in which the approved and adopted planning is displayed and which is regarded as a reference during the course of a project.
See also:
Create Baseline Report,
Status Report entry

Basic load refers to a recurring activity or one that continues throughout the entire duration of a project, e.g.: project management, phone calls, meetings, etc. PLANTA offers various options for planning basic load.
See also:
Plan Basic Load

Basic load projects are projects that consist exclusively of basic load tasks and on which only basic load is posted. This is one of multiple options for planning basic load.
See also:
Basic Load entry

The Budget module is a central board for the planning and management of project budgets and costs. In addition, at the portfolio level, you can plan and manage budgets in the corresponding module.
See also:
Costs and budget planning in PLANTA project ,
Project Budgeting,
Portfolio Budgeting

PLANTA supports the use of several calendars. To create a calendar, you need to have made decisions and gathered information about future planning.
See also:
Calendar,
Calendar Parameters
Basic Calendar Period Parameters modules

In program change management, a change request is a formalized call for the alteration of the properties of a particular product feature. (Source: Wikipedia).
See also:
Change Request ,
Change Request Parameter

See:
Change Request entry

In PLANTA project you can create checklists for todo items.
See also:
Todo Items entry

See:
Presence entry

Conversion factors are required for the actual calculation of costs and effort. As a result, the resource effort (load) is converted into monetary values.
See also:
Conversion Factors module,
Costs, Budget, Benefits and Revenues module

Cost centers are organizational units in which costs are incurred. Depending on which area a resource that incurs costs belongs to, the corresponding cost center is loaded. This allows you to generate cost reports broken down by cost center.
See also:
Cost Centers module,
Allocate Costs to Cost Centers,
Cost Center Parameters

See:
Budget and Cost Planning in PLANTA project

In PLANTA, cost resources are a special type of resource whose costs are planned not in units of time but in currency.
See also:
Create Resources,
Resource Parameters
Post Costs module

In a cost trend analysis, the project's current status in terms of costs is compared with the data from the status reports.
See also:
Cost Trend Analyses module

Cost type groups are used to group cost types (outline cost scaling), which in turn are used to group costs (fine cost scaling). In the Budget module, budgets, costs, and effort is displayed summarized to the cost type groups.
See also:
Create and Edit Cost Type Groups,
Cost Type Group Parameters
Cost Types entry

Cost types are used to break down, summarize, and calculate costs. For each resource, a Default Cost Type is defined which is automatically adopted during resource assignment and can be changed per resource assignment or load if necessary.
See also:
Create and Assign Cost Types,
Cost Type Parameter

The critical path in a project consists of all the critical tasks in a task chain. Tasks are critical when they do not have a total float. In PLANTA, there may be critical tasks that are not on the critical path. This is because tasks, just like projects, can have target completion dates that automatically set the total float to 0.
See also:
Critical path parameter, Total float

PLANTA Customizer is a tool developed by PLANTA for customization/configuration of the PLANTA software application.
See also:
General Information on Customizer,
Customizer role

Customizer mode is a mode in which you can view and, if necessary, modify the structure of user modules, provided you have Customizer rights and access to Customizer menu items. If the requirements are met, you can switch from a module’s user mode to customizer mode by pressing CTRL + F3 (for individual data areas) or F9 (for the entire module).
See also:
User Mode entry,
Customizer Rights parameter

See:
Network Cycle entry

In PLANTA, a deep link is a hyperlink that leads directly to a specific subpage or piece of content within the PLANTA software.

See:
Deeplinks module,
Customize Deeplinks

See:
Progress entry

See:
Deviations entry

The Department Board is the resource manager's processing center. It contains important editing and information modules.
See also:

Department Board,
Role,Resource Manager in PLANTA project panel

See:
Resource Manager entry

See:
Resource Manager entry

The Dependencies module is one of three ways to map dependencies between projects in PLANTA project.
See also:
External Tasks and External Links

In PLANTA there are 2 types of deviations:

1. Deviations in the values of the same parameter across different plans, e.g., Budget in the current plan versus Budget in the baseline, and

2. Deviations between the values of different parameters, e.g. Total costs vs. Budget.

See also:
Deviations area in the Dashboard module,
Deviations module
Budget, Costs, and Revenues (Delta View) module
As well as the Deviation ... field in various modules

Several demo process models related to the DIN 69901/1-5 standard are included in the scope of supply of the PLANTA software.
See also:
Working with Process Models ,
Process Model Templates module

See:
PLANTA Online Help entry

In PLANTA, durations are considered at the project and task levels. A distinction is made between actual, planned, remaining, and total values.
See also:
Actual, Planned, Remaining Duration (Project),
Actual, Planned, Remaining Duration (Task),
Although durations exist at resource assignment level, they are not typically taken into account and are therefore mostly irrelevant.

This refers to the Earliest start and Earliest end parameters.
See also:
Earliest start (Project),
Earliest end (Project),
Earliest start (Task),
Earliest end (Task)

The earned value analysis or performance analysis serves to assess the process of projects.
(Source: Wikipedia)
See also:
Earned Value Analysis module ,
Earned Value Evaluations in the Module Info Board ,
EVA Project Parameter
EVA Task Resource Parameters
EVA Task Parameters

Effort means timeframes required to complete a project, process, or todo item. A distinction is made between actual, target, total, and remaining values. In PLANTA, resource effort spread across individual days are referred to as Loads.
See also:
Remaining, Actual, Total Effort (Project),
Remaining, Actual, Total Effort (Task),
Remaining, Actual, Total Effort (Resource Assignment),
Load entry

See:
PLANTA Employee role

The Employee Board is the project member's processing center. It provides an overview of the utilization of the employee and of the open items to be completed, process steps, etc.
See also:
Employee Board panel

The end date is the end date for projects, tasks, and resources. PLANTA distinguishes between the requested, actual, and calculated end date.
See also:
Requested/Calc./Actual end (Project),
Requested/Calc./Actual end (Task),
Requested/Calc./Actual end (Resource Assignment)

Error treatment allows you to identify the error source. Here, it depends on whether the PLANTA error type is already known and documented in the PLANTA online help, and whether a solution or workaround is available. If the error has not yet been documented, you can send a description of how to reproduce the error to the PLANTA Hotline. To resolve errors related to project and portfolio management, the Customizing component, or of a technical nature—such as those concerning the installation or update of PLANTA software—please refer to the relevant troubleshooting guides in the corresponding documentation sections.
See also:

Error Treatment,
Error Classification,
Known Issues (Project and Portfolio Management),
Known Issues (Customizing),
Known Issues (Technology/Installation)

In PLANTA, the External links function is one of the three options for mapping dependencies between projects. External links connect the activities of different projects.
See also:
Dependencies and External Tasks entries

In PLANTA, the External tasks function is one of the three options for mapping dependencies between projects. This function allows you to have tasks of another project displayed in the schedule of another project.
See also:
Dependencies and External Link entries

Favorites are all planning objects marked with a yellow star symbol. They are listed in the user menu.
See also:
User Menu

See:
Historization entry

When calculating a schedule, the float is determined at each project level (project, activity, resource assignment) based on the combination of certain factors (links, duration, preferred dates, etc.). In the Gantt chart, it is represented by green arrows.
See also:
Gantt chart legend in the Schedule module,
Date, Resource, and Cost Planning

In PLANTA, employees have the option to provide an estimate of the remaining effort if they believe it differs from the calculated amount.
See also:
Progress module,

Send Forecast module,
Forecast module on resource assignment

The functional ID of a project (idea, proposal, program) and of a task is generated automatically and, unlike the technical ID, can be changed at a later date.
See also:
Technical ID,
Functional Project ID,
Functional Task ID,
Change Functional ID of the Project

A Gantt chart is a graphical representation of a schedule below the scale.
See also:
Schedule,
Graphical Editing in Gantt Chart

In PLANTA, gates are master milestones. In addition to the standard display in the network diagram, these can also be shown on the horizontal time axis below the scale.
See also:
Schedule with Gatesproject parameter,
Milestone Overview module,
Task Define Task as Milestone/Master Milestone

A hammock task is a task that is characterized by recurring, project-related activities. This process continues throughout the entire duration of the project.
See also:
Hammock Task parameter on tasks

In PLANTA, historization refers to the process of saving changes to data tables and data fields.
See also:
Historization of data tables

See:
Historization,
Project History entry

In PLANTA you can define for each resource how many hours per day he or she is supposed to work. These hours are compared against the resource’s time recording.
See also:
Hours to Be Worked function

PLANTA Hybrid allows you to integrate the agile PLANTA component (pulse) with the traditional PLANTA Project component and synchronize data across both systems, enabling you to leverage the benefits of both agile and traditional project management in project planning and project control.
See also:
Introduction PLANTA Hybrid (traditional + agile)

An idea is the preliminary planning stage of a project. In this preliminary stage, projects are outlined.
See also:
Create New Idea,
Idea panel

In PLANTA, you can automatically send information via email to the persons in charge.
See also:
Send Info module

Each new subproject in a project structure automatically inherits the values of some parameters (upon creation) from its immediate parent project and the stakeholders from the main project of the project structure.

See also:
Subprojects module

PLANTA offers a universal interface that allows you to flexibly configure all standard interfaces in PLANTA using parameters or to create new interfaces.
See also:
Universal Interface

In PLANTA, risk management is realized in accordance with ISO 27001.
See also:
Risk Management entry

In business administration, a Key Performance Indicator (KPI) refers to metrics used to measure and/or determine progress or the degree of completion with respect to key objectives or critical success factors within an organization. (Source: Wikipedia)
See also:
Project Core Data module,
Program Core Data module,
Proposal Core Data module,
KPI Parameters

This refers to the Latest start and Latest end parameters.
See also:
Latest Start and Latest End on projects,
Latest Start and Latest End parameters on tasks

In PLANTA, liability is edited as part of cost planning in the Budget module.
See also:
Liability in the Budget module

Links represent dependencies between tasks.
See also:
Link tasks / Links,
Link Parameter

Loads are the effort incurred by the resources assigned to the task per period (date) Load records are either generated automatically after resource allocations have been made and the schedule has been calculated, or they can be entered manually when using the MAN load profile.
See also:
Schedule,
Load Parameter
Scheduling (Calculation of the Projects) module

Load Profiles entry

Load profiles control the distribution of the load on the resource over a specific period of time. These are defined by default for each resource in the Resource Data Sheet module (Default Load Profile field), are adopted as default values when a resource is assigned to an operation, and can be modified at the resource assignment level.
See also:
Load Profiles

Via the Locked (Project) or Task locked parameters you can completely lock time recording or restrict it via the Key date model parameter.
See also:
Time Recordingentry
Lock Time Recording

A main project is a parent project at the highest level of a project structure.
See also:
Structure Projects,
Subprojects

See:
Department Manager entry,
Multi-Project Manager entry,
Portfolio Manager entry,
Program Manager entry,
Project Manager entry,
Person Responsible for the Task entry

In order to be able to plan and control projects with PLANTA, you have to enter master data in the PLANTA system (basic data). Basic data are, e.g., personal data, users, resources, conversion factors, cost types, etc.
See also:
Create and Manage Master Data

In PLANTA, master milestones are milestones with greater importance than other milestones.
See also:
Milestone entry

The Microsoft Project interface allows you to import and export data to and from Microsoft Project.
See also:
PLANTA project and Microsoft Project,
Microsoft Project module

Milestones are events of particular importance, such as a topping-out ceremony when building a house. In PLANTA, a distinction is made between milestones and master milestones.
See also:
Define Task as Milestone/Master Milestone,
Milestones/Master Milestones module variant in the Schedule module,
Milestone Overview module,
Milestone parameter on tasks
Schedule with Gates on projects

In milestone trend analysis (MTA), the milestone or master milestone trend is calculated and displayed based on the status reports.
See also:
Configure Trend Analysis module,
Info Board module,
Schedule module,
Status Report module

In PLANTA project, model parameters are parameters that influence the calculation of schedules and costs as well as resource allocation. They are defined in the Model and Model Parameters module.
See also:
Planning Model Parameters
Date, Resource, and Cost Planning

Modification Rights refer to the permission to enter and edit/change data and possibly delete them. They are allocated explicitly by changing the settings of particular parameters.
See also:
Access Rights
User Rights

In PLANTA Portfolio Management, a multi-portfolio manager is a user who has the highest level of permissions in the portfolio area (i.e., the right to create new portfolios, delete portfolios, and view and edit portfolios). To do this, the respective person must have entry 2 (Multi-Portfolio Manager) in the Object rights parameter and the corresponding modules in the user menu (in the standard system, the Portfolio Management role).
See also:

Portfolio Management ,
User Rights,
Rights Management,
Form a Portfolio

The Multi-Project Board is the multi-project manager’s processing center. It includes various editing modules as well as overview modules that allow him to get a quick overview of his projects.
See also:
PLANTA Multi-Project Management role

In PLANTA, a multi-project manager is a user who has the highest permissions in the Project module, meaning the right to create new planning objects (of all types: projects, programs, ideas, initiatives), delete them and view and edit all data for all planning objects. To do this, the respective person must have entry 1 (Multi-Portfolio Manager) in the Object rights parameter and the corresponding modules in the user menu (in the standard system, these are the Multi-Project Management, PM Administration, and Program Management roles).
See also:
Multi-Project Management, PM Administration and Program Management roles in PLANTA project,
User Rights,
Rights Control

Net Present Value is the net capital value. Net present value is a financial metric used in dynamic investment analysis.
(Source: Wikipedia)
See also:
NPV parameter on projects

A network cycle occurs when no last task can be found within a network cycle in the calculation of a schedule.
See also:
Cycle Search module,
Network Cycle parameter on projects
Task with Cycle parameter on tasks

See:
Information entry

The PLANTA Online Help describes the PLANTA software’s standard system. It is available via https://help.planta.de/ .

See also:

About PLANTA’s Online Help

See:
Todo Items entry

Opportunity Management for Projects and Programs in PLANTA
See also:
Create and Edit Project Opportunities,
Create and Edit Program Opportunities,
Opportunity Parameters

An opportunity-based measure is a targeted action designed to capitalize on opportunities by increasing, optimizing, sharing or consciously accepting their probability of occurrence and/or gross profit level
See also:
Record Opportunity Measures,
Opportunity Measure Parameters

See:
Cost Center entry

In contrast to the Schedule module, the outline planning is carried out on a phase level and in person days in the Outline Plan module. In the standard system, outline planning is only available for proposals.
See also:
Outline Plan

Overhead cost projects are projects to which only overhead costs are posted. Unlike regular projects, these have posting type = 1 and are not planned like regular projects; instead, they are treated solely as time recording projects.
See also:
Overhead Cost Project,
Post Overhead Costs

Overhead costs are costs incurred due to, for example, vacation and/or sickness that cannot be posted on regular projects. To this end, special projects—referred to as overhead cost projects—are created in PLANTA, to which only overhead costs are posted.
See also:
Overhead Cost Project,
Post Overhead Costs

One period corresponds to one date. On this date, a resource can be scheduled, or leave or absence times can be entered for it.
See also:
Resource Data Sheet,
Resources module,
Availability module,
Start Period and End Periode on resources

are resources with Resource type = 1 (internal, external).
See also:
Resource Data Sheet

See:
Person Responsible for the Task entry

The person responsible for a task is defined in the Person responsible for the task field in the Schedule or Task module.
See also:
Person responsible for the task parameter on tasks

In PLANTA, a distinction is made between actual, remaining, and total values for various items (such as expenses, costs, etc.) and at multiple levels (project, task, etc.). The planned value is the initially planned value.
See also:
Actual, remaining, total values for costs and effort,
Actual, remaining, total values for project durations,
Actual, remaining, total values for task durations

See:
Deviations entry

The planning horizon is one of the basic concepts of scheduling in PLANTA and describes the period during which resources are available for scheduling in projects. The planning horizon of a resource is defined via the Start period and End period parameters in the Resource Data Sheet module .
See also:
Date, Resource, and Cost Scheduling

In PLANTA, projects, proposals, ideas, and programs are called planning objects. The planning object type is determined by the Type parameter.
See also:

Planning Objects
My Planning Objects module

The Status parameter is used to classify planning objects into active, inactive, archived, and template objects.
See also:
Project Core Data module,
Proposal Core Data module,
Program Core Data module,
Status parameter on projects (programs, proposals)

See:
Simulation entry

See:
Status Report entry

PLANTA Enterprise is the PLANTA edition that offers portfolio management features in addition to project management.
See also:
PLANTA Project entry
General Information on PLANTA Enterprise,
Portfolio Management,
Plan Portfolio tutorial

PLANTA Project is PLANTA’s core product for project planning and management.
See also:
General Information on PLANTA Project,
Project Management,
Plan and Control a Project tutorial

See:
PLANTA portfolio entry

In PLANTA, a portfolio manager is a manager of a particular portfolio. Unlike a multi-portfolio manager, a portfolio manager is only allowed to manage the data for their own portfolio. However, he cannot create new portfolios or delete existing ones. The manager of a portfolio is defined in the Portfolio Manager field in the Portfolio Core Data module of the respective portfolio.
See also:
Create a Portfolio tutorial,
User Rights,

Rights Management

A posting is the recording of actual data (actual hours, actual costs, actual revenues).
See also:
Reverse Postings entry,
Post Revenues module,
Post Costs module ,
Time Recording module

The Priority parameter can be used to determine which projects receive the available resource capacity first. The priority is defined in the Project Core Data of the projects.

See also:

“Replanning” section in the Scheduling topic

PLANTA provides its customers with an option for process model-based project management. Process models are frameworks that outline the steps used to plan and manage projects.
See also:
Working with Process Models tutorial,
Process Model Templates ,
Process Model Templates ,
Process Step, Process Rule, Process Status entries

Process rules are rules that can be defined for process steps or process phases in process models within PLANTA, which can be used for process-model-based project management.
See also:
Process Rule,
Process Model Templates ,
Process Rule Parameter,
Process Model, Process Step, Process Status entries

PLANTA provides you with a means to base your project management on process models. In the Process Status module, a model with the corresponding process steps is selected, activated, and processed.
See also:
Working with Process Models ,
Process Status Bar in the Info Board module,
Process status bar in the Dashboard module,
Process Model entry, Process Step, Process Rule

PLANTA provides you with a means to base your project management on process models. Process steps are individual steps within a project process model.
See also:
Working with Process Models tutorial,
Process Step panel,
Process Model Templates ,
Process Process model, Process Status, Process Rule entries

In PLANTA, the program manager is the manager of one or more programs. The program manager of a program is defined in the Manager field in the Program Core Data module of the respective program. The program manager may edit the data for their programs, but cannot create new programs or delete existing ones (in PLANTA, these rights are held by a multi-project manager).
See also:
Program Management role,
User Rights,
Rights Management

Programs (program management) is an option for bundling projects.
See also:

Program Management

The progress of a project or task refers to the degree to which it has been completed (degree of completion).
See also:
You can track the progress of the entire project and all its tasks in the Progress module, and the progress of individual tasks in the Task module.

In PLANTA, a project is a central planning object. A project is distinguished from an idea or a plan, which are merely preliminary stages of planning for a project. PLANTA offers a range of processing and information modules that enable optimal planning and management of corporate projects.
See also:
Planning Objects entry,
Tutorial Project Workflow ,

Project,
Project Parameters help area

A project is completed when the project target has been achieved. The project conclusion is the official end point of a project. Afterwards, no more effort is incurred for the achievement of the project objective.
See also:
Complete Project

You can centrally store and manage documents, notes, and bulletin board entries related to a planning object in a dedicated module.
See also:
Documents module in the Project panel,
Documents module in the Portfolio panel,
Documents module in the Program panel

See:
Status Report entry

See:
PM Administration role

See:
Project Manager entry

In PLANTA Manager, a project manager is responsible for one or more projects. Unlike a multi-portfolio manager, a portfolio manager is only allowed to manage the data for their own projects. He/she cannot create new projects or delete existing projects. The project manager of a project is defined in the Manager field in the Project Core Data module of the respective project.
See also:
Project Management role,
User Rights,

Rights Management

See:
Status Report entry

A project team is made up of all persons that are directly involved in the project.
See also:
Project Core Data,
Proposal Core Data

See:
Project Template entry

In PLANTA, both active projects and template projects can be used as templates for creating new projects or schedules.
See also:
Schedule entry,
Copy Schedule
Copy Entire Project Structure module

A proposal is a preliminary stage of project planning in which a project idea is fleshed out. In PLANTA, proposals are planning objects alongside ideas, projects, and programs.
See also:
Create New Proposal panel,
Proposal panel,
PLANTA portfolio component,
Ideas entry

Quality gates are so called controlling elements which serve as a bridge between portfolio management and project management. Functionally similar to gates or master milestones in planning objects, quality gates offer the opportunity to make the project execution phase more transparent through date-bound “section checks”.
See also:
Quality Gates module

The planning objects or modules most recently accessed by the logged-in user are displayed in the user menu under Recently/last viewed
See also:
User Menu

The Time Recording module allows you to record attendance times (a sort of “time clock” function) if these are not imported from an external system as scheduled working hours.
See also:
Record Hours Worked,
Absence module

See:
Time Recording entry

In PLANTA, a distinction is made between planned, actual, remaining, and total values for various objects (such as expenses, costs, etc.) and at multiple levels (project, task, etc.). The remaining value is the remainder.
See also:
Actual, remaining, total values for costs and effort,
Actual, remaining, total values for project durations,
Actual, remaining, total values for task durations

Replanning is a schedule calculation of all planning objects. This completely reorganizes the capacity utilization of the scheduled resources.
See also:
Replanning (Calculation of all Planning Objects) module

See:
Status Report entry

Prior to DB 39.5.13, the term "reporting” was used for time recording.

See also:

Time Recording entry

See:
Status Report entry

Resources include, for example, people (employees) or material resources that are necessary for carrying out processes or tasks within the project. In PLANTA, resources are part of the master data that is entered when the system is set up; they can then be selected from the list boxes during the planning process and assigned to operations. In PLANTA, a logical distinction is made between resource default data (master data) and resource assignment data (data for resources in a specific project or activity).
See also:
Resource assignment entry,
Create/edit resources and their master data in the Resource Data Sheet module ,
Plan resources in the Schedule module,
Resource Parameters

Resource management

In PLANTA, resource allocation refers to the assignment of resources to the tasks required to complete them. In PLANTA, a logical distinction is made between resource data and resource assignment data. When a resource is assigned to an activity, the settings from the resource parameters (DT467) are copied to the resource assignment parameters (DT466). These can then be modified on a project- or task-specific basis as needed, without having to change the resource's default settings.
See also:
Resource entry,
Plan Resources in the Schedule module,
Resource Assignment Parameters,
Create Resources

In PLANTA, calendars can be stored at different levels. The resource calendar is selected for the respective resource in the Resource Data Sheet module in the Calendar name field. The settings for this calendar are applied when creating period records.
See also:
Claendar module

In PLANTA, a resource manager is the manager of a department, also called department manager. The resource manager is responsible for scheduling, rescheduling, and ensuring the optimal utilization of his department's resources. The resource manager is defined by entering a department in the Department Name field in the Users module and by assigning the corresponding modules (in the standard system: Resource Management role).
See also:
Resource Management role

A resource structure represents a hierarchical arrangement of resources.
See also:
Generate (change) resource structure,
Resource Structure module,
Resource Structure (Display) module,
Check Resource Structure module

Revenue resources are resources with Resource type =8.
See also:
Revenues entry
Create Resources,
Resource Parameters
Post Revenues module

In PLANTA, revenues are planned in the form of revenue resources in projects and their actual load is recorded manually in the Post Revenues module. The revenue data are displayed separately from costs in the Budget module and other analysis modules.
See also:
Revenue Resources entry

In PLANTA, there are cases where you cannot simply delete or correct erroneous entries. In such a case, reverse postings are either posted automatically in the background or must be entered manually.
See also:
Reverse Postings

In PLANTA, you can assign different permissions to users. A distinction is made between access rights to modules and menu items, and access and modification rights for specific objects (planning objects, resources, etc.). Modification rights allow a user to edit/change data (objects) or to create new data. They may also include the right to delete data. Modification rights are allocated explicitly by changing the settings of certain parameters.

See also:
User Rights

Risk management refers to the process of identifying, analyzing, and assessing risks, as well as managing and communicating them.
See also:
Create and Edit Project Risks,
Create and Edit Program Risks
Risk module

A risk management measure is a targeted action taken to manage risks by reducing, avoiding, transferring, or deliberately accepting their likelihood of occurrence and/or the extent of potential damage.
See also:
Create Risk Measure,
Risk Measure Parameter

Risk management for projects and programs in PLANTA
See also:
Create and Edit Project Risks,
Create and Edit Program Risks
Risk Parameters

Risk treatment refers to the systematic process of managing risks by identifying and assessing them, and then taking specific measures to control, reduce, or avoid them.
See also:
Risk Treatment
Risk module

A road map is the approved and therefore frozen version of a simulation.
See also:
Simulation module
Simulation entry

SAP WBS elements can be used to link the SAP project structure to the PLANTA project structure.
See also:
Alternative Structures entry,
Account Assignment Elements entry,
SAP WBS module,
Create SAP WBS Elements

See:
Simulation entry

A schedule is a project timeline in which individual work packages (referred to as “tasks” in the project management component) are scheduled. For the creation and editing of schedules, PLANTA offers a module of the same name.
See also:
Schedule module,
Copy Schedule module,
Outline Plan module

Schedule calculation is a process of calculating schedules and allocating the resources planned for the project. It is part of the schedule calculation, which is initiated via the Edit → Calculate Schedule menu item or via the corresponding button in the toolbar.
See also:
Date, Resource, and Cost Scheduling

See:
Standard Schedule entry

The term scheduling is used as an umbrella term for two types of scheduling: time scheduling and schedule calculation The schedule calculation is part of the comprehensive schedule calculation, which includes not only the calculation of dates and resource loading but also the calculation of costs. To calculate the schedule, select Edit → Calculate schedule from the menu, or click the Calculate button on the toolbar.
See also:
Time Scheduling and Schedule Calculation entries
Date, Resource, and Cost Scheduling,
Scheduling Status (Display),
Scheduling Status module

In PLANTA's portfolio management, simulations allow users to run through and compare different planning scenarios regarding deadlines and capacity utilization. The required scenario can be defined as a road map.
See:
Simulation module
Road map entry

In PLANTA, a skill is a capability or a competence of a resource.
See also:
Create Skills,
Assign Skills to a Resource,
Skills panel,
Skill Parameters

See:
PLANTA Online Help entry

A stakeholder can be an individual or a group of people who are actively involved in a project and/or wish to be kept informed of the project's progress.
See also:
Project Core Data,
Proposal Core Data,
Stakeholder Parameters

PLANTA provides several standard schedules that can be used as templates for creating custom project schedules. The schedules for active projects can also be used as templates.
See also:
Schedule module,
Copy Schedule module,
Outline Plan module,
FAQ

The start date is the date on which projects, tasks, and resources begin. PLANTA distinguishes between the target, actual, and calculated start dates.
See also:
Project Core Data ,
Schedule ,
Requested/Calc./Actual start (Project),
Requested/Calc./Actual start (Task),
Requested/Calc./Actual start (Resource Assignment)

See:
Planning Object Status,
Status Report Status entry

A status report provides an overview of the project's current status from the date the report was written, covering various factors such as: dates, costs, effort, etc.
See also:
Create Project Status Report,
View, Release, Delete Status Report,
Create Portfolio Status Report,
View, Release, Delete Portfolio Statusbericht,
Create Program Status Report,
View, Release, Delete Program Status Report,
Cancel Status Report Release

The Report status parameter shows the current status (created, approved, baseline, etc.) of a status report.
See also:
Status module,
Status Report module,
Report Status parameter on project status reports

Is the code of an object within a structure that identifies the object according to the hierarchical structure. In PLANTA, the structure code is used to control access to planning objects and resources.
See also:
Cost Center Structure Code,
Resource Structure Code,
Rights Control

This is a task via which the parent project is linked to the child project.
See also:
Structure Projects,
Structure Task parameter on tasks

In PLANTA, various objects can be structured.

1. You can structure projects by splitting them into main and subprojects. This is referred to as project structures or structured projects.

See also:
Structure Projects

2. When tasks within a project are organized, a structured schedule or work breakdown structure is created.

See also:
Work Breakdown Structure

3. Resources can be hierarchically structured to form a resource structure.

See also:
Resource structure entry
Other items, such as cost types, cost centers, skills, etc., can also be structured.

Projects can be divided into subprojects to facilitate clearer planning and organization.
See also:
Strcuture Projects,
Subprojects module,
Edit Planning Objects module

Tasks can be organized hierarchically within a schedule. The parent tasks in such a structure are referred to as summary tasks.
See also:
Structure Tasks / Work Breakdown Structure,
Schedule module,
Summary Task parameter on tasks

Several systems can be assigned to a project. The project costs can be allocated to them on a percentage basis.
See also:
Systems ,
Allocate Costs to Systems module

Projects are divided into individual work packages. In PLANTA, such work packages are called Tasks.
See also:
Tasks in a Schedule,
Task Parameters
Task Data Sheet module

The technical ID of a project (idea, proposal, program, request) and of a task is generated automatically and, unlike the functional ID, cannot be changed later.
See also:
Functional ID entry,
Technical Project ID on projects
Technical Task ID onon tasks

See:
Project Template entry

See:
Project Template module, Standard Schedule

See:
In PLANTA, you can record the hours worked on projects.
See also:
Overview of the Time Recording Options in PLANTA,
Time Recording module

Time scheduling is a calculation of dates based on estimated task durations and dependencies, taking the calendar into account but not considering resources. No loading takes place. The calendar is automatically included in the schedule calculation, which is performed via the menu option Edit → Calculate Schedule.
See also:
Date, Resource, and Cost Scheduling

A threshold value (limit value) refers to the value used as a limit for a display, such as a traffic light.
See also:
Threshold Values module

In PLANTA, to-dos can be recorded and managed as smaller tasks within larger work packages (tasks). From a data logical point of view, tasks are subordinate to operations.
See also:
Todo Items module,
Schedule module,
Task module,
Todo Item Parameters

In PLANTA, a distinction is made between actual, remaining, and total values for various objects (such as expenses, costs, etc.) and at multiple levels (project, task, etc.). The total value is the total value of actual and remaining values.
See also:
Actual, remaining, total values for costs and effort,
Actual, remaining, total values for project durations,
Actual, remaining, total values for task durations

PLANTA software is a multilingual application All interface elements can be translated using the PLANTA Customizer.
See also:
Translation,
Language of the PLANTA Software in the General glossary

The user menu is a module that contains a user-specific, structured collection of links to modules and panels. In addition, the user menu includes a quick access section with a list of recently viewed planning objects and favorite planning objects.

See also:
User Menu in the Introduction and Program Operation help area

This is a module mode in which PLANTA users work, as opposed to the customization mode, where the module's structure is displayed and can be modified if the user has customizer rights.
See also:
Customizer Mode entry,
Customizer Rights parameter

Volume parameters display information about the number of components within an object, such as the number of activities in a project.
See also:
Volume Parameters Panel,
Project Volume Parameters module,
Resource Volume Parameters

Work Breakdown Structure
See:
WBS entry

The Weekly Calendar is a module in the Employee Board that displays all pending tasks (processes, assignments, etc.) as well as the logged-in employee’s presence or absence in a calendar from Monday through Friday.

The PLANTA Wiki is the PLANTA documentation platform where PLANTA provides product documentation for PLANTA Project up to version DB 39.5.16 and for the agile component pulse up to release 31. Starting with version 39.5.17 of PLANTA Project and release 32 of the agile component, the PLANTA Wiki is replaced by the new PLANTA Online Help.
See also:
PLANTA Online Help entry,
wiki.planta.de

In PLANTA, a work breakdown structure means a schedule in which tasks are structured hierarchically.
See also:
Structure Tasks / Work Breakdown Structure,
Schedule module,
WBS module

Workflow management refers to process-oriented project management. PLANTA allows users to plan and manage projects in a process-oriented manner.
See also:
Working with Process Models tutorial,
Process Status module

In PLANTA, work packages are called tasks
See also:
Task entry

Costs, effort and budgets are planned in PLANTA on an annual basis. The presentation and processing of data in modules is organized into so-called annual segments.
See also:
Budget,
Budget (Portfolio) module