In the screen shots below you can see what activity information I have chosen to copy and the new prefix I have selected for the Activity IDs:
I may need to create a new WBS or Activity Code for the copied activities so that they stay grouped together. I don’t worry too much about where they should be pasted right away. The first step is to highlight the activities that are being copied and then paste them. In most situations I do want to replicate the durations and logic. This has the added benefit of creating a new section in the WBS for the new activities while they are being pasted.īefore copying the activities it would behoove us to make sure the durations and logic are complete so that we can also copy this information as well. Most of my activity relationships will be defined by proximity, not the type of work.Īs an alternative, we can copy an entire section of the Work Breakdown System and paste it elsewhere. Some schedulers use the prefix to indicate the type of work, but when I am adding relationships I want the activities in the same location to have the same prefix. I want the submittals to have the same prefix, the Stage 1 activities to have the same prefix, and so forth. Nearly always my prefixes are based on locations. When this activity is copied for the second floor the new prefix (FLR2) tells us the location while the original suffix (1000) indicates the type of work. Let’s say that Activity ID FLR1_1000 is layout on the first floor of the building. In the Project Default settings we cannot leave the prefix for new activities blank, and why would we? Copying activities without the ability to assign new prefixes would frankly not be much fun. P6 really wants us to use prefixes in our Activity IDs. Besides just copying a bunch of activities, however, we also need to consider how the Activity IDs can save us time. The northbound lanes are copied and used as the basis for the southbound lanes. The first floor logic is copied and used as the basis for the second floor. I have not truly built a baseline schedule from scratch for quite a few years because I am always copying part of the logic. In the baseline schedule the latter example is how we save time. Traditionally we develop fragnets for two reasons: (1) to represent additional work that is not part of the original scope, or (2) to represent repetitive work in the original scope. A fragnet may be just a few activities, or dozens. If we think of the entire schedule as being a network diagram then a fragnet is a sub-network. Here are my top five favorite P6 tricks based on 30 years of experience using Primavera software: 1. And since one of my most recent training clients actually builds commercial fishing boats I suppose the analogy is even more appropriate for them! While there are also several time-saving tricks for updating a schedule, today I am going to focus on the building of a brand new schedule. Primavera P6 will save you a boat-load of time while building a schedule if you know where to look.
0 kommentar(er)
