This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
en:gui5:handbuch:kapitel_2:2.02.02_projekt [2021/09/29 13:18] alexandra |
en:gui5:handbuch:kapitel_2:2.02.02_projekt [2021/12/14 11:23] (current) alexandra [Portfolio] |
||
---|---|---|---|
Line 13: | Line 13: | ||
* **Basic Information:** | * **Basic Information:** | ||
- | * **Project Number:** This alphabetical field uniquely identifies the project in the system. The project number can be changed at any time, but must be unique in the database. This number is usually preset with a number range and is inherited by all project-related elements (subprojects, [[..:kapitel_2:2.02.04_arbeitspaket|work packages]], [[..:kapitel_2:2.02.05_meilenstein|milestones]], etc.). | + | * **Number:** This alphabetical field uniquely identifies the project in the system. The project number can be changed at any time, but must be unique in the database. This number is usually preset with a number range and is inherited by all project-related elements (subprojects, [[..:kapitel_2:2.02.04_arbeitspaket|work packages]], [[..:kapitel_2:2.02.05_meilenstein|milestones]], etc.). |
* **Status:** This field indicates whether the project is active, passive or completed. When you create a new project, the system defaults this field to passive. Further characteristics (interrupted, terminated) can be defined by the administrator. | * **Status:** This field indicates whether the project is active, passive or completed. When you create a new project, the system defaults this field to passive. Further characteristics (interrupted, terminated) can be defined by the administrator. | ||
- | * **Name:** This field identifies the project. | + | * **Description:** In this field a summarizing description of the project can be entered. |
- | * **Description:** In this field a summarizing DeepL description of the project can be entered. | + | * **Start of Planning/End of Planning:** The Plan Start field defines the expected project start and the Plan End field defines the expected project end. An entry for these fields is mandatory. This forms the basis for the [[..:kapitel_2:2.05_auswertungssystem|evaluations]] (Gantt diagram, milestone trend analysis, ...) of the information system. |
- | * **Project Period (from/to):** The Plan Start field defines the expected project start and the Plan End field defines the expected project end. An entry for these fields is mandatory. This forms the basis for the [[..:kapitel_2:2.05_auswertungssystem|evaluations]] (Gantt diagram, milestone trend analysis, ...) of the information system. | + | * **Note:** Further comments on the project can be entered here. |
- | * **Comment:** Further comments on the project can be entered here. | + | |
* **Structure:** | * **Structure:** | ||
* **Main Project:** The highest organizational unit of a project structure. It does not itself have a superordinate project. | * **Main Project:** The highest organizational unit of a project structure. It does not itself have a superordinate project. | ||
- | * **Superior Project:** The field Superior Project characterizes the existence of a superordinate project. If the element is not occupied, then the project itself is a superordinate project. The project structure is displayed using the [[..:kapitel_a:glossar#Projektstrukturplan|project structure plan]]. When you create subprojects, this entry is filled automatically. | + | * **Parent Project:** The field Superior Project characterizes the existence of a superordinate project. If the element is not occupied, then the project itself is a superordinate project. The project structure is displayed using the [[..:kapitel_a:glossar#Projektstrukturplan|project structure plan]]. When you create subprojects, this entry is filled automatically. |
- | * **Subprojects:** This element contains a list of all assigned subprojects. After defining subprojects, they are automatically transferred to the parent project as subprojects. | + | * **Subordinate projects:** This element contains a list of all assigned subprojects. After defining subprojects, they are automatically transferred to the parent project as subprojects. |
- | * **Tasks:** This element contains a list of all assigned [[..:kapitel_2:2.02.04_arbeitspaket|work packages]] or [[..:kapitel_2:2.02.03_vorgang|tasks]]. | + | * **Processes:** This element contains a list of all assigned [[..:kapitel_2:2.02.04_arbeitspaket|work packages]] or [[..:kapitel_2:2.02.03_vorgang|processes]]. |
* **Milestones:** This element contains a list of all assigned [[..:kapitel_2:2.02.05_meilenstein|milestones]]. | * **Milestones:** This element contains a list of all assigned [[..:kapitel_2:2.02.05_meilenstein|milestones]]. | ||
Line 34: | Line 33: | ||
{{:en:gui5:handbuch:kapitel_2:bildschirmfoto_2021-09-29_um_13.07.44.png?|}} | {{:en:gui5:handbuch:kapitel_2:bildschirmfoto_2021-09-29_um_13.07.44.png?|}} | ||
- | * **ext. Involved Parties:** | + | * **External Stakeholders:** |
- | * **External Order:** This field indicates whether the project is external. If the checkbox is activated, the selected project is an external project, otherwise it is an internal project. For external projects, the system requires the assignment of a sold-to party. | + | * **External Project:** This field indicates whether the project is external. If the checkbox is activated, the selected project is an external project, otherwise it is an internal project. For external projects, the system requires the assignment of a sold-to party. |
- | * **Contact:** The contact of the project can be entered in this field. | + | * **Company:** The contact of the project can be entered in this field. |
- | * **Purchasing/Functional/Technical Contact Person:** The field Contact Person identifies the contact person for the project. After selecting a customer, this field is filled with the contact persons of this customer. The contact persons are managed in the [[..:kapitel_2:2.01.21_basic_-_ansprechpartner|contact person]] mask. | + | * **Commercial/Specialist/Technical Contact Person:** The field Contact Person identifies the contact person for the project. After selecting a customer, this field is filled with the contact persons of this customer. The contact persons are managed in the [[..:kapitel_2:2.01.21_basic_-_ansprechpartner|contact person]] mask. |
- | * **Invoice Recipient:** If the project invoices are to be split up proportionally among several customers, the individual recipients can be entered here with a percentage. The procedure is as follows: First a normal invoice is created, this is then converted into several invoices with the action "Split invoice" and each recipient receives an invoice with his percentage share. The sum of the individual invoices then equals the total amount again. | + | * **Invoice Recipients:** If the project invoices are to be split up proportionally among several customers, the individual recipients can be entered here with a percentage. The procedure is as follows: First a normal invoice is created, this is then converted into several invoices with the action "Split invoice" and each recipient receives an invoice with his percentage share. The sum of the individual invoices then equals the total amount again. |
- | * **End Customer:** Here you can enter an end customer that differs from the ordering party. | + | * **Alternative End Customer:** Here you can enter an end customer that differs from the ordering party. |
- | * **Internal Involved Parties:** | + | * **Internal Stakeholders:** |
* **Unit:** In this field, you define the responsible unit (usually a location or a department). The heads of these units then have the same authorization for this project as the project managers. Units can be edited in the [[..:kapitel_2:2.01.27_basic_-_unit|unit]] mask. | * **Unit:** In this field, you define the responsible unit (usually a location or a department). The heads of these units then have the same authorization for this project as the project managers. Units can be edited in the [[..:kapitel_2:2.01.27_basic_-_unit|unit]] mask. | ||
* **Project Manager:** This field identifies the project manager of the project. The project manager automatically becomes project manager of all defined sub-projects. This ensures that the project manager has the authorization to create and change data for this project. Normally, an employee is only granted access to a project once he or she has joined the project team. | * **Project Manager:** This field identifies the project manager of the project. The project manager automatically becomes project manager of all defined sub-projects. This ensures that the project manager has the authorization to create and change data for this project. Normally, an employee is only granted access to a project once he or she has joined the project team. | ||
* **Project Team:** This multiple selection enables the project team to be put together. The project managers of the subprojects and the processors of the assigned [[..:kapitel_2:2.02.04_arbeitspaket|work packages]] are automatically transferred to the project team. | * **Project Team:** This multiple selection enables the project team to be put together. The project managers of the subprojects and the processors of the assigned [[..:kapitel_2:2.02.04_arbeitspaket|work packages]] are automatically transferred to the project team. | ||
- | * **Steering Committee:** The members of the steering committee can be entered here. | + | * **Project Board:** The members of the steering committee can be entered here. |
- | * **Project Partner:** Here you can enter the internal and/or external project partners and their role in the project. | + | * **Project Partners:** Here you can enter the internal and/or external project partners and their role in the project. |
Line 64: | Line 63: | ||
* **Probability:** For passive projects this field indicates the probability that the planned project will become an active project (=order). This probability is taken into account proportionally in [[..:kapitel_a:glossar#Kapazitätsplanung|capacity planning]] and is used in the proposal system. When a project is activated, the system automatically sets this probability to 100%. | * **Probability:** For passive projects this field indicates the probability that the planned project will become an active project (=order). This probability is taken into account proportionally in [[..:kapitel_a:glossar#Kapazitätsplanung|capacity planning]] and is used in the proposal system. When a project is activated, the system automatically sets this probability to 100%. | ||
* **Priority:** This field indicates the priority of the selected project. | * **Priority:** This field indicates the priority of the selected project. | ||
- | * **Order Type:** This element serves as an indicator for the later settlement of the project (effort or fixed price). This field is also used in some versions as an indicator for the valuation of finished and unfinished activities. | + | * **Billing Type:** This element serves as an indicator for the later settlement of the project (effort or fixed price). This field is also used in some versions as an indicator for the valuation of finished and unfinished activities. |
- | * **Project Type:** This field assigns a definable project type to the project, which can be used as a selection criterion in the evaluations. | + | * **Category:** This field assigns a definable project type to the project, which can be used as a selection criterion in the evaluations. |
- | * **Strategic Relevance:** An evaluation of the project for the strategic relevance to the project landscape can be stored here. | + | * **Secret:** If this project is secret, you can choose the option here. |
+ | * **Strategy:** An evaluation of the project for the strategic relevance to the project landscape can be stored here. | ||
* **Class:** Here you can specify whether the project must be made/can/should be made. | * **Class:** Here you can specify whether the project must be made/can/should be made. | ||
Line 73: | Line 73: | ||
* **Product:** Here the project can be assigned a product (either as a pure entry or as an object product from the product management module). | * **Product:** Here the project can be assigned a product (either as a pure entry or as an object product from the product management module). | ||
+ | * **Complexity:** | ||
+ | * **Order Volume:** What is the order volume for the project? | ||
+ | * **Number of External Contacts:** How many contact person does the company have? | ||
+ | * **Contract Type:** The contract liability level. | ||
+ | * **Number of Suppliers:** How many suppliers does the project have? | ||
+ | * **Risk Probability:** What is the likely risk for the project? | ||
+ | * **Project Effort:** How big is the effort for this project? Approximately how many days are needed? | ||
+ | * **Number of Employees:** How many employees are needed for the project? | ||
+ | * **Relevance:** The importance of the project for the company. | ||
+ | * **Complexity:** These parameters determine the complexity of the project. | ||
+ | |||
+ | * **Tailoring:** If a tailoring was created for this project, this field contains a link to show the tailoring. Tailorings can be created via Actions > Administration > Create tailoring. | ||
=====Risk Assessment===== | =====Risk Assessment===== | ||
Line 90: | Line 102: | ||
* **Status Reports:** Status reports are an important part of project management and project controlling. They document the progress of the project plan. The status report often contains status information about dates, costs and quality (sometimes also other information), reasons, progress information (expected project end, remaining costs, ...). | * **Status Reports:** Status reports are an important part of project management and project controlling. They document the progress of the project plan. The status report often contains status information about dates, costs and quality (sometimes also other information), reasons, progress information (expected project end, remaining costs, ...). | ||
* **Project Change Requests:**In project change management, a change request is a formalized request to change the properties of a specific product feature. The change request often contains the participants/responsible persons, the priority, a categorization and the quantitative effects (effort, costs, sales, ...) on the project. | * **Project Change Requests:**In project change management, a change request is a formalized request to change the properties of a specific product feature. The change request often contains the participants/responsible persons, the priority, a categorization and the quantitative effects (effort, costs, sales, ...) on the project. | ||
- | * **Fertigstellungsgrade:** Here the project manager can regularly enter the degrees of completion of the project (for example for controlling or POC valuation). | + | * **Estimates:** Here the project manager can regularly enter the degrees of completion of the project (for example for controlling or POC valuation). |
- | * **Risiken:** Here (if the Risk Management module is enabled) the risks are displayed. | + | * **Risks:** Here (if the Risk Management module is enabled) the risks are displayed. |
=====Key Figures===== | =====Key Figures===== | ||
Line 98: | Line 110: | ||
* **Expenses:** | * **Expenses:** | ||
- | * **Target Expenditure:** This field is determined by the system during planning and defines the expected project duration in hours or days. During planning, this value is updated (analogous to planned effort) and when planning is completed (status transition to "advance work" or "active"), this value is not changed. | + | * **Target Time:** This field is determined by the system during planning and defines the expected project duration in hours or days. During planning, this value is updated (analogous to planned effort) and when planning is completed (status transition to "advance work" or "active"), this value is not changed. |
- | * **Plan Effort:** This field defines the expected project duration. This field is either determined automatically according to the [[..:kapitel_a:glossar#ButtomUp-Prinzip|ButtomUp principle]] or is specified by the user in [[..:kapitel_a:glossar#TopDown-Planung|Top-Down planning]]. This value is identical to the planned effort until the status changes to "Advance work" or "active". | + | * **Planning Time:** This field defines the expected project duration. This field is either determined automatically according to the [[..:kapitel_a:glossar#ButtomUp-Prinzip|ButtomUp principle]] or is specified by the user in [[..:kapitel_a:glossar#TopDown-Planung|Top-Down planning]]. This value is identical to the planned effort until the status changes to "Advance work" or "active". |
- | * **Actual Effort:** This field contains the recorded times for the assigned project. These actual efforts are transferred to the projects and [[..:kapitel_2:2.02.04_arbeitspaket|work packages]] each time a change is made in the [[..:kapitel_2:2.3.01_timetracker|TimeTracker]] recording component. | + | * **Periodic Planning Time:** The current plan costs from the schedule. |
- | * **Billable Effort:** This field contains the billable effort for the assigned project. | + | * **Actual Time:** This field contains the recorded times for the assigned project. These actual efforts are transferred to the projects and [[..:kapitel_2:2.02.04_arbeitspaket|work packages]] each time a change is made in the [[..:kapitel_2:2.3.01_timetracker|TimeTracker]] recording component. |
- | * **Billed Effort:** This field contains the billed times for the assigned project. These billed times are transferred to the projects and work packages each time the invoice is issued or cancelled. | + | * **Billable Time:** This field contains the billable effort for the assigned project. |
- | * **Expected Remaining Effort:** This field shows the last remaining effort estimate entered minus the subsequently entered effort. | + | * **Billed Time:** This field contains the billed times for the assigned project. These billed times are transferred to the projects and work packages each time the invoice is issued or cancelled. |
+ | * **Estimated Remaining Effort:** This field shows the last remaining effort estimate entered minus the subsequently entered effort. | ||
+ | * **LastTrackingRestriction:** Tracking of cost for this project is not allowed before this date. | ||
+ | |||
+ | * **Figures:** | ||
+ | * **Offer Value:** The sum of the completed offer. | ||
+ | * **OrderConfirmationTracked:** The sum of the completed order. | ||
+ | * **TurnoverContractPlanned:** The forecast based on contracts. Depending on the type of contract, compiled from milestones, payment schedule or the sum of plan expenses * external hourly rate plus all costs. | ||
+ | * **TurnoverChargeable:** The sum of actual expenses * external hourly rate in addition to all costs. | ||
+ | * **TurnoverTrackedProject:** The sum of the completed invoices. | ||
+ | * **Total Costs:** The sum of planned expenses * internal hourly rate + internal other budgets. | ||
+ | * **Actual Costs:** The sum of actual expenses * internal hourly rate + other expenses (drive, travel, receipts, item sales, incoming invoices). | ||
+ | * **LeftoverBudget:** The difference between total costs and actual costs (total costs - actual costs). | ||
+ | * **OrderValueNet:** The sum of the completed order positions. | ||
+ | * **IncomingInvoiceNet:** The sum of the completed incoming invoice positions. | ||
+ | * **ExternLeftoverBudget:** The difference between OrderValueNet and IncomingInvoiceNet (OrderValueNet - ExternLeftoverBudget). | ||
+ | |||
+ | * **EVA:** | ||
+ | * **CPI:** The cost-based performance measure of earned value analysis. It is formed from the ratio of earned value and planned expense. This means that if the CPI is greater than 1, the project results were delivered at less cost than originally planned, while a value less than 1 means the budget is overdrawn. | ||
+ | * **SPI:** The time-based performance measure of earned value analysis. It is formed from the ratio between earned value and planned expense. This means that if the SPI is greater than 1, the project results were delivered faster than planned. If the number is less than 1, the project is progressing too slowly. | ||
=====Calculation===== | =====Calculation===== | ||
Line 120: | Line 151: | ||
{{:en:gui5:handbuch:kapitel_2:bildschirmfoto_2021-09-29_um_13.15.36.png?|}} | {{:en:gui5:handbuch:kapitel_2:bildschirmfoto_2021-09-29_um_13.15.36.png?|}} | ||
- | |||
- | * **Order Data:** | ||
- | * **Order Number**, **Order Date:** The order number and order date of the project can be entered here. This order data can be used for the invoice printout. The order number and the order date are automatically transmitted by the system when an [[..:kapitel_2:2.4.03_auftragsbestaetigung|order confirmation]] is accepted in a defined way. | ||
- | * **Order Value:** This field can be used to define the fixed price (maximum upper limit of all invoices for this project). If this order value is defined here, the automatically determined value Planned Sales represents only the theoretical project budget, based on the planned values from the [[..:kapitel_2:2.02.04_arbeitspaket|work packages]] and [[..:kapitel_2:2.02.09_budget|budget management]]. The order value is transferred automatically by the system when an [[..:kapitel_2:2.4.03_auftragsbestaetigung|orer confirmation]] is transferred in a defined form. | ||
- | * **Incoming Order:** The type of incoming order (fax, letter, e-mail, ...) can be entered here. | ||
- | * **Discount:** Here it can be noted whether the customer receives a discount. | ||
- | * **Cash Discount:** This field indicates whether the customer receives a discount if he pays the amount immediately. | ||
* **Travel Expense Regulation:** | * **Travel Expense Regulation:** | ||
- | * **Travel Expense Settlement Type**, **Travel Expense Flat Rate** and **Travel Expense Flat Rate per day:** Here you can store the defaults for the settlement of the project's trips (no settlement, per diem, by expense). You can change these default settings per trip. | + | * **T&E Billing Type**, **T&E Flat Rate** and **T&E Daily Flat Rate:** Here you can store the defaults for the settlement of the project's trips (no settlement, per diem, by expense). You can change these default settings per trip. |
* **Currencies and Rates:** | * **Currencies and Rates:** | ||
* **Currency:** The currency field indicates the project currency. The project currency overwrites the general system currency (see also [[..:kapitel_2:2.01.01_system_-_konfiguration|configuration]]) and the customer currency (see also [[..:kapitel_2:2.01.13_basic_-_kontakt|Contact]]). This field is defaulted with the currency from the [[..:kapitel_2:2.01.01_system_-_konfiguration|configuration]] mask. After selecting a customer, the local currency from the configuration is changed by the customer currency if necessary. The currencies can be defined and changed in the screen [[..:kapitel_2:2.01.06_key_-_waehrung|currency]]. | * **Currency:** The currency field indicates the project currency. The project currency overwrites the general system currency (see also [[..:kapitel_2:2.01.01_system_-_konfiguration|configuration]]) and the customer currency (see also [[..:kapitel_2:2.01.13_basic_-_kontakt|Contact]]). This field is defaulted with the currency from the [[..:kapitel_2:2.01.01_system_-_konfiguration|configuration]] mask. After selecting a customer, the local currency from the configuration is changed by the customer currency if necessary. The currencies can be defined and changed in the screen [[..:kapitel_2:2.01.06_key_-_waehrung|currency]]. | ||
* **Exchange Rate:** After selecting a project currency, the Exchange rate field is automatically preset with the valid exchange rate of the project currency to the local currency (see also [[..:kapitel_2:2.01.01_system_-_konfiguration|configuration]]). Here you can also define a different project exchange rate (e.g. for international projects where the currency risk is to be minimized). This exchange rate is also binding for quotations and invoices. The exchange rates are managed in the [[..:kapitel_2:2.01.07_key_-_kurs|exchange rate]] mask. | * **Exchange Rate:** After selecting a project currency, the Exchange rate field is automatically preset with the valid exchange rate of the project currency to the local currency (see also [[..:kapitel_2:2.01.01_system_-_konfiguration|configuration]]). Here you can also define a different project exchange rate (e.g. for international projects where the currency risk is to be minimized). This exchange rate is also binding for quotations and invoices. The exchange rates are managed in the [[..:kapitel_2:2.01.07_key_-_kurs|exchange rate]] mask. | ||
- | * **External Hourly Rate (fixed and variable):** These fields indicate the general hourly rate (fixed or variable) for further calculation for the defined project. If this field is filled (and the corresponding field in the work package is not), all work activities are charged with this rate and the system no longer takes into account the rates from the masks [[..:kapitel_2:2.01.13_basic_-_kontakt|contact]], [[..:kapitel_2:2.01.24_basic_-_mitarbeiter|employees]] or [[..:kapitel_2:2.01.23_basic_-_taetigkeit|activities]] (see also [[..:kapitel_a:glossar#Preisfindung|pricing]]). The variable rate is higher than the fixed hourly rate. | + | * **External Hourly Rate (fixed and time-related):** These fields indicate the general hourly rate (fixed or variable) for further calculation for the defined project. If this field is filled (and the corresponding field in the work package is not), all work activities are charged with this rate and the system no longer takes into account the rates from the masks [[..:kapitel_2:2.01.13_basic_-_kontakt|contact]], [[..:kapitel_2:2.01.24_basic_-_mitarbeiter|employees]] or [[..:kapitel_2:2.01.23_basic_-_taetigkeit|activities]] (see also [[..:kapitel_a:glossar#Preisfindung|pricing]]). The variable rate is higher than the fixed hourly rate. |
Line 142: | Line 166: | ||
{{:en:gui5:handbuch:kapitel_2:bildschirmfoto_2021-09-29_um_13.16.31.png?|}} | {{:en:gui5:handbuch:kapitel_2:bildschirmfoto_2021-09-29_um_13.16.31.png?|}} | ||
- | * **Actions:** In this field, projectations can be entered or assigned. | + | * **Customer Actions:** In this field, actions can be entered or assigned. |
* **Meetings:** This field allows to enter or assign meetings. | * **Meetings:** This field allows to enter or assign meetings. | ||
- | * **Action List:** This field allows the entry of events. | + | * **Decisions:** This field allows the entry of decisions. |
- | * **ext. Documentation:** If the flyer is available, external files can be assigned here. | + | * **Risks:** This field allows the entry of risks. |
+ | * **External Documentations:** If the flyer is available, external files (like Project Acceptance, Documentations and Invoices) can be assigned here. | ||
=====Final Report===== | =====Final Report===== | ||
Line 151: | Line 176: | ||
{{:en:gui5:handbuch:kapitel_2:bildschirmfoto_2021-09-29_um_13.17.11.png?|}} | {{:en:gui5:handbuch:kapitel_2:bildschirmfoto_2021-09-29_um_13.17.11.png?|}} | ||
- | * **Creator & Summary:** A summary of the final report (Project Closing Document - PCD) can be stored here. | + | * **Creator & Overview:** A summary of the final report (Project Closing Document - PCD) can be stored here. |
* **Description of the Individual Points:** Detailed information for the PCD can be entered here. | * **Description of the Individual Points:** Detailed information for the PCD can be entered here. | ||
* **Lessons Learned:** Lessons Learned can be entered here, which can also be viewed by users without access to the project. | * **Lessons Learned:** Lessons Learned can be entered here, which can also be viewed by users without access to the project. | ||
Line 162: | Line 187: | ||
{{:en:gui5:handbuch:kapitel_2:bildschirmfoto_2021-09-29_um_13.17.52.png?|}} | {{:en:gui5:handbuch:kapitel_2:bildschirmfoto_2021-09-29_um_13.17.52.png?|}} | ||
- | * **Technical Setting & Details:** | + | * **Technical Details:** |
- | * **int. Key:** This numeric field uniquely identifies the project. This number is proposed by the system. | + | * **Key:** This numeric field uniquely identifies the project. This number is proposed by the system. |
- | * **Offer Value:** The total of all bid values for the project is stored here (net). | + | * **Sales Pipeline:** The sales activity related to this project. |
- | * **Invoice Value:** The total of all invoice values of the project is stored here (net). | + | |
- | * **Indicators for Recording and Reporting:** | + | * **Indicators for Tracking and Reporting:** |
- | * **Operational Activity:** This indicator controls the properties of the project work packages. This indicator is an evaluation criterion in capacity evaluations and is used, for example, for internal projects or permanent projects so that these projects are not taken into account when calculating the workload of employees. | + | * **Production Effort:** This indicator controls the properties of the project work packages. This indicator is an evaluation criterion in capacity evaluations and is used, for example, for internal projects or permanent projects so that these projects are not taken into account when calculating the workload of employees. |
- | * **Total of Work Packages in the Activity cannot be Overbooked::** This indicator controls the properties of the activities in the project. If the indicator is set, you can only record in the [[..:kapitel_2:2.3.01_timetracker|TimeTracker]] on the activity (or the total of the assigned work packages) as long as the planned effort is not exceeded. | + | * **Not Overbookable:** This indicator controls the properties of the activities in the project. If the indicator is set, you can only record in the [[..:kapitel_2:2.3.01_timetracker|TimeTracker]] on the activity (or the total of the assigned work packages) as long as the planned effort is not exceeded. |
- | * **Work Packages cannot be Overbooked:** This indicator controls the properties of the project work packages. If the indicator is set, you can only enter data in the [[..:kapitel_2:2.3.01_timetracker|TimeTracker]] for the work package as long as the planned effort has not been exceeded. | + | * **Jobs not Overbookable:** This indicator controls the properties of the project work packages. If the indicator is set, you can only enter data in the [[..:kapitel_2:2.3.01_timetracker|TimeTracker]] for the work package as long as the planned effort has not been exceeded. |
- | * **Time Recording only after the Start of the Plan:** This indicator controls the properties of the project work packages. If the indicator is set, you can only record time in the work package in the time tracker if the start of the work package has been reached. | + | * **Limit Time Tracking to Estimated Begin Date:** This indicator controls the properties of the project work packages. If the indicator is set, you can only record time in the work package in the time tracker if the start of the work package has been reached. |
- | * **Time Recording only before End of Plan:** This indicator controls the properties of the project work packages. If the indicator is set, you can only record time in the work package's time tracker as long as the end of the work package has not been reached. | + | * **Limit Time Tracking to Estimated End Date:** This indicator controls the properties of the project work packages. If the indicator is set, you can only record time in the work package's time tracker as long as the end of the work package has not been reached. |
- | * **Project not Overbookable:** This indicator controls the properties of the project work packages. If the indicator is set, data can only be entered in the [[..:kapitel_2:2.3.01_timetracker|TimeTracker]] for the work packages of the project as long as the planned effort of the project is not exceeded. | + | * **Limit Time to Estimated Time Project:** This indicator controls the properties of the project jobs. If the indicator is set, data can only be entered in the [[..:kapitel_2:2.3.01_timetracker|TimeTracker]] for the jobs of the project as long as the planned effort of the project is not exceeded. |
* **Check Indicators:** | * **Check Indicators:** | ||
- | * **Checked on**, **Checked on Key Date:** The check date of the project and the key date of the check can be entered in these fields. | + | * **Last Checked**, **Auditdate:** The check date of the project and the key date of the check can be entered in these fields. |
- | * **Last Status Change to Passive, Active or Completed:** The most important status changes are listed here (passive - entered, active/preliminary work, completed/cancelled). The complete history of all status changes can be found in the menu item "View - Show Event Log". | + | * **Last Status Change to Passive, Active or Closed:** The most important status changes are listed here (passive - entered, active/preliminary work, completed/cancelled). The complete history of all status changes can be found in the menu item "View - Show Event Log". |