ISIS PAPYRUS CASE STUDIES

Internet Bank: The Key is Integration

Implementing a multi channel, One-to-One business document solution for Web delivery and optional automated print.

Case Study

The bank implemented a banking portal as a virtual customer service branch office. Outstanding customer service by providing 24/7 access for personalized statements and reports were set as requirements. Depending on the client profile, the same document must also be printable in high quality, automatically be enveloped and mailed. Leveraging existing business data directly from the business application on the mainframe for electronic document presentment and optional printing was a prerequisite.

The Web creates new challenges.

The Requirements:

• Internet Banking document service based on existing z/OS mainframe application programs delivering the business data for the statements and reports.

• Viewing of the statements and reports in the browser in PDF format

• Optional printing of same documents on different printers

• E-mail notification with Hyperlink in documents on new available statements in the e-Postbox

• Around the clock access: 24 hours, 7 days
  

Freedom of Platform Choice with Papyrus

• Legacy business data is fully supported

• Single time document design and formatting for 100% identical results on Web and paper

• Fast document development using 100% WYSIWYG ­Papyrus Designer

• Business-user departments are empowered to edit text and marketing messages using Papyrus EYE user friendly Flash GUI.

• DocEXEC high speed batch and ad hoc formatting on 11 platforms

• Repository for central management and administration of all document resources, building blocks, user authorization and document processes.

• WebArchive – AFP to PDF generation on the fly

• PrintPool for central output management adding OMR and Barcodes

• Using central print and mail facilities for statements not viewed through the internet.

• E-mail Server for e-mail notification and URL

 

Internet Bank solution

How the complete production cycle was implemented

Step 1: Document Design

Document resources, data, logic and layout definitions are developed with the integrated WYSIWYG Papyrus Designer on Windows Vista. They are stored in the central Papyrus WebRepository. The business department uses the Papyrus WebPortal with the Papyrus EYE GUI to take part in the document development process and e. g. deliver marketing messages for promotions to be included in statements and reports.

Step 2: Document Assembly

Business users authorized by their role and privilege edit text elements in a front-end document application either WebPortal or Papyrus Client based. To secure that only those text elements go into production that have been authorized, a sign-off process based on the ‘four eye principle’ was implemented. All building blocks generated by the users are versioned, possibly validated with date and time and stored in the WebRepository. They are automatically selected by Papyrus DocEXEC when formatting the document into AFP and/or PDF. Change Management based on user authorization and versioning of objects are integrated standard functions of the system.

Step 3: Formatting

The input data is read by DocEXEC. The layouts/forms, resources and text elements are dynamically loaded by DocEXEC to be formatted with the business data into an AFP or PDF file. At the same time also all needed indexes are generated by DocEXEC. In case of missing elements, an error log file is generated.

Step 4: DB Check-In

The documents produced in batch are checked into the Papyrus WebArchive objects database.

Step 5: Notify by E-mail

The customer is informed by an e-mail notification which contains a URL that his documents are available. These e-mail notifications are sent at night.

Step 6: Web Viewing

The user logs in through the bank's website where security and authorization is performed by the banking portal. The WebArchive interface generates a list of available documents for this customer. Once the user selects a document from WebArchive, they are converted on the fly from AFP to PDF for viewing. Alternatively they can already be stored in the Webarchive in PDF with bookmark indexes.

Step 7: Printing (optional)

Statements that were not viewed by the clients on the Web are automatically transferred after a certain time period from the WebArchive into the PrintPool. Each night a bundling and sorting run produces an AFP file with enveloping OMR markers. They are automatically mailed using the central print and enveloping setup.

By the way...

Although the solution shows a fairly complex application, there were less than 6 weeks of total on-site support needed from ISIS Papyrus. This included the document development effort and the setup of the central Repository and Archive.

The total project phase was five months.