User Manual

2.5 Core Technologies


The aim in developing the Workflow was to offer a modern approach to data preparation and output of print data for digital printing systems. In order to focus on the usability, flexibility and openness of the system, the decision was made to integrate core technologies that offer open access without using proprietary formats.

In this Article we'll cover the following topics:

  • which core technologies by which OEM partners are being used
  • what the core development modules are called
  • how these core modules are interconnected

1. OEM-Partners und OEM-Technology

In the Workflow the following core technologies have been integrated in a way in which innovations from software developers can be made directly available to users of the Workflow. We are keeping a keen eye on market trends and developments that stand out in the forefront and are continually adding them to our system.

1.1. callas Software

Two technologies from callas Software GmbH (D - Berlin) are used in the Workflow in the form of SDKs.

pdfToolbox – this is used to display all PDF validation issues, PDF corrections and preview image rendering for the Workflow. This technology is also used when PDF-based color management and barcode generation is required.

pdfChip – This maps the imposition, inprinting and optimised collection of variable data to create the final print PDF. Precision, flexibility and speed enables output results which meet the extremely high standards required in the print industry, particularily digital printing.

Further information can be found on the callas website.


1.2. Color Logic

Software from ColorLogic (D - Rheine) is used in the Workflow in the form of an SDK.

CrossXColor – This is used to map the creation of color profiles and the implementation of color transformations in the output. The handling of color space-expanding colors is mapped on the basis of NColor profiles as well as the conversion of Spot Colors using proprietary algorithms.

Further information can be found on the Color Logic website.

1.3. Global Graphics

From Global Graphics (GB - Cambridge) three different SDKs are used in the Workflow.

HHR – with the implementation of the Harlequin Host Renderer SDK, the high performance Harlequin rendering engine can be used.

ScreenPro – with the implementation of ScreenPro, this digital printing optimised screening technology is now available.

PrintFlat – in conjunction with the implementation of ScreenPro, PrintFlat, a software that can be used to compensate for printer head variations and the resulting striation is now available.

More information about these technologies can be found on the website of Global Graphics.

Additional Software

Our OEM partners also sell independent applications, which may make sense as supplemental additions to the Workflow.

Especially for the analysis of measurement data Color Logic offers the ColorAnt tool. With this tool you can analyze measurement data directly from the Workflow to optimize results or edit data accordingly to achieve the desired results.

callas pdfToolbox is available for creating test and correction profiles. If you also want the full desktop application experience, we recommend purchasing the full version of callas pdfToolbox.

2. Core PPD development modules

Both in the manual as well as the software, the naming conventions of our software are used again and again. To familiarise yourself with these terms we have compiled a brief description for each module:

Is the engine that (a) formulates the output of print data render which includes color management - and (b) integrates the core software technology behind our OEM partners. In order that measuring devices from different manufacturers can be controlled directly from the Workflow, the corresponding protocols from manufacturers such as: Barbieri, Xrite and Konica Minolta were also integrated in ZuniComm.

The Print Management System serves as a backend system (a) for access to all databases and (b) to calculate processing steps in the form of subworkflows. Both the frontend and ZuniComm use an internal RestAPI to permanently access information from the PMS backend.

The WebGui is our frontend, which is based on HTML, CSS and JavaScript using the Angular Framework. The frontend implements and allows user interaction with the system in order to easily map complex processes. This technology is also leveraged for the user interface of the Adobe Illustrator Plug-In.

Paper Engine
The Paper Engine provides the tools for creating, modifying and drawing objects in the browser.

Impose Engine
With the Impose Engine, all calculations to optimize substrate space consumption in the backend are calculated and the result is passed on to the Paper Engine.


Previous Article 2.4 License Management
Still Need Help? Contact Us