where it all comes together. the adaptive mosaic reporting technology begins with the concept of a...

Mosaic ReportingWhere it all comes together

The Adaptive Mosaic Reporting Technology begins with the concept of a Mosaic.

A Mosaic Report is constructed by assembling a number of various components. The Mosaic Report, being one possible configuration of a given set of components.

KnowRisk’s Mosaic Reporting mimics this concept and applies it to software.

The Concept of Mosaic

Within the software realm there are a wide variety of different components. An example of a single component can be an extract from the database, a word processor document segment or a spreadsheet report.

All components are maintained in a repository and their sequence of assembly is configured and stored by this innovation for reuse.

Mosaic Reporting enables the user to configure the individual components and produce a final document; the Mosaic.

What Mosaic Reporting does

MosaicReporting

OR OR

Given a set of components, a multitude of Mosaics can be defined.

In theory the number could be endless, however, in practice only a few resulting configurations will pass the test of usability and compliance.

In this case the sequence in which components should be assembled and printed are saved as a template and can be used over and over again. Furthermore the user is given the option of editing, adding or deleting components according to their requirements.

Multiple Mosaics can be prepared from the same set of components or, components from different Mosaics can be intermingled to create other documents.

Theory vs. Practicality

Template

An important aspect is that the task of designing components and resulting Mosaic assembly can be separated.

A practical example in point is preparation of a policy document. Multiple documents can share a common work team and a core set of objectives. The result is, with minimal effort, a new policy document can be created by Mosaic Reporting.

Individual components from this collection can be used in different set of documents and on multiple occasions.

Other examples of common components could be organisation chart, building layout, contact information in case of emergency.