Workflow Documentation

Data Environment
Registration form. Database format.

Supplemental Data
None.

Web Integration
Data can come from any source, no additional processing needed. It is likely that "on-line" registration would be submitted via the WEB. The data file created should be delimited this is easily done via a web scripting language, although much of the data, such as flight information, might come from another source.

Data Conditioning
Open in Excel and save as a delimited file format. Underscore statement. Header files cannot have spaces in VIPP. The spaces were replaced with underscores.

Quark File Conditioning
The letterhead design was saved as an EPS and used as a background image.

Asset Library
VIPP Project folder or VIPP Project Container

Coding
The stationery design, created in Quark, is imported as an EPS image background. The text was imported from an RTF file into Designer, which allows insertion of fields into the text. Conditional logic, created using Proform Designer's GUI based logic wizards, was used to change the basic letter text. The contents change based on if the attendee was flying or not. Within these two contexts, there also were several variables including flight information, smoking preference and others.

Lytrod's Proform Designer creates VIPP code and resources and the document is ultimately composed and assembled at the VIPP enabled engine from the raw data.

RIP and Print Process
The VIPP enabled engine does the composition, imposition, RIP and print process.

Provided is a VIPP Project Container, JOB6.VPC, the VPC file contains all of the files including a job submission file. The VPC can be launched using the VIPP Project Manager or on supported DFEs.

Since not all DFEs support Project Containers, a VIPP Project Folder, JOB6, is also provided. The project folder contains all files, including the data file, needed to run the application. Simply copy the JOB6 folder and its contents to the XGFC/Projects folder on the VIPP enabled engine.

The production print stream is the data file, in this case hosp_conf_registration.csv, which contains the VIPP job ticket and database data. In a production print environment, the data file would be sent to the VIPP enabled printer via LPR (this can be done via Lytrod's Proform Designer or via any standard LPR demon). For demonstration, you may simply open the project folder and "print" the data file: hosp_conf_registration.csv.

It is important to note that Lytrod supports VIPP image caching which dramatically improves job processing, as the variable images are ripped only once for the entire job.

Scalability
Unlimited. This is the advantage of the dynamic document construction method used by VIPP. The document is composed at the RIP in real time, as the data is sent to the printer.

Turnaround Time
30 minutes.

Overall Caveats and Considerations
None.