Browse Prior Art Database

System and method for adaptive warning in financial software Disclosure Number: IPCOM000233902D
Publication Date: 2013-Dec-27
Document File: 4 page(s) / 154K

Publishing Venue

The Prior Art Database


In the use of financial/ERP software the user enters continuously, for the whole day, economically important data. In the case of human error, many operations are easily remediable (invoicing, inventory movement...). Other operations (urgent bank transfers, fiscal operations...) are more delicate. The classic message "Are you sure?" is not effective in this context because the operator repeats several times a day the operation and get used to the warning. The proposal is to use the computer’s camera to assess the user fatigue and produce, in an adaptive way, the warning only when necessary.

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

Page 01 of 4

System and method for adaptive warning in financial software

The system disclosed here uses images taken by a camera to give feedback to a user. There are , for example, there are numerous solutions to evaluate the ergonomics of the position taken by the user to the monitor. The study of eye movement has also found a strong correlation with the state of attention. It is

possible today to monitor the degree of attention while driving of motor vehicles and for the conduction of utensils machinery.

Here is disclosed a software solution to articulate the degree of attention monitored through the camera with the context of the task that we are carrying out. We are able in this way to issue a warning message only when it is statistically more necessary (conditions of low attention and critical transaction request). This methodology is much more effective than the systematic emission of warning messages, to which the operator gets used and does not pay attention.

The system is represented in the figure:


Page 02 of 4

The software code (1) is analyzed to assign a weight at every function/transaction supported in order to create a catalogue of level of criticality (2). The weight is assigned by the software analyst depending on the

possible damage. For example an urgent bank transfer will have a higher weight compared to a transaction easily cancellable.

The sequence of transactions required over the time is monitored and integrated by all the other available data at ru...