One copy of the final schedule may be kept for a period of six months to one year after delivery, but that is one copy per project. If a project manager makes a total of 100 global changes per month, at an average of three global changes per day, this could account to more than 24,000 pages over the course of 2 years, which results in 24,000 extensive copies of the project schedule in the Primavera P6 database.Īs a result, project managers need to delete the extra copies of each schedule upon the successful completion and delivery of each project. However, project managers can avoid the potential loss of data by creating a backup copy of the schedule each time, when making a global change. Whenever a project manager’s tasks are delayed or incomplete, the schedule cannot be returned to the previous state. Remove Extra Copies of Schedules If Previously Saved The best way to avoid this problem is to rename the abbreviation of each aspect of the project with a month and the year, in addition to the existing abbreviations identification.
However, multiple projects with the same abbreviation may actually cause a project manager to accidentally use the constraint and resources for one project in another project schedule mistakenly. For example, completing the slab of cement concrete for the first floor maybe abbreviated with one SLB. Project managers have a tendency to abbreviate titles within the names of activities, rules, schedules, and tasks. Rename Tasks, Activities, and Milestones With Appropriate Comment Follow these four steps to clean up your Oracle Primavera P6 database and improve your production through Primavera P6 schedules. However, a project management database within the Primavera P6 database can grow so large that it causes the computers to run slow, perform basic functions at a slower rate, and is incapable of being useful due to repetitive, confusing terminology and abbreviations and names.
This is not necessarily a bad thing, as some functions and global changes may actually be used in future projects. Over time, your Primavera P6 database will grow and become tough to manage at times.
0 kommentar(er)
