Print Statement Routing and Bundling

Using Preferences to Streamline and Tailor Print Delivery Processes

Routing and bundling for a given client can be fully defined and managed through the Doxim Business Process Manager (BPM) user interface. Routing allows documents to be separated based on user options such as delivery preferences (e.g. Hold at branch), or size and weight restrictions (as dictated by the local postal service).

Typically the data in a file that is processed through Doxim BPM is not received in the order in which the content will be output (e.g. to print.) The print routing and bundling capabilities built into Doxim BPM allow the order to be reset as needed. This helps keep documents with similar preferences and attributes together.

Doxim BPM creates bundles of documents to be processed, printed, uploaded or otherwise grouped together. This allows bundles to be defined by document attributes or their route for delivery to the customer such as documents that are mailed, oversized mail, those that need to be held at a location for pick up or by other attributes contained in the data stream.

Statements, as an example, can be routed based on the following criteria:

Preferences

Preference Management in Doxim BPM makes is possible to customize statements at a company, branch and customer level, enabling a whole new world of targeted member communications not available until today.

Preferences refer to the characteristics of a specific statement – such as a statement level preference by a bank customer to have their statement held at their home branch for pickup.

There are many preference options available in Doxim BPM, including:

Customer Information

Customer Information is obtained directly from the customer records of the statement. Customer information preferences that can be used in route configuration include:

• Age – e.g. youth, pensioners
• Language
• Province/State code
• Etc.

Template Preferences

Template preferences allow for different statement templates to be included in the same job based on criteria such as user profiles – e.g. pensioners can receive statements with larger print.

Plexing Preferences

Plexing allows for preferences to be set for different print output modes – simplex, duplex, mix. It is also possible for these preferences to be set differently for different parts of a document – e.g. the statement itself vs. the associated check images that are printed with the statement.

Image Preferences

Preference management also extends to the way in which check images are captured and presented on the statement. Doxim BPM supports 17 different pre-configured check layouts allowing the head office, branch or member to dictate things such as:

• Number of check images on a page
• Display of front and back sides of the item
• Display front and backs side by side or one on top of the other
• Ordering of the images (e.g. by Processing Date / Clearing Date Order or Check Number Order)

Branches

Branches are defined during the setup, or can be ingested from the incoming datastream.

Service Status/Condition and Customer Information

Service status/conditions are calculated values based on composed statement characteristics. For service status/conditions, routes can be configured based on criteria such as:

• Page count
• Sheet count
• Mail weight
• Number of images (e.g. checks)
• Inserter bucket selection
• Image exception
• Etc.

A Routing Tree in BPM is used to define how statements are grouped and bundled on output from production processing.

Each route defined within Doxim BPM is represented as a node on the Routing Management Interface that the operator uses. There can be many levels of nodes nested within each other.

For example: a route can be defined for all statements to be mailed. Within that node, statements can then separated into regions of Canadian, US and Foreign. Further, within each region mail can be separated by sheet count. The result of these routing nodes is a set of bundles can be defined for each mail weight category separated by region containing only statements to be mailed.

A Production Control Report can also be created which define the contents of each route and a detailed bundling report can be created to define the location of each statement and each bundle.

The routing tree set up tool can also be used to define very small runs for testing output and quality control prior to a very large run being initiated.

To find out more, please contact us