Opinions and discussion on content management and document management by two of the biggest guys in the business. *Measured by combined weight

Output Management Acquisitions

Follow Marko

Follow Lee

Disclaimer

The opinions shared here represent those of the contributor themselves and not those of their employers nor that of Big Men On Content as a whole.

A vendor you might not have run across, Optio, is being acquired by Bottomline Technologies. Optio is a competitor of Document Sciences which was acquired recently by EMC. No one seems to really know what to call this space. The best term is probably output management but looking at a Venn diagram of related products is like trying to read a newspaper through a bubble bath. Composition, publishing, customer communication, transactional document management. Whatever you call it, two similar products in this field being snapped up at the same time by bigger fish is generally reason to take notice.Output Management – high volume extraction, transformation,format and consumption of content through multiple distribution channels of presentation, has been an obvious hole in Documentum’s core capabilities for years. I suspect part of the lack of interest in this area was rooted in a gentleman’s agreement with the likes of Adobe, ArborText and other publishing oriented partners to stay neutral. Consolidation and acquisition now make format and application agnosticism barriers to growth. Customers want as many features as possible from a single vendor to eliminate the complexities of integration inherit in these types of systems.

This is the case even when the one stop shop myth is revealed for what it is during implementation.Optio, Omtool, StreamServe and Document Sciences are all examples of companies that have in some form or fashion built companies around “documents” that MS Office will never see and in volumes that boggle the mind. The Optio acquisition is not surprising because they have been bleeding money for a while but what it does suggest is that document output management may have a difficult time standing alone without being closely tied to an ERP or some other technology stack. For Streamserve in particular a casual observer might see a closer relationship with SAP as almost inevitable.

Documentum has traditionally been weaker when it comes to providing good tools for getting content out of the repository. The very term output seemed to stick in the sales guy’s throat. Those of you that have used Site Caching Services and it’s less successful step-brother Site Deployment over the years will attest to the relative lack of innovation in the arena of content consumption for Documentum. There are certain architectural themes that run through major software companies. These themes guide everything from product pitch to platform choice. Documentum was no different and one of the guiding themes for at least the first 10 years was the desire to have everything in one repository, and once you have it – NEVER let it go.

It was this desire to control all content that seemed to make the EMC / Documentum combination such a natural fit. Unfortunately, once the most obvious content consumption problem was solved for the web publishing suite, it seemed no one seriously looked at the potential of other large volume content consumption capabilities for the core product set. A brief attempt with RightSite left some with scalability scars and no upgrade path. (until now – warning: this link is a shameless plug) ISV’s have been building add-ons to do this in Documentum for years but now there seems to be the realization within EMC that someone might want to do something more with content than put it on a website. I imagine that sometime in the middle of the development of TaskSpace someone asked the question “just how are we going to print all these transactions anyway.” Enter Document Sciences.

The addition to the portfolio is a logical next step once the decision was made internally to get into transactional content. I only hope there is an equal level of commitment to integrate the engineering, sales and partner networks and deliver a true product to the market instead of just one more unused line in a license agreement.

Tagged as: , , , , , , ,

Categorised in: Content Management, EMC

2 Responses »

  1. Your observations are typical for the marketplace. As Founder and Chief Architect of ISIS Papyrus (http://www.isis-papyrus.com) I know exactly what you are talking about. I have fought that kind of ignorance for the last twenty years. Somehow when people started to talk about the ‘paperless office’ they tought that documents have gone away. But let me correct you that Output Management is not printing, but mostly accepting output from multiple applications and manage it, in most cases that does not yet include printing. The there is Document Composition which is the ability to design a dynamic formatting document template (not a form or Word-like document) that will accept a huge variety of inout data and create a legally acceptable and presentable/printable document in PDF or AFP (an IBM format) at high-speed. Paprus does 50 MILLION pages per hour on a current Intel server! Which is why we do half the documents for credit cards issued in America. Then there is print management, which is a lot more than routing a file to the printer. How would you handle these volumes manually? You need a function called post-processing that will control enveloping machines with barcodes and verify if all documents have been printed and not torn up by the printer or eneveloping equipment. And then there are the transactional document and process related documents.
    By the way, none of the companies you mention (Doc Sciences, …) actually have proper print and output management.

    NONE of the above is handled by AIIMs ECM definition but I see the need to merge it. But what to call it is an issue. Without a new three-letter acronym shoebox to put software in people are lost. I proposed to the analyst crowd in 2001 that we need to close the communication loop and announced the inbound-process-outbound functionality of Papyrus to their blank eyes. NOW – five years later – they all go. Oh, we might actually have to create outbound (not inbound scan) documents for workflow. But the problem is not solved by hard-coding the document. I has to be more flexible than everything else and that is not possible with Java/XML. No dynamic document formatting and you can shove your agile SOA-BPM enterprise …

  2. The ignorance in this case is for some a result of a poor marketing job on the part of the industry. The nomenclature of this market is at the heart of the issue. “Output” implies sending not receiving. When EMC refers to this with Document Sciences – they really do mean output.(from a repository to something else) Marketing folks within OM vendors mentioned above realize that print management as a term isn’t sexy. The term I surmise they’d prefer, Document Management, has rightly or wrongly been consumed by the ECM market space. “Customer” laden tag lines and product names are confusing and in the end always made it more difficult for me to educate the buyers on why they should invest in a particular output mgmt.solution. If I have one piece of advice – its “lead with what you do”

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: