Professional Documents
Culture Documents
ABSTRACT
If you use (or planning to use) Oracle URM, but find it somewhat clumsy or confusing chances are you didnt get the proper product introduction. Stop by this session for a live demonstration and crystal-clear explanations by the author of The Oracle UCM Handbook, that will dispel confusion and install clarity on Universal Records Management, Physical Records Manager and The Records Manager Enterprise Edition.
INTRODUCTION
Hi, Im Dmitri Khanine from ECM Solutions, elite special forces unit focusing almost exclusively in Oracle UCM space. Im the author of The Oracle UCM Handbook and I also run the Independent Oracle UCM Knowledge Center. Weve just completed another large Oracle URM rollout about a month ago and Im here to share the tips, tricks, insider information and time-saving gothchas. So lets get started... Actually, lets start by reviewing the main reasons why most organizations do implement Records Management in the first place... and what results should you expect out of a successful implementation. I dont want you to spend an hour... much less a day or a month... even considering to implement a solution that might not bring you the results you expect. So lets see...
1. The system you pick must be able to apply your records management policies and practices on content in external and remote repositories such as file systems, other CMS repositories and email archives as well as your nonrecords content. If it doesnt youll be forced to migrate the content of your entire enterprise into this new system or fail. 2. Your new URM must be easy use. If its not your business folks will use all of their smarts to avoid it. Ive seen it and Im sure youve seen it happen more than once. All license costs, all installation and configuration efforts, the budgets spent on professional services tons of money, time and reputations end up burning in flames every day in organizations around the world large and small. 3. The system must be... hot-pluggable. Lets face it you dont have years to perform complex customizations, integrate systems or migrate your content. If the new URM is not usable straight out of the box - youll be forced to play catch-up and scramble to show quick results to your business sponsors. Oracle URM lets you place a solid checkmark into all of these boxes. It also Certified against all parts of DoD 5015 v3 and out of the box comes with adapters for File System, Documentum, FileNet, MS SharePoint and others. So it lets you add retention management that matches and exceeds industry standards - almost instantly. It easily scales up to millions of records, but can also run on a very small footprint. Ok, so now heres...
RETENTION
Retention is the act of keeping information for specified periods of time, depending on the type of content or depending on applicable laws or regulations. The most common types of retention are time-based (i.e. keeping the content for 10 years from the date of filing), event-based (i.e. employee terminated) and a combination of the two.
DISPOSITION
After retention period is over, authorized people within the organization take appropriate action to dispose of the content. Please note that it URM does not simply delete content when it no longer need to be retained. Disposition does not always mean deletion. Yes, content may need to be physically or electronically destroyed after a period of retention, but it can also be stored internally in an archive location or transferred to external storage facility. Disposition in Oracle URM is defined as a set of disposition instructions that define when and how the content will be disposed of. Disposition instructions are based on the time periods and triggers item status changes or simple act of previous disposition action completing.
RECORD CONTENT
Record content, as opposed to regular managed content, is managed on a retention schedule. It is being marked as record on filing, retained according to retention rules and then goes into disposition.
Session # 607
As shown on the diagram, the item remains content until the Cutoff, and then it enters Disposition. Once again, cut off may be time or event-based. The filing date may be the items check in date (which is the most common case) or it may be the date that it is marked as being retained. Older URM 10gR3 differentiated Record vs. Non-record content. Content marked as Record could not be revisioned and after the cutoff, their metadata was also fixed and could not be modified. URM 11g lifts these restrictions and let administrator control whether or not the content should be revisioned.
RETENTION SCHEDULE
Retention Schedule is a hierarchy that defines specifically how the content is actually retained. Retention schedule is defined on 3 levels: Retention Categories is the place where disposition instructions and security settings are actually applied.
Series is a hierarchy that allows you to organize your retention categories (Retention Categories cannot be nested). Series can also be hidden which allows you to prevent your contributors from filing content into the work-in-progress structures. Record Folders is a level below Retention Categories, that allows you to organize items with similar retention and security. Record Folders can be nested.
So heres how the entire Retention Schedule looks in Oracle URM user interface:
Session # 607
FREEZE
Items in a record folder or individual content items may be frozen which prevents them from being updated, deleted or destroyed. This is useful when you need to comply with audit or litigation requirements.
CLASSIFIED CONTENT
Classified content is sensitive information that requires protection against unauthorized disclosure. Unclassified content is the opposite and Declassified content is the content that used to be classified in the past. Typical classifications include Top Secret, Secret, Confidential and Unclassified. And that was the last one. Were now ready to proceed to...
The videos are available on uTube and heres the link: http://www.youtube.com/watch?v=j1zAzaXCJwQ Once the environment is up, you are ready to proceed with the following four major steps involved in the setup.
Session # 607
If Physical Content Management is enabled, additional roles will also be available. Once your security is defined, you (or your Records Officers) can start working on creating the Retention Schedule.
This lets you apply your retention policies to content more consistently with less administrative effort and less disruption for users without the need to migrate your existing content out of your existing systems across the enterprise. You can also freeze items in SharePoint and apply retention by search criteria and item locations. Please note that MS SharePoint 2003 and 2007 adapters are currently only supported with URM 10gR3 And now if youve used or planning to use the older Oracle URM 10gR3 the following section will give you some valuable insights. So heres ....
Clear, easy and logical! Records Manager Corporate Edition a stripped down version and the Records Manager DoD Edition the full one are now merged into the single Oracle URM product. So is the Physical content manager now a part of the single Oracle URM product. Route all changes to disposition rules through a workflow when needed to get approvals or notify stakeholders automatically You can now create and check in Report Templates for easy to create and consistent looking reports! Nice interface changes, such as obsolete and out of date items are now shown as crossed out...
Session # 607
Print option is now available on every screen... User dashboards... Records and Physical menus on the top have been given a major face lift most of the options are now available there in one place!
CONCLUSION
Youve just completed your light-speed introduction to Oracle URM, where we looked at the reasons why organizations deploy Records Management and the benefits they expect to achieve, core concepts and terminology used in record management such as Retention and Disposition and weve looked at steps involved in setting up your own Oracle URM enterprise deployment. For more inside information and time-saving tips go to ECM Solutions web site at http://stellentExperts.com
REFERENCES
1. Oracle Content Management web site: http://www.oracle.com/technetwork/middleware/contentmanagement/overview/index.html 2. The Oracle UCM Handbook (Packt Publishing, 2010): https://www.packtpub.com/oracle-universal-contentmanagement-ucm-handbook/book 3. Oracle URM 11gR1 Setup, Administrator and User Guides, available at http://download.oracle.com/docs/cd/E17904_01/ecm.htm 4. Oracle URM 10gR3 Record Manager DoD Edition and Oracle Universal Record Manager Adapters Administration guides, available at http://download.oracle.com/docs/cd/E10316_01/urm.htm
Session # 607