30 April 2010

GARP Integrity

The third part of GARP is Integrity
It's much needed in Washington D.C.
Where bills' metadata
Reveals the stat-a
The Records and pols authenticity

29 April 2010

Philology from Philadelphia

In Philadelphia, Info360 (neé AIIM expo) opened and closed last week with minimal impact. Often a launching pad for emerging technologies and a listening post for industry trends, this version was most notable for what wasn’t there, especially from a RIM perspective.

First, the asset side of the ledger:
Microsoft SharePoint 2010 dominated the show floor with a generous partner pavilion and a large, accessible bank of laptops for group “immersions” and individual exploration. The mock case study showed at least some of Redmond’s expanded RIM functionality
Cloud computing vendors provided second-level saturation, proclaiming the advantages of their tools while trying to assuage buyers’ fears
The show’s small footprint allowed a thorough viewing with minimal loss of shoe leather
EMC, HP and Oracle presented credible displays. In terms of RIM, their common theme was, “We speak SharePoint, too.”
The concurrent, adjacent OnDemand trade show gave AIIM attendees the chance to explore the hardware side of RIM
OmniRim proffered their paper-based solution’s integration with SharePoint

On the other side, some major vendors seemed scared off by Microsoft. For example:
IBM limited itself to a kiosk in the SharePoint pavilion -- barely mentioning Contextual Analytics, its potentially game-changing technology announced at ARMA last October
Open Text claimed only a 10’ x 10’ booth near a corner of the show floor, and the booth person who addressed me did not speak RIM

As Gimmal Group’s Mike Alsup commented, it felt like a throwback to 1995. Capture was a major theme, and many of the new, small vendors who populated the 10 x 10s on the periphery showed document management technologies. Plasmon even showed a jukebox full of double-sided WORM disks.

Cloudy, with a chance of meatballs

As noted, the secondary theme -- not mutually exclusive with SharePoint -- was cloud computing. Priscilla Emery, owner of ECM Scope (and a former Sr. VP at AIIM) observed:

“Cloud approaches to support document management are re-emerging but I was struck by the lack of e-mail management approaches being fully integrated into many of them. From a records management point of view these "solutions" won't hold water and only demonstrate a serious lack of understanding how to support e-discovery and audit applications. “Of course, SharePoint has been the basis for many of these applications and more. And, yet as I look at what CIOs seek as the basis for their enterprises' infrastructure and communication applications, I do see more of them taking a very serious look at Google as the provider of choice in the cloud. I see a serious disconnect in the ECM [Enterprise Content Management] market here and, maybe an opportunity for those ECM vendors adventurous enough to explore it.”

While Google had no booth, it interpreted its view of information management at a well-attended keynote address. Among exhibitors, vendors Alfresco and SpringCM offered cloud-based ECM suites with records management tools.

AIIM – The Organization versus The Show

In the last six months, AIIM has promoted and emphasized its focus on RIM, prominently featuring records issues in its publications and heavily promoting its certificate program for electronic records. Exhibitors at the trade show did not replicate this focus, showing minor interest, at best, in records and information management.

In addressing RIM, AIIM still faces a basic contradiction: AIIM is primarily a vendors’ organization, and vendors make products and tools. RIM is essentially a discipline to be practiced. It uses tools, but it is not defined by them. Further, RIM practitioners are not buyers of software tools, at least not outside a partnership with their IT stakeholders.

If AIIM wants to offer significant value to RIM practitioners, it will have to teach its vendor-members to be problem solvers more than software merchants. Records practitioners need ECM tools and expertise, but that need is likely to go unfulfilled until ECM vendors gain perspective on how their products can be applied to RIM.

13 April 2010


The state of a program's transparency
Can measure the ease those who care can see
A RIM program's ways
That emerge through the haze
And that challenge all skeptics to dare and see.

Ten Years After: RIM Standards Evolve Slowly

Ten years ago, the tech world was still exhaling in relief and self-congratulations on dodging the Y2K bullet. Leading-edge records managers joined the techies, smiling that their fledgling stock of electronic records were largely intact; disaster recovery tactics went unused.

In this heady environment, a group of RIM luminaries adapted Australia’s DIRKS (Design and Implementation of Recordkeeping System) to worldwide applicability. In 2001, ISO published a records management standard, 15489, that remains an important reference and guide for measuring RIM success today.

Eight years later, ARMA International published its Generally Accepted Recordkeeping Principles (GARP), which owes much to ISO 15489. To call it derivative is not quite accurate. Think of it more as a re-interpretation that reflects the changes, the evolution of RIM over a ten-year period.

That GARP and 15489 have much in common is not surprising. The discipline of Records Management, dating back, at least, to the 4th Century BCE, evolves slowly, befitting its heritage and longevity. Unlike practices based on ephemeral developments, RIM wears technology like a runway model at a fashion show: She shows dress after dress, but the walk never changes. Records’ value is in the content, not the visible format or medium. The best practices of records management evolve with the needs of the records users, and those morph slowly over the years. Records managers rarely say, “Gee whiz!” to mercurial novelty.

(It is possible that the current buzz words -- Cloud Computing, Web 2.0, and others that rapidly multiply the entry-points and touch-points for records -- may accelerate the evolution of RIM, but that is conjecture at this point.)

Ten years offer only a narrow perspective of changes in RIM practices. Nonetheless, there is value in noting the differences between ISO 15489 and GARP. The Delta helps us see how the role of the records management professional has changed.

There is considerable, basic congruence between ARMA’s GARP and ISO’s 15489. Both encourage improvement, not perfection. Every records program, not matter how good or bad, can get better

Six basic areas overlap: Availability, Retention, Disposition, Protection, Compliance, and Integrity. While the wording varies a bit, ARMA and ISO agree on these, basically.

However, the ISO standard lacks GARP’s first two principles. Accountability and Transparency describe RIM’s governance and explicitly stated organization; policies; and strategies. This is analogous to metadata. It is not about the mechanics of keeping records, but, rather, the structure, politics, budget, and administration of organizing and sustaining records’ usefulness within an organization

GARP’s addition of Accountability and Transparency to the canon reflects the different roles records management filled in organizations in 2000 (when 15489 coalesced) and GARP’s natal year, 2009. At the millennium, records management was a disciplined service. It was largely paper-based, and its roots in library science were apparent. By 2009, it was Records & Information Management, a tech hybrid, striving for recognition as a full-fledged profession, parallel to legal and finance.

On the other hand, ISO 15489 offers guidance in two areas that GARP largely ignores.

First, ISO 15489 articulates the use of records management to measure and reduce organization’s risk. GARP, and its derivative Maturity Model, imply that as recordkeeping practices improve, that is, become more mature, the organization will inherently lower its records risk. But it offers no guidance for the kinds of decisions that records managers make regularly, balancing needs and costs to find an acceptable level of risk.

Similarly, ISO 15489 gives considerable attention to the role of records management in organizations’ operations. It requires records management to continually contribute to the improvement of business processes. This tends to cost-justify a records program based on improved efficiency. GARP alludes to improved operations in its Availability principle, but the Maturity Model mentions return-on-investment only at the highest, or Transformational, level. Making the case that implementing GARP makes good economic sense requires inserting a couple of extra steps that borrow from 15489.

In a decade, the discipline of records management “rose from the basement to boardroom”, to quote ARMA workshops. While still a business service, today’s records leaders carry consultative and strategic responsibilities as well. Part of GARP’s raison d’être is to give new “Chief Records Officers” a tool, language, and model easily understood by other management professionals. Intentionally, GARP derives from the financial world’s Generally Accepted Accounting Principles. It is both content and packaging. In 2000, such a need was only a glimmer.

ISO 15489 are complementary – different but without contradiction. Both serve records managers well. In 2010, records programs need to meet internationally-accepted standards more than ever. Simultaneously, records managers can try to make their programs, as GARP puts it, transformational.

The RIM program that subscribes to both GARP and ISO 15489 will 1) be full-featured and 2) function effectively. Aspiring and progressing toward both appears to be a path toward a successful program.