User Tools
en:handbuch:kapitel_2:2.02.07_anordnungsbeziehung
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
en:handbuch:kapitel_2:2.02.07_anordnungsbeziehung [2012/03/27 11:51] 192.168.0.65 |
en:handbuch:kapitel_2:2.02.07_anordnungsbeziehung [2019/10/25 14:11] (current) |
||
|---|---|---|---|
| Line 13: | Line 13: | ||
| * **Job A:** This field defines the predecessor for which the jump sequences apply. Only jobs and milestones which belong to a selected project, can be assigned. | * **Job A:** This field defines the predecessor for which the jump sequences apply. Only jobs and milestones which belong to a selected project, can be assigned. | ||
| * **Job B:** This field defines the successor for which the jump sequences apply. Only jobs and milestones which belong to a selected project, can be assigned. | * **Job B:** This field defines the successor for which the jump sequences apply. Only jobs and milestones which belong to a selected project, can be assigned. | ||
| - | * **Project Order:** The field Project Order determines the chronological jump sequences of the jobs of the same project. Altogether, there are four standard relationships to choose from: Start-Start, Start-End, End-Start, End-End. The first criteria relates to the predecessor job, the second to the successor job. Actually, only the process relationship (Ablaufbeziehungen) start-start (test can only start, when development has started) and end-start (development can only start when the specification has been completed) has relevance. | + | * **Project order:** The field Project Order determines the chronological jump sequences of the jobs of the same project. Altogether, there are four standard relationships to choose from: Start-Start, Start-End, End-Start, End-End. The first criteria relates to the predecessor job, the second to the successor job. Actually, only the process relationship (Ablaufbeziehungen) start-start (test can only start, when development has started) and end-start (development can only start when the specification has been completed) has relevance. |
| * **Min Time:** Considering the jump sequence, this value specifies the minimum idle time in days between the jobs. Example: At least two days (work days in a 5-day week) should lie between discussing the concept and creating the specification sheet. | * **Min Time:** Considering the jump sequence, this value specifies the minimum idle time in days between the jobs. Example: At least two days (work days in a 5-day week) should lie between discussing the concept and creating the specification sheet. | ||
| * **Max Time:** Considering the jump sequence, this value specifies the maximum idle time in days between the jobs. Example: Three days at the most (work days in a 5-day week) should lie between discussing the concept and creating the specification sheet. | * **Max Time:** Considering the jump sequence, this value specifies the maximum idle time in days between the jobs. Example: Three days at the most (work days in a 5-day week) should lie between discussing the concept and creating the specification sheet. | ||
| - | * **Days per Week:** Here it can be controlled if the weekends should be defined as idle time. If the value is set to 5, the idle time is only Monday through Friday. If this field is not occupied, the default value 7 is used. Example: There should be 2 days between the first and second coat of paint for a door. It is not important if this drying period is in the week or on the weekend => Days per Week = 7. | + | * **Days per week:** Here it can be controlled if the weekends should be defined as idle time. If the value is set to 5, the idle time is only Monday through Friday. If this field is not occupied, the default value 7 is used. Example: There should be 2 days between the first and second coat of paint for a door. It is not important if this drying period is in the week or on the weekend => Days per Week = 7. |
| * **Note:** This field is designated for comments. | * **Note:** This field is designated for comments. | ||
en/handbuch/kapitel_2/2.02.07_anordnungsbeziehung.1332841882.txt.gz · Last modified: 2019/10/25 14:09 (external edit)
