then make a decision: export it, \u00a0delete it, or archive it.<\/p>\n
cleaning things up simplifies<\/em> them and calms the mind. the next time you log in, you’ll be able to get around much faster and easier. just do it!<\/p>\n <\/p>\n say it with me… “i will stop making everything global. i will stop making everything global. i will….”<\/p>\n you get the point.<\/p>\n use p6’s ability to store data inside a project<\/a>. items to focus on: global calendars, activity codes, global layouts.<\/p>\n these 3 data objects hardly ever get created as “project” objects when in a lot of cases they could. look at your current project or the last project you completed. 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.<\/p>\n <\/p>\n 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.<\/p>\n if you have more than 2 super-users, then i know why your db is nightmare…<\/strong><\/p>\n ready to know why?… because super-users create anything they want, whenever they want it.<\/p>\n identify one administrator and one backup administrator. make these folks your gatekeepers and your data integrity managers.<\/p>\n why would you make everyone in your company a windows domain administrator? same thing goes for p6.<\/p>\n <\/p>\n saunter up to your friendliest neighbourhood database administrator, and have them make a copy of your production database.<\/p>\n declare it your sandbox – a place to create any projects you like, copy projects to your hearts content and generally make a mess….<\/p>\n …so you don’t make a mess of your production database.<\/p>\n a sandbox database is the best planning playground you could ever imagine!<\/strong><\/p>\n use it for training new users, doing scenarios and previewing xers from other companies.<\/p>\n <\/p>\n curious question: if you were in charge of getting a new accounting system set up for your company, would you install it, login as the administrator and start logging expense transactions (all of this in the span of say, 15 minutes)?<\/p>\n no, you wouldn’t.<\/strong><\/p>\n you’d take some time to plan your set up before you started booking expenses. you’d ask: what accounts should be setup? what invoice templates? what workflow would be best? who should have access to what parts of the software?<\/p>\n so why do this with primavera when it’s clearly an enterprise<\/em><\/strong>\u00a0project planning tool. (keyword: enterprise<\/em>)<\/p>\n you wouldn’t set up an enterprise accounting system in 20 minutes and start logging expenses… so why do the same thing with your enterprise project management system?<\/strong><\/p>\n many organizations install p6 and start planning right away, hoping to take advantage of the powerful features of the software, but with no thought into a proper setup of:<\/p>\n a proper implementation of p6, like the ones we do with small to medium-sized companies everyday, would cover the design of these and other important data objects.<\/p>\n and it would layout a strategy to keep your database organized.<\/p>\n want implementation advice? contact me<\/a>.<\/p>\n <\/p>\n the problem with importing xer files from other companies is that their global data comes along for the ride. any calendars, 世界杯时间比赛时间
, codes, etc. used in a project go with the project when it is exported and end up in your database. so global data from other companies’ pollute your p6 database every time you import an xer file they send you.<\/p>\n this is the biggest reason p6 databases become a data-entangled nightmarish mess!<\/strong><\/p>\n remember that sandbox database you were going to setup? this is where it becomes invaluable.<\/p>\n import your xers to your sandbox database, cleanse the imported project’s associated global data, then re-export and import to your production db.<\/p>\n it sounds like a lot of work but you can automate this process with tools like xer manager<\/a> or even using global changes.<\/p>\n <\/p>\n try at least one of the suggestions above and i’m sure you’ll be taking proper steps in the right direction.<\/p>\n stay tuned for this series on primavera p6 databases and data cleansing as we’ve got more great tutorials to share on this topic.<\/p>\nstop making everything global!<\/h2>\n
audit your primavera super-users<\/h2>\n
have somewhere to play<\/h2>\n
get implementation help<\/h2>\n
\n
don’t import directly to production<\/h2>\n
what next?<\/h2>\n
![\"training](\"https:\/\/no-cache.hubspot.com\/cta\/default\/297539\/d5a50117-6be5-4dc0-86bd-98dab5a4a234.png\")
<\/a><\/span>