In simple terms, CURE consists of a database, a group of programs, and a variety of transaction layouts.  The programs function to apply transactions to accounts in the database and to report in various ways on the progress of the transactions to accounts in the system, their effects on various accounts and the resultant state of the accounts in the database.  Cure's competitive advantage over other systems lies in:

The relative power of its transactions

Its various methods of transaction entry

The ergonomics of its user interface

Its flexibility

The CURE batch system can be logically viewed as having three phases:

Data Entry

Edit/Production

Reporting

In the data entry phase any data to be applied to the database is collected and structured for submission to the CURE system.

Data may be entered in a variety of ways:

Data may be entered via a traditional entry process where a user creates transaction records and stores them in a file.  This technique is useful when the user must enter similar transactions for participants from hard copy.  Numerous facilities and text editors such as ISPF are available for this purpose.

Data may be extracted from the on-line journal file if processes have been performed on-line.  This extraction can be accomplished as part of the edit/production phase as a standalone task.

Data may be entered using transactions created from the conversion or manipulation of external files in some other format.  These external files may be formatted uniquely or they may be from one of the more popular packages (Lotus, dBase...)

It should be noted that the data phase is not limited to transactions only.  The company master or plan control file is a database which may be updated on-line in real time. Manipulation of the data elements in the control file can cause standard transactions to be processed in a variety of ways thus making a 'generalized' system extremely flexible.

In the Edit/Production phase transactions are processed against the existing database in accordance with the rules and conventions set forth in the plan control file.  As transactions are processed the resulting impact on the database is recorded.

During the Edit/Production phase:

Internal audits are performed.

Control totals are accumulated.

Plan driven processes such as vesting and available amount

Calculations are performed, and

Gains and losses are apportioned.

If the process is a production the resulting database changes will be stored. if the process is an edit, they will not be stored.

The Reporting phase produces hard copy documentation, external files, checks, forms, etc.  Any or all of this output can be customized for a client or generic output will be provided.

  Return to our Home Page.