To discuss your particular
requirements, email us at

Reference Project

clSysTech and INVARIS at ÄVN

Document Composition

Document Composition Overview

Automating the output of business documents for medium and large organisations is usually achieved with a professional Document Composition solution. Simple office software, such as a word processor, is not going to be powerful enough to automatically produce large volumes of documents, such as customer mailings, end-of-month invoices, etc. Further, simple word processor tools on a user client cannot easily guarantee a Corporate Design for the business documents or ensure fundamental requirements for those documents (e.g. legal company information) are always output. Finally, when your data is in an application database, e.g. in your SAP ® system, then how do you get that data into a word processor?

The INVARIS Document Composition system is designed to provide these requirements:

Not all Document Composition systems can provide all of these requirements. Some are good at mass production and integrate well into systems such as SAP, others are better at producing lower volume interactive documents. Interactive documents also need special consideration, generally it is not desirable to allow a user to change all parts of the documents, rather he or she should be limited to making changes and additions in pre-defined parts of a document.

Document Test System

INVARIS also offers a unique Document Test Center for implementing a professional Change Management strategy for the continuous maintenance of document layouts. Sample raw data is stored in a database so that when changes are made to the rules applied to that data and/or the resources (e.g. text building blocks) used in documents, a complete range of automated document tests can be carried out. The Document Test Center will compare previous (standard) results with new output and immediately highlight any documents that show a difference from their previous formatting.

The system thus allows "negative tests" to be conducted in a formalised, controlled fashion. Your developers can not only be assured, that a change they implemented for a specific document layout was sucessful, they can also quickly determine whether their changes have had any "negative" side affects and eliminate those too! The end user is not longer your guinea-pig and confidence returns in the change management process for document production.