Method and system for providing a contract management system using an action-item table6338071Abstract Described is a novel relational database architecture that is adapted to storing information regarding the terms of one or more contracts, and the actions required to be performed under it. The database resides on a computer-readable storage medium as part of a multi-user computer network. By using simple subroutines readily apparent to one skilled in the computer arts, one can automatically generate alerts whenever an action needs to be performed. These alerts are then transmitted to users along the multi-computer network, appearing in an e-mail message that specifies the action, the individuals performing it, and the duties of each of these individuals. In this manner, one can ensure timely execution of the actions required under a contract. Claims What is claimed is: Description FIELD OF THE INVENTION
TABLE 1
ENTITY RELATIONSHIP DIAGRAM KEY
.diamond.-------------------------.circle-solid.
Relationship: one many
PK = primary key
FK = foreign key
CS = contract summary
int = integer
varchar = alphanumeric character
datetime = date and time
money = dollar amount
text = text
(.eta.) = referring to a field .eta. characters in length
At the highest level, the relational database of the invention may be understood as providing a relational structure principally among contract items and action items. The contract items describe the terms of the contract and the events that arise under it, while the action items describe and any action that these events require. For example, a contract item could provide "Payment due supplier," whereas the corresponding action item would provide "pay $ 500 to supplier on May 5." In one presently preferred embodiment, additional items facilitate the execution of the action items, such as product items, client items, employee items, and contact information for both employees and clients. FIG. 4 is an entity relationship diagram (ERD) showing elements of the relational database according to one embodiment of the present invention. Each rectangle in the diagram corresponds to a table in database. For each rectangle, the title of the table is listed above the rectangle. Within each rectangle, columns of the table are listed. Above a horizontal line within each rectangle are listed key columns, columns whose contents are used to identify individual records in the table. Below this horizontal line are the names of non-key columns. The lines between the rectangles identify the relationships between records of one table and records of another table. Table 2, below, describes the contents of each field with the tables depicted in FIG. 4.
TABLE Field Contents
CStblCONTRACT (402)
contract_id: Int (PK) Contract
Identification number
contract_type_id: Int (FK) Contract
type
identification number
contract_status_id: Int (FK) Contract
status
identification number
code: Int Generated
code value
contract_name: varchar (50) Contract
name
contract_title: text Contract
title
contract_comment: text Comments
regarding
the contract
agreement_request_recd_date: Agreement
request
datetime receive date
(?)
execution_copies_sent_date: Date
execution
datetime copies of
the contract
are sent
executed_copies_sent_date: Date
executed copies
datetime of the
contract are
sent
effective_date: datetime Effective
date of the
contract
expiration_date: datetime Expiration
date of the
contract
renewal_date: datetime Renewal date
of the
contract
termination_date: datetime Termination
date of
the contract
access_fee: money Access fee
access_fee_desc: varchar Access fee
(50) description
consulting_fee: money Consulting
fee
consulting_fee_desc: Consulting
fee
varchar (50) description
design_fee: money Design fee
design_fee_desc: varchar Design fee
(50) description
license_fee: money License fee
license_fee_desc: varchar License fee
(50) description
other_customer_fee: money Other
customer fees
other_customer_fee_desc: Other
customer fees
varchar (50) description
other_fee: money Other fee
other_fee_desc: varchar Other fee
description
(50)
tech_access_fee: money Technology
access
fee
tech_access_fee_desc: Technology
access
varchar (50) fee
description
discount_penalty: money Discount
penalty
discount_penalty_desc: Discount
penalty
varchar (50) description
royalties: money Royalties
royalties_desc: varchar (50) Royalties
description
CStblCONTRACT_STATUS (404)
contract_status_id: Int (PK) Contract
status
identification number
contract_status: varchar Contract
status
(20)
CStblACTION_ITEM (406)
action_item_id: Int (PK) Action item
identification number
contract_id: Int (FK) Contract
identification number
action_type_id: Int (FK) Action type
identification number
frequency_id: Int (FK) Frequency
identification number
action_desc: text Action
description
action_begin_date: datetime Action
begin date
action_end_date: datetime Action end
date
action_amt: money Action
amount
action_amt_desc: varchar Action
amount
(50) description
CStblFREQUENCY (408)
frequency_id: Int (PK) Frequency
identification number
frequency_desc: varchar Frequency
(20)
number_months: Int Number of
months
CStblACTION_STATUS (410)
action_status_id: Int (PK) Action
status
identification number
action_status: varchar (20 Action
status
CStblACTION_ITEM_MAP (412)
action_item_map_id: Int Action item
map
(PK)
identification number
action_item_id: Int (FK) Action item
identification number
action_status_id: Int (FK) Action
status
identification number
action_date: datetime Action date
action_comment: text Action
comment
CStblACTION_TYPE (414)
action_type_id: Int (PK) Action type
identification number
action_type: varchar (50) Action type
CStblACTION_EMPLOYEE_MAP (416)
action_emp_map_id: Int Action
employee
(PK) map
identification
number
emp_id: Int (FK) Employee
identification number
action_item_id: Int (FK) Action item
identification number
role_id: Int (FK) Role
identification
number
CStblEMPLOYEE (418)
emp_id: Int (PK) Employee
identification number
emp_first_name: varchar Employee
first name
(50)
emp_last_name: varchar Employee
last name
(50)
emp_email: varchar (50) Employee
email
address
CStblROLE (420)
role_id: Int (PK) Role
identification
number
role_desc: varchar (20) Role
description
CStblCONTACT (422)
contact_id: Int (PK) Contact
identification
number
contract_id: Int (FK) Contract
identification number
client_id: Int (FK) Client
identification
number
address_id: Int (FK) Address
identification number
role_id: Int (FK) Role
identification
number
contact_first_name: varchar Contact
first name
(50)
contact_last_name: varchar Contact last
name
(50)
contact_phone: varchar (20) Contact
phone
number
contact_extension: varchar Contact
extension
(20) number
contact_pager: varchar (20) Contact
pager
number
contact_email: varchar (50) Contact
email
address
CStblCLIENT (424)
client_id: Int (PK) Client
identification
number
client_name: varchar (50) Client name
CStblCLIENT_MAP (426)
client_map_id: Int (PK) Client map
identification number
contract_id: Int (FK) Contract
identification number
client_id: Int (FK) Client
identification
number
client_comment: varchar Client
comment
(255)
CStblADDRESS (428)
address_id: Int (PK) Address
identification number
client_id: Int (FK) Client
identification
number
street1: varchar (50) First line
of street
address
street2: varchar (50) Second line
of street
address
street3: varchar (50) Third line
of street
address
city: varchar (50) City
state: varchar (50) State
country: varchar (50) Country
zip_code: varchar (20) Zip code
phone: varchar (20) Phone number
fax: varchar (20) Fax number
internet: varchar (50) Internet
uniform
reference
locator
CStblPRODUCT_MAP (430)
product_map_id: Int (PK) Product map
identificaiton number
contract_id: Int (FK) Contract
identification number
product_id: Int (FK) Product
identification
number
product_desc_id: Int (FK) Product
It is understood that the examples and embodiments described herein are for illustrative purposes only and that various modifications or changes in light thereof will be suggested to persons skilled in the art and are to be included within the spirit and purview of this application and scope of the appended claims. For example, tables may be deleted, contents of multiple tables may be consolidated, or contents of one or more tables may be distributed among more tables than described herein to improve query speeds and/or to aid system maintenance. Also, the database architecture and data models described herein are not limited to biological applications but may be used in any application. All publications, patents, and patent applications cited herein are hereby incorporated by reference.
|
Same subclass Same class Consider this |
||||||||||