Forrester recently surveyed 233 IT decision-makers who have plans to implement or upgrade to at least some part of MOSS 2007 and asked: "Which of the following best describes your organization's time line for implementing or upgrading to Microsoft Office SharePoint Server?". The results? 21% will upgrade immediately and 41% will do so within 6 months.
With this level of adoption the issue of scalability comes up more and more. In one sense you have architectural concerns with any solution that scales horizontally, uses banks of load-balanced Web servers, application servers, and clusters of SQL servers on the back end. Add high availability and you quickly get a complex environment. To Microsoft's credit there is quite a bit available on performance guidelines. But looking through these, and coping with notions of site collections, lists, file arrangements, performance of folder hierarchies versus flat files, and automatic versus manual partitioning, the bottom line seems to be that even on the new 64 bit architecture with 4 screaming Intel processors, and SQL 5 -- the upper limit of the content repository is 500GB.
I went to the AIIM conference in Boston last week.My first AIIM show was in 1993 — where the ratio of demos to production systems was about a billion to one. For the historians out there, the 1993 show in Chicago had over 33,000 attendees. New optical disk jukeboxes and digital scanners were the rage. So it was good to see how far the industry has come in providing mature and productive solutions. Yet — AIIM is still something of a chaotic, disorganized, vendor-feeding frenzy that seems to somehow work for most attendees.
It's probably the Boston convention center and not AIIMs fault, but is it really so hard to have something available to eat before 11AM in the morning? I gave a talk on ECM Strategy Tuesday morning and wrongly assumed some protein would be available. I was not looking for something as complicated as an egg sandwich, just perhaps a donut. The Dunkin Donut cart seemed to have more interest then any booth — an impossible line and very poor inventory.
On January 16, 2008, Oracle announced it has entered into an agreement to acquire Captovation, a provider of document capture solutions. With Captovation, Oracle extends its solution for ECM for transactional content by adding a strong capture solution. The acquisition is expected to close by February 2008. Captovation already has joint customers with Oracle/Stellent and had actually partnered with Optica even prior to Stellent's acquisition. In this sense the acquisition is not surprising. "Oracle Capture" will be the new product brand.
For Oracle customers, it makes a more complete ECM solution, one that can address paper capture for invoice processing for ERP applications or more convincingly incorporate unstructured content for Siebel. For Captovation customers it means increased R&D, investment protection, and access to Oracle's global support and services.
HP’s plans to acquire Exstream combined with EMC’s intent to buy Document Sciences demonstrates that output management for transactional content is becoming critical to many large organizations. But how do you rationalize these two acquisitions? First let’s look at EMC. They add to their consistently improving transactional content assets. Whether it involves invoice processing, account notices and policies for insurance, or new account opening, DOM gives EMC more complete support of the document lifecycle. More to the point, Forrester’s predicted growth in Interactive DOM is very important for the major ECM players. Interactive DOM makes more use of ECM then Structured applications that are essentially batch processes with little human involvement. Interactive applications need human-centric business process management to help author, store, version, and manage content dynamically. EMC can now link their broad ECM platform to Document Sciences for this emerging area.
In October of last year, I published "Give DOM its Due" and argued that for years, document output management (DOM) had been pegged as a back-office operation that produces customer statements and bills. And that now, customer experience demands will thrust DOM into a major software category supporting the growing and diverse content that enterprises must assemble and deliver to customers. A few weeks ago EMC purchased Document Sciences. And now on January 22, HP has signed a definitive agreement to acquire Exstream Software, a privately-held provider of document creation and publishing software for print, mail and online channels. HP expects to close on this transaction in the second quarter of HP's 2008 fiscal year.
Exstream continues to be a leading choice for the high-volume segment of the DOM structured market and will greatly strengthen HPs document automation capability. Initially targeting service providers — a tough crowd — Exstream followed an object-oriented development model to allow re-use of document components, which was quickly adopted by service providers to provide similar applications to many customers. Today's focus is heavily in the interactive and on-demand DOM segments with strong direct sales. While revenue numbers were not available, Exstream has 300plus employees.
While market drivers like compliance, eDiscovery, and risk management get a lot of press (and point to great opportunity for records management), the fact is that many organizations are not ready for full-blown RM programs. Why? Mostly due to organizational immaturity — not correctly aligning roles, responsibilities, and budget ownership (for more on this, click here). But there is also the problem of mutliple repositories containing records; organizations struggle with the question of moving records to a central repository or investigating federated RM.
Ever think about how much time, energy and money we expend on managing line of business data? Just drive past the Oracle headquarters in Redwood Shores and you'll see a glimmering green city of glass all built on revenue from managing business data. OK, they make some money in other areas these days, but the emerald city was build on database revenue. Managing structured information is key to the success of any organization. The number in the bottom line needs to be accurate or very bad things happen.
On the other side of the coin lives unstructured information. While some unstructured information has been afforded the respect given to structured business data (engineering drawings, legal documents, pharmaceutical documentation, insurance claims documents to name few) the vast majority has languished virtually unmanaged in file servers and on PC hard drives. Even companies with the right resources and motivation, like Oracle which has the ability to manage structured and unstructured data in its database as well applications to take advantage of both, have made only minimal progress at bridging these disparate worlds.
I recently co-presented at a workshop on eDiscovery. Before I spoke about what enterprises are doing about exploding discovery costs and the fragmented solutions landscape, a very experienced corporate general counsel spoke to the IT-heavy audience. The theme of his presentation was "help a lawyer today." That's right CIOs and IT project managers - your legal team is not going to tell you how to handle eDiscovery. You are going to be responsible for effeciently and defensibly collecting information in response to regulatory and legal requests. In fact, legal is relying on your expertise in technologies to better manage information.
The moral of the story is that IT must take the leadership role in creating a formal, cross-functional team and process for managing eDiscovery. Don't fret - here's a few cheat sheets to get you started:
At the AIIM show in mid April, Xerox Global Services gathered a number of information management industry pundits to talk about issues related to eDiscovery. The conversation shed light on myriad issues that organizations face to meet the requirements of the newly amended Federal Rules of Civil Procedure (FRCP). You can listen to a podcast of the discussion here. The major points of note:
Adobe has put an end to much speculation, announcing that it will take Flex into the open source realm and make the source and documentation available under the Mozilla Public License. This move certainly ratchets up the battle between Flex and Microsoft’s Silverlight technology — both are used to create rich Internet apps. Microsoft has targeted Flash and Flex, so Adobe apparently has come to believe that open source is the best option for gaining ubiquity for Flex. Traditionally, Microsoft has had the edge with developers; Adobe with designers. Adobe is clearly hoping this move will shake that up.