Method, system, and program for defining and managing complex contingent rules, and exceptions thereto, in a rule-based computer system

• US 7,783,587 B1
• Filed: 11/13/2008
• Issued: 08/24/2010
• Est. Priority Date: 11/17/2004
• Status: Expired due to Fees

• Current Assignee: Jeffrey G. Long
• Original Assignee: Jeffrey Long
• Inventors: Jenkins, Jimmy J., Long, Jeffrey G.
• Primary Examiner(s): Holmes; Michael
• Application Number:
  US12/270,600
• Time in Patent Office: 649 Days
• Field of Search: 706/46
• US Class Current: 706/46
• CPC Class Codes: G06N 5/025 Extracting rules from data

Abstract

An apparatus for storage, selective inspection, and execution of complex, contingent rules, comprises a computer having one or more central processing units, a user interface, and magnetic, optical, or other media for data and program storage and retrieval. Rules are defined partly as programs and partly as data. Access procedures are provided for selecting certain appropriate rules under defined conditions. Output procedures are provided for conveying the results of the rule selections to people, to the computer executing the rules, and to other computers.

Claims

1. A computer-readable storage medium having stored thereon elements of a system for the creation and/or execution of workorders, comprising:

a plurality of functional software objects;

tables of rule information, such rule information comprising;

existential rules that declare the existence of each and every type of entity and specific entities known to said system, which rules contain only a declaration of each entity'"'"'s identifier and metadata, said metadata comprising at least one of the following;

a Pin Flag to specify whether the exact contents of an existential entity are referred to literally in the system, and therefore require coordination with a user before being changed;

a Research Flag to indicate whether the rule requires further research on the part of a rule-maker;

internal notes regarding the rules;

an updated by entry for indicating the source of the last update to the rule; and

the date and time of the latest update to the rule;

non-existential attribute rules that declare known attributes of entities specified in the existential rules in terms of other existential entities known to the system, or certain general values, or both, said attribute rules comprising;

a first primary key column as a foreign key to an existential rule defining possible entities;

a second primary key column specifying an attribute type as a foreign key to an existential rule defining valid attribute types;

at least one foreign key to at least one existential rule;

columns for values representing at least one of the following;

general number, general date and time, general text, or general Boolean;

metaprotocol columns

non-existential protocol rules defining certain conditions under which implicit workorders will be generated, as well as the specific actions and contents of each step of each implicit workorder, as well as certain metadata, said protocol rules comprising;

a plurality of primary key columns as foreign keys to various existential rules defining possible entities;

a primary key column specifying an attribute type as a foreign key to an existential rule defining valid attribute types;

at least one foreign key to at least one existential rule;

columns for values representing at least one of the following;

general number, general date and time, general text, or general Boolean;

metaprotocol columns;

non-existential meta-protocol rules defining rules for creating masks, and mask sequences, for determining which of said protocol rules to follow and in what order they are followed, as well as certain metadata;

an interface to the system, comprising;

a mechanism permitting modification, directly by an administrator without recourse to further software programming, if not marked by a true value in the pin flag column, of at least one of the following;

said existential rules, said attributes rules, said protocol rules, said meta-protocol rules, and a combination of said rules;

a mechanism permitting the specification of an explicit workorder either by users or by the system, or by both;

wherein at least one of said existential rules and said non-existential rules are used by said functional software objects to govern either the creation or execution of an implicit workorder or both the creation and execution of an implicit workorder.

2. The computer-readable storage medium of claim 1, each row further comprising another column in the primary key for a sequence number to permit specification of more than one value for a particular attribute of a particular entity.

3. The computer-readable storage medium of claim 1, further comprising a plurality of additional functional software objects and data comprising:

representations of said non-existential rules, wherein;

said tables of rule information correspond to a conventional rules table having at least one primary key column and at least one non-primary-key column;

each non-primary-key column of said conventional table is represented by a row in said tables of rule information;

each row having columns which collectively constitute the primary key of each of said tables of rule information, said columns comprising;

the primary key corresponding to the primary key column of said conventional table;

an attribute type of said primary key; and

each row having at least one non-primary key column for each existential entity in the system to which the current entity has a relationship, the population of said at least one non-primary-key column determined by the attribute type of the primary key; and

each row having at least one column for metadata regarding that row;

wherein each said column is a foreign key to one of a plurality of associated pre-defined existential tables, with the exception of columns containing date-time, numeric, Boolean, or free-form text.

4. The computer-readable storage medium of claim 3, each row further comprising another column in the primary key for a sequence number to permit specification of more than one value for a particular attribute of a particular entity.

5. The computer-readable storage medium of claim 1, further comprising a plurality of additional functional software objects and data comprising:

a sequence number column in the tables of rule information containing meta-protocol rules so that the system may create and check masks in a specified order; and

a “

stop flag”

column in the tables of rule information containing meta-protocol rules so that the system may, upon successful creation and application of a given mask, stop creating and checking further masks before it has checked all rules in said tables of rule information containing meta-protocol rules.

6. The computer-readable storage medium of claim 5, wherein said medium is communicatively coupled to a general purpose computer, further comprising a plurality of additional functional software objects and data comprising:

instructions to the computer, in the form of a workorder, that can be assigned to a computer service and thereby executed by the computer in due sequence, or alternatively can be executed immediately by the computer.

7. The computer-readable storage medium of claim 5, further comprising a plurality of additional functional software objects and data comprising:

a product or services attribute table specifying which specific work attribute values to use when determining input values from a stimulus workorder to the mask-generation process, based upon the current protocol of the stimulus workorder.