Browse Prior Art Database

Apparatus for Autonomic Scanner system software Disclosure Number: IPCOM000211546D
Publication Date: 2011-Oct-11
Document File: 3 page(s) / 51K

Publishing Venue

The Prior Art Database


The problem that this discloses is the automated ability to administer an enterprise capture/scanner based system. Normally, an administrator that deals with issues directly and many times has to do analysis if something goes wrong. There are many areas to interpret such as logging, operating system constructs (such as perfmon counters), or database issues. Many times these pieces of data can be misinterpreted or ignored by the administrator and this could lead to bad decisions on what to do.

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

Page 01 of 3

Apparatus for Autonomic Scanner system software

The purpose of this invention is to create an autonomic system that controls and provides predictive information about a scan system. Current solutions basically have an administrator or an assistant figure a lot of this on their own and many of the tasks are very detail oriented, which they can miss or misinterpret.

The autonomic system will control various functions such as monitoring a scanner's endorser and figure out when it is time to order a new ink cartridge. Based on historical data the scanning system can predict whether it needs to create a new instance for processing because the loads will be higher, or to figure out what is causing an intermittent failure. Normally, these functions are monitored by an administrator but in many cases the administrator is simply too busy to deal with these issues on a day to day basis. Having this autonomic system will greatly simplify their life by handling or summarizing the issues. Essentially, it will become an assistant to the administrator for the capture system dealing with day to day issues.

The system is composed of four major elements:

1. Various input streams - this can be anything that can explain what the Capture system is doing. Many of the streams already exist in the capture system. Some common examples are

a. Error logs

b. Performance counters

c. A database containing the capture system statistical information

d. XML files that explain various pieces of custom behavior or configuration files for the Business intelligence logic.

2. A Database transformation service - this piece will convert the input streams into a special database designed for Business Intelligence database. This is a classic Extract Transform and Load (ETL) for data mining. Normally this is a combination of programmatic components along with the database's ETL facility. This component will be used in an OS Service or daemon.

3. A database with business intelligence feature - This is a data store with all the information to help make decisions on what to do with all the raw data. Using the business intelligence, data warehouse, and mining feature provid...