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.

Hint: You can find more on this topic in the section 4.3.08 'record project change'.

The mask contains the following elements:

On the “Master data” tab:

• 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).
• 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 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.
• 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 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).
• 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. The employees are managed in the mask employee.
• Note: This field can be used for comments on the project changes.

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.