Browse Prior Art Database

Using Analysis For Automating Business Transactions Disclosure Number: IPCOM000201742D
Publication Date: 2010-Nov-21
Document File: 7 page(s) / 136K

Publishing Venue

The Prior Art Database


We study the operator's behaviour when executing business transactions by recording his actions and analysing them later. Then, based on the analysis results, we create an automated business transactions.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 28% of the total text.

Page 01 of 7

Using Analysis For Automating Business Transactions

     Hundreds of thousands of operators perform various
business transactions on a daily basis, such as in the IBM
Daksh center and other MBPS centers. Most of these
transactions require the involvement of the operator (e.g.,
filling fields, clicking buttons, etc..).As a result, these
processes become exhausting and time consuming, which leads to
reduced productivity, and even reduces the quality of the
service in certain cases.

     Consider, for example, the Ruby hotel in Haifa, which is
part of the world wide Carmel hotels chain. The Hotel chain
outsources its PO validation against suppliers invoices to the
IBM DAKSH center in India. The operator in Daksh works in an
application that presents invoice details (as processed by an
OCR engine from the scanned image of the invoice), beside the
windows of the details of the PO and the supplier, that are
opened by the operator. See the exemplary screen below:

Page 02 of 7

(This page contains 00 pictures or other non-text object)

Window 1: This is a simple notepad window with the invoice
details as produced by the OCR engine that processed the
scanned image of the invoice.

Window 2: General supplier's information, opened by the

Window 3: The PO details, opened by the operator..

Widnow 4: The letter manager window, where the operator does
his main work. This is a tool for sending messages to the
suppliers. The letter manager contains pre-defined message
forms. The operator can choose between the forms by entering
the form code into the field "Code", depending on his
decision of what should be sent to the supplier.

The Operator works as follows:


Page 03 of 7

After loading the information windows, the operator has to
compare the PO details (as they appear in the 3rd window)
against the invoice details (as they appear in the 1st window).
The operator goes over all the supplies in the PO, and for
each one he checks if it's quantity, unit price, total price
are the same in the invoice. Then he checks if the overall
total price is the same. After doing all the checks, the
operator sends the supplier a message using the "Letters
Manager" (4th window). The message depends on the comparison
- if the invoice matches the PO, the operator selects an
appropriate code in the Code field, which brings the
pre-defined acceptance letter text
- if there is a price mismatch (as in the exemplary screen)
the operator selects the code that brings a pre-defined letter
text that explains the problem to the supplier.
- if there is calculation error in the invoice, the operator
selects the code that brings the pre-defined calculation error
letter text.

After choosing the proper Code for the message, the operator
has to fill the empty fields in the predefined message form.
In our example he has to fill the invoice date and the invoice

    To do that, the operator has to read the invoice text to
find the information. Then he has to copy / type it to the
proper message field. The operator waste...