User Manual

Workflow
The following diagram shows an overview of the workflow required to integrate a
bounce system into a retail environment.
There are 7 steps to complete a full integration. These are:
1. Use Policy Architect to set the data sources and define the Template Fields that
will be used in creating the product images. Template Fields are derived either
directly from the Product Data Fields in the imported data sources or from
transformations on the Product Data Fields.
2. Use Template Architect to create a Collection of image templates for each EPOP
type and for each offer type using the Template Fields defined in step 1
Steps 1 & 2 often become an iterative process as the templates are developed.
3. Use Policy Architect to define the scheduling policies that determine when the
data will be acquired from the defined data sources and when the images will
be transmitted to the EPOP devices.
4. Acquire the Data Values according to the transformation and policy rules
defined in steps 1 & 3.
5. Render the product images using the Data Values acquired in step 4 and the
Template Collection defined in step 2.
6. Update the EPOP devices according to the scheduling rules defined in step 3.
7. Use Reporter to view the update statistics.
The following guide details how to install the Bounce Architect, Processor and Manager
elements of the Bounce software suite (see Bounce Communicate Installation Guide for how
to install and use Bounce Communicate element).
It also details how to create an Architect Policy and Template configuration files and how to
load these onto a PC running Processor, Communicate and Manager