Skip to main content

We were recently asked what are archiving process was and we were not sure why/when archiving makes sense?   Does anyone have suggestions about what archiving criteria should be for projects and what the frequency should be?

@MGMullen - we archive on an annual basis.  In Portfolios it is a time consuming process, thus why we only perform once a year.  We worked with key stakeholders to identify how far back data should be maintained, which was about any inception to date reporting needs. So I think every company could be different depending on business rules. We do this to move out projects that are no longer needed for financial reporting and thus can be removed.  

Note; You cannot report on items in the archive database so be cautious on how much and how frequent you archive. There is an ability to restore from the archive, which is nice, but you want that to be an exception and not a common practice. 


If any work is being archived and we are unarchiving it, what can we do to the work to stop it from being archived again?


@e5735558  - I believe the first option would be to ensure it is not selected from the list of work when archiving.  Archiving isn’t automatic, that I’m aware of, and instead you choose projects from a list based on a date & branch of the WBS. 

Here at NASCO we use a lot of Planview’s web services and so we have a process where we have criteria coded that pulls back a list of projects that meet that criteria. This list of projects is reviewed by Finance (as they are our largest stakeholder) and identify if any should not be archived.  We then move everything that is approved to be archived to a new branch in our work hierarchy.  This way when we are doing the archiving process we are only looking at that one branch in the work hierarchy so no projects are accidentally archived.


Reply