Perceptive Retention Policy Manager

Document retention in Perceptive Content is one of those things that you probably said “I’ll deal with later” during your initial implementation. Now it’s five years later, and your servers are overflowing with documents. Let RPI show you how to use Retention Policy Manager to make retention simple. Learn how to set up document phases to automate document deletion, move them to alternative (cheaper) storage, and migrate OSMs!

John Marney:
My name is John Marney and I’m the Manager of Solution Delivery here for the Imaging practice here at RPI Consultants. This is Alex Lindsey, he is our Senior Solution Architect, and we’re going to be talking about a maybe little-known but often-considered module for Perceptive Content called Retention Policy Manager.

Couple record keeping or administrative items real quick. In your GoToWebinar, there’s a bar that runs down the middle that splits the video from the presentation. If you mouse over that you can drag that either way, so if really want to see more video and our beautiful faces you’re welcome to, but the presentation is really what you’re after.

Another item, the slides, or the slide deck, will be available and sent to you after this presentation, so don’t feel like you have to screenshot everything you see. As well, a high quality recording of this will be available on our YouTube here within the next week or two. We have a bunch of webinars coming up so the editing will take a little bit of time. Finally, you’re free to use the questions window in the GoToWebinar to ask questions. We have a moderator standing by to ask them during the presentation or after.

Let’s get this kicked off. A little bit about RPI first. We have been working Perceptive and Kofax products for around 16 years. There are roughly 15 members in this practice, in this team. However, the remainder of RPI Consultants focuses on Infor Lawson Consulting. That’s around 60 people. Our headquarters are currently in Baltimore, we have an office in Tampa, and of course the imaging team, that’s us, are based here in Kansas City.

What do we do? For Perceptive Content we do a lot of eForm and iScript development. That’s both for enhancing existing implementations or adding new implementations. That also includes whole workflow designs or redesigns, brand new processes that you want to implement. We do a lot of upgrades and health checks, as I’m sure many of you are familiar with right now as 6.7 going end of life very soon. Upgrades are becoming a very hot commodity.

We also do a lot with Kofax and Intelligent Capture and any other OCR platforms that will work with these products. We do a lot of migration system to system or from legacy systems. We also support clinical and HL7 implementations.

One quick plug, come see us at our booth at Inspire. It’s in Nashville this year, and we are platinum sponsors. We’d love to see you if you’re there. You can also schedule some time to meet with us to discuss whatever’s on your mind, anything about your system or not at all. To do so, go to rpic.com/inspire.

Okay. Launching into Retention Policy Manager, or RPM. What is Retention Policy Manager? Well, it is a software add-on to Perceptive Content. It’s one of those things that many people own but don’t always know how to configure or use, and it’s often asked about. Many people will go through their initial implementation, especially a big accounts payable implementation, and they know they need to consider retention, but it’s not really on the front of their mind. Three, four, five years down the road, we’re starting to see our usage of disk space start to balloon and we’re thinking, “How do I get rid of some of these things?”

It is for … Retention Policy Manager is exactly for that purpose. It’s for the systematic removal or transfer of documents. There are various removal methods or transfer methods that you don’t have to delete documents. You can choose through half the life cycle to move them to cheaper storage. It is separately licensed. It has its own agent. It’s typically installed on the primary co