Differences

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

--- en:handbuch:kapitel_2:2.02.07_anordnungsbeziehung [2009/09/09 14:38]
192.168.0.54
+++ en:handbuch:kapitel_2:2.02.07_anordnungsbeziehung [2019/10/25 14:11] (current)
@@ Line 1: / Line 1: @@
 [[2.02.06_trendtermin|{{|previous}}]] [[en:handbuch:handbuch|{{|Home}}]] [[2.02.08_fertigstellungsgrad|{{|next}}]]
-====== 2.02.07 Order Relationship ======
+====== 2.02.06 Project Timing/Order Relationship ======
-The order relationship menu (earlier jump sequence) administers the temporal relationship between two different work packages and/or milestones, which belong to the same projects. The here defined jump sequences and/or order relationship between the predecessor and  successor, are the basis for the networked/linked Gantt charts (see also document type project analysis in the analysis module) and are for the extended/advanced planning possibilities on the basis of the network planning technique (see also  [[4.2.1.2 Projekt Planning]]) (siehe auch  [[4.2.1.2 Projektplanung]])  .
+The **Project Timing/Order Relationship** form (earlier jump sequence) administers the temporal relationship between two different jobs and/or milestones, which belong to the same projects. The here defined jump sequences and/or order relationship between the predecessor and  successor, are the basis for the networked/linked Gantt charts (see also document type project analysis in the analysis module) and are for the extended/advanced planning possibilities on the basis of the network planning technique.
-**Tip:** For more on this subject see chapter 4.2.05 Milestones and Order Relationships  4.2.05 Meilensteine und Anordnungsbeziehungen.
+**Note**: The jump sequences can be defined in the project using the action "01 - Project Planning" .
-Note: The jump sequences can be defined in the project with help of the action "01 - Project Planning" .
+{{:en:handbuch:kapitel_2:project_timing.png|}}
-{{:handbuch:kapitel_2:sprungfolge.gif?direct}}
+The form consists of the following elements:
-The menu consists of the following elements:
+    * **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.
-    * **Predecessor:** This field defines the predecessor for which the jump sequences apply. Only work packages and milestones which belong to a selected project, can be asigned.
+    * **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.
-    * **Successor:** This field defines the successor for which the jump sequences apply. Only work packages and milestones which belong to a selected project, can be assigned.
+    * **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.
-    * **Jump Sequence:** The field jump sequence determines the chronological jump sequences of the work packages 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 work package, the second to the successor work package. Practically, 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.
+    * **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.
-    * **Minimum Interval:** Considering the jump sequence, this value specifies the minimum idle time in days between the work packages. Example: At least two days (work days in a 5-day week) should lie between discussing the concept and creating the specification sheet (Pflichtenheft).
+    * **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.
-    * **Maximum Interval:** Considering the jump sequence, this value specifies the maximum idle time in days between the work packages. Example: Three days at the most (work days in a 5-day week) should lie between discussing the concept and creating the specification sheet (Pflichtenheft).
+    * **Note:** This field is designated for comments.
-    * **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.
-    * **Comments:** This field is designated for comments.

Projectile-Online-Handbuch

User Tools

Site Tools

Differences

Page Tools