Abstract:
A contract system automates negotiation and generation of contract documents by managing the work flow in a contract approval process. Multiple users, coupled by a computer network, access a contract database containing multiple contracts with multiple contract components therein. The system manages communications and security between a client system and the contract database. A client applet facilitates user input at the client system and assists in a standardization of legal phrasing and contract negotiation. The client applet enforces business rules to qualify a contract for expedited approval. Generalized templates are employed to enable rapid prototyping and creation of new contracts. A method governs the automated contract negotiation and generation process within a business organization with assistance from a graphical user interface.

Description:
BACKGROUND OF THE INVENTION 
     1. Field of the Invention 
     The present invention pertains generally to electrical computers and more particularly to systems and methods for automating the negotiation and generation of a contract. 
     2. Description of Related Art 
     Sales contracts are important elements of modern business. Among other characteristics, a modern sales contract typically includes business terms (such as prices, quantities, delivery dates and discounts), legal phrasing, and approvals by the parties. A single large sales contract may be quite complex and require input from diverse groups within a business organization, including a legal department, a business department, and other appropriately authorized personnel. Other parties to the contract may also provide input requiring modification to contract language and terms. Furthermore, large businesses are often drafting, negotiating, and executing multiple contracts with various parties simultaneously. As such, managing the contract flow and approval process for such concurrent contracts presents considerable obstacles and risks to proper contract negotiation and generation. In addition, these difficulties are commonly amplified by time constraints introduced by typical business pressures. 
     The advent of computer systems and networks has provided some attractive opportunities for computer assistance of contract generation; however, computer systems and networks have also introduced new difficulties and amplified old ones. For example, modern contracts are typically emailed to the various contract parties and their agents for revision, negotiation, and approval. Edits may be made to the electronic document contained in the email and rerouted to the parties for review. Recipients may also print hard copies of such electronic documents for review and editing purposes. Such uncontrolled proliferation of electronic and hard copy contract documents presents version control concerns, unauthorized disclosure risks, unauthorized modification risks, and interruptions in the approval process. 
     Products have also been introduced to assist a user in drafting contracts. Such products typically provide boilerplate legal phrasing from which a user may select choices of fill-in-the-blank legal clauses. One such product, the Quicken Family Lawyer Deluxe by Intuit, Inc., asks a user a series of context-sensitive questions and combines provisions and terms determined to be appropriate for the answers provided. 
     These approaches lack significant characteristics desired by a large business seeking to automate the contract generation process. As discussed, a document-based, or e-mail-based, approach present document proliferation risks and approval process delays. Furthermore, products like Quicken Family Lawyer Deluxe do not provide desired workflow management, such as access control, approval coordination, or collaboration features. Therefore, need exists for an automated contract negotiation and generation system providing groupware-like collaboration mechanisms, version control, and workflow management. Moreover, need exists for an automated contract negotiation and generation system capable of applying defined business constraints to expedite the approval process of contracts therein. 
     BRIEF SUMMARY OF THE INVENTION 
     It is an object of the present invention to provide a system that automates contract negotiation, approval, and generation among multiple users coupled by a network. 
     It is another object of the present invention to provide a method for using a computer system and network to automate contract negotiation, approval, and generation. 
     Additional objects, advantages, and novel features of the invention will be set forth in part in the description which follows and in part will become apparent to those skilled in the art upon examination of the following or may be learned by practice of the invention. The objects and advantages of the invention may be realized and attained by means of the instrumentalities and combinations particularly pointed out in the appended claims. 
     To achieve the foregoing and other objects, in accordance with the purposes of the present invention, as embodied and broadly described herein, the system of this invention may comprise a sharable contract database of editable data defining a contract as a plurality of discrete contract components that has a class level assigned to each user in a hierarchy of users having access to the sharable contract database; a contract status indicator field in the sharable contract database that indicates a negotiation status of the contract and is capable of changing during an automated contract negotiation process; and at least one database field in the sharable contract database that indicates a dynamic user access mode based on the class level and the contract status indicator, the user access mode being capable of preventing a user in the hierarchy of users from changing the editable data in the sharable contract database. 
     The present invention may also comprise, in accordance with its object and purposes, a method having the steps of providing a web server computer that stores a contract negotiator applet; providing a client computer coupled to the web server computer; loading the contract negotiator applet to the client computer from the web server computer; executing the contract negotiator applet on the client computer; providing a contract database coupled to a broker; and accessing the contract database by the contract negotiator applet via the broker. 
     A system in accordance with the present invention provides advantages over other computer-based contract systems. Such a system stores all contracts and all contract components in a central repository or contract database. Multiple users may access the contract data for which they are responsible based on predefined access rights and hierarchies. The status of a contract at any single point in the automated process assists in controlling access to the contract database and defines the next approval level required in the contract approval flow. When a contract is approved, a new version of the contract is generated, and the previous version is maintained within the system so that a user can view previous versions of the contract. The system also allows standardized contract clauses to be used throughout the system and also allows customized information to be entered into the contract database. The system supports expedited approval policies by applying business rules to control specific contract terms. 
    
    
     BRIEF DESCRIPTION OF THE DRAWINGS 
     FIG. 1 depicts a general purpose computer capable of operating as a database server, a web server, or a web client executing an applet embodiment in accordance with the present invention. 
     FIG. 2 depicts a high level overview of a system in accordance with the present invention. 
     FIG. 3 depicts a high level overview of the client-server component architecture in accordance with a present invention. 
     FIGS. 4A and 4B depict a flow chart illustrating an automated contract negotiation system in accordance with the present invention. 
     FIGS. 4C and 4D depict a flow chart illustrating an alternate embodiment of an automated contract negotiation system in accordance with the present invention. 
     FIGS. 5A and 5B depict a diagram depicting data tables and table relationships in a database in accordance with the present invention. 
     FIG. 6 illustrates a Q&amp;A generic template screen with the Pricing tab selected. 
     FIG. 7 illustrates a Q&amp;A generic template screen with the Clarification tab selected. 
     FIG. 8 illustrates a Q&amp;A generic template screen with the Clause tab selected. 
     FIG. 9 illustrates a BLOB generic template screen with the Pricing tab selected. 
     FIG. 10 illustrates a No Pricing generic template screen with the Clarification tab selected. 
     FIG. 11 illustrates a screen for selecting an account team responsible for a selected contract. 
     FIG. 12 illustrates a comment view screen in accordance with the present invention. 
     FIG. 13 illustrates a Quick Close Terms and Conditions screen in accordance with the present invention. 
     FIG. 14 illustrates an exemplary Quick Close template in accordance with the present invention. 
     FIG. 15 illustrates a second exemplary Quick Close template in accordance with the present invention. 
     FIG. 16 illustrates a screen for entering a new contract into a system in accordance with the present invention. 
     FIG. 17 illustrates a &#34;User Entry/Maintenance&#34; screen to allow a Class 6 user to manage users in a system in accordance with the present invention. 
     FIG. 18 illustrates a screen to allow a Class 6 user to manage class hierarchies according to a Class 1 user in accordance with the present invention. 
     FIG. 19 illustrates a screen to allow a Class 6 user to globally replace instances of a user name within multiple hierarchies in accordance with the present invention. 
     FIG. 20 illustrates a &#34;Clause Support&#34; screen to allow a Class 6 user to maintain clauses in a contract baseline in accordance with the present invention. 
    
    
     DETAILED DESCRIPTION OF THE INVENTION 
     One operating environment in which the present invention is potentially useful encompasses the general purpose computer. In such a system, data and program files may be input to the computer, which reads the files and executes the programs therein. Some of the elements of a general purpose computer are shown in FIG. 1, wherein a processor 101 is shown having an input/output (I/O) section 102, a Central Processing Unit (CPU) 103, and a memory section 104. 
     The I/O section 102 is connected to keyboard 105, display unit 106, disk storage unit 109, and disk drive unit 107. Generally, in contemporary systems, the disk drive unit 107 is a CD-ROM driver unit capable of reading a CD-ROM medium 108, which typically contains programs 110 and data. Computer program products including mechanisms to effectuate the system and methods in accordance with the present invention may reside in the memory section 104, on a disk storage unit 109, or on the CD-ROM medium 108 of such a system. Alternately, disk drive unit 107 may be replaced by a floppy drive unit, a tape drive unit, or other storage medium drive unit. Examples of such systems include SPARC systems offered by Sun Microsystems, Inc., personal computers offered by IBM Corporation and by other manufacturers of IBM-compatible personal computers, and other systems running the UNIX-based operating system. In accordance with the present invention, procedural components of a program product may be executed by CPU 103, and the program product and associated data may be stored on disk storage unit 109, disk drive unit 107 or other storage medium drive unit coupled to such system. 
     FIG. 2 illustrates the logical architecture of a preferred embodiment of the present invention. Web server 200 provides access to a computer network, such as a LAN, a WAN, an Internet, an Intranet, and an Extranet, and has access to a JAVA™ Contact Negotiator Client Applet 208 applet loaded on a storage medium. In a preferred embodiment, the JAVA applet provides the Graphical User Interface (GUI) of an automated contract negotiator and generator system and conducts communications between Contract Negotiator client system 202 and web server 200. Contract Negotiator Client system 202 is coupled to web server 200 via a TCP/IP network 204 or any other suitable network. A user may access web server 200 using a standard web browser, such as Microsoft Internet Explorer 4.01. Such a user may enter a specific URL (i.e., web site address) into the web browser at Contract Negotiator client system 202 to access a web site on web server 200. When a network connection is established between the client system 202 and the web server 200, the JAVA applet is accessed by web server 200 and loaded into Contract Negotiator client system 202, which then executes the JAVA applet. Because the JAVA applet does not reside on Contract Negotiator client system 202 until it is downloaded via web server 200, the applet is known as a &#34;zero-footprint&#34; application. 
     JAVA is a programming language similar in syntax to C++. When JAVA is initially compiled, the result is a &#34;byte-code&#34; set of instructions. The byte-code instructions operate on a web browser that, in turn, issues the i instructions to the operating system. The web browser is specific to the platform on which it is executing, whereas a JAVA applet is generally platform-independent because the JAVA code is actually executed within a JAVA Virtual Machine (JVM). A JVM interprets platform-independent byte-code instructions for execution on a specific platform. A JVM may also compile the downloaded byte-code instructions to produce machine code for the specific platform. JAVA applets also have restricted access to system resources to prevent unauthorized access to a client system by an Internet-borne applet or virus. 
     The web browser on Contract Negotiator client system 202 may execute both byte-code instructions and machine code. Contract and user data used by the contract negotiator application is stored on storage medium 210 and serviced by database server 206, which runs Informix software on a dual-processor Digital UNIX system in a preferred embodiment. The JAVA applet accesses the contract and user data through the web server 200, which runs Microsoft Windows NT 4.0 software on an HP NetServer Pro in a preferred embodiment. Web server 200 accesses the contract and user data via communication with database server 206 over TCP/IP network 214. 
     Furthermore, a system in accordance with the present invention may interface to other corporate back-office applications. Database server 206 is coupled via a TCP/IP link to corporate back-office systems 212, commonly on mainframe MVS systems running back-office applications. Customized application procedural interfaces (APIs) are generally used to accomplish the back-office communication. One example of a back-office system is a billing order entry system. Such a system is an order entry system that is used to establish hierarchies within a customer&#39;s corporate structure and to store discount contract information. The system builds corporate customer billing hierarchies, and feeds these to billing systems for multiple-level invoicing. An interface to the billing order entry system may be used to automate further procedures. For example, once a contract has been finalized and approved (the status for which is maintained in the contract database), the system may issue a message to the back-office billing order entry system, thereby triggering installation or activation of the services for that customer. The back-office system can also send messages to the database server to update the contract database with contract status changes that result from services activated in the back-office system. 
     FIG. 3 illustrates the architecture of a system for executing a contract negotiator in accordance with the present invention. The system employs a reusable client-server component architecture, herein called &#34;netRoaster.&#34; The netRoaster subsystem resides between proxy server 304 and brokers 308. The netRoaster client element operates on proxy server 304. The netRoaster server element operates on brokers 308. In addition, a &#34;webRoaster&#34; component is combined with the JAVA applet and executed by browser 300. Proxy server 304 operates as the webRoaster server, and browser 300 operates as the webRoaster client. In the preferred embodiment of the invention, a webRoaster component is combined with a contract negotiator JAVA applet embodying the GUI and communications functionality of the contract negotiator. Client system 300 executes a web browser, such as Microsoft Internet Explorer 4.01, which executes one or more client applets. Web server 302 distributes the most current client applet code to client system 300 upon request via a TCP/IP network connection 313. 
     Client system 300 is also connected to proxy server 304 via a TCP/IP network. Proxy server 304 runs on the same physical machine as web server 302 and is used by webRoaster to provide access to the underlying scaleable database server and architecture (i.e., the netRoaster subsystem). Proxy server 304 obtains a reference to the least loaded of brokers 308 for each unique client-server connection. Brokers 308 provide web server 302 with access to data in contract database 3 12 through a database server and business objects 310. Brokers 308 also provide automatic tracking of unique, persistent memory stores available to each client. Moreover, brokers 308 provide extensibility, because business objects 310 may be scaled to support changing requirements without affecting a concurrently running netRoaster subsystem. 
     Central registry 306 is the first component initiated in a netRoaster architecture. Central registry 306 provides plug-and-play configuration, so that authorized brokers and clients need only know the DNS (Domain Naming System) name of the central registry in order to gain access to the netRoaster subsystem. Central registry 306 also provides scaleability, because brokers 308 are started after central registry 306 and, thereafter, individually register themselves with central registry 306. Furthermore, central registry 306 is responsible for maintaining a list of currently available brokers 308 at all times. New brokers may be brought on-line dynamically (i.e., without any reconfiguration). Central registry 306 also allows dynamic load-balancing of brokers 308 to insure that each new client-server connection request is routed to the least loaded broker upon request. Brokers 308 provide the traditional server tier in a multiple tiered client-server communication model. 
     After at least one of broker 308 has been started successfully, the client applet (also known as a webRoaster applet, since it includes the standard webRoaster component) may be started. The webRoaster applet provides the client applet GUI in a separate browser frame on client system 300. A webroaster applet looks equivalent to a standalone application, however, it still has the same access restrictions as any other JAVA applet. The webRoaster applet also provides a GUI screen engine that simplifies access to the netRoaster architecture. 
     The webRoaster applet connects to proxy server 304, which is used by webRoaster applets to provide access to the scaleable netroaster architecture. After proxy server 304 obtains a reference to the least-used broker for a particular client-server connection, it then connects to the referenced broker via a JAVA Remote Method Invocation (RMI). If a broker connection is lost, proxy server 304 provides access to a standby broker or web server (automatic fail over). Proxy server 304 also provides proxy communications between the webRoaster applet and the netRoaster broker, which allows the broker to interact with a webRoaster applet as if it were a standard netRoaster client application. 
     Business objects 310 provide the means for the netRoaster brokers 308 to interact with the contract database 312. Business objects 310 provide a database-independent abstraction layer for supporting client-server interactions with database 312 based on business functions, not merely database calls. 
     Business objects 310 also provide reusable components to satisfy business needs. Business objects 310 also use an industry-standard ODBC (object-oriented database connectivity) interface via the JDBC-ODBC bridge 316, where JDBC means &#34;JAVA Database Connectivity.&#34; The use of business objects 310 enables more efficient development by reducing co-dependencies between client and server development teams. 
     A preferred method of automatically negotiating and generating a 30 contract, in accordance with the present invention, is depicted in FIGS. 4A and 4B. There are six classes of users currently defined for a preferred embodiment of the present invention, but a greater or lesser number of user classes is feasible without departing from the characteristics of the present invention. These classes represent, in part, approval levels needed for contracts. The number and definition of user classes depends on the business process supported by a contract negotiator system. The configuration of user levels described herein correspond to a particular embodiment of the present invention, but other configurations are also contemplated in accordance with the present invention. 
     In this configuration, the first user class (Class 1) comprises sales representatives, who generally initiate each sales contract. Class 2 comprises pre-sale analysts, who make initial business and credit evaluations and provide pre-sale information regarding the Class 1-proposed sale contract. Class 3 comprises of branch management, who may review and make comments regarding ongoing contracts, but who do not modify contracts through the contract negotiator system. Class 4 users comprise business development analysts, who must approve the business characteristics of the proposed contract before the contract is executed. Class 5 comprises legal personnel who, at certain stages in the negotiation and generation process, have full access to all aspects of the contract data, subject to contract status restrictions. Also, in a preferred embodiment of the present invention, an administrator class (Class 6) is defined to manage authorized users of the system, to input legal phrasing, and to adjust contract trees within the system. 
     A Class 6 administrator does not have authority to modify contracts within the negotiation and generation process, but may provide modifications to user&#39;s contract baselines, templates, and other system components that affect subsequently initiated contracts. Subclasses of users, called &#34;point-class users&#34; (e.g., class 2.1), may also be defined. 
     Each contract is assigned a &#34;team&#34; associated with a permanent hierarchy and comprising users from each class who are responsible for that particular contract. A Class 6 user initially assigns each Class 1 user with a permanent hierarchy. Non-Class 6 users cannot add other users to or remove other users from a Class 1 user&#39;s permanent hierarchy. Other, non-permanent users may be added to the contract team by any class of user. Each contract further specifies a minimum and maximum number of users at each level of hierarchy required to completely review and approve the contract. For example, a particular contract may require a minimum of one Class 2 user and a maximum of three Class 2 users in its team. 
     As depicted in FIGS. 4A and 4B, a Class 1 user initiates a new contract in block 400 and inputs proposed contract terms and comments in block 402. When the Class 1 user initiates a contract, the contract negotiator system automatically assigns team members according to the Class 1 user&#39;s permanent hierarchy. The permanent hierarchy comprises users from each class, except Class 6, who are immediately and permanently responsible for that particular contract, and represents part of a contract team. 
     When a user logs into a contract negotiator, they are presented with a list of those contracts to which they are assigned as a team member. The list also includes a contract status and serves to solicit reviews and/or approvals from higher-class users. In block 404, the Class 1 user submits a contract, containing relevant terms and comments, into the contract negotiation process. After submission, all classes of team members may access (with appropriate class and status access restrictions) the contract. For example, Class 2 users may access the contract to provide pre-sale and credit review and to make comments regarding the contract (step 405). A Class 2 user may also &#34;true up&#34; contract database 412 to make it consistent with changes made to a corresponding hard-copy contract derived from the database. Except for these actions, Class 2 users have no other write-type access authority to contract database 412. Primarily, the Class 2 user performs informational and administrative tasks, not necessarily a strict &#34;approval&#34; task that impacts the system&#39;s workflow management. Likewise, in block 428, Class 3 users may review and make comments regarding the concurrently negotiated contract by accessing contract database 412 through the contract negotiator system, but Class 3 users have no write-type access authority to contract database 412. 
     A submitted contract proceeds to a Class 4 user (a business development analyst) in block 406, who manages the business impact of the contract. In block 408, the Class 4 user submits the proposed contract to the Class 5 user in the legal department, who may, in block 410, add to or modify the contract, or return it to the other users in the hierarchy for modification and review. In a preferred embodiment of the present invention, the modifications to the contract are made in a central repository (i.e., contract database 412) accessed through a contract negotiator system. 
     The contract may flow among the class users until all members of the contract team are satisfied with the terms and language of a contract (referred to as &#34;automated negotiation&#34; herein). When all required levels of approval have been obtained in block 413, a user in block 414 may obtain an executable copy of the contract 416 (e.g., by printing out a hard copy) and send it to the customer for review and/or execution in block 418. If the customer makes or requires modifications to the contract terms in block 420, the changes may be entered into the automated contract negotiation system as described above. This process continues until a signed contract is obtained, or the contract generation is aborted (e.g., if the parties cannot reach agreement). If the contract is signed in block 422, a Class 2 user in block 424 assigns a &#34;signed-external&#34; status to the contract in contract database 412. If the contract is aborted, a Class 2 user in block 426 assigns a &#34;void&#34; status to the contract in contract database 412. Any modifications made to the contract document external to the contract database are amended in the database (or &#34;trued up&#34;). 
     Alternately, another embodiment (illustrated in FIG. 4C and 4D) in accordance with the present invention requires that the legal department capture (in block 466) a summary 472 of the contract terms and legal phrasing determined in the negotiation process and manually incorporate this information into a hard copy or soft copy external document stored on an external storage medium 488. Subsequent modifications are made by the classified user in the contract document 476 rather than the contract database 470. Otherwise, the process is equivalent to the process of FIG. 4A. 
     Unlike alternate methods of computer-assisted contract generation, contract negotiator is a database-driven system, in which a contract comprises many components stored in different table entries in a database. Each contract is assigned a number (or ID) that is used as a key to the records in the various table entries containing components of the contract. As each contract is approved within a central repository or database, a snapshot of the approved contract becomes the next version. Users will have access to view all versions of the contract over the course of the negotiation. 
     FIGS. 5A and 5B illustrate a database table diagram for a database in accordance with the present invention. Each table is identified by a labeled block in the figure, and the fields within each table are described within this specification. A solid interconnecting line represents a primary and foreign key relationship in the physical database. In addition, a dotted interconnecting line represents a programmatic relationship in a stored procedure, view, or trigger (e.g., tables that are updated together by software). Furthermore, an interconnecting line with a solid circle on one end represent a &#34;one to many&#34; relationship, where the end with the circle represents the &#34;many&#34; and the end without the circle represents the &#34;one.&#34; 
     Five types of tables are managed in a contract negotiator database: 
     (1) user --  tables; (2) contract --  tables; (3) support --  tables; 
     (4) generic --  template --  tables; (5) quick --  close --  tables; and 
     (6) custom --  screen --  tables. The user --  tables include a User table, 
     a User --  Hierarchy table, a User --  Login table, a Branch table, a Channel table, a Region table, and a Title table. These tables are populated and managed by Class 6 users only. 
     The User table defines users who have access to the contract negotiator system and is depicted below: 
     
                                           TABLE__________________________________________________________________________UserColumn Name   Key Type   Size Description__________________________________________________________________________user.sub.-- id   Y   CHAR   10   User ID (usually Social Security                   Number)first.sub.-- name       VARCHAR              20   User&#39;s first namemiddle.sub.-- initial       CHAR   1    User&#39;s middle initiallast.sub.-- name       VARCHAR              25   User&#39;s last nametitle   Y   VARCHAR              30   User&#39;s titlevnet        VARCHAR              7    VNET of userdepartment  VARCHAR              4    Department number of userlocation    VARCHAR              3    Location code of userbranch      INTEGER     Branch IDchannel     INTEGER     Channel IDregion      INTEGER     Region IDemail       VARCHAR              25, 10                   Email address.sales.sub.-- city.sub.-- cd       VARCHAR              4    Sales City Code of useraccess.sub.-- flag       CHAR   1    Team/National Access flag.                   Default is `T` for team.update.sub.-- flag       CHAR   1    Comment Only/Full Access flag.                   Default is `F` for full access.__________________________________________________________________________ 
    
     The User --  Hierarchy table is used to define a user hierarchy in the contract negotiator system. One entry is required for each user-parent relationship within the hierarchy. 
     
                                           TABLE__________________________________________________________________________User.sub.-- HierarchyColumn Name   Key Type   Size Description__________________________________________________________________________user.sub.-- id   Y   CHAR   10   User ID (usually Social Security                   Number)class1.sub.-- user.sub.-- id   Y   CHAR   10   Class1 User ID to which this                   user hierarchy is associatedeffective.sub.-- date       DATE        Effective date of hierarchyexpire.sub.-- date       DATE        Expiration date of hierarchy__________________________________________________________________________ 
    
     The User --  Login table includes User ID, password, and class information. 
     
                                           TABLE__________________________________________________________________________User.sub.-- LoginColumn Name   Key Type   Size Description__________________________________________________________________________user.sub.-- id   Y   CHAR   10   UserID (usually Social Security                   Number)password    VARCHAR              15   User&#39;s password. Defaulted to                   User ID.class       CHAR   1    Class of useractive.sub.-- flag       CHAR   1    Active/Deactivated flag. Default                   is `T` (true).__________________________________________________________________________ 
    
     The Branch table includes branch information for a given branch ID. 
     
                                           TABLE__________________________________________________________________________BranchColumn Name   Key Type   Size Description__________________________________________________________________________branch.sub.-- id   Y   INTEGER     Branch IDbranch.sub.-- name       VARCHAR              15   Branch description/name__________________________________________________________________________ 
    
     The Channel table includes channel information for a given channel ID, where &#34;channel&#34; denotes. 
     
                                           TABLE__________________________________________________________________________ChannelColumn Name   Key Type   Size Description__________________________________________________________________________channel.sub.-- id   Y   INTEGER     Channel IDchannel.sub.-- name       VARCHAR              15   Channel description/name__________________________________________________________________________ 
    
     The Region table includes region information for a given region ID, where &#34;region&#34; denotes a specific geographical or marketing region. 
     
                                           TABLE__________________________________________________________________________RegionColumn Name   Key Type   Size Description__________________________________________________________________________region.sub.-- id   Y   INTEGER     Region IDregion.sub.-- name       VARCHAR              15   Region description/name__________________________________________________________________________ 
    
     The Titles table includes titles for a given class. 
     
                       TABLE______________________________________TitlesColumn Name      Key     Type      Size   Description______________________________________title      Y       VARCHAR   30     titleclass              CHAR       1     class number______________________________________ 
    
     The contract tables are a Contract --  Status table, a Class --  Permission table, a Status --  Chg table, a Status table, a Contract --  Admin table, a Clarifi --  Comments table, a Component table, a Contract --  Customer table, a Contract --  Tree table, a Std --  Comp --  Tree table, a Support --  Team table, a Contract --  Type table, a Contract --  Sub --  Type table, a Hierarchy --  Rule table, and an Access --  Permission table. 
     The Contract --  Status table tracks each status change to the contract, along with the User ID of the person who made the change. Status changes coordinate the workflow progressions through the contract process. 
     
                                           TABLE__________________________________________________________________________Contract.sub.-- StatusColumn Name    Key       Type   Size Description__________________________________________________________________________contract.sub.-- number    Y  CHAR   6    Contract Numbercontract.sub.-- version    Y  CHAR   2    Contract Version (00-99)user.sub.-- id    Y  CHAR   10   User ID (usually Social                   Security Number)status.sub.-- cd    Y  CHAR   5    Contract Statuscontract.sub.-- type    Y  CHAR   4    Type of contract.contract.sub.-- sub.sub.-- type       CHAR   4    Sub type of contractmodify.sub.-- date       DATE        The date of the new contract                   statuspre.sub.-- status.sub.-- cd    Y  CHAR   5    Previous status of the                   contractqc.sub.-- flag       CHAR   1    Flag to indicate a quick close                   contractlast.sub.-- ct.sub.-- chged       DATETIME    Last changed date and time                   for a contract__________________________________________________________________________ 
    
     The Class --  Permission table regulates access to contracts based on contract status and user class. 
     
                                           TABLE__________________________________________________________________________Class.sub.-- PermissionColumn Name   Key Type   Size Description__________________________________________________________________________status.sub.-- cd   Y   CHAR   5    Contract statusclass       CHAR        Class of useraccess.sub.-- mode       CHAR   1    Allowed access mode (read,                   write, comment)contract.sub.-- creator       CHAR   1    Access modes for a contract                   creator__________________________________________________________________________ 
    
     The Status --  Chg table tracks the next allowable contract statuses depending on the current contract status. Valid status codes and status text are defined by the Status table. 
     
                                           TABLE__________________________________________________________________________Status.sub.-- ChgColumn Name   Key Type   Size Description__________________________________________________________________________status.sub.-- cd   Y   CHAR   5    Status codeuser.sub.-- class       CHAR   1    User classallowable.sub.-- status       VARCHAR              50   Codes of next allowable statuses__________________________________________________________________________ 
    
     The Status table is used to define the text for each status value in Contract --  Status. 
     
                                           TABLE__________________________________________________________________________StatusColumn Name   Key Type   Size Description__________________________________________________________________________status.sub.-- cd   Y   CHAR   5    Status IDstatus.sub.-- type       VARCHAR              5    Status Typedescription VARCHAR              25   Description of the status__________________________________________________________________________ 
    
     Access restrictions to the contract database are dependent on user class and contract status. The following table shows the default access rights each class of user has for each status available in a contract. Actual user access may be further limited on a user-by-user basis in the user&#39;s profile, which is managed by a Class 6 user. 
     
         ______________________________________Contract StatusesStatus       Class 1 Class 2 Class 3                              Class 4                                    Class 5______________________________________Incomplete   W       C       C     N     NSubmitted    C       C       C     C     NBD In Progress        C       C       C     W     CReturn for Rework        W       C       C     C     CApproved with Changes        C       C       C     C     CApproved     C       C       C     C     CCanceled     C       C       C     C     CRequest Executable        C       C       C     C     CLegal In Progress        C       C       C     C     WLegal Returned        C       C       C     C     CLegal Complete        C       C       C     C     CVoid         R       R       R     R     RExternal     C       W&#39;      C     W&#39;    CSigned-External        R       W&#39;      R     W&#39;    RExecutable   C       C       C     C&#39;    CIssued       C       C       C     C&#39;    C______________________________________ C  Comment Access C&#39; Comment Access, but the status can be changed by a Class 4 user to &#34;BD In Progress&#34;, in which the Class 4 user has Write/Update Access capabilities. N  No Access R  Read Only Access W  Write/Update Access W&#39; Write/Update Access  limited to the following functions: Class 2 and Class 4 users may update the status to SignedExternal after the contract is taken external and signed by the customer. Class 2 and Class 4 users may also update the pricing templates to &#34;true up&#34; the terms of the contract held in the system with the final signed external copy. 
    
     When first initiated by a Class 1 user, the contract has an &#34;Incomplete&#34; status. When the Class 1 user submits the contract into the system for approval by a Class 4 user, the status is changed to &#34;Submitted&#34; and the contract is distributed to all users, subject to class and status access restrictions (e.g., Class 5 users do not review the contract until a Class 4 user changes the contract status to a &#34;Legal In Progress&#34;). A Class 4 user (also called a Business Development (BD) Analyst) may change the status to &#34;BD In Progress&#34; and make modifications, clarifications, and comments to the contract. If a Class 4 user changes the contract status to &#34;Return for Rework&#34;, the contract is available for the Class 1 user to modify as necessary. 
     A Class 4 user may also change the status to either &#34;Approved&#34; or &#34;Approved with Changes.&#34; The status &#34;Approved&#34; indicates that the Class 4 user approved the contract without changing terms therein. (Examples of such terms include contract terms made available for modification in the &#34;Pricing&#34; template.) Alternately, the status &#34;Approved with Changes&#34; indicates that the Class 4 user modified terms within the contract. After either type of approval, the contract is routed to the Class 1 user for review. The Class 1 user may then request that an executable contract be generated by changing the status to &#34;Request Executable&#34;, which causes the contract to be routed back to the Class 4 user. In an exemplary embodiment of the present invention, the Class 4 user may change the status to &#34;Legal In Progress&#34; to submit the contract to the legal department. By changing the status to &#34;External&#34;, Class 5 user may &#34;take the contract external&#34; of the system, which involves printing a summary of contract terms. The external summary may be used by a Class 5 user to generate a hard-copy contract, which may be signed by the parties. When the external contract is signed, the status is changed to &#34;Signed-External.&#34; 
     In another exemplary embodiment of the present invention, when the Class 1 user requests an executable, the Class 4 user may change the status to &#34;Legal in Progress&#34;, which will route the document to a Class 5 user for possible modifications to the legal text. The Class 5 user does not, however, have write access authority to change contract pricing or duration terms. A Class 5 user may change the contract status to &#34;Legal Returned&#34; to require additional rework by the Class 1 or Class 4 user. Alternately, a Class 5 user may change the contract status to &#34;Legal Complete&#34;, which is effectively an approval by the legal department. If, after a &#34;Request Executable&#34; status, no legal text modifications are required, the Class 4 user may change the status to &#34;Executable.&#34; From this status, an executable copy may be printed by a Class 1 user for execution by the parties. Such printing results in an &#34;Issued&#34; status. 
     A new contract version is initiated if, after submission by a Class 1 user, any non-comment changes are made to the contract components and the contract is approved. When a new version is generated, the status of the previous version is automatically set to &#34;Void.&#34; A &#34;Canceled&#34; status terminates the progression of the contract through the contract flow, but leaves the contract in the contract database for archival purposes. A Class 2 or Class 4 user may also change the status to &#34;Void&#34; to indicate that the contract was made executable but was not signed by the customer. The &#34;Void&#34; contract remains in the contract database for archival purposes. 
     The Contract --  Admin table assigns a unique contract number to each new contract. There is only one row in this table, which is accessed with a lock to prevent other Class 6 users from accessing the table simultaneously. 
     
                                           TABLE__________________________________________________________________________Contract.sub.-- AdminColumn Name    Key       Type   Size Description__________________________________________________________________________next.sub.-- contract.sub.-- no       CHAR   6    Next Avail Contract Number__________________________________________________________________________ 
    
     The Clarifi --  Comments table defines clarifications and comments associated with a specific contract or a specific clause in any specific contract. 
     
                                           TABLE__________________________________________________________________________Clarifi.sub.-- CommentsColumn Name    Key       Type   Size Description__________________________________________________________________________contract.sub.-- number    Y  CHAR   6    Contract Numbercontract.sub.-- version    Y  CHAR   2    Contract Version (00-99)component.sub.-- id    Y  INTEGER     Component IDuser.sub.-- id       CHAR   10   User ID (usually SSN) who                   created the commentcomment.sub.-- datetime       DATETIME    The date and time that the                   comment was createdcomment.sub.-- type       VARCHAR              5    Type of commentcomment.sub.-- text       TEXT        Text of the comment__________________________________________________________________________ 
    
     The Component table stores the individual contract components. 
     
                       TABLE______________________________________ComponentColumn Name Key    Type      Size Description______________________________________component.sub.-- id       Y      INTEGER        Component IDcomponent.sub.-- desc              VARCHAR   32   Component                             descriptioncomponent.sub.-- type.sub.-- ver       Y      INTEGER        Version of                             componentcomponent.sub.-- type.sub.-- cd       Y      INTEGER        Type of component______________________________________ 
    
     The Contract --  Customer table records information pertaining to the customer involved in the contract. 
     
                       TABLE______________________________________Contract.sub.-- CustomerColumn Name Key    Type      Size Description______________________________________contract.sub.-- number       Y      CHAR      6    Contract Numbercontract.sub.-- version       Y      CHAR      2    Contract Version                             (00-99)company.sub.-- name              VARCHAR   40   Company Namenasp.sub.-- id     VARCHAR   8    NASP IDcontact.sub.-- name              VARCHAR   30   Contact Nameaddress1           VARCHAR   50   Address fieldaddress2           VARCHAR   50   Additional address                             fieldcity               VARCHAR   25   Cityregion             VARCHAR   15   State or regionpostal.sub.-- cd   VARCHAR   9    postal codecountry            VARCHAR   25   Countryphone              VARCHAR   20   Phone numberfax                VARCHAR   20   Fax number______________________________________ 
    
     The Contract --  Tree table stores contract components for specific contracts, which are configured as a tree of tables. 
     
                                           TABLE__________________________________________________________________________Contract.sub.-- TreeColumn Name      Key Type    Size                      Description__________________________________________________________________________contract.sub.-- number      Y   CHAR    6   Contract Numbercontract.sub.-- version      Y   CHAR    2   Contract Version                      (00-99)component.sub.-- id      Y   INTEGER     Component IDparent.sub.-- comp.sub.-- id          INTEGER     Parent item                      component IDhide.sub.-- component          CHAR    1   Flag indicating if                      component should                      be hidden. Default                      is for &#34;FALSE.&#34;position.sub.-- id          SMALLINT    Position of child                      under its                      parentcomplete.sub.-- flag          CHAR    1   Flag for completed                      componentoptional.sub.-- flag          CHAR    1   Flag for optional                      componentincluded.sub.-- flag          CHAR    1   Flag for included                      componentcomponent.sub.-- type.sub.-- ver          INTEGER     Component.sub.-- type.sub.-- versioncontract.sub.-- order          INTEGER     Order of component within                      a contract__________________________________________________________________________ 
    
     The Std --  Comp --  Tree table stores the base or default components that are used to build contract trees. When a new contract tree is created, the necessary rows are copied from Std --  Comp --  Tree to Contract --  Tree. 
     
                                           TABLE__________________________________________________________________________Std.sub.-- Comp.sub.-- TreeColumn Name      Key Type    Size                      Description__________________________________________________________________________component.sub.-- id      Y   INTEGER     Component IDcontract.sub.-- type          CHAR    4   Contract Typecontract.sub.-- sub.sub.-- type          CHAR    4   Contract Sub Typecontract.sub.-- order          INTEGER     Component order of a                      contractparent.sub.-- comp.sub.-- id          INTEGER     Parent item&#39;s component IDhide.sub.-- component          CHAR    1   Flag that indicates if                      component should be                      hidden. Default is `F`.position.sub.-- id          INTEGER     Position of child under its                      parentcomplete.sub.-- flag          CHAR    1   Flag for completed                      componentoptional.sub.-- flag          CHAR        Flag for optional                      componentincluded.sub.-- flag          CHAR    1   Flag for included                      componentcomponent.sub.-- type.sub.-- ver          INTEGER     Component.sub.-- type.sub.-- version__________________________________________________________________________ 
    
     The Support --  Team table defines the various team members for a specific contract. One entry per team member is required for each contract. 
     
                       TABLE______________________________________Support.sub.-- TeamColumn Name Key    Type      Size Description______________________________________contract.sub.-- number       Y      CHAR      6    Contract Numbercontract.sub.-- version       Y      CHAR      2    Contract Version                             (00-99)user.sub.-- id       Y      CHAR      10   User ID                             (usually Social                             Security                             Number)hide.sub.-- contract              CHAR      1    Flag that                             indicates if contract                             should be hidden                             from user&#39;s                             menu. Default                             is `F`.is.sub.-- hier.sub.-- user              CHAR      1    `T` if user is                             part of hierarchy______________________________________ 
    
     The Contract --  Type table defines the various types of contracts available within the contract negotiator system. 
     
                       TABLE______________________________________Contract.sub.-- TypeColumn Name Key    Type      Size Description______________________________________contract.sub.-- type              CHAR       4   Contract Typedescription        VARCHAR   50   Description of a                             contract type______________________________________ 
    
     The Contract --  Sub --  Type table defines the various subtypes for a Contract --  Type table. 
     
                       TABLE______________________________________Contract.sub.-- Sub.sub.-- TypeColumn Name Key    Type      Size Description______________________________________ct.sub.-- parent.sub.-- type              CHAR      4    Parent contract type                             of a sub typecontract.sub.-- sub.sub.-- type              CHAR      4    Contract Sub Typedescription        VARCHAR   50   Description of a                             contract sub                             type______________________________________ 
    
     The Access --  Permission table defines various access permissions for each user. 
     
                       TABLE______________________________________Access.sub.-- PermissionColumn Name Key    Type      Size Description______________________________________access.sub.-- cd       Y      INTEGER        Access codeaccess.sub.-- desc VARCHAR   75   Access description______________________________________ 
    
     The Hierarchy --  Rule table defines the minimum and maximum number of people who may be hierarchy members for a particular contract at a particular class level. 
     
                       TABLE______________________________________Hierarchy.sub.-- RuleColumn Name Key    Type      Size Description______________________________________class              CHAR      1    Class numberreq.sub.-- users   INTEGER        Minimum number                             of class usermax.sub.-- users   INTEGER        Maximum number                             of class user______________________________________ 
    
     The support tables are a Countries table, a States table, a Component --  Types table, a QC --  Contract --  Points table, a QC --  Annual --  Commit table, a QC --  Local --  Price --  Val table, an Err --  Messages table, a Transaction --  Log table, and a Transaction table. 
     The Countries table is used to map countries and their countries codes. 
     
                       TABLE______________________________________CountriesColumn Name Key    Type      Size Description______________________________________country.sub.-- cd       Y      INTEGER        Country codecountry            VARCHAR   25   Country namecomponent.sub.-- type.sub.-- cd              INTEGER        Component type                             code, that                             are using                             this country table______________________________________ 
    
     The States table maps state abbreviations to state names. 
     
                       TABLE______________________________________StatesColumn Name Key    Type      Size Description______________________________________state.sub.-- cd       Y      CHAR       2   State codestate.sub.-- name  VARCHAR   15   State name______________________________________ 
    
     The Component --  Type table describes each component type, and serves as a class engine for an application client. 
     
                       TABLE______________________________________Component.sub.-- TypeColumn Name Key    Type      Size Description______________________________________component.sub.-- type.sub.-- cd       Y      INTEGER        Unique component                             type codecomponent.sub.-- type              CHAR      6    Short name for each                             componenttype.sub.-- desc   VARCHAR   25   Full description                             of each componentclass.sub.-- name  VARCHAR   35   Java class name                             for each componentquick.sub.-- close CHAR      1    Flag to indicate                             quick close                             component. Default                             is `F`______________________________________ 
    
     The QC --  Contract --  Points table stores contract points for a contract that has a Quick Close component. 
     
                       TABLE______________________________________QC.sub.-- Contract.sub.-- PointsColumn Name Key    Type      Size Description______________________________________contract.sub.-- number       Y      CHAR      6    Contract numbercontract.sub.-- version       Y      CHAR      2    Contract versionpts.sub.-- avail   INTEGER        Available points                             for a contractpts.sub.-- used    INTEGER        Used points for                             a contractannual.sub.-- commit              VARCHAR   8    Annual commit                             values for                             a contractyear               INTEGER        Term period of a                             commitment______________________________________ 
    
     The QC Annual --  Commit table stores point matrices for the various Quick Close type contracts. 
     
                       TABLE______________________________________QC.sub.-- Annual.sub.-- CommitColumn Name Key    Type      Size Description______________________________________component.sub.-- type.sub.-- cd       Y      INTEGER        Component Type                             Codeannual.sub.-- commitment              VARCHAR   8    Annual commitment                             valuesyear               INTEGER        Term period of a                             commitmentpoints             INTEGER        Points for a                             component______________________________________ 
    
     The QC Local --  Price --  Val table stores point matrices corresponding to the Quick Close local price template. 
     
                       TABLE______________________________________QC.sub.-- Local.sub.-- Price.sub.-- ValColumn Name Key    Type      Size Description______________________________________discount           INTEGER        Discount valueterm               INTEGER        Term period of                             commitmentstd.sub.-- sdyr    CHAR      1    standard discount                             or notpoints             INTEGER        Points for a                             component______________________________________ 
    
     The Error --  Messages table stores applications specific error messages. 
     
                       TABLE______________________________________Error.sub.-- MessagesColumn Name    Key    Type      Size Description______________________________________error.sub.-- cd    Y      INTEGER        Error numbererror.sub.-- desc           VARCHAR   50   Description of error codeerror.sub.-- usage           VARCHAR   35   Origin of an error message______________________________________ 
    
     The Transaction --  Log table tracks each transaction acted on in the contract, along with the User ID of the acting user, allowing a form of version tracking. 
     
                                           TABLE__________________________________________________________________________Transaction.sub.-- LogColumn Name     Key Type   Size                    Description__________________________________________________________________________contract.sub.-- number     Y   CHAR   6   Contract Numbercontract.sub.-- version     Y   CHAR   2   Contract Version (00-99)tranx.sub.-- datetime     Y   DATETIME   The date and time that the                    transaction occurreduser.sub.-- id     Y   CHAR   10  User ID (usually SSN) who                    performed the transactioncurrent.sub.-- status.sub.-- cd         INTEGER    Contract Status Codepre.sub.-- status.sub.-- cd         INTEGER    Previous Status Codetransaction.sub.-- cd         INTEGER    Transaction Codecomments      VARCHAR                200 Any comments on each                    transaction__________________________________________________________________________ 
    
     The Transaction table defines transaction log code and their associated description. 
     
                       TABLE______________________________________TransactionColumn Name     Key     Type      Size  Description______________________________________transaction.sub.-- cd     Y       INTEGER         Transaction codetranx.sub.-- description             VARCHAR   50    Description of the                             transaction type______________________________________ 
    
     The generic template tables are Respond --  Free --  Text, and Generic --  Templates. The Respond --  Free --  Text table includes user responses to Q&amp;A or the &#34;BLOB&#34; templates for specific contracts. BLOB stands for &#34;Binary Loaded OBject. 
     
                                           TABLE__________________________________________________________________________Respond.sub.-- Free.sub.-- TextColumn Name     Key        Type   Size                  Description__________________________________________________________________________contract.sub.-- number     Y  CHAR   6  Contract Numbercontract.sub.-- version     Y  CHAR   2  Version Number (00-99)component.sub.-- id     Y  INTEGER   Component IDtemplate.sub.-- type.sub.-- cd        INTEGER   Component Type Codeuser.sub.-- id     Y  CHAR   10 User ID (usually SSN)change.sub.-- datetime        DATETIME  Date and time of blob updaterespond.sub.-- free.sub.-- text        BLOB      Blob__________________________________________________________________________ 
    
     The Generic --  Template table includes Q&amp;A and &#34;BLOB&#34; templates and clauses for each component. Each instance of the Generic --  Template table is associated with a default Q&amp;A or default &#34;BLOB&#34; item. 
     
                                           TABLE__________________________________________________________________________Generic.sub.-- TemplateColumn Name      Key         Type  Size                  Description__________________________________________________________________________component.sub.-- id      Y  INTEGER  Component IDdefault.sub.-- free.sub.-- text         BLOB     Question to ask user or blob                  template to be completed by                  the usercomponent.sub.-- type.sub.-- cd         INTEGER  Component Type Codecomponent.sub.-- type.sub.-- ver         INTEGER  Component Type Version__________________________________________________________________________ 
    
     The Quick Close tables are QC --  Term --  Conditions, QC --  Credit, QC --  Paging, QC --  Cellular, QC --  Local --  Price, QC --  Hype --  Term, QC --  Vmt, QC --  Audio --  Conf, QC --  Access, QC --  Dedic --  Leased, and QC --  Op --  Provision. 
     The QC --  Term --  Conditions table stores information for Terms and Conditions Quick Close options. 
     
                                           TABLE__________________________________________________________________________QC.sub.-- Term.sub.-- ConditionsColumn Name     Key        Type  Size                 Description__________________________________________________________________________contract.sub.-- number     Y  CHAR  6  Contract Number (000001-                 000099)contract.sub.-- version     Y  CHAR  2  Version Number (00-99)component.sub.-- id        INTEGER  Component IDdivestiture  CHAR  1  Business divestiture flagdownturn     CHAR  1  Business downturn flagq.sub.-- a   CHAR  1  Quality Assurance flagtech.sub.-- change        CHAR  1  Technology change flagchronic.sub.-- service        CHAR     Chronic Service Level                 Agreement flagstd.sub.-- util        CHAR  1  Reduction in standard                 utilization flagearly.sub.-- term.sub.-- penalty        CHAR  1  Reduction in early term                 penalties flagramp.sub.-- month3        CHAR  1  Ramp period of 3 months flagramp.sub.-- month6        CHAR  1  Ramp period of 6 months flagramp.sub.-- month12        CHAR  1  Ramp period of 12 months flagemp.sub.-- benefit        CHAR  1  Employee benefit program flagcomp.sub.-- pts        INTEGER  Quick Close points for each                 component__________________________________________________________________________ 
    
     The QC --  Credit table stores information for the Credits and Additional -Discount Quick Close Option. 
     
                                           TABLE__________________________________________________________________________QC.sub.-- CreditColumn Name     Key        Type  Size                 Description__________________________________________________________________________contract.sub.-- number     Y  CHAR  6  Contract Numbercontract.sub.-- version     Y  CHAR  2  Version Number (00-99)component.sub.-- id        INTEGER  Component IDinst.sub.-- waiver        INTEGER  Installation waivercost.sub.-- conversion        INTEGER  Cost of conversion bonuscost.sub.-- conv.sub.-- opt        INTEGER  Invoice Credit/Deposit to Fund                 selectioncomp.sub.-- pts        INTEGER  Quick Close points for each                 component__________________________________________________________________________ 
    
     The QC --  Paging table stores information for the NetworkMCI Paging Service Quick Close Option. 
     
                       TABLE______________________________________QC.sub.-- PagingColumn Name     Key    Type     Size Description______________________________________contract.sub.-- number     Y      CHAR     6    Contract Numbercontract.sub.-- version     Y      CHAR     2    Version Number (00-99)component.sub.-- id            INTEGER       Component IDpage.sub.-- disc INTEGER       Discount on paging usagecomp.sub.-- pts  INTEGER       Quick Close points for each                          component______________________________________ 
    
     The QC --  Cellular table stores information for the NetworkMCI Cellular Service Quick Close Option. 
     
                       TABLE______________________________________QC.sub.-- CellularColumn Name     Key    Type     Size Description______________________________________contract.sub.-- number     Y      CHAR     6    Contract Numbercontract.sub.-- version     Y      CHAR     2    Version Number (00-99)component.sub.-- id            INTEGER       Component IDcellular.sub.-- disc            INTEGER       Discount on cellular usagecomp.sub.-- pts  INTEGER       Quick Close points for each                          component______________________________________ 
    
     The QC --  Local --  Price table stores information about the Local Pricing Quick Close Option. 
     
                       TABLE______________________________________QC.sub.-- Local.sub.-- PriceColumn Name     Key    Type     Size Description______________________________________contract.sub.-- number     Y      CHAR     6    Contract Numbercontract.sub.-- version     Y      CHAR     2    Version Number (00-99)component.sub.-- id            INTEGER       Component IDdisc.sub.-- percent1            INTEGER       Local price discountterm1            INTEGER       Termstd.sub.-- dsyr1 CHAR     1    Standard discount or notdisc.sub.-- points1            INTEGER       Discount pointscomp.sub.-- pts  INTEGER       Quick Close points for each                          component______________________________________ 
    
     The QC --  Hype --  Term table stores information for the Domestic Hyperstream Quick Close Option and Frame Relay Quick Close Option. 
     
                       TABLE______________________________________QC.sub.-- Hype.sub.-- TermColumn Name     Key    Type     Size Description______________________________________contract.sub.-- number     Y      CHAR     6    Contract Numbercontract.sub.-- version     Y      CHAR     2    Version Number (00-99)component.sub.-- id            INTEGER       Component IDadditional.sub.-- HPP            CHAR     1    Additional discount about                          standard HPPcomp.sub.-- pts  INTEGER       Quick Close points for each                          component______________________________________ 
    
     The QC --  Vmt table holds the information for VNET, MCI Toll Free Platform and NetworkMCI One Platform templates. 
     
                                           TABLE__________________________________________________________________________QC.sub.-- VmtColumn Name     Key        Type  Size                 Description__________________________________________________________________________contract.sub.-- number     Y  CHAR  6  Contract Numbercontract.sub.-- version     Y  CHAR  2  Version Number (00-99)component.sub.-- id        INTEGER  Component IDinterstate   INTEGER  Discount on interstate voice                 trafficintrastate   INTEGER  Discount on intrastate voice                 trafficinternational        INTEGER  Discount on international voice                 trafficrace.sub.-- succ        INTEGER  Race to success promotion                 discountinternational.sub.-- outb        VARCHAR              20 Postalize International                 Outbound Ratesrate.sub.-- protection        INTEGER  Rate Protectioncomp.sub.-- pts        INTEGER  Quick Close points for each                 component__________________________________________________________________________ 
    
     The QC --  Audio --  Conf table stores information for the Audio Conferencing Quick Close Option. 
     
                       TABLE______________________________________QC.sub.-- Audio.sub.-- ConfColumn Name      Key    Type     Size Description______________________________________contract.sub.-- number      Y      CHAR     6    Contract Numbercontract.sub.-- version      Y      CHAR     2    Version Number (00-99)component.sub.-- id             INTEGER       Component IDaudio.sub.-- conf.sub.-- disc             INTEGER       Discount on audio                           conferencingcomp.sub.-- pts   INTEGER       Quick Close points for                           each component______________________________________ 
    
     The QC --  Access table stores information for the Access Quick Close Option. 
     
                       TABLE______________________________________QC.sub.-- AccessColumn Name      Key    Type     Size Description______________________________________contract.sub.-- number      Y      CHAR     6    Contract Numbercontract.sub.-- version      Y      CHAR     2    Version Number (00-99)component.sub.-- id             INTEGER       Component IDaccess.sub.-- disc             INTEGER       Access discountframe.sub.-- relay.sub.-- waive             CHAR     1    Waive A/C for frame                           relaycomp.sub.-- pts   INTEGER       Quick Close points for                           each component______________________________________ 
    
     The QC --  Dedic --  Leased table stores information for the Dedicated Leased Line Quick Close Option. 
     
                       TABLE______________________________________QC.sub.-- Dedic.sub.-- LeasedColumn Name     Key    Type      Size Description______________________________________contract.sub.-- number     Y      CHAR      6    Contract Numbercontract.sub.-- version     Y      CHAR      2    Version Number (00-99)component.sub.-- id            INTEGER        Component IDNPP.sub.-- level INTEGER        NPP levelsNPP.sub.-- flag  CHAR      1    NPP flagnpp.sub.-- disc  INTEGER        Discount valueterm             INTEGER        Term period of                           commitmentcommitment       VARCHAR   8    Commitmentcomp.sub.-- pts  INTEGER        Quick Close points for                           each component______________________________________ 
    
     The custom --  screen --  tables are CS --  Index, CS --  Data --  Table --  ID, CS --  Char, CS --  Integer, CS --  Float, CS --  Varchar, and CS --  Blob. 
     The CS --  Index table stores information for all tabs and screens associated with a contract component. 
     
                       TABLE______________________________________CS.sub.-- IndexColumn Name Key    Type     Size Description______________________________________component.sub.-- id       Y      INTEGER       Component IDcomponent.sub.-- type.sub.-- ver       Y      INTEGER       Component Type                            Versiontab.sub.-- id      INTEGER       Tab IDtab.sub.-- order   INTEGER       Order of a tabscreen.sub.-- id   INTEGER       Screen ID______________________________________ 
    
     The CS --  Data --  Table --  ID table is a custom screen support table that stores information about custom screen data table descriptions associated with a specific data table ID. 
     
                       TABLE______________________________________CS.sub.-- Data.sub.-- Table.sub.-- IDColumn Name    Key     Type       Size  Description______________________________________data.sub.-- table.sub.-- id    Y       INTEGER          Data Table IDtable.sub.-- desc            VARCHAR    25    Table Description______________________________________ 
    
     CS --  Char table stores user response data for the character data type field. 
     
                       TABLE______________________________________CS.sub.-- CharColumn Name Key    Type     Size Description______________________________________contract.sub.-- number       Y      CHAR     6    Contract numbercontract.sub.-- version       Y      CHAR     2    Contract versioncomponent.sub.-- id       Y      INTEGER       Component IDcomponent.sub.-- type.sub.-- ver       Y      INTEGER       Component Type                            Versionfield.sub.-- id       Y      INTEGER       Field IDchar.sub.-- datafield              CHAR     75   Character data type                            data______________________________________ 
    
     The CS --  Integer table stores user response data for the integer data type field. 
     
                       TABLE______________________________________CS.sub.-- IntegerColumn Name Key    Type     Size Description______________________________________contract.sub.-- number       Y      CHAR     6    Contract numbercontract.sub.-- version       Y      CHAR     2    Contract versioncomponent.sub.-- id       Y      INTEGER       Component IDcomponent.sub.-- type.sub.-- ver       Y      INTEGER       Component Type                            Versionfield.sub.-- id       Y      INTEGER       Field IDint.sub.-- datafield              INTEGER       Integer data type                            data______________________________________ 
    
     The CS --  Float table stores user response data for the float data type field (i.e., floating point). 
     
                       TABLE______________________________________CS.sub.-- FloatColumn Name Key    Type     Size Description______________________________________contract.sub.-- number       Y      CHAR     6    Contract numbercontract.sub.-- version       Y      CHAR     2    Contract versioncomponent.sub.-- id       Y      INTEGER       Component IDcomponent.sub.-- type.sub.-- ver       Y      INTEGER       Component Type                            Versionfield.sub.-- id       Y      INTEGER       Field IDfloat.sub.-- datafield              FLOAT         Float data type                            data______________________________________ 
    
     The CS --  Varchar table stores user response data for the varchar data type field, a variable length character data type. 
     
                       TABLE______________________________________CS.sub.-- VarcharColumn Name Key    Type      Size Description______________________________________contract.sub.-- number       Y      CHAR      6    Contract numbercontract.sub.-- version       Y      CHAR      2    Contract versioncomponent.sub.-- id       Y      INTEGER        Component IDcomponent.sub.-- type.sub.-- ver       Y      INTEGER        Component Type                             Versionfield.sub.-- id       Y      INTEGER        Field IDvc.sub.-- datafield              VARCHAR   100  Varchar data type                             data______________________________________ 
    
     The CS --  Blob table stores user response data for the text data type field. 
     
                       TABLE______________________________________CS.sub.-- BlobColumn Name Key    Type     Size Description______________________________________contract.sub.-- number       Y      CHAR     6    Contract numbercontract.sub.-- version       Y      CHAR     2    Contract versioncomponent.sub.-- id       Y      INTEGER       Component IDcomponent.sub.-- type.sub.-- ver       Y      INTEGER       Component Type                            Versionfield.sub.-- id       Y      INTEGER       Field IDblob.sub.-- datafield              TEXT          Blob data type data______________________________________ 
    
     The Custom --  Screen tables are useful for new contract generation and new Custom --  Screen development. These generic templates, associated with a data type, are used to store user response data from custom screens. For example, a new Custom --  Screen may be developed for defining discounts based on a list of numbered regions. The screen developer may use a CS --  Integer table to store the numbered region value and a CS --  Float table to store the discount percentage input by the user. The generic table is selected by the developer according to data type and includes fields for corresponding to the individual data type instance with the appropriate contract and contract component. As such, these custom screen tables provide a set of generic data type tables to standardize and expedite custom screen development. 
     FIG. 6 depicts a contract negotiator user screen for an exemplary contract in accordance with the present invention. The particular screen illustrated is a Question and Answer generic template (Q&amp;A). Left window 600 comprises text identifying the associated contract, as identified by the contract number 616 (i.e., &#34;0001122-01&#34;). Most user screens within a contract negotiator system support a button bar and/or a menu to provide a user with functionality within the system. The button bar 620 and menu 622 of a preferred embodiment in accordance with the present invention is context sensitive. Left window 600 also comprises a tree view of the contract (shown generally at 602). Contract tree 602 initially shows only the base levels of the contract tree; however, the tree view may be expanded to display the detailed components of the contract. When a detailed component is selected in the left window, the right side of the contract negotiator screen will present a work area 606 having a notebook for data entry. 
     Colors and other visual markings are used to indicate the various characteristics of contract components. Such characteristics include whether a component is included in the contract, whether the component is complete/incomplete, and whether a component is in error. Contract components in a tree are colored in green and preceded by a check mark if they are included in the contract and have no system-verifiable problems outstanding. Red is used, with a preceding &#34;X&#34;, to show those contract components that are incomplete or in error. Contract components that are not included in the contract are black. The contract number, contract version number, customer name, and status are displayed in the title bar 604 at all times. In FIG. 6, the contract version number is indicated by the suffix following the dash (i.e., &#34;01&#34;). 
     A system in accordance with the present invention supports a Q&amp;A generic template as a notebook presented in the work area (shown generally at 506). Three tabs are positioned at the top of the notebook: &#34;Pricing,&#34; &#34;Clarification,&#34; and &#34;Clause.&#34; Pricing tab 610 corresponds to a notebook comprising top list box 608 and bottom edit box 612. Top list box 608 includes questions populated with the contents of RTF (Rich Text Format) text that prompt the user to enter contract-specific information. The text entered in top list box 608 is originally input by a Class 6 user preparing the contract tree, and all other class users have read-only access to the top list box. Bottom edit box 612 is editable and allows a user to respond to the questions in top list box 608 by inserting text into bottom edit box 612. &#34;Include&#34; check box 614 allows a user to indicate whether an optional contract component is to be included in the contract. When &#34;include&#34; check box 614 is checked, the associated contract component or clause is included in the contract. If the information displayed in either top list box 608 or bottom edit box 612 exceeds the visible work area, scroll bars 618 and 620 are available to allow a user to scroll beyond the initially displayed area. 
     FIG. 7 illustrates the Clarification tab 701 of a Q&amp;A work area. All classes of users have access to view the contents of Clarification tab 701, but only Class 4 users are able to modify information contained therein. If the information entered exceeds the visible work area, scroll bar 702 is available to allow a user to scroll beyond the initially displayed area. Text entered by a Class 4 user in a clarification edit box 704 is viewable by other users within the contract negotiator system and are printed out with a contract summary with an embodiment of the invention illustrated in FIGS. 4C and 4D. 
     FIG. 8 illustrates the Clause tab 801 of a Q&amp;A work area. The Clause tab includes standard legal text for the contract component in text box 804. The text is read-only and cannot be modified by Class 1-5 users. A Class 6 user enters the standard legal text by editing the contract baselines, discussed later. 
     FIG. 9 illustrates a BLOB generic template in a notebook presented in the work area (shown generally at 900). Three tabs are presented at the top of the notebook: Pricing, Clarification, and Clause. With regard to the BLOB generic template, Pricing tab 902 has an edit area 912 that will be initially populated with the contents of an RTF text that prompts the user to enter contract-specific information. The authorized user may edit the RTF text with appropriate responses or partially or completely modify the text therein. Clarification tab 904 and Clause tab 906 are equivalent to the corresponding tabs in the Q&amp;A generic template. &#34;Include&#34; check box 908 is also equivalent to the include check box in Q&amp;A in the generic template. If the information displayed in edit area 912 exceeds the visible work area, a scroll bar 910 is available to allow a user to scroll beyond the initially displayed area. 
     In FIG. 10, a &#34;No Pricing&#34; template is illustrated. This template corresponds to contract elements that lack pricing components. Class 4 users may enter clarifications, and all users may view the clarifications 1000 and clause 1002 text, as described for the Q&amp;A template and the BLOB template. In an embodiment of the present invention, the clarifications may be output from the system in a contract summary. The &#34;include&#34; check box 1004 operates as previously described. 
     FIG. 11 depicts a Team Screen used to search, add, and remove users from the list of team members responsible for a contract. The work area shown includes five tabs at 1101 corresponding to the first five class levels in the contract hierarchy. When a Class 1 user initiates a contract, the permanent hierarchy assigned to the Class 1 user is automatically assigned to the contract. Members of this hierarchy may not be removed, except by a Class 6 (administration) user. Other members of the team, however, may be added and removed as desired by team members at any class level (i.e., these other users are non-permanent). After the Class 1 user submits the contract, it is electronically distributed to all team members and presented to each team member when they log on to the system. 
     Upper box 1102 lists users assigned to the contract team. Lower box 1104 depicts additional users corresponding to the displayed class available to be added to the contract team if desired. If the list of names displayed in either upper box 1102 or lower box 1104 exceeds the visible work area, vertical scroll bars (not shown) are available to allow a user to scroll beyond the initially displayed area. Furthermore, if the list elements extend horizontally to exceed the visible work area, horizontal scroll bar 1114 is available to allow a user to scroll horizontally beyond the initially displayed area. To add a new team member, a user selects the name of a person to be added from list 1105 and selects the &#34;Add&#34; button 1108. The selected user&#39;s name is then added to team list 1103, and the contract will be distributed to that person as appropriate. To search for an available team member in list 1105, a user enters the partial or complete name of a person to be searched in the &#34;Name box 112&#34; and presses the search button 1106. If the name of the person searched is found, the list 11 05 is scrolled to display the located name within the visible work area. To remove a non-permanent member of the contract team, a user selects the member&#39;s entry in the team list 1103 and selects remove button 1110. The team member name is then deleted from list 1103, and the contract will no longer be routed to that user. Members of a Class 1 user&#39;s permanent hierarchy cannot be removed from the contract team in this manner. 
     FIG. 12 shows a comment view screen that displays all the comments made regarding the contract, listed by date/time in ascending order. The name of the user who entered the comment (1202), the date and time of the comment entry (1204), and the section of the contract (1206) in which the user was working when the comment was entered are displayed with the comment text in work area 1200. As shown generally at 1208, the contract tree includes a contract component labeled &#34;General Comments&#34;, which a user may select to display the comment work area. 
     The term &#34;Quick Close&#34; refers to a special type of contract that enables an expedited approval process by negotiating terms that meet certain defined business parameters. Some components of a contract that represent the services offered are designed to have Quick Close options. When these contract components are selected and completed within the defined business parameters, an expedited time frame for approval is guaranteed within the business organization. This guarantee is in accordance with the business organization&#39;s policies, and a system in accordance with the present invention enables automation of such policies. When a contract component associated with a Quick Close option is selected by a user, one of several possible Quick Close screens is displayed. By selecting from those services with Quick Close options and allocating no more than a maximum number of points available, based on the contract term and the minimum annual commitment of a customer, there is a commitment by the business organization to expedite processing the contract to approval. 
     The Quick Close point maximum (i.e., total available points) is controlled by the terms and conditions screen illustrated in FIG. 13. A user selects an annual minimum commitment (i.e., the minimum number of dollars that a customer commits to spend annually) from list box 1300. Each combination of commitment value and contract duration (i.e., contract term in box 1302) is allocated a certain number of points. In a preferred embodiment, the available points are determined from a 2-dimensional data grid provided by a business department within the organization, with commitment values and contract duration being the two dimensions. The resulting value represents the total points available for allocation among Quick Close components and is displayed generally at 1304. The total available points value 1304 is stored in the central repository (i.e., the contract database) and allocated as the user selects and manipulates various contract component options associated with the current contract. 
     FIG. 14 shows a screen for an exemplary Quick Close contract component. In work area 1400, a user may enter discount percentage values in the boxes shown at 1402. Each discount corresponds to a point allocation shown in column 1404. For example, the greater the interstate voice traffic discount, the greater the points allocated to that discount. Likewise, the relationship between a Quick Close option value and the allocated points may also be inverse. For example, the higher the rate cap on interstate voice, the lower the point value allocated to that option. The system automatically sums the number of points allocated in the displayed section, shown at 1406. The total number of points allocated throughout the contract are displayed at 1408. The total points remaining available for allocation, based on the total points available value (shown generally at 1304 in FIG. 13), are shown at 1410. 
     FIG. 15 illustrates two columns of check boxes shown generally at 1500. In this exemplary display, a user may allocate available points among the countries shown, up to a maximum of 10 countries. Specifically, FIG. 15 shows six countries selected as indicated by value 1502. The selection of six countries requires an allocation of 30 points (shown at 1504), in this example, which are applied against the total available points of FIG. 13. In addition, Class 4 users may enter clarifications, and all users may view the clarifications and clause text using tabs 1506 and 1508, as described for the Q&amp;A template, the BLOB template and the No Pricing template. 
     As shown in FIG. 16, Class 1 users with a defined hierarchy are able to create new contracts. No other class users have this capability. When a new contract is requested, before a contract tree structure is displayed, a pop-up box (1600) is displayed to the user. Pop-up box 1600 prompts the Class 1 user to input the name of the customer in box 1602, the contract type in box 1604, and a subtype in box 1606. Contract types are defined by a Class 6 user and are constructed corresponding to the business requirements. Contract subtypes describe a hierarchical relationship among various contract types. The Class 1 user may indicate whether the new contract is an amendment to an old contract using radio buttons at 1608. An amendment has data storage dedicated to describing the history of the contract. For example, such information may identify the original contract or contracts from which the amendment derives. The Class 1 user may abort the initiation of a new contract by selecting &#34;Cancel&#34; button 1610. Otherwise, the Class 1 user may complete the initiation of a new contract by selecting &#34;OK&#34; button 1612. The Class 1 user may then begin entering terms and comments into the contract tree of the new contract. The new contract is not distributed to other team members corresponding to this new contract until the Class 1 user submits the contract for approval to a Class 4 user. 
     Class 6 users administer the contract negotiator system. Administration includes activities such as adding, editing, and removing new users from the system. Class 6 users also assign permanent hierarchies to Class 1 users and maintain clauses in contract baselines (i.e., default contract trees). 
     FIG. 17 shows a screen used by a Class 6 user to add and update users to a contract negotiator system. In list box 1700, the names of valid users within the system are displayed. If the list of names displayed in list box 1700 exceeds the visible work area, a vertical scroll bar is available to allow a user to scroll beyond the initially displayed area. Likewise, a horizontal scroll bar 1702 allows a user to scroll horizontally to view the entire length of a name entry. A Class 6 user may search for a name in list box 1700 using search box 1704 and search button 1706. To search for an existing user, a Class 6 user enters a partial or complete name of the desired user in the search box 1704. If the entered name is found after the Class 6 user presses the search button 1706, the name will be displayed within the boundaries of the displayed area in list box 1700. The Class 6 user can select the user name by double clicking on the name in the list box 1700. When selected, the details corresponding to the selected name appear in work area 1708. User box 1710 displays the User ID from the User table discussed previously. Likewise, the name, title and VNet number are also illustrated generally at 1712. A VNet number is an identifier that allows employees at remote locations to use MCI Telecommunication Corporation&#39;s VNet system to access advanced telecommunication capabilities. Other relevant information concerning the user is also identified generally at 1712. At 1714, two types of access rights are selectable. If &#34;Team&#34; is selected, the user only has access to those contracts for which he or she is a team member. If &#34;National&#34; is selected, the user has access to all contracts within the contract database. At 1716, restrictions on the write access rights granted to the user are selectable. If &#34;Comment Only&#34; is selected, the user may only make comments in a contract to which he or she has access. If &#34;Full&#34; is selected, the user has full read and write rights to those contracts in which he or she has access. These access rights may also be restricted by the current status of the contract. For example, if the current status of the contract is &#34;Legal in Progress&#34;, a Class 1 user is restricted from modifying the contract. 
     A Class 6 user may add a user to the system by entering the appropriate data in the fields in work area 1708 and selecting the &#34;Add User&#34; button 1718. The user class and subclass are determined by the position title selected from the &#34;Title&#34; drop down list 1720. A subclass refers to a &#34;point&#34; class, such as &#34;Class 2.1.&#34; When a user is added, a default password that equals their User ID is automatically assigned. When a password is reset using &#34;Reset Pwd&#34; button 1722, the user&#39;s password is reset to his or her User ID. 
     To edit the user information for an existing user, a Class 6 user selects the name of the user in list box 1700 and edits the information displayed in work area 1708. In this mode, &#34;Add User&#34; button 1718 is renamed &#34;Update User.&#34; When the Class 6 user completes changes to the selected user&#39;s information, selecting the &#34;Update User&#34; button 1718 posts the changes to the contract database. During the edit process, the user is not removed from the system. The updates merely replaces the existing entry when the &#34;Update User&#34; button 1718 is selected. 
     To deactivate a user from the system, the Class 6 user selects the user from list box 1700. The user information is displayed in the work area 1708. If the Class 6 user selects the &#34;Deactivate&#34; button 1724, the user is flagged as &#34;deactive&#34; in the database. The user&#39;s record remains in the database for reference purposes, but that user is thereafter denied access (i.e., prevented from logging on) to the system. Furthermore, deactivated user records are not shown in lists for adding users to teams or hierarchies. Deactivated user records are displayed in the User Add/Update Screen with an indicator to allow a deactivated user to be reactivated. Users that are already included in permanent hierarchies may not be deactivated until they are removed from those hierarchies. 
     To reactivate a user, the Class 6 user edits the deactivated record. When the deactivated record is brought into edit mode, the &#34;Deactivate&#34; button 1724 is renamed &#34;Reactivate.&#34; By selecting the &#34;Reactivate&#34; button, the user record is reactivated with the password set to the default (i.e., the User ID). Thereafter, the user may be added to teams and permanent hierarchies again. 
     FIG. 18 shows a screen that allows a Class 6 user to search all of the Class 1 users and to create or edit Class 1 permanent hierarchies. The Class 6 user enters the full or partial name of a Class 1 user in name field 1800. The system searches user names displayed in list box 1802 when the Class 6 user presses &#34;Search&#34; button 1804. If the user name entered in box 1800 is found, the name is displayed within the viewable area of list box 1802. The Class 6 user selects names from this list by clicking on the name in list box 1802. To add the selected name to a permanent hierarchy, a Class 6 user selects &#34;Add&#34; button 1806, which adds the name to the displayed list box at 1810. The names displayed in list box 1810 correspond to the selected tab of the five class tabs shown generally at 1812. Double clicking on a name in list box 1808 will also add it to the permanent hierarchy. To remove a user from a hierarchy, the Class 6 user selects the name of a user in list box 1810 and selects &#34;Remove&#34; button 1808. 
     When the permanent hierarchy screen initially appears to a Class 6 user, only the Class 1 tab is accessible. Once the Class 1 user is selected, however, the other tabs become accessible. A permanent hierarchy cannot be saved until all required hierarchy minimums have been established. Selecting &#34;OK&#34; button 1820 saves the permanent hierarchy in the database and dismisses the screen. 
     FIG. 19 shows the &#34;Replace All&#34; screen, which allows a Class 6 user to replace one user for another in all permanent hierarchies in which the original user existed. To do so, a Class 6 user enters a full or partial name in the &#34;Existing User&#34; field 1900 and selects the &#34;Search&#34; button 1902. The search results are populated in bottom list box 1904, which includes vertical scroll bar 1918 to allow the user to view user names that exceed the visible area of the list box. The &#34;Existing User&#34; is selected by double clicking on the user entry in list box 1904, and the selected user is loaded into &#34;Existing User&#34; box 1906. 
     To select a new user to replace the original user in the permanent hierarchy, the Class 6 user enters a full or partial name in the &#34;New User&#34; field 1908 and selects &#34;Search&#34; button 1910. The search results are populated in bottom list box 1904. The Class 6 user selects the new user by double clicking on the user name in list box 1904, and the user name is loaded in box 1912. After the Existing and New Users are entered into boxes 1906 and 1912, the Class 6 user updates the permanent hierarchy in the database by pressing &#34;OK&#34; button 1914. Alternately, the Class 6 user may abort the &#34;Replace All&#34; action by pressing &#34;Cancel&#34; button 1916. The screen illustrated in FIG. 19 may be used to replace all instances of a user in all permanent hierarchies in the system, but instances where the user is included in a permanent hierarchy associated with a pending application, the Existing User name is not replaced. 
     FIG. 20 shows a screen used by a Class 6 user to maintain the clauses in the contract baseline. The Class 6 user selects the contract type in drop box 2000. By pressing the down arrow at 2002, the Class 6 user is presented with a list of contract types supported within the system. The contract tree associated with the contract type is displayed in window 2004. The Class 6 user may expand the tree and select a textual clause for export, replacement, or deletion. Furthermore, a new clause may be inserted in the contract tree. 
     A contract clause (which corresponds to the Clause tab in a Q&amp;A screen, for example) may be selected by clicking on the clause label, such as the &#34;Fixed Text&#34; clause label 2022. To export a clause to a file within a file system, the Class 6 user enters a valid file name in box 2006 and selects &#34;Export Clause&#34; button 2010. The text of the selected clause is then stored in the indicated file in RTF format. To replace a clause, the Class 6 user enters a valid file name in box 2006 and selects &#34;Replace Clause&#34; button 2012. The . RTF formatted text in the valid file name is associated with the selected clause label. To insert a clause, the Class 6 user enters a valid file name in box 2006, selects a clause label, such as &#34;Fixed Text&#34; label 2022, and selects the &#34;Insert Clause&#34; button 2014. The RTF-formatted text in the valid file name entered in box 2006 is associated with a new clause label inserted in the contract tree after the selected clause label. To delete a clause, the Class 6 user selects a clause label and selects &#34;Delete Clause&#34; button 2016, which removes the selected clause label from the contract tree. Clause labels may be renamed by a Class 6 user by selecting a clause label, pausing briefly, and selecting the same clause label for a second time. In this manner, the user may edit the clause label in accordance with the familiar Microsoft Windows RENAME style. The &#34;hidden checkbox&#34; 2008 can be checked to classify the clause as &#34;hidden.&#34; 
     While the method disclosed herein has been described and shown with reference to particular steps performed in a particular order, it will be understood that these steps may be combined, sub-divided, or re-ordered to form an equivalent method without departing from the teachings of the present invention. Accordingly, unless specifically indicated herein, the order and grouping of the steps is not a limitation of the present invention. 
     Moreover, while there have been described herein the principles of the present invention in conjunction with a specific database configuration, it is to be clearly understood that the foregoing description is made only by way of example and not as a limitation to the scope of the invention. Particularly, it is recognized that the teachings of the foregoing disclosure will suggest other modifications to those persons skilled in the relevant art. Much of the modifications made involve other features which are already known per se and which may be used instead of or in addition to features already described herein. Although claims have been formulated in this application to particular combinations of features, it should be understood that the scope of the disclosure herein also includes any novel feature or any novel combination of features disclosed either explicitly or implicitly or any generalization or modification thereof which would be apparent to persons skilled in the relevant art, whether or not such relates to the same invention as presently claimed in any claim and whether or not it mitigates any or all of the same technical problems as confronted by the present invention. The applicants hereby reserve the right to formulate new claims to such features and/or combinations of such features during the prosecution of the present invention or of any further application derived therefrom.