dkfasad.blogg.se - Backup primavera p6 oracle database

#Backup primavera p6 oracle database how to#

When this is not a formal part of the closeout process, it often gets missed. It is easy to add a Project Level User Defined field for “Archive Date” in P6 and fill in this date as part of the project closeout process while the contractual requirements are fresh in everyone’s mind.

#Backup primavera p6 oracle database how to#

How to track the date to archive the P6 project? Monthly backup schedules are priceless when you are in a claims situation, so think long and hard about whether these should be kept. Typically, there are many what-if and backup copies of the project as well, and the project team should look at which of these are required.

(Alternatively, the key project information could stored be in a datawarehouse like EP-datawarehouse rather than keeping the entire project.)Īll of these factors can be difficult to track after the fact, so we normally recommend that clients decide how long a project should be kept as part of their formal project closeout process.

If the project is needed for portfolio reporting such as fiscal year performance or program reporting, you need to keep it to avoid changing all of your reporting metrics.

You should also plan on keeping the file for at least as long as any contractual obligations exist, such as warranty periods or post project audit periods.

If you're actively working in or referring to the file (such as in a claims situation or if you are building your next TA plan), you obviously don’t want to archive it.

First and foremost, if there are regulatory or corporate governance requirements around project documents, you need to be in compliance with those requirements.

How long you should keep a project file depends on a number of factors: I hate to start off with “It Depends” ( Nicole's favorite), but it really does. How long should you keep a P6 project file?