Legal KM

Open-source Evergreen Koha PMB NewGenLib

Proprietary Dynix from SirsiDynix Horizon from SirsiDynix Symphony from SirsiDynix Talis (UK and Ireland) Unicorn from SirsiDynix Voyager from Ex Libris, formerly from Endeavor Millenium from Innovative Interfaces, Inc. Virtua from VTLS ILMU from Paradigm Systems and Universiti Teknologi MARA (UiTM)

Enterprise wikis are often used for: collaboratively building documentation creating and maintaining knowledge bases project management gathering tacit knowledge (knowledge not related to any specific project but essential to getting things done in an organization) meeting management, from agenda to minutes and action items. Generally, an enterprise wiki will be used in a much wider variety of ways than an Internet wiki, because it is intended to support the wide-ranging needs of the people within an organization.

On an enterprise wiki, the contribution level is much higher based on the fact that people are contributing as part of the daily course of their work,

Market Shifts Toward Infrastructure Vendors

Content management is becoming part of enterprises' infrastructure and consequently is being delivered by large vendors of enterprise infrastructure such as IBM, Microsoft and Oracle.

IBM, Oracle and EMC are competing at the high end of the market, while Microsoft is commoditizing the market at the low end. Recently, HP entered the ECM market by acquiring Tower Software, a niche vendor long known for its integrated document and records management.

More than 54% of the market, as measured by total software revenue, is held by just three vendors — EMC, IBM and Open Text

Pure-play content management vendors and vertical-market specialists such as Interwoven, Xerox, Xythos Software and Vignette are fighting to compete. Bright spots for the pure-play vendors and vertical specialists are the mid-market and CEVAs

IBM and Oracle have the potential to drive the market forward by creating a powerful message based on broader enterprise information management (EIM). Since they own the key stack components, such as the database, the information access, business intelligence (BI), analytics and reporting tools (and often line-of-business applications), they can bring together structured data and unstructured content. On the other hand, choosing a suite from a stack vendor may involve tradeoffs as some functional components may not be equivalent to best-of-breed offerings.

Of all the infrastructure vendors, Microsoft has driven the most change in the ECM market over the past 18 months with Windows SharePoint Services (WSS) and Microsoft Office SharePoint Server (MOSS) 2007.

Adopting WSS or MOSS for mass deployment, and an ECM suite for high-end, content-centric processes and best-of-breed Web content, will remain a useful strategy for enterprises during the next three to five years. This coexistence strategy could reduce the costs and some of the risks of content management for an entire enterprise.

For many organizations, the need to increase workers' productivity and innovation is more important than ever. Critical goals include improving users' Web experience and connecting workers to relevant content and to each other.

see "Report Highlight for Dataquest Insight: E-Discovery Market Drives New Search, Content and Records Management Investments"

Specialists like Interwoven and Vignette are moving into Web-based CEVAs and interactive marketing and customer experience. They remain among the few choices enterprises have for high-end, enterprise-class, externally-facing Web content management (WCM) solutions. In the mid-market, Hyland Software, SunGard Data Systems and Saperion use their imaging and archiving heritages to address transactional content applications such as medical records, claims processing and accounts payable invoice processing.

Integration/Federation Grows in Importance as Organizations Look to Establish an Information-Centric Infrastructure

The ideal ECM architecture would enable one repository, or a few repositories with a common database — but this is not an ideal world. Dealing with multiple, siloed content repositories is a fact of life for many organizations. In Gartner's 2008 survey of nearly 400 respondents (see Note 1), 69% of enterprises indicated they had more than six repositories.

see "New Standard Will Make Content Repositories Interoperable"

Enterprises keep a vast amount of information locked up in documents, spreadsheets and other forms of unstructured data ("content"). To maximize the value of this information, enterprises need to integrate the various types and stores of content, integrate content with structured data, and integrate internal content with content and structured data outside the enterprise.

XML is becoming increasingly important for content creation, component management, output and integration with other applications. The term "mashup" has become synonymous with content couplings that were formerly difficult to achieve, even with traditional integration resources. Enterprise mashups that integrate content with business application data or with Web content via Really Simple Syndication (RSS) feeds or APIs remain rudimentary compared with the explosion of consumer mashups.

IBM intends to deliver ECM-focused widgets for creating mashups as part of the FileNet P8 platform.

User Empowerment vs. Governance

A Range of Needs Leads to Application Specificity and a Fragmented Focus From Vendors

Social software encourages informal collaborative activities that fall outside the traditional scope of transactional applications, formal workflows or engineered teams. The rapid growth of social network interactions and the desire for open innovation will require IT organizations to develop a new approach that balances the need for corporate security with the requirement to accommodate frequent customer and partner conversations. IT staff will still be expected to manage this content at the back end of the life cycle.

Wikis, blogs, podcasts and instant messaging have become staples in many enterprises, especially as marketing tools or as means of communicating with customers, prospects, employees and partners.

Enterprise and information architects should assess how able their ECM vendor(s) are when it comes to providing Web 2.0 features or integrating with third-party solutions for collaboration and communication to avoid creating more content silos. Usability remains a critical characteristic of perceived success or failure for ECM.

Interwoven, Open Text and EMC are among the ECM vendors focusing development efforts on increased support for mobile clients, such as BlackBerrys and the iPhone, and for offline capabilities.

Today, however, all this content creation and sharing typically happens outside any formal content management strategy. Organizations should take advantage of evolving, richer user interfaces and tools for content creation, consumption and multichannel output.

Alternative Delivery Models

The capital outlay required for ECM, and the internal resources needed to implement and maintain ECM suites, can be daunting. It is not unusual for an organization to spend $1 million or more on software and services for a large deal. In a 2008 survey (see Note 1), 22% of the respondents indicated they were spending over $1 million on content management software purchases in 2008, while 14% were spending between $500,000 and $1 million. In addition, it can take at least six to 18 months to deploy an ECM application.

Gartner clients are increasingly asking about SaaS, shared services and open source as alternative delivery approaches to implementing on-premises, commercial software. Yet the penetration of open-source and SaaS solutions today represents less than 5% of the overall ECM software market (based on total software revenue)

Market Definition/Description

Gartner defines today's ECM suites as encompassing the following core components: Document management for check-in/check-out, version control, security and library services for business documents. Document imaging for capturing, transforming and managing images of paper documents. Records management for long-term archiving, automation of retention and compliance policies, and ensuring legal, regulatory and industry compliance. Workflow for supporting business processes, routing content, assigning work tasks and states, and creating audit trails. Web content management for controlling the content of a Web site through the use of specific management tools based on a core repository. It includes content creation functions, such as templating, workflow and change management, and content deployment functions that deliver prepackaged or on-demand content to Web servers. Document-centric collaboration for document sharing and supporting project teams.

Though not explicitly identified as a core component, information access, or search, technology has always been a critical component of an ECM suite, and it will play an even bigger role in helping companies sift through structured and unstructured information. All ECM products ship with a search engine embedded as a core component, so that users can create a full-text index and search the content stored in repositories. Most ECM vendors re-license the search engine from another provider, typically Autonomy-Verity or Fast (see "Q&A: ECM and Information Access Technologies Grow Ever-More Entwined").

Inclusion and Exclusion Criteria

Evaluation Criteria

Vendor Strengths and Cautions

Interwoven

Interwoven has increasingly focused its strategy on being a best-of-breed content management vendor, with a strong message around Web-based and vertical-specific solutions.

Although Interwoven has all the core ECM capabilities and related components such as DAM, it delivers and emphasizes these as stand-alone offerings for different business scenarios. The suite is only loosely coupled, and cross-selling opportunities are limited.

Gartner believes that Interwoven's future lies in high-end WCM, analytics and marketing solutions. It can continue to carve out a successful position with its consistent marketing messages and Web-based solutions, but this won't be easy given the increasing competitive pressures and changing market dynamics. Interwoven must continue to penetrate the accounting, legal and professional services markets and expand into adjacent markets such as the government sector — otherwise, like others, it faces a stagnant future in the traditional document and records management arena.

Microsoft

More so than any other vendor, Microsoft has driven ECM market transformation with SharePoint 2007. Microsoft has brought BCS to the masses by bringing the cost per seat down and tying simple content management to the familiar desktop tools that users use every day.

With MOSS 2007, Microsoft provides an integrated product suite that provides at least basic capabilities in the six core ECM functional components, along with portal and search capabilities. The fact that it is built on the Microsoft stack will appeal to a broad range of organizations for whom Microsoft is a strategic partner.

While MOSS 2007 has attracted interest and gained some traction as a records management tool, a WCM solution and a platform for building CEVAs, it still has to mature in these areas.

Feedback regarding large, decentralized deployments of MOSS 2007 indicates a need for improvements in scalability and in management and replication functionality. Microsoft has begun providing tools and published guidance to address these challenges.

Microsoft must continue to ramp up support, training and partner certification as there is a clear "skills gap" between the demand SharePoint has created and the supply of well-trained implementation personnel.

Objective

Objective, an Australia-based vendor, has a strong vertical-market focus on the public sector in Asia/Pacific and Europe

The Objective suite, which has evolved through development rather than acquisition, is well-integrated and addresses the core ECM functional components.

Historically, Objective has delivered most professional services itself, rather than through partners. Recently, it has begun to establish relationships with major system integrators, but it needs to expand further and extend this partner channel.

There were wikis for different practice groups and they were searchable.

Their early success created a big demand. Every group wanted wikis. Updating was given to assistants, clerks & associates. However the technology was not perfect. You had to sign on separately for each wiki and they were creating silos of information. To solve this issue they looked at a number of enterprise tools and found most too feature rich and complex for lawyers to use them.

They went with Thought Farmer for its simplicity and ease of interface. (see my review - ThoughtFarmer – Intranet 2.0). It has Web 2.0 features – staff profile, tagging, RSS, social networking, email publishing, - also search with relevancy ranking.

The presenter’s thoughts on lessons learned include: select an easy to use tool, do not force participation, transfer the process of updating to groups and develop a process for each group. You should also offer training and share success stories. They held individual training in 10 to 15 minute sessions.

They have found that not all users will be active contributors and the ROI is hard to measure. The tool should also be more Blackberry friendly. However, overall it seems to be a great success.

Over the last year, his firm has created three to four thousand pages in the wiki. Lee estimates that 60% of his employees make at least one change to the wiki each day.

Lee really likes the flexibility of the wiki platform. People can work in the wiki the way that they want to work. Of course, that has lead to some disagreements over the way to organize content.

Lee sees a conflict between the need for rules and the freedom to contribute. There are places where the wiki is not organized in a way that works for him. But it does work for others.

Lee also likes that the wiki is externally hosted. He lets PBwiki worry about keeping the server up and all the "plumbing" headaches. He wants to be out of the IT business.

One of his biggest issues is keeping the wiki in people's minds as a way to communicate. It takes some time for people to realize that they can communicate through the wiki. Lee still sees lots of email communication that could be better handled in the wiki. They are also still transitioning some of the content from Lotus Notes into the wiki.

"Enterprise RSS": It's A Middleware Decision

Social Analytics: Redefining Business Intelligence

Enterprise 2.0: Long-term Issues

Enterprise 2.0: Vendors To Watch (alpha order)

Enterprise 2.0: Open Source Efforts To Watch