primavera p6 calendars have a big problem and it becomes a major pain in the butt as your list of calendars grows and grows.
as planners and schedulers, we are tasked with managing mountains of project data everyday; progress updates, scenario projects, reports, reports and more reports. data can quickly take over your life if you’re not careful. and you don’t have time for that.
that’s why a good system for organizing aspects of your project and project data goes a long way.
my biggest frustration with primavera p6 calendars is the global calendar register and it’s constant unruliness. (if you have a nicely organized global calendar register, send me a screenshot because i’d like to see it.)
for most, me included, the global calendar register is usually an unorganized dump of any calendar that anyone ever thought of, mostly with unintelligible names.
and then, of course, there are the calendar copies.
why do we have 6 copies of calendar “qj03-global” numbered -1 to -6? i see p6 global calendar registers with 100’s of calendars everyday, with no clear way to discern which global calendars were meant to be there, which were artifacts of project imports, and which can be reused for a future project.
if your primavera p6 calendar register looks like alphabet soup, then here are some seriously easy tips for helping to get your global calendar register organized.
organize primavera p6 calendars with a simple prefix
having a standard global calendar naming convention is the best way to get your primavera p6 calendars under control.
primavera will let you name calendars anything you want. but since the global calendar list can only be organized alphabetically, adding a prefix to your calendar names is going to quickly organize the list. here are some ideas for new naming convention:
- dept-calendarname
- yy-calendarname
you can add a department acronym to group all departmental calendars together. alternatively, grouping them by year of creation is an option as well with a yy prefix.
you can also combine both concepts for something like this:
- dept-yy-calendarname
organizing p6 global calendars by project
many companies have given up on trying to reuse global calendars for other projects, which was how the designers meant them to be used. primavera p6’s global calendars are too prone to editing by users to allow for re-use on other projects.
project calendars have proven too difficult to work with as well and many companies have also given up on trying to focus there – mainly because importing projects in your database always adds global calendars to your register from those imported projects.
but all is not lost. use a projectid prefix to help organize calendars, like so:
- projid-calendarname
this tip alone will solve many issues for organizing your primavera p6 global calendar register. combine this strategy with our first tip will yield even better organization.
- dept-projid-calendarname
- yy-projid-calendarname
use this simple calendar audit layout
i’m a big proponent of keeping things organized, but i don’t want to spend hours doing it. but taking 5 minutes to purge and organize every few months goes a long way.
this simple calendar layout will show you which primavera p6 calendars are being used and which are not assigned to any project. use it to find and delete any calendars that are not assigned to projects.
these are likely artifacts from imported projects that have been deleted. unfortunately, p6 global calendars don’t get deleted when their originating project is deleted.
- open all projects in your database. (not recommended in p6 eppm).
- setup the group and sort as follows. make sure “hide if empty” is not checked.
- click ok.
look for any calendar entries with no projects listed underneath them.
you can see quite a few in the screenshot above. those entries represent global calendars that are not assigned to any project. i recommend you delete these primavera p6 calendars. you’ll see a much cleaner global calendar register as a result.
wrap-up
i’ve heard that improvements are coming for primavera p6 that address the issues around lingering enterprise data artifacts during importing of .xer files. i’m looking forward to seeing these, possibly in 2014. it will take use one step closer to having a project database that is easier to organize and requires less time to maintain. now, time to get back to scheduling, what primavera p6 was designed for.
