Cleanse Schedule Dialog Box
Use the Cleanse Schedule dialog box to specify how you want the schedule to be cleansed.
- Cleared — None of the items for that option are included in the cleanse.
- Selected — All items for that option are included in the cleanse.
- Shaded — Some, but not all, of the items for that option are included in the cleanse.
When you click a cleanse option, the list of related issues displays in the right pane, allowing you to include all, none, or only certain items.
You can include or exclude individual activities. In addition, lags (durations on relationships) can either be removed or converted to activities.
The numbers in the parenthesis next to each cleanse option tell you how many items you have included for that option. For example, (2/4) means that you have included two out of four possible items.
When you run a schedule cleanse, the system creates a scenario instead of updating the source schedule file.
Field | Description |
---|---|
Redundant Logic | Lower redundancy Index to zero by removing unnecessary (redundant) links. |
Hard Constraints | Removes all hard constraints (Mandatory Start, Mandatory Finish, Must Start On and Must Finish On) from the schedule. |
Soft Constraints | Remove all soft constraints (Finish On or After, Finish On or Before, Start On or After, Start On or Before, As Late As Possible) from the schedule. |
Remaining Leads | Removal of negative lags (leads) from the schedule. This results in a more realistic forecast. |
Remaining Lags | Elimination of positive durations on relationships. Achieve this either by removing the lags or converting the lags to activities.
Acumen defines a remaining lag as follows:
|
Links to Summaries | This feature converts relationships that involve summary activities into equivalent relationships by connecting only non-summary activities. This is helpful because only "real" work in the schedule has relationships and summary activities can potentially be removed.
If a relationship of the same type is already being created, then the existing relationship is kept and its lag is updated if the newer lag is bigger. |