Open Admin -> Users and if you find more than 2 super-users, strongly consider revising access for anyone that does not require it to perform their job. Could those Calendars you created have been Project Calendars? You can easily keep your db’s Global objects list lean by creating objects as local to a project. Look at your current project or the last project you completed. These 3 data objects hardly ever get created as “Project” objects when in a lot of cases they could. Items to focus on: Global Calendars, Activity Codes, Global Layouts. Use P6’s ability to store data inside a project. Say it with me… “I will stop making everything Global. The next time you log in, you’ll be able to get around much faster and easier.
Then make a decision: export it, delete it, or archive it.Ĭleaning things up simplifies them and calms the mind. I guarantee those 30 minutes will be the most productive you’ve had all week! Seriously, take 30 minutes with a co-worker and go through your P6 database to identify: old data to keep, data no longer in use, redundant data, unknown or mystery data. Thankfully, I’ve got a few ways you can use immediately to start taking back control to get your database looking spiffy and new again.
You do your work, but you want to get out of there as quickly as you can. You may act like these don’t bother you, but somehow logging in to P6 in the morning feels sort of like using the restroom at a crowded arena. Many of you work in Primavera P6 databases that are a complete nightmare – hundreds of global calendars, duplicate resources all over the place, redundant codes and more copies of projects than anyone should ever need in their lifetime. This is the first part in our series on Primavera P6 databases and data cleansing.