Sometimes it might be helpful to take an activity and split it into two. Any un-actualized activity can be split. If an activity is partially actualized (or in-progress), it can be split at the data date (separating the finished portion from the in-progress portion) or within the in-progress portion itself. Fully actualized activities, however, may NOT be split.
To split an activity, right-click an activity and select . The Split and Link Activity window opens.
The Split Date
The Split After Date defaults to where the mouse was right-clicked while hovering over the activity. If PolyTime is enabled and the schedule time unit has been set to less than days, the split after time will also default to where the mouse was right-clicked while hovering over the activity.
Descriptions and IDs
The two new activities will inherit the original description with – 1 and – 2 appended respectively. They will be left blank if the original activity had no description.
If the original activity contains an ID, the two new activities will inherit the original ID with _ 1 and _ 2 appended respectively.
Converting to a Delay
The second activity may be converted into a delay/gain as long as the original activity hasn’t had any resources assigned to it, and as long as it doesn’t have any embedded nodes to the right of the split after date. To make the conversion, check the corresponding checkbox.
Resource Assignment
The resource assignment for split activities will depend on the distribution chosen.
If no resources have been assigned, the resource assignment section will be disabled.
If the original activity has 10 widgets assigned per day,
- And the first option is chosen, 10 widgets will be assigned per day to the first activity
- And the second is chosen, 10 widgets will be assigned per day to the second activity
- And the third option is chosen, 10 widgets will be assigned per day to the first activity and 10 widgets will be assigned per day to the second activity
If the original activity had 10 widgets assigned per duration,
- And the first is chosen, 10 widgets will be assigned per duration to the first activity
- And the second is chosen, 10 widgets will be assigned per duration to the second
- And the third option is chosen, the assignment will depend on the split date: if its duration were split in half, 5 widgets would be assigned per duration to the first activity and 5 widgets would be assigned per duration to the second activity. If its duration were split after 4/5, 8 widgets would be assigned per duration to the first activity and 2 widgets would be assigned per duration to the second activity.
When allocated proportionally, resources will be assigned in whole numbers, with the first activity’s quantity being rounded-up and the second activity’s being rounded-down.
When finished, click OK to close and save the window.
NetPoint will automatically split the activity and maintain the links directly into and out of the original activity, while creating a new finish-to-start link between the new activities.
Embed Handling for a Split Activity
If the original activity has an embed before the split date, it will be part of the first activity. If the embed falls after the split date, it will be part of the second activity. Either way, the embed’s date will always be maintained. The offset may or may not be recalculated, depending on its type and behavior. Any unlinked embeds will be deleted.
Display of the Split Activities
Both activities will maintain the original bar color and node color. Any display settings will also be maintained (e.g. whether or not float, drift, etc. are turned on). However, custom positioning will be maintained only for the first activity. The second activity will be reset.
Annotations, Targets, Hammocks & Codes
Annotations will remain with the first activity, with the placement being held constant to keep the annotation in the same location.
Target information will also remain with the first activity; the second activity will be treated as a new activity.
If the original activity was a hammock member, both split activities will remain members.
Both activities will also inherit any codes assigned to the original activity.