Anda di halaman 1dari 4

Sequence Logic

What

A projects schedule is its logic network: the order in which activities occur. SureTrak uses the Critical Path Method (CPM) to create a schedule. Sometimes a users project has activities that happen out of sequence. SureTrak can handle this situation in two different ways. Retained Logic and Progress Override: These two options affect how activities out of sequence are progressed. Retained Logic: Retained logic dictates that an out of sequence activity cannot be completed until all of its predecessor activities have been completed. All predecessors must finish before any remaining duration can be scheduled. This may result in progress displaying past the data date if activities are performed out of sequence.

Progress Override: Progress override ignores the logic relationship to the out of sequence activity and allows the activity to complete even though the predecessor activity is not complete. An activitys remaining duration can be scheduled at earliest possible date (usually data date) if it is started out of sequence. Relationships to predecessors are maintained display-wise but not used for scheduling.

How

Select Tools, Schedule and choose between Retained Logic or Progress Override.

Out-of Sequence Logic in Scheduling Diagrams

The calculations for the activities that have an AS are: Retained Logic: EF = Internal Early Start + duration 1 Progress Override: EF = Data Date + duration 1 The data date is used because the predessor relationship is completely ignored for the progress override setting.

Out-of Sequence Logic in the Bar Chart View

These are two examples of how out of sequence logic can show up in a schedule: Example 1: Completed Activities out of Sequence

Retained Logic

Note that the third activity must wait until ALL the predecessors in the chain are completed. It is being delayed until the first activity is finished.

Progress Override

Example 2: Activities in Progress out of Sequence

Retained Logic

Note that the remainind duration of the second activity must wait until all the predecessors in the chain are completed. The work on the second activity will resume after the first activity is finished. This shows progress past the data date. Progress Override

Float Settings
Open Ended Activities (No Successors) Select the Tools, Schedule option from the menu. SureTrak offers two ways to show open ends: Critical or Non-critical. Non-critical is the default setting. Suretrak will allow activities with no successor to float to the end of the project.

Selecting critical will cause each open-ended activity to act as though it had a mini project finish date. The backward pass for an open-ended string will begin with the early finish date of the activity instead of the project finish or must finish by date. In essence, this sets all open-ended activities to 0 Total Float. This may also make any predecessors to the open-ended activity to be critical or at least decrease a portion of their float.

Common Logic Problems


Lag Time Effect on Float

Lag will often take away some or all of the free float between an activity and its successor. Lag could also cause Float to be increased or decreased between other activities.

Actuals Past the Data Date

Problem: Put Actual Dates on activities because user wants to determine the starts
and finishes but Suretrak calculates its own dates.

Solution: Use relationships and/or constraints.

Problem: User updates the schedule and does not move the data date.

Solution: Move Data Date first and then report progress.

______________________Network Statusing Workshop_____________________ Written:

1. What problems can arise from entering actual dates past the data date?

2. Describe why adding lag in a relationship between two activities does not always
decrease the Total Float in the schedule.

3. When would a user want to use Progress Override as opposed to Retained Logic in
their schedule?

4. I updated my project and now all the relationships in the project are being ignored.

Most of the unfinished activities are being scheduled at the Data Date rather than after their Predecessors. Whats wrong?