Orchestrate Your Statement Production Services

Doxim BPM Operator Console Makes it Easy

The BPM operator console provides the process operator with a unique view into, and control over, the entire end-to-end process – from file marshalling to eventual output to print and archive. Some of the key operator console functions include:

The Statement Console

This is used to browse for and add customer preference, statement, check and marketing message files to a job for downstream processing.

The Statement Console window is used to marshal files for a particular job

The Global Progress Window

This is a unique capability in Doxim BPM giving the operator a complete view, with drill downs, into the progress of every job in the system, along with its real-time status. Statuses tracked include:

• Running – The job is running but not finished
• Waiting – the job is set to go but waiting for services to be made available to run, or for the operator to make decisions required to run the job
• Finished – The services related to the job have completed
• Completed –Once completed, a job can be cleaned-up (deleted or moved to back-up)

Jobs can be further segregated by clicking the top of each column to auto sort, so the operator can focus on different job types at any given time – e.g. processing, finished, completed

The Global Progress Window provides the operator with access to service level details of each job. By clicking the job line in the Global Progress Window the operator can open up the Individual Job Process window.

The Individual Process Window

The Individual Job Process window is an interactive screen that shows a snap shot of the progress of each task within a job along with its status and percentage complete. The operator can see the details of a job and make a decision as to what to do, e.g. to expedite it if need be.

Bundle Decision Window

The Bundle Decision Window provides the operator with unprecedented flexibility into decisioning on a bundle by bundle basis. So, depending on a number of variables, the operator can make decisions to force out a bundle to speed the output process, which in turn maximizes the chance of meeting customer SLAs. For example:

A job may consist of 40,000 statements, split across a number of bundles:

• 39,000 to go to mail
• 150 items to be repaired
• 850 items designated hold at branch

It’s nearing the end of his day and the operator is trying to get as many jobs processed as possible. Having visibility into all this bundle information allows the operator to make decisions, for example the 39,000 to go to print tonight and to address the hold and exception bundles for processing in the morning.

To find out more, please contact us