|Publication number||US7689899 B2|
|Application number||US 10/092,101|
|Publication date||Mar 30, 2010|
|Filing date||Mar 6, 2002|
|Priority date||Mar 6, 2002|
|Also published as||US20030172343|
|Publication number||092101, 10092101, US 7689899 B2, US 7689899B2, US-B2-7689899, US7689899 B2, US7689899B2|
|Inventors||Mark Hendricks Leymaster, Preston Holliday Abbott, Christopher D. Crisci, Seshadri Venkata Krishna, Shriram Narayanan|
|Original Assignee||Ge Corporate Financial Services, Inc.|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (37), Referenced by (26), Classifications (12), Legal Events (3)|
|External Links: USPTO, USPTO Assignment, Espacenet|
This invention relates generally to document generation, and more specifically, to methods and systems for generating documents relating to involved transactions.
Businesses engaging in complex involved transactions, referred to herein as “deals,” such as commercial financing, mergers, acquisitions and real estate transactions, generate lengthy and complex documents in order to negotiate, finalize, and document such deals. Computer software applications for text editing and document production may be used to generate these transactional deal documents. Word processing and text editing software may assist a user with the input and editing of text-based documentation. If properly prepared, at least some known word processing applications can present a blank entry form or boilerplate form into which customizing data, referred to herein as deal data, is manually entered and manually edited in a text format. Word processing applications also allow previously completed documents or document templates to be retrieved and re-edited to form new documents, one at a time.
Word processing applications are commonly used to edit and produce the documents required in business transactions. Complex business deals may require hundreds of pages of custom documents to specify the rights and obligations of the parties involved in the business deal. To acquire and maintain the expertise needed to determine the terms of such transactions, and to correctly generate, edit, and audit the complex documents accompanying each such transaction requires a significant commitment of personnel, time, and cost.
In one aspect, a document assembly production system including a server and at least one remote computer is provided. The server has a plurality of templates and other document assembly assets stored therein. The remote computer is configured to communicate with the server to access the plurality of templates and the other assembly assets to assemble fully formatted documents without using any document-assembly software and word processing software stored on the remote computer.
In another aspect, a document assembly production system including a server and a remote system is provided. The server includes a processor module which generates a HTML page displaying a series of questions on the remote system relating to a desired structure of a document to be assembled.
In another aspect, a document assembly production system including a server and at least one remote computer is provided. The server is in communication with a processor module. The server is configured to generate a web page displaying a series of questions on at least one remote computer to be responded to by a user, and fill in a plurality of fill points within an incomplete assembled document stored in the server to complete an assembled document.
In another aspect, a document assembly authoring system including a server and at least one remote computer is provided. The server has a plurality of templates and other document assembly assets stored therein. The remote computer is in communication with the server. The server has an administration module for creating and managing the plurality of templates and the other document assembly assets.
In another aspect, a secure computer-based method for assembling output documents using a server coupled to a database and at least one remote computer is provided. The database has a plurality of templates stored therein. The method includes displaying document structure questions at the remote computer, where the questions displayed are controlled by logic and conditions imbedded in a user selected template, and are displayed in a tree format. The method also includes receiving a response for each question displayed, altering the displayed structure question tree based on at least one response received from a user, and generating the assembled documents based on the responses received from the user.
Example embodiments of systems and processes that facilitate integrated network-based electronic reporting, document assembly, and workflow process management related to a Deal Document Assembly Coordination System (DDACS) are described below in detail. The systems and processes facilitate, for example, electronic submission of document type and structural choices, as well as customizing information for document assembly using a remote system, automated validation of information, and HTML based reporting for internal and external system users. The DDACS permits a business entity to manage document assembly and the workflow relating to a business deal.
In the example embodiment, the DDACS is utilized to collect, track, display, and disseminate real time information, including data that relates to a deal involving a business entity relationship or “deal data.” Deal data includes at least one of general business information for a business entity, a deal description or deal definition, a deal template and structure, allied deal information, assembled documents, and the parties involved in the financial transaction or deal. The DDACS prompts the users to input certain deal data, select a class of document to be assembled, and then prompts the user to select from a list of issues and matters those specific documents that are necessary for the business deal. The user is then prompted to supply specific data for the deal, such as names and dates, and after checking the data for validity and consistency, the DDACS then enables the user to assemble the output document relating to the business deal so that the deal may be negotiated and documented. In addition, the DDACS provides the user with help features, supporting detail and other advice during the generation of the deal documents that facilitate speeding the completion of the document assembly. The DDACS also provides the user with a plurality of reports regarding the deal data entered and whether additional deal data is needed.
Deal data relating to a business deal and the business entities involved in the deal is received by the DDACS and stored in a database. The DDACS updates the database with deal data received, tracks the deal data received, provides deal data to a user, generates reports relating to the business deal, and allows an attorney to review the assembled document before it is presented to the parties.
In the DDACS, deal data is stored in the database. The network based DDACS provides convenient access to deal data, including at least one of a deal type, a business group involved with the deal, a regional location of the business unit, a deal workflow stage, a deal completion status, a type of document to assemble, a person that created the selected deal entry, a person that last edited the selected deal entry, deal description text, selected deal input documents, and the customer involved in the deal. In the example embodiment, users are authorized by the DDACS administrator to gain access into the DDACS, and each user logs onto DDACS using a local HTML browser. Once the DDACS home page is accessed, the user may choose from a list of saved deals or customer names that the user has been given to manage or enter deal data.
In one embodiment, a server-based computer program is provided, and the program is embodied on a computer readable medium and utilizes a Structured Query Language (SQL) database with remote client software for administration but a remote HTML browser interface for standard document assembly management, data entry, and reporting. In an example embodiment, the system is web-enabled and is executable using a business-entity intranet. The DDACS is accessible by individuals having an authorized access outside the firewall of the DDACS hosting business-entity through the Internet. The system operates in a Windows® environment (Windows is a registered trademark of Microsoft Corporation, Redmond, Wash.).
The systems and processes are not limited to the specific embodiments described herein. In addition, components of each system and each process can be practiced independently and separately from other components and processes described herein. Each component and process also can be used in combination with other assembly packages and processes.
In the example embodiment, input documents 22 are used by a processor module 24 on server system 12 in conjunction with information stored on database 20. Processor module 24 also retrieves information from database 20 and input documents 22 such that information may be displayed on remote systems 14. Remote system 14 then directs the processor module 24 in the creation of assembled documents 26, also known as output documents, as the user adds, changes, and deletes information displayed on remote system 14 and stored in database 20. The assembled document 26 can be delivered to remote system 14 or directed elsewhere by the user. Assembled documents 26 relate to the business deal, sometime also referred to as the financial transaction.
In the example embodiment, each input document 22 is a native Word™ formatted file containing appropriately formatted text and graphics that may be used in a particular class of assembled documents and a template selected by the user via DDACS 10 for a particular assembled document 26. (Word is a trademark of Microsoft Corporation, Redmond, Wash.). At least some input documents 22 are several pages in length. Input documents 22 are created in a word processor, and not in DDACS 10. Input documents 22 do not have to be stored in database 20 though they must be in a designated server directory. However, as discussed below, synchronizing information relevant to each specific input document 22 is stored in database 20. If processor module 24 calls for an input document 22 that does not include corresponding synchronizing information, or alternatively, fails to locate a requested input document 22, processor module 24 “locks” the corresponding template and does not generate assembled document 26.
In the example embodiment, assembled document 26, also known as an output document, is the final document assembled by processor module 24. Assembled document 26 is a native Word™ formatted file. However, assembled document 26 may be delivered in formats other than Word™ formats. Typically, assembled document 26 is built of many input documents 22, and when complete, contains several logical documents. A logical document is a part of an assembled document 26 that is logically complete of itself, for example, an Appendix or a Reporting Form. An assembled document 26 may be comprised of many logical documents. A single logical document may be comprised of several input documents 22, while another input document 22 may contain several logical documents in the order they would appear in assembled document 26.
Input documents 22 are created on word processor system 32, and are synchronized with DDACS 10 through administration server module 34. Administration server module 34 determines synchronizing information about each input document 22, which information is then stored in database 20. Administration server module 34 also creates, revises, and manages templates 36 and passwords 38. If processor module 24 (shown in
In the example embodiment, each template 36 is one of a potentially infinite set of control structures. Each template 36 is a highly structured set of relational database tables that contain much of the content displayed by DDACS 10, in addition to the logic that controls all visible and invisible operations from a structure interview and input document selection to insertion of data into appropriate “blanks” in assembled documents 26. Each template 36 is stored in database 20.
The term “structure” as used herein refers to an organization of a particular output document, roughly analogous to a list of logical documents that might be listed in a table of contents for that output document. As discussed below in detail, the structure is defined as a result of a user responding to questions presented on a Deal Structure interview page filtered with the business logic built into a template 36. Fill points are specially formatted “blanks” in input documents 22 which, when used in an assembled document 26, receive appropriate user-supplied data under template 36 control.
Each workstation, 54, 56, and 58 is a personal computer having a web browser. Although the functions performed at the workstations typically are illustrated as being performed at respective workstations 54, 56, and 58, such functions can be performed at one of many personal computers coupled to LAN 52. In the example embodiment, in order to perform DDACS administration functions, an administration client module 33 must be installed on the workstation. Workstations 54, 56, and 58 are illustrated as being associated with separate functions only to facilitate an understanding of the different types of functions that can be performed by individuals having access to LAN 52. In an example embodiment, remote system 14 could be workstation 54 which can be used by a user to assemble a document using information stored in database 20.
Server system 12 is configured to be communicatively coupled to various individuals, including employees 60 and to third parties, e.g., outside attorneys, 62 perhaps via an ISP Internet connection 64. The communication in the example embodiment is illustrated as being performed via the Internet, however, any other wide area network (WAN) 66 type communication can be utilized in other embodiments, i.e., the systems and processes are not limited to being practiced via the Internet. In addition, and rather than WAN 66, local area network 52 could be used in place of WAN 66.
In the example embodiment, any authorized individual having a workstation 68 that includes administration client module 33 (shown in
As explained above, the architecture of system 40 as well as various components of system 40 are example only. Other architectures are possible and can be utilized in connection with practicing the processes described below.
After logging into system 10 through remote system 14, a deal definition page is displayed to the user that enables the user to select a class of document to assemble by choosing a deal template (described as a “structure” in the example embodiment) 340. The deal definition page also prompts the user to input data relating to a business group in which the deal originates, a current stage in the workflow for the deal, an approval status of the deal, and whether this is to be a new document assembly or a revision to an existing document to be assembled. Once the user selects deal template 340 by utilizing remote system 14, the deal definition page displays a list of deals that the user has been approved to manage and that correspond with the entered data (shown in
After selecting deal template 340, system 10 displays a deal structure page that includes designated deal structure questions 350 that were previously entered by an administrator utilizing administration client module 33 and administration server module 34, and stored in deal template 340. The user then responds to the designated deal structure questions 360 by utilizing remote system 14 and processor module 24 (shown in
After responding to deal structure questions 360, needed input document files 370 and synchronized dates for those files 380 are determined and called by processor module 24. Previously, administration client module 33 in communication with administration server module 34 synchronized input documents, recorded synchronized date information 380 about each approved input document 390, and stored the synchronized date information in database 20 (shown in
After completing responses to specific deal information questions 400, system 10 readies the documents to be assembled 420 from the selected deal structure 340 and approved input documents 390. System 10 enables the user to save, re-load, and edit 430 the transaction documents. Before permitting a document to be assembled, system 10 validates 440 that the input documents include the appropriate date assigned thereto. If the input documents are not validated 444, the user will receive an error message 450, and the document will not be assembled. Furthermore, if input documents are validated 454, then system 10 directs document builder 410 to complete generating output documents 470. More specifically, the specially coded blanks in each input document are “filled” using a search-and-replace method, the deal information data, and the fill points managed by processor module 24 and the selected template. When the document is fully built, the generated assembled document 470 is displayed to the user for review within the browser, or for downloading. Lastly, if requested by the user via remote system 14, system 10 generates a plurality of reports 480 relating to the document assembly (e.g., a listing of unanswered deal structure questions).
In the example embodiment, prior to the user logging into DDACS 10, a deal generator administrator designates the user name to be entered into User Name field 502 for each user and a corresponding password to be entered into Password field 504. In addition, the deal generator administrator designates which deals the user may access for assembling documents and how that user's workgroup will be labeled.
Business Group label 528 displays a business group within the business entity to which the user is assigned. Business Region pull-down list 530 enables the user to input a regional location where the deal is assigned. Deal Workflow Stages pull-down list 534 enables the user to input a current stage in the workflow of the deal. Deal Workflow Status pull-down list 532 enables the user to input a decision status of the deal's closure (i.e., pending or won). Structure pull-down list 536 enables the user to select a class of document to be assembled, here captioned the “Structure” of the deal. After the user inputs data in Business Region pull-down list 530, Deal Approval Status pull-down list 532, Deal Workflow Stages pull-down list 534, and Structure pull-down list 536, the user selects Open button 538. User interface 520 also displays a navigational bar common to all DDACS 10 pages: a Home tab 540, a Deal Home tab 542, a Reports tab 544, a Contact Us tab 546, a Help tab 548, and a Sign Off tab 550. A Profile button 552 allows users to change their passwords.
In the example embodiment, user interface 580 displays list of deals 596 in a chart form that includes the following headers: Deal ID 598, Deal Name 600, Class 602, Customer 604, and Select 606. From list of deals 596, the user selects a deal that the user intends to manage for document assembly. More specifically, after selecting the deal by clicking on a Go button 607, that deal's data is loaded so the user is enabled to add, change, or delete deal data relating to the selected deal. User interface 580 also displays the common navigational bar including a Home tab 608, a Deal Home tab 610, a Reports tab 612, a Contact Us tab 614, a Help tab 616, and a Sign Off tab 618.
In the example embodiment, Deal Structure page 642 also displays a tree-like list of yes-or-no questions 656 relating to possible issues and matters that may be involved in the selected deal, subject to management by the user. If a listed issue or matter is involved in the selected deal, the user should respond “yes” to the particular questions. To respond “yes,” the user clicks to the left of the text for the deal structure question in check box 658. To answer “no,” the user leaves click box 658 empty next to the particular deal structure question. If there are any related or “follow-up” deal structure questions, the deal structure question tree 656 expands just below the parent question and displays the subsequent deal structure child questions indented, as shown in
Preview button 654 enables the user to preview input documents so far called by the selected deal structure before the document to be assembled is finalized. Once saved, the user can also revise the deal structure choices by resetting “yes” answers to “no” by clicking on previously checked boxes. When this occurs, the check box goes blank and the now irrelevant subordinate follow-up questions are no longer displayed. User interface 640 also displays a Deal Structure tab 662 and a Deal Information tab 664. The user clicks Deal Information navigation button 664 when the deal structure interview has been completed.
In the example embodiment, Deal Information page 682 also displays Deal Information List 696 which includes a list of information questions 698 and question ID suffixes 699 and data fields 700 wherein each question 698 is unique and is followed by a question ID suffix 699 and its own unique question ID number field 700. To navigate directly to a known question ID, the user clicks the Find button 694, fills in the question ID in the dialog that appears, and is immediately moved to that information question. Each question 698 prompts the user for information that is entered into data fields 700. The information entered into data fields 700 is subsequently saved and then utilized to replace fill points in an incomplete document to be assembled that the processor module 24 (shown in
After entering the information into data fields 700, the information is validated on user interface 680, and, if this web page determines that the information entered is not valid, then the user is advised of such and asked to reenter the information. Validation includes testing for illogical data, as well as numbers outside of present limits or with improper separators. In the example embodiment, the validation occurs without interrogation of the processor or the HTML server by the HTML page on remote system 14 (shown in
In the example embodiment, when the user has selected Save tab 664 from user interface 680 and the information is successfully saved, user interface 720 will display a message 734 advising the user that the information has been successfully saved. In the example embodiment, user interface 720 also displays the common navigation bar, including a Home tab 736, a Deal Home tab 738, a Reports tab 740, a Contact Us tab 742, a Help tab 744, and a Sign Off tab 746.
In the example embodiment, user interface 840 also displays a Deal Structure tab 858, a Deal Information tab 860, a Save tab 862, a Copy Deal tab 864, a Build Document tab 866, and a Pre-Compiler tab 868. Copy Deal tab 864 enables the user to save a duplicate set of deal data under a different Deal ID number, as might be useful for creating or comparing alternative assembled document structures. All of the previously entered responses are also duplicated in such copies. Pre-Compiler tab 868 enables the user to confirm that the saved deal data is approved for document assembly into DDACS 10 without actually building the corresponding assembled documents.
In the example embodiment, user interface 920 displays a menu bar 922 at the top of user interface 920 that enables the administrator to navigate and manage the administrative operations included within DDACS 10. Menu bar 922 includes: File pull-down list 924, Edit pull-down list 926, Tools pull-down list 928, Information Builder pull-down list 930, and Help pull-down list 932. User interface 920 also displays a Structure ID pull-down field 934, a Structure Name pull-down list 936, a Created By label 938, and a Modified By label 940. Structure ID pull-down list 934 displays a number, e.g., 222 in the example embodiment, that corresponds with a specific template 36 (shown in
User interface 920 also displays a Structure Questions and Related Documents panel 942, a Structure Questions list 944, and a Documents list 946. Structure Questions list 944 displays the top portion of an inventory of all of the Structure Questions that are available for use in any template within DDACS 10. Documents list 946 displays the top portion of the inventory of all of the Document links that are included within DDACS 10. Structure Questions and Related Documents panel 942 displays on administration client module 33 for a selected template a tree-like list of working Structure Questions and Related Documents 948 that have been selected for use in the structure tree by an administrator from Structure Questions list 944 and Documents list 946 of document links. Tree-like list of Structure Questions and Related Documents 948 for the selected template is the source of the processor's deal structure displayed on remote system 14 (shown in
User interface 920 also includes an up arrow button 954 and a down arrow button 956. Up arrow button 954 and down arrow button 956 enable the administrator to move working structure questions and working document links up or down as they appear within the structure tree shown in panel 942. In the example embodiment, up arrow 954 and down arrow 956 only allow the administrator to move working structure questions and working document links up or down as they appear within their own hierarchical level on the structure tree as shown on panel 942. A Promote button 958 and a Demote button 960 enable the administrator to move working structure questions and working document links up a hierarchical level or down a hierarchical level as they appear within the structure tree and panel 942.
The working structure questions and working document links that are displayed on the structure tree panel 942 relate to possible issues, subject matter and contents that may be involved in a class of selected deals addressed by a particular template. If an issue, content or matter included in the selected template is actually involved in a given deal, a user using remote system 14 should respond “yes” to the particular structure questions. To respond “yes,” the user clicks in check box 658 to the left of the text for the structure question (shown in
Where it has been so designated by the administrator when a template is created or edited, a structure question may be designated as “Mandatory,” which is shown with a checkmark 961 in the example embodiment of user interface 920. This results in a deal structure question being automatically marked “yes” in the processor if the antecedent deal structure question is answered “yes.” This result may span more than one subordinate level on the structure tree, and also automatically include one or more document links.
User interface 920 also displays an Options panel 962 that includes an In Progress radio button 964, an Enabled radio button 966, a Protected radio button 968, and a Frozen radio button 970. The administrator can select from In Progress radio button 964 and Enabled radio button 966. In Progress radio button 964 is selected when the administrator is still in the process of building a specific template 36 and specific template 36 is not ready to be tested or used by a user on remote system 14. Enabled radio button 966 is selected when the administrator has completed building a template 36 and template 36 is ready for testing or production use by a user on remote system 14. Protected radio button 968 is selected by the processor automatically when an enabled template 36 has caused a processor audit failure during the assembly of a production document so DDACS 10 wishes to protect template 36 from further use until the audit problem is resolved. Frozen radio button 970 is not selected by the administrator, but instead is activated automatically by DDACS 10. Frozen radio button 970 is activated as soon as an enabled template 36 has been used to assemble an output document for a specific deal. By freezing template 36 that has already been used in a specific deal, changes to the logic in a frozen template 36 are prevented so that, if a saved deal's data is used to assemble a document in the future, DDACS 10 presentation and the assembled document will reliably match the original assembled document. Thus, DDACS 10 facilitates preventing subsequent changes to templates 36 that have already been used in one or more specific deals such that documents relating to that specific deal stored in database 20 (shown in
User interface 920 also displays an Undo button 972 that enables an administrator to undo a last action taken, a Save button 974 that enables an administrator to save their entries on user interface 920, a Close button 976 that closes user interface 920, a Structure Question bar 978, and Document Editor bar 980.
Structure Questions and Related Documents panel 942 displays on administration client module 33 for a selected template tree-like list of working Structure Questions and Related Documents 948 that have been selected for use in the structure tree by an administrator from Structure Questions list 944 and Documents list 946 of document links. Tree-like list of Structure Questions and Related Documents 948 for the selected template include at least one working document link 982 and at least one working structure question 984.
Structure Question ID field 1002 displays an automatically assigned number that corresponds with the structure question being added, edited or deleted from DDACS 10 (shown in
Copy From button 1012 enables an administrator to copy an existing structure question content so that a new structure question can be completed by editing by the administrator. Delete button 1014 enables the administrator to delete an existing structure question. Save button 1016 enables the administrator to save an existing structure question within DDACS 10 by adding it to Structure Question list 944. The administration module will not permit a revised Structure Question to be saved if that Structure Question is used in any Frozen or Locked template. Close button 1018 enables an administrator to close user interface 1000. In the example embodiment, when Close button 1018 is selected and the editor contains unsaved content, the administrator will be asked whether the user wants to close user interface 1000 without saving to facilitate preventing loss of work. If the administrator forgets to save, user interface 1000 offers an opportunity to save without requiring it.
When selected, Where Used button 1020 displays a list of other templates 36 (shown in
Document ID field 1042 displays an automatically assigned number that corresponds with the document link being added, revised, or deleted from Document list 946. File Name field 1044 displays an input document file name used in the specific document link. Like Structure Question list 944, Document list 946 is stored in database 20 (shown in
New button 1052 enables an administrator to add a new document link to Document field 946. In the example embodiment, when a new document link is added, the data fields shown on user interface 1040 are initially blank. Delete button 1054 enables the administrator to delete an existing document link from Document list 946. Save button 1056 enables the administrator to save a new document link within DDACS 10. The administration module will not permit a revised document link to be saved if that document link is used in any Frozen or Locked template. Close button 1058 enables an administrator to close user interface 1040. In the example embodiment, when Close button 1058 is selected the user will be asked whether the user wants to close user interface 1040 with or without saving.
When selected, Where Used button 1060 displays a list of other templates 36 (shown in
User interface 1080 displays a Structure ID field 1082 that displays a number, e.g., 222 in the example embodiment, that corresponds with a specific template 36 (shown in
A left arrow button 1090 enables the administrator to insert a specific information question from Application Questions list 1086 into the information tree such that it displays in Documents and Related Application Questions panel 1084, and a right arrow button 1092 enables the administrator to remove a specific information question from the information tree and thus from Documents and Related Application Questions panel 1084.
User interface 1080 also includes an up arrow button 1094 and a down arrow button 1096. Up arrow button 1094 and down arrow button 1096 enable the administrator to move information questions up or down within those information questions associated with a given document link, as they appear within the information tree. By moving the deal information questions up and down, the administrator can select the order in which the deal information questions appear on user interface 680 (shown in
User interface 1080 also displays an Undo button 1098 that enables an administrator to undo a last action taken, a Refresh button 1100 that enables a user to refresh and update user interface 1080, and an Application Question Editor bar 1102 that enables an administrator to open an Application Question Editor so to add, edit, and delete the information questions.
Word Field Name field 1122 displays a fill point name that corresponds with a previously configured “fill-in” section within an input document that may be used in a document to be assembled. Thus, the field name shown in Word Field Name field 1122 illustrates where the data to be entered in response to the information question exemplified will be located within a document to be assembled. Question Title pull-down edit box 1124 displays and allows creation and revision to a title that corresponds with the specific information question as it would appear in Application Questions list 1086 and any corresponding working information question in any template. Question Text pull-down edit box 1126 displays and allows creation and revisions to a specific information question as it may appear on user interface 680 (shown in
Answer Data Type pull-down list 1130 displays a type of answer that DDACS 10 (shown in
Answer Category Section 1132 offers an administrator choices to add features to an information question such as creating multiple choice answers that will be provided to a user for a specific information question, configuring a default answer based on a response to another information question, or to add or revise a prefix or suffix automatically added to any response to this information question. The multiple choice answers are offered as appropriate to the processor user on remote system 14 (shown in
Multiple Instance Section 1136 enables the administrator to select how the specific deal information question should be shown with repeating elements of an assembled document, for example multiple signatories, on user interface 680 through remote system 14. This check box in conjunction with Allow Multiple Instance check box 1008 (shown in
New button 1144 enables an administrator to add a new deal information question to Application Questions list 1086. Delete button 1146 enables the administrator to delete an existing information question from Application Questions list 1086. Save button 1148 enables the administrator to save a new information question within DDACS 10. Copy From button 1150 supplies the content of an existing Information Question for editing as a new Information Question is created, so that the administrator need not enter all the data from scratch. Close button 1152 enables an administrator to close user interface 1120, and an offer to save any unsaved work will be made as appropriate.
DDACS 10 therefore enables a business entity to manage deal data, including at least one of business information, a deal description or definition, a deal template and structure, deal information, deal document links, and the client parties involved in the business deal. DDACS 10 also prompts the users to input deal data, and to then select from a list of issues and documents the specific logical documents that are actually involved in the business deal using professionally meaningful questions and expert logic built into the template selected for that deal rather than the names of those documents. DDACS 10 then enables the user to generate the assembled documents relating to the business deal such that the deal can be negotiated and documented. In addition, DDACS 10 provides the user with help features, notes, and other comments during the generation of the deal documents that help the user to easily navigate the questions involved and generate and finalize the deal documents. Lastly, DDACS 10 provides the user with a plurality of reports regarding deal data entered into the system and advises when additional information is needed to assure that the deal assembled documents are complete. By enabling a business entity to implement business rules and better manage deal data, DDACS 10 facilitates reducing transaction costs for the business entity, facilitates reducing the amount of time spent on each transaction by the business entity, and facilitates generating documents that better reflect the terms and conditions of the deal.
While the invention has been described in terms of various specific embodiments, those skilled in the art will recognize that the invention can be practiced with modification within the spirit and scope of the claims.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US4663615||Dec 26, 1984||May 5, 1987||International Business Machines Corporation||Document creation|
|US4831526||Apr 22, 1986||May 16, 1989||The Chubb Corporation||Computerized insurance premium quote request and policy issuance system|
|US4962475||Mar 15, 1988||Oct 9, 1990||International Business Machines Corporation||Method for generating a document utilizing a plurality of windows associated with different data objects|
|US5043891||Sep 5, 1989||Aug 27, 1991||Wang Laboratories, Inc.||Document generation apparatus and methods|
|US5144555||Nov 13, 1990||Sep 1, 1992||Hitachi, Ltd.||Method and apparatus for supporting of making formatted document|
|US5228121||Sep 8, 1992||Jul 13, 1993||Digital Equipment Corporation||Document generation using information engineering|
|US5267155||Mar 6, 1992||Nov 30, 1993||Medical Documenting Systems, Inc.||Apparatus and method for computer-assisted document generation|
|US5272623||Nov 7, 1990||Dec 21, 1993||The United States Of America As Represented By The Secretary Of The Navy||Software programming method for forming Government contracting documents|
|US5434962||May 24, 1994||Jul 18, 1995||Fuji Xerox Co., Ltd.||Method and system for automatically generating logical structures of electronic documents|
|US5446653||Jun 22, 1994||Aug 29, 1995||Aetna Casualty And Surety Company||Rule based document generation system|
|US5511193||Feb 19, 1993||Apr 23, 1996||Apple Computer, Inc.||Text services manager providing multiple instances of input methods for text language processing and automatic synchronization between met hods|
|US5630126||Dec 13, 1994||May 13, 1997||International Business Machines Corp.||Systems and methods for integrating computations into compound documents|
|US5634019||Jun 6, 1995||May 27, 1997||Microsoft Corporation||Method and system for in-place interaction with contained objects|
|US5634054||Jul 17, 1995||May 27, 1997||General Electric Company||Document-based data definition generator|
|US5655130||Oct 14, 1994||Aug 5, 1997||Unisys Corporation||Method and apparatus for document production using a common document database|
|US5659676||Sep 20, 1994||Aug 19, 1997||International Business Machines Corporation||Systems and methods for creating and refreshing compound documents|
|US5669005||Oct 11, 1995||Sep 16, 1997||Apple Computer, Inc.||System for automatically embedding or incorporating contents added to a document|
|US5671429||Jun 1, 1993||Sep 23, 1997||Fuji Xerox Co., Ltd.||Document processing system providing facilitated modification of document images|
|US5692206||Nov 30, 1994||Nov 25, 1997||Taco Bell Corporation||Method and apparatus for automating the generation of a legal document|
|US5740455||May 16, 1995||Apr 14, 1998||Apple Computer, Inc.||Enhanced compound document processing architectures and methods therefor|
|US5742816||Sep 15, 1995||Apr 21, 1998||Infonautics Corporation||Method and apparatus for identifying textual documents and multi-mediafiles corresponding to a search topic|
|US5819302||Apr 29, 1996||Oct 6, 1998||Sun Microsystems, Inc.||Method and apparatus for automatic generaton of documents with single-layered backgrounds from documents with multi-layered backgrounds|
|US5953718||Nov 12, 1997||Sep 14, 1999||Oracle Corporation||Research mode for a knowledge base search and retrieval system|
|US6014680||Aug 29, 1996||Jan 11, 2000||Hitachi, Ltd.||Method and apparatus for generating structured document|
|US6061698||Oct 22, 1997||May 9, 2000||International Business Machines Corporation||Merging tagged documents and scripts having dynamic content|
|US6072461||Aug 15, 1997||Jun 6, 2000||Haran; Yossi||Apparatus and method for facilitating document generation|
|US6182095||Apr 30, 1998||Jan 30, 2001||General Electric Capital Corporation||Document generator|
|US6209004||Aug 28, 1996||Mar 27, 2001||Taylor Microtechnology Inc.||Method and system for generating and distributing document sets using a relational database|
|US6243740||Feb 13, 1998||Jun 5, 2001||Xerox Corporation||Public interactive document|
|US6272485 *||Feb 18, 1999||Aug 7, 2001||Creative Internet Applications, Inc.||Transferring selected formatted documents over a computer network using interface script|
|US6307962||Nov 7, 1997||Oct 23, 2001||The University Of Rochester||Document data compression system which automatically segments documents and generates compressed smart documents therefrom|
|US6446048 *||Sep 3, 1999||Sep 3, 2002||Intuit, Inc.||Web-based entry of financial transaction information and subsequent download of such information|
|US6601057 *||Oct 30, 2000||Jul 29, 2003||Decentrix Inc.||Method and apparatus for generating and modifying multiple instances of an element of a web site|
|US20010047326 *||Mar 13, 2001||Nov 29, 2001||Broadbent David F.||Interface system for a mortgage loan originator compliance engine|
|US20020046235 *||Mar 2, 2001||Apr 18, 2002||Tony Foy||Document creation and delivery|
|US20020178190 *||May 22, 2001||Nov 28, 2002||Allison Pope||Systems and methods for integrating mainframe and client-server data into automatically generated business correspondence|
|US20070208606 *||May 3, 2007||Sep 6, 2007||Jpmorgan Chase Bank, N.A.||Workflow management system and method|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US7900132 *||Mar 1, 2011||Adobe Systems Incorporated||Method and system to process an electronic form|
|US7996760 *||Dec 15, 2004||Aug 9, 2011||Sap Ag||Acquisition of user data over a network|
|US8037004 *||Jun 11, 2007||Oct 11, 2011||Oracle International Corporation||Computer-implemented methods and systems for identifying and reporting deviations from standards and policies for contracts, agreements and other business documents|
|US8042037 *||Oct 29, 2004||Oct 18, 2011||Glovia International, Inc.||Sequencing of markup language documents|
|US8229954||Jan 4, 2012||Jul 24, 2012||Commvault Systems, Inc.||Managing copies of data|
|US8352954||Jan 8, 2013||Commvault Systems, Inc.||Data storage resource allocation by employing dynamic methods and blacklisting resource request pools|
|US8386239||Jun 17, 2010||Feb 26, 2013||Holovisions LLC||Multi-stage text morphing|
|US8396838||Sep 7, 2010||Mar 12, 2013||Commvault Systems, Inc.||Legal compliance, electronic discovery and electronic document handling of online and offline copies of data|
|US8505010||Mar 28, 2011||Aug 6, 2013||Commvault Systems, Inc.||Storage of application specific profiles correlating to document versions|
|US8543381||Jun 17, 2010||Sep 24, 2013||Holovisions LLC||Morphing text by splicing end-compatible segments|
|US8612394||Sep 30, 2011||Dec 17, 2013||Commvault Systems, Inc.||System and method for archiving objects in an information store|
|US8725688||Sep 3, 2009||May 13, 2014||Commvault Systems, Inc.||Image level copy or restore, such as image level restore without knowledge of data object metadata|
|US8725731||Jan 23, 2012||May 13, 2014||Commvault Systems, Inc.||Systems and methods for retrieving data in a computer network|
|US8725964||Sep 7, 2012||May 13, 2014||Commvault Systems, Inc.||Interface systems and methods for accessing stored data|
|US8769048||Jun 18, 2008||Jul 1, 2014||Commvault Systems, Inc.||Data protection scheduling, such as providing a flexible backup window in a data protection system|
|US8782064||Jun 29, 2012||Jul 15, 2014||Commvault Systems, Inc.||Managing copies of data|
|US8849762||Mar 31, 2011||Sep 30, 2014||Commvault Systems, Inc.||Restoring computing environments, such as autorecovery of file systems at certain points in time|
|US8930319||Sep 13, 2012||Jan 6, 2015||Commvault Systems, Inc.||Modular backup and retrieval system used in conjunction with a storage area network|
|US9003117||Mar 6, 2013||Apr 7, 2015||Commvault Systems, Inc.||Hierarchical systems and methods for performing storage operations in a computer network|
|US9003137||Mar 6, 2014||Apr 7, 2015||Commvault Systems, Inc.||Interface systems and methods for accessing stored data|
|US9021198||Jan 20, 2011||Apr 28, 2015||Commvault Systems, Inc.||System and method for sharing SAN storage|
|US9092378||Sep 23, 2014||Jul 28, 2015||Commvault Systems, Inc.||Restoring computing environments, such as autorecovery of file systems at certain points in time|
|US9104340||Sep 26, 2013||Aug 11, 2015||Commvault Systems, Inc.||Systems and methods for performing storage operations using network attached storage|
|US9135364||Nov 9, 2012||Sep 15, 2015||Google Inc.||Delivery of web pages with markup for speed|
|US20060129905 *||Dec 15, 2004||Jun 15, 2006||Sap Ag||Acquisition of user data over a network|
|US20130191737 *||Dec 21, 2012||Jul 25, 2013||Dictaphone Corporation||Method, system, and apparatus for data reuse|
|U.S. Classification||715/224, 706/46, 705/17, 705/44|
|International Classification||G06F17/24, G06F17/00|
|Cooperative Classification||G06Q20/40, G06Q20/204, G06F17/243|
|European Classification||G06Q20/40, G06Q20/204, G06F17/24F|
|Jun 24, 2002||AS||Assignment|
Owner name: GE CAPITAL COMMERCIAL FINANCE, INC., CONNECTICUT
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:LEYMASTER, MARK HENDRICKS;ABBOTT, PRESTON HOLLIDAY;CRISCI, CHRISTOPHER D.;AND OTHERS;REEL/FRAME:013026/0159;SIGNING DATES FROM 20020404 TO 20020610
Owner name: GE CAPITAL COMMERCIAL FINANCE, INC.,CONNECTICUT
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:LEYMASTER, MARK HENDRICKS;ABBOTT, PRESTON HOLLIDAY;CRISCI, CHRISTOPHER D.;AND OTHERS;SIGNING DATES FROM 20020404 TO 20020610;REEL/FRAME:013026/0159
|Sep 8, 2006||AS||Assignment|
Owner name: GE CORPORATE FINANCIAL SERVICES, INC.,CONNECTICUT
Free format text: CHANGE OF NAME;ASSIGNOR:GE CAPITAL COMMERCIAL FINANCE, INC.;REEL/FRAME:018230/0044
Effective date: 20030801
|Sep 30, 2013||FPAY||Fee payment|
Year of fee payment: 4