

The correct number of “open ends” would of course be two the first activity will not have a predecessor and the last one will not have a successor. As you should know, the Schedule Log has a topic called “Warnings” that discusses, among other concerns, the number of activities that are missing predecessors or successors. I always check the Schedule Log before I publish a schedule. The WBS Summary is the only activity type in Primavera P6 that works sans logic.

On the surface, this seems like a great idea because logic is not required.

To review, the WBS Summary calculates its Start and Finish date (and therefore, duration) from all other activities that have the same WBS code. While I consider my self pretty adventurous when it comes to Primavera P6, I admittedly have little use for one particular activity type, the WBS Summary.
