I often review P6 databases and I am horrified that they neither Summarize their database nor understand the importance of this function or understand the P6 functions that affect how Summarized data is calculated and where it is viewed.
Why Summarize Projects
When Projects are not Summarized then the information from unopened P6 projects seen in the Projects, Activities and Tracking windows will be blank when the project has never been Summarized or out of date if the project has been updated since it was last Summarized.
Aim
The aim of this paper is to explain what the author has found by experimentation:
Summary
When a database is not Summarized and/or if users do not understand all the functions associated with Summarization then resource data read from unopened projects in views such as the Projects, Tracking and Activity windows will either be blank, or will be incorrect, or will not display data to the level required by users.
The sample data used in this example has three projects with three WBS Nodes and three activities being assigned the one resource with a Units per Time period of 8 hours per day and an availability of 16 hours per day.
What summarisation does
The resource data in the Activities window is not linked to the Projects window or Tracking window data, except when a project is open. Thus the data in the Projects and Tracking window of projects that have not been Summarized data is different when a project is open or closed.
The project resource data in the Projects window and Tracking window is read from a “Summary table” that is populated when either:
When all three projects are open the Summary resource data is correct in the Projects window, but note the Total Activities (number of activities) is not Summarized.
When SUMMARIZE 1 project is open then only that project’s data is correct, the other two projects are now showing zero costs or resource data.
When SUMMARIZE 3 project is Summarized and SUMMARISE2 is open then only those two projects summary data is correct and SUMMARIZE 1 data is not correct.
NOTE: The project was Summarized on 28 April 2020, so now the Total Activities is correct but P6 shows an incorrect Last Summarized Date of 20 April 2010! This appears to be a glitch in the software.
Earn 25% commission when your network purchase Uplyrn courses or subscribe to our annual membership. It’s the best thing ever. Next to learning, of course.
Projects or a database are summarized in two ways:
The author recommends that every database is Summarized every night using a Job Services.
These topics are covered later in this paper:
When the User Preferences, Startup Filters, Resource Summary Data option is NOT checked then the Summary table resources’ spread data is not loaded and resource spreads are not available in the Tracking window when this is not checked.
The software took a little longer to load as it is not loading summary data and the author's small database took 37 seconds to load unchecked and 43 seconds to load with it checked. There could be significant time savings with a large database.
The Projects window, Setting tab, Summarized Data determines how many levels of the WBS is saved in the Summary table and available in the Tracking window. If Summarize to WBS Level 2 is selected then only the Project Node and the first WBS Node may be seen and the Project Node is considered by P6 as the first WSB level 1. When set to zero all levels are Summarized.
When SUMMARIZE 3 is Summarized with the setting of Summarize to WBS Level 2, as shown on the right.
Then when the project is closed you will only see WBS Level 2 in the Tracking Window. But when the project is open you will see all three levels.
The Admin Preferences, Options, Specify the interval to summarize and store resource spreads decides at what time interval that data is save in the Summary table in weeks, months or By financial period.
The following is an example of how this works:
The User Preferences, Resource Analysis, All Projects options allows the reading of the Summary table resource spread data for unopened projects.
Therefore, projects must be Summarized for this to give accurate data.
When:
Then when the Tracking window is opened:
When:
Then when the Tracking window is opened:
When:
Then when the Tracking window is opened,
When all Projects are opened the histogram displays an overload as there are three activities at the same time and the resource has an availability of 2 (16 hours per day).
When:
When a User is:
The following recommendations are made:
If you want to learn more about Planning and Control with Microsoft Project, please check out my online course here.
Leave your thoughts here...
All Comments
Reply