User Tools

Site Tools


en:handbuch:kapitel_2:2.02.13_projektaenderungsantrag

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
en:handbuch:kapitel_2:2.02.13_projektaenderungsantrag [2009/12/04 14:25]
192.168.0.52
en:handbuch:kapitel_2:2.02.13_projektaenderungsantrag [2019/10/25 14:11] (current)
Line 1: Line 1:
 [[2.02.12_statusbericht|{{|zurück}}]] [[handbuch:​handbuch|{{|Home}}]] [[2.02.14_programm|{{|weiter}}]] [[2.02.12_statusbericht|{{|zurück}}]] [[handbuch:​handbuch|{{|Home}}]] [[2.02.14_programm|{{|weiter}}]]
  
-====== 2.02.13 Project-Change ======+====== 2.02.12 Project-Change ======
  
 Change management is the organization,​ administration and transaction of change-requests during the project progress. The mask project-change allows the definition of change-requests for the project. Here, changes can be stored, evaluated and qualified by the user. Change management is the organization,​ administration and transaction of change-requests during the project progress. The mask project-change allows the definition of change-requests for the project. Here, changes can be stored, evaluated and qualified by the user.
Line 7: Line 7:
 **Hint:** You can find more on this topic in the section 4.3.08 '​record project change'​. **Hint:** You can find more on this topic in the section 4.3.08 '​record project change'​.
  
-{{:​handbuch:​kapitel_2:​projektaenderung1_neu.gif|}}+{{:en:​handbuch:​kapitel_2:​project_change_request1.png|}}
  
 The mask contains the following elements: The mask contains the following elements:
  
-===== On the Tab "​Master ​Sheet": ​=====+On the "​Master ​data" ​tab:
  
  
-    * **Number:​** ​This alphabeti field indicates the project change clearly in the system.  +    * **Number:** This alphabeti field indicates the project change clearly in the system.  
-    * **Status:​** ​Here the user enters the status of the project change. As status in standard is declined, recorded, approved and open stored. ​ The status can be defined and changed in the Collections (CRStatusSC). ​  +    * **Status:** Here the user enters the status of the project change. As status in standard is declined, recorded, approved and open stored. ​ The status can be defined and changed in the Collections (CRStatusSC). ​  
-    * **Discreption:​** ​This field designates the project change.  +    * **Discreption:​** This field designates the project change.  
-    * **Employee:​** ​Here, the system defaults the appropriate employee of the project change. The employees are managed in the mask [[en:​handbuch:​kapitel_2:​2.01.24_basic_-_mitarbeiter|employee]] . +    * **Employee:​** Here, the system defaults the appropriate employee of the project change. The employees are managed in the mask [[en:​handbuch:​kapitel_2:​2.01.24_basic_-_mitarbeiter|employee]] . 
-    * **Date:​** ​The field date designates the date and the time of the project change. By default, the current date is here preseted by the system. +    * **Date:** The field date designates the date and the time of the project change. By default, the current date is here preseted by the system. 
-    * **Project:​** ​This field defines the project, to which the defined project change belongs. A project change can be assigned to a main project and to a sub-project as well. The projects can be defined and changed in the mask [[en:​handbuch:​kapitel_2:​2.02.02_projekt|Project]] . +    * **Project:​** This field defines the project, to which the defined project change belongs. A project change can be assigned to a main project and to a sub-project as well. The projects can be defined and changed in the mask [[en:​handbuch:​kapitel_2:​2.02.02_projekt|Project]] . 
-    * **Change-Type:​** ​This field designates the type of the project change (general reason, request from the customer, errors, IT issues, market changes, ...). The change-type can be defined and changed in the collections (CRReason). +    * **Change-Type:​** This field designates the type of the project change (general reason, request from the customer, errors, IT issues, market changes, ...). The change-type can be defined and changed in the collections (CRReason). 
-    * **Priority:​** ​Thid field designates the priority of the chosen project changes. +    * **Priority:​** Thid field designates the priority of the chosen project changes. 
-    * **Participating Employees:​** ​This multiple selection allows the assignment of participating employees to the change-request+    * **Participating Employees:​** This multiple selection allows the assignment of participating employees to the change-request. The employees are managed in the mask [[en:​handbuch:​kapitel_2:​2.01.24_basic_-_mitarbeiter|employee]]. 
-Diese Mehrfachauswahl ermöglicht die Zuordnung beteiligter Mitarbeiter zum Änderungsantrag. The employees are managed in the mask [[en:​handbuch:​kapitel_2:​2.01.24_basic_-_mitarbeiter|employee]] ​verwaltet+    * **Note:** This field can be used for comments on the project changes.
-    * **Bemerkung:** - Dieses Feld kann für Bemerkung zur Projektänderung verwendet werden.+
  
-{{:​handbuch:​kapitel_2:​projektaenderung2_neu.gif|}} +{{:en:​handbuch:​kapitel_2:​project_change_request2.png|}}
- +
-===== Auf dem Reiter "​Kommentare":​ ===== +
- +
- +
-    * Änderung Aufwand (Ja, Grund, Aufwandsabweichung) - Hier muss bei Änderung am Aufwand das Kennzeichnen "​Ja"​ gesetzt werden und der Grund sowie die Aufwandsabweichung in Stunden oder Personentagen eingegeben werden. +
-    * Änderung Kosten (Ja, Grund, Kostenabweichung) - Hier muss bei Änderung im Bezug auf die Kosten das Kennzeichnen "​Ja"​ gesetzt werden und der Grund sowie die Kostenabweichung in EUR eingegeben werden. +
-    * Änderung Umsatz (Ja, Grund, Umsatzabweichung) - Hier muss bei Änderung im Bezug auf den Umsatz das Kennzeichnen "​Ja"​ gesetzt werden und der Grund sowie die Umsatzabweichung in EUR eingegeben werden. +
-    * Änderung Termin (Ja, Grund, Terminabweichung) - Hier muss bei Terminänderungen das Kennzeichnen "​Ja"​ gesetzt werden und der Grund sowie die Terminabweichung in Kalendertagen eingegeben werden. +
-    * Änderung Ressourcen (Ja, Grund) - Hier muss bei Änderung im Bezug auf die Ressourcen das Kennzeichnen "​Ja"​ gesetzt werden und der Grund eingegeben werden. +
-    * Änderung Ziel (Ja, Grund) - Hier muss bei Änderung im Bezug auf das Ziel das Kennzeichnen "​Ja"​ gesetzt werden und der Grund eingegeben werden.+
  
 +On the "​Comments"​ tab:
  
 +    * **CR Duration (Yes, Reason, DurationValue):​** Here, you must set the feature "​Yes"​ in changes to the effort and you have to enter the reason and the effort difference in hours or in person-days,​ as well.
 +    * **CR Cost (Yes, Reason, CostValue):​** Here, you must set the feature "​Yes"​ in changes to the costs and you have to enter the reason and the cost difference in EUR, as well. 
 +    * **CR Turnover (Yes, Reason, TurnoverValue):​** Here, you must set the feature "​Yes"​ in changes to the turnover and you have to enter the reason and the turnover difference in EUR, as well. 
 +    * **CR Date (Yes, Reason, DateValue):​** Here, you must set the feature "​Yes"​ in changes to the appointments and you have to enter the reason and the appointment difference in calendar days, as well. 
 +    * **CR Ressource (Yes, Reason):** Here, you must set the feature "​Yes"​ in changes to the resources and you have to enter the reason.
 +    * **CR Goal (Yes, Reason):** Here, you must set the feature "​Yes"​ in changes to the target and you have to enter the reason.
en/handbuch/kapitel_2/2.02.13_projektaenderungsantrag.1259933111.txt.gz · Last modified: 2019/10/25 14:09 (external edit)