Unfortunately, many companies have not set up their security settings or a strict methodology for creating layouts, calendars, or activity codes. This tends to cause chaos in your database. Many times, we hear complaints about how they have so many duplicate projects, duplicate calendars, lists of layouts and so on. So what can you do to keep your database clean? Follow these three easy steps to make sure you never run into these problems again:
1. IMPLEMENT PRIMAVERA P6 USING CPM SOLUTIONS’ CONSULTANTS
CPM’s consultants are knowledgeable when helping clients implement Primavera P6 for their company. Implementing P6 entails setting up the EPS, OBS, security settings, and much more. Why is this useful? You will start with a fresh database that is secure, organized, and ready-to-use.
2. SET-UP YOUR SECURITY SETTINGS
Not every user should be a Superuser. If you establish a proper Organizational Breakdown Structure with secure settings, then you’ll be off to the right start. Resources should have access and the ability to edit information for the projects that they are assigned to and no more. This allows administrators to control what data can be modified and which cannot. For example, administrators should be the only P6 users capable of creating Global Activity Codes. If not, then your database would be filled with Global Activity Codes that are only relevant to a specific project.
3. SET UP A STANDARDIZED METHODOLOGY FOR CREATING LAYOUTS, CALENDARS, AND ACTIVITY CODES
Set up a standard methodology by identifying global, pre-defined calendars, codes, and layouts that P6 users can personalize for projects and resources. This will eliminate the unnecessary build-up of data across the enterprise and keep your database clean. P6 users, except for administrators, should not be able to create Global data. If you already have a cluttered database, then it’s time for a wake-up call for all of your users. Let them know that new best practices and methodologies will be in place on a specific date and make it happen! Give users enough time to save their data as project and resource-specific and then clean up the database on that date. Set pre-defined standard layouts, codes, calendars, and more in your database so that the same basic data is available at the start of the project.
Keeping a strict database can be difficult for companies from 2-1000 users because everyone wants to see their layouts or codes at the top of long lists. If you set-up the right security and methodologies from the beginning, or even during projects, then you’ll be able to monitor and maintain a clean database for the future.