How to Use Single Instancing to Control Storage Expense - Page 2

High-Volume Transaction Output applications

To understand how this is accomplished, let us look at a typical scenario in the HVTO world. High-volume documents are produced in batches of hundreds of thousands of documents-or perhaps even millions. Typically, they are produced by corporate applications and composition engines on a daily, weekly, monthly or annual basis. The layout of every document in a batch is identical; only the individual transactional data presented within the document is unique (such as name, address, line items, usage statistics, policy details, etc.).

Composition elements such as branding, graphics, fonts, forms and marketing messages are identical across every document in the batch. These common resources are present in every document, yet are stored over and over again inside the ECM solution as one complete set for each individual customer document. The size of the composition resources associated with a customer-facing document today far exceeds the size of the individual transactional content within that document-often by a factor of 10:1.

Solutions that offer single instancing technology for HVTO intelligently separate the common resources found within a high-volume document batch from the unique transactional content. Pointers are inserted within the transactional content that link the now much smaller transactional document to the composition resources. This process happens seamlessly during the loading of the ECM solution.

When the ECM solution receives a document retrieval request, the composition resources and the transactional content are combined in real time, perfectly reconstituting the original document with 100 percent accuracy. The storage savings are often dramatic, and it is not uncommon to see a 90 percent or higher storage reduction. In many cases, ROI can be achieved in months.