MOREQ2010 CLASSIFICATION SERIES

RM implementations should be standards compliant. After all for those in the public sector who have invested in such technology that underpins core systems and that gives us tangible benefits, the thought of abandoning it for something else is not a realistic one. Simplistically I only have one birth certificate or passport or drivers licence — why would a business want multiple copies of a record or aggregation of a record? MoReq abandons three big aspirations that all those previous specifications shared. With this new approach to RM there is no need for a monolithic RM system. Module 3 recognises that digital recordkeeping does not have to be limited to the EDRMS paradigm — the insight that has now been picked up by MoReq

How many records or copies of the record do we want to manage? You are commenting using your Facebook account. Notify me of new comments via email. You are commenting using your Twitter account. MoReq sees ERM as a capability that could be embodied within each separate application that the organisation uses, or that could sit behind those applications and manage records created within them. Thinking Records James Lappin’s records management blog. Systems that end-users do not interact with directly, but instead capture and store records that users had created in other systems Systems that do not store records, but instead govern and protect records held in other systems Line of business systems or single purpose applications that are not intended to be a general records system but which have have the ability to manage the records that they capture Systems that can fulfill two or more of those roles — for example a system that could be deployed as a traditional EDRM that some end-users would interact with directly, but which also possessed the capability to manage records held in other content repositories The old aspirations that MoReq abandons MoReq is a major change from all previous specifications of electronic records management systems.

The disadvantage of this is that vendors had to configure their systems to cover all sectors and all eventualities, which pushed up the cost for them of developing compliant systems.

MoReq has been written to encourage different models of records management system to emerge. It has been quite radically simplified from the previous version The concept of a primary classification has been dropped in favor of a more flexible approach It accepts of a modular, SOA Service Oriented Architecture structure for an RM system Each of these bullets deserve serious discussion and analysis that cannot be provided in a blog post, but I can summarize that the new specification both simplifies and allows far more flexibility in your implementations and vendor selections.

Join us for a fast-paced discussion to learn about digital trends from an enterprise customer perspective Simplistically I only have one birth certificate or passport or drivers licence — why would a business want multiple copies of a record or aggregation of a record?

This means even those organisations with corporate-wide EDRM systems still get the problem of managing records in multiple repositories. This is a huge change in direction, and one that I certainly welcome.

We wanted to take a moment to say a special thank you to a few people who took the time to write extended reviews of the book A South African records process perspective!

  THE CHALLENGE SEASON 27 EPISODE 3 CAMILANATOR JUDGEMENT DAY

Moreq a DOD slayer? | Blog | Real Story Group

Systems that end-users do not interact with directly, but instead capture and store records that users had created in other systems Systems that do not store records, but instead govern and protect joreq2010 held in other systems Line of business systems or single purpose applications that are not intended to be a general records system but which have have the ability to manage the records that they capture Systems that can fulfill two or clasification of those roles — for classificatin a system that could be deployed as a traditional EDRM that some end-users would interact with directly, but which also possessed the capability to manage records held in other content repositories The old aspirations that MoReq abandons MoReq is a major change from all previous specifications of electronic records management systems.

In fact with this new standard, you may potentially even have your own internal RM program certified, rather than the standard simply being restricted to a particular classificatiin software solution. I, like many others, need to think very carefully about the implications of this, particularly when authorities are procuring new systems. Jon Garde points out that the span of years of many of these retention periods is longer than the life of most records systems.

Some basic factoids about the new standard: What Is a Real Quadrant?

The ICA specifications were developed between classificaation by a multinational team of experts including people like Richard Blake and Hans Hofman. Four words to drop from your RFP – and one to add June 7, In product selection, as in life, the key to differentiating among possible alternatives is precision Hi James, I am a member of the MoReq project team.

With this new approach to RM there is no need for a monolithic RM system. Be that as it may, what I would like to put the table is that even though records managers face an ever incredibly difficult task, that at the end of the day they cannot address multiple system s issues unless they address the problems at a process level.

I would urge anyone with an interest in the functionality of records management systems to consider joining the DLM Forum. MoReq sees ERM as a capability that could be embodied within each separate application that the organisation uses, or that could sit behind those applications and manage records created within them.

I would like to draw your attention to some specifications issues by the International Council on Archives that appear to be not so well known by colleagues in Europe. There is just too much to comprehend and I would strongly advocate a call to go back to basics. RM is going through a very difficult period of change, much of it depicted by extreme denial. It is likely that your various content repositories will have been procured from various vendors, written in various programming languages, and have varying quality APIs.

Ed Fowler of Cap Gemini said that organisations will need to get used to the fact that their records will be created and stored in many different content repositories, and that few if any of these repositories will have records management functionality.

  SUDESH LEHRI COMEDY NIGHTS WITH KAPIL

Module 1 is a high-level overview document that sets the scene and articulates first principles.

Real Story Group

You are commenting using your Twitter account. If a sector has specific requirements they are able to write a separate MoReq module to capture those needs.

Likewise just to be super clear, Moreq has yet to be tested in the field, and suppliers and end users have yet to actually adopt it, since it’s brand spanking new.

Notify me of new comments via email. All MoReq compliant systems have to comply with a core set of requirements. Finally, what I have promised myself, despite feelings of suicide may be a serious option, is that I intend over the next 6 months fighting my way through every single page of the in MoReq with the hope that I can understand exactly what it is and what it is trying to achieve.

Moreq at least is an attempt to move the discussion forward, and could significantly shift the ground rules. You suspect there’s something not right in the arbitrary positioning Vendors that wished to target that sector could add that clasxification to their system and ask for it to be tested and certified against that module. I have an article on the project appearing in the forthcoming issue of the Canadian journal Archivaria issue Marc Fresko was critical of MoReq MoReq will bring interesting effects for records managers.

Out of MoReq will sprout a variety of different applications, which will need a variety of different seties methodologies.

Jon wants a MoReq compliant system to be able to export a record and its associated metadata at any point during the retention period, so that the receiving system could understand what retention policy has been applied to the record, when that retention period started, and how ,oreq2010 it had left to run.

An aggregation can be a multilevel hierarchy in its own right, so it can sit separate from the business classification, whose role is not so much to act as the only means of navigating around the records system, but more to apply retention rules to records. But they are also able to submit systems for testing that meet a completely different model, for example:. The new records system could c,assification apply the remainder seriess the retention period.

MoReq is a major change from all previous specifications of electronic records management systems. The only way to understand the problem is to understand the process and then try and fit it to the system s. Just as is what is the bottom line benefit to a business forcing a vendor to be MoReq complaint?

Turning to the new MoReq I am not so convinced that line classufication business system vendors will incorporate electronic records management functionality into their systems — what is the benefit imperative to them?