Workflow Documentation

Data Environment
Typical data for this type of application would be database data from the dealer's database.

Supplemental Data
None.

Web Integration
Data can come from any source, no additional processing needed. Perhaps a data file might be submitted via the WEB to a print service bureau, in this case a Lytrod/VIPP workflow would be very efficient as such a small amount of information would be transferred.

Data Conditioning
auto_kit1.csv: Information needed from the excel file was retrieved and saved it into a comma separated format.

Quark File Conditioning
Quark files were saved into an eps format for use in Lytrod Software's Proform Designer. Also, to make the design a more manageable task, the border.eps was resampled into a low resolution file for viewing only. The original file (border.eps) will be used at the time of printing for best quality.

Asset Library
VIPP Project folder or VIPP Project Container

Coding
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.

Using Proform Designer's conditional logic wizard, the map image and location of the service center would change based on the state field in the database. The conditional logic wizard was also used to determine if the text: "It's been X long months" should print. In this case, using Proform Designer's field builder the date was extracted into a virtual field so the logic could be created

The address side of the postcard was designed by placing the EPS image of the postcard onto the background plane and placing the variable address fields on the design. The postnet barcode was generated the field builder using the VIPP POSTNET transform.

Once the postcard is created, to impose the job properly the Proform Designer multi-up function is used. The z-sort option allows for the proper positioning of the front and back . The for menu from Lytrod's Proform Designer is shown below:

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

Provided is a VIPP Project Container, JOB19.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, JOB19, is also provided. The project folder contains all files, including the data file, needed to run the application. Simply copy the JOB19 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 auto_kit1.csv, which contains the VIPP job ticket and the line data as described above. 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: auto_kit1.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. Since only the data is needed to actually run the application the documents are being dynamically composed at the VIPP enabled print engine, pre-composition issues of large print runs are not experienced with the Lytrod/VIPP workflow.

Turnaround Time
1.5 Hours.

Overall Caveats and Considerations
Zip code had 4 digits so the VIPP transform POSTNET (which inserts check digits) errors out.

There are two workarounds:

1. Ensure that data has appropriate number of digits in the zip code fields: 5, 9, or 11.

2. Enable Lytrod's Proform Designer's unique capability to validate length of the postal code by using the new function command.