Patent Application
20100274803
This application claims the benefit of Japanese Patent Application No. 2009-109795 filed on Apr. 28, 2009, the disclosure of which is incorporated herein by reference.
1. Field of the Invention
The present invention relates to a document preparation support apparatus, a document preparation support method, and a document preparation support program.
2. Description of the Related Art
Various techniques of efficiently preparing a document concerning an agreement between a plurality of parties concerned, such as a contract document, have been disclosed.
Japanese Laid-Open Patent Application, Publication No. 2006-65421 (paragraph [0004]) (to be referred to as Patent Document 1 hereinafter) discloses a system in which: contract patterns corresponding to contract types are sequentially displayed; a selection of a case required for each contract pattern is received; a template in accordance with the contract pattern or the case is displayed where necessary; and a contract document is finally prepared by editing the template by a user.
Japanese Laid-Open Patent Application, Publication No. 2003-108879 (paragraph [0008]) (to be referred to as Patent Document 2 hereinafter) discloses a system in which: a proposal similar to a request of a customer is obtained; a difference between information on a commodity currently possessed by the customer and each of candidate commodities to be proposed to the customer; the difference is compared to the customer's request to determine a commodity to be proposed from among the candidate commodities; and the obtained proposal is edited based on information on the determined commodity to be proposed.
In Patent Document 1, however, a template as a knowhow is associated with each of the cases (corresponding to a clause of the present invention). Thus, it is not possible to present a template using a passage described in a given clause as a key, which is not enough to minutely avoid a risk in a contract.
Further, Patent Document 1 does not disclose a technique in which, if a user finds a new risk, a new knowhow is created or an existing knowhow is updated for avoiding the risk.
Patent Document 2 requires extra time and labor for inputting information on a commodity currently possessed by the customer. This cannot inevitably avoid a possibility of neglecting an input of the information. Additionally, if there is no difference between the information on a commodity currently possessed by the customer and the information on a candidate commodity to be proposed to the customer (that is, if the candidate commodity meets a customer's request), the system does not give warning on a possible risk in the contract.
In light of the above problems, the present invention has been made in an attempt to provide a document preparation support apparatus and the like capable of supporting an efficient preparation of a contract document while utilizing information on previous contracts and knowhows and avoiding risks in a contract.
A document preparation support apparatus outputs a knowhow and a response example for each critical passage. The document preparation support apparatus includes: a storage unit; and a control unit. The storage unit includes; first corresponding information that stores the knowhow in association with a search key for extracting a critical passage; and second corresponding information that stores a response example in association with a search key for extracting a critical passage. The control unit receives a document; extracts a critical passage from the received document using a prescribed search key from among the search keys; searches the first corresponding information and the second corresponding information using the prescribed search key used for the extraction to obtain a knowhow and a response example; and outputs the obtained knowhow and response example in association with the critical passage.
Other features and advantages of the present invention will become more apparent from the following detailed description of the invention, when taken in conjunction with the accompanying exemplary drawings.
Next is described in detail an exemplary embodiment for carrying out the present invention with reference to the related drawings.
A contract document is generally prepared in such a repeated manner that a contractor draws up a draft, an owner revises it, the contractor again revises it, etc. If the parties to the contract finally agree to the revised draft, it becomes the contract document. A passage subjected to such a revision often relates to a contract condition on which there is a conflict of interest between the parties to the contract.
Description hereinafter is made assuming that a contract document related to a trade business.
Below are described a RFP 1 and a response document 2 with reference to
In
In the first clause 310 of
In the second clause 310, the clause title 311 is “2. Damages” and the clause content 312 is “Buyer has the right . . . ”.
In
A section column 313 includes the clause title 311 of the clause 310 containing a critical passage. A requirement column 314 includes the critical passage (more specifically, the critical passage and terms before and after the passage; to be described in detail hereinafter). A comment column 315 includes a response.
For example, the first row of the response document 2 describes that the clause content 312 of the clause 310 with the clause title 311 as “1. General” has a critical passage of “address” and that “Goods shall not be . . . ” is prepared in response to the critical passage.
The RFP 1 is typically exchanged between the parties to the contract. However, the response document 2 is not necessarily exchanged between the parties to the contract and may be made use of within the owner that receives the RFP 1 from the contractor. Further, the RFP 1 and the response document 2 may be exchanged within one business enterprise.
Next is described a document preparation support apparatus 3 with reference to
As shown in
The auxiliary storage device 16 stores therein: a rule group database 31; a phrase specifying search rule database 32; a phrase-phrase specifying search rule database 33; a phrase-numerical value specifying search rule database 34; a phrase with numerical value specifying search rule database 35; a rule-knowhow corresponding information 36; a knowhow database 37; a rule-template corresponding information 38; a template database 39; a buffer data 40; and an output format 41 (to be described in detail hereinafter).
A critical passage extract part 21, a response document edit/preparation part 22, and a knowledge edit/preparation part 23 are programs. To simplify description, it is assumed herein that the parts 21 to 23 as programs directly perform their respective functions. Actually, however, it is the central control unit 11 that reads and loads the parts 21 to 23 as programs from the auxiliary storage unit 16 into the main storage unit 15, and executes the functions written in the parts 21 to 23 as programs.
In
Next is described the rule group database 31 with reference to
The rule group database 31 stores therein, in association with a rule group ID stored in a rule group ID column 111; an applied flag in an applied flag column 112; and a rule group in a rule group column 113.
A rule group ID in the rule group ID column 111 is an identifier for uniquely identifying a rule group. The rule group used herein is a group to which a rule belongs.
A rule used herein is a search key used when a critical passage is extracted from the RFP 1 (see
An applied flag in the applied flag column 112 is information on whether or not a rule group to which a search key used when a critical passage is extracted from the RFP 1 is selected by a user. The applied flag herein is either “1” indicating that the rule group is selected by the user or “0” indicating that the rule group is not selected by the user.
A rule group shown in the rule group column 113 is a name of the rule group.
Four examples of the rule group are shown herein, that is, a “phrase specifying search”, a “phrase-phrase specifying search”, a “phrase-numerical value specifying search”, and a “phrase with numerical value specifying search”. However, any other rule group may be present.
Next is described a phrase specifying search rule database 32 with reference to
The phrase specifying search rule database 32 stores therein, in association with a rule ID stored in a rule ID column 121: an applied flag in an applied flag column 122; a keyword in a keyword column 123; a synonym in a synonym column 124; and a relevant word in a relevant word column 125.
A rule ID in the rule ID column 121 is an identifier for uniquely identifying a rule group. The rule group used herein is a group to which a rule belongs. Respective rules correspond to respective records (rows) in the phrase specifying search rule database 32.
An applied flag in the applied flag column 122 is information on whether or not a rule as a search key used when a critical passage is extracted from the RFP 1 is selected by a user. The applied flag herein is either “1” indicating that the rule is selected by the user or “0” indicating that the rule is not selected by the user.
A keyword in the keyword column 123 is used as a search key.
A synonym in the synonym column 124 is used as a search key and has a meaning similar to a corresponding keyword.
A relevant word in the relevant word column 125 is used as a search key and has a meaning relevant to a corresponding keyword.
The synonym column 124 and the relevant word column 125 may or may not be blank.
In extracting a critical passage, a keyword, a synonym, and a relevant word stored in a record of the phrase specifying search rule database 32 are always combined and are used as one search key.
For example, a record on the second row of the phrase specifying search rule database 32 has the keyword of “special test”, the synonym of “performance test”, and the relevant word of “complete test”. This means that a critical passage is searched from the RFP 1 using a search condition of ““special test” or “performance test” or “complete test””.
A plurality of rules may be used as a search key. For example, the applied flag column 122 of
Next is described a phrase-phrase specifying search rule database 33 with reference to
The phrase-phrase specifying search rule database 33 stores therein, in association with a rule ID stored in a rule ID column 131: an applied flag in an applied flag column 132; a phrase 1 in a phrase 1 column 133; a phrase 2 in a phrase 2 column 134; and a distance in a distance column 135.
The rule ID in the rule ID column 131 is the same as that of
However, as described above, the rule ID used herein uniquely identifies a rule only in the phrase-phrase specifying search rule database 33.
The applied flag in the applied flag column 132 is the same as that of
The phrase 1 in the phrase 1 column 133 is used as a search key.
The phrase 2 in the phrase 2 column 134 is also used as a search key.
The distance in the distance column 135 is a distance (in units of “words”) between the phrase 1 and the phrase 2.
In extracting a critical passage, a phrase 1, a phrase 2, and a distance stored in a record of the phrase-phrase specifying search rule database 33 are always combined and are used as one search key.
For example, a record on the first row of the phrase-phrase specifying search rule database 33 has the phrase 1 of “material”, the phrase 2 of “piping”, and the distance of “10”. This means that a critical passage is searched from the RFP 1 using a search condition of [“material” and the “piping” are present at the distance within “10” words].
A plurality of rules may be used as a search key. For example, the applied flag column 132 of
The aforementioned describes a case where there are two phrases. However, a configuration is possible in which there are three or more phrases. In that case, the distance is defined as a distance between, for example, the initial phrase and the last (third) phrase.
Next is described a phrase-numerical value specifying search rule database 34 with reference to
The phrase-numerical value specifying search rule database 34 stores therein, in association with a rule ID stored in a rule ID column 141: an applied flag in an applied flag column 142; and a phrase in a phrase column 143; a numerical value in a numerical value column 144; a unit in a unit column 145; a condition in a condition column 146; and a distance in a distance column 147.
The rule ID in the rule ID column 141 is the same as that of
However, as described above, the rule ID used herein uniquely identifies a rule only in the phrase-numerical value specifying search rule database 34.
The applied flag in the applied flag column 142 is the same as that of
The phrase in the phrase column 143 is used as a search key, such as “start current”, and is described together with a numerical value (to be described next).
The numerical value in the numerical value column 144 is used as a search key and is described together with a phrase such as “start current”.
The unit in the unit column 145 is a unit of a corresponding numerical value. If the numerical value is simply the number of corresponding phrases, the unit column 145 may be blank.
The condition in the condition column 146 is an applied condition of a corresponding numerical value. For example, The symbol “≧” represents “equal to or more than”; “>”, “more than”; “≦”, “equal to or less than”; “<”, “less than”; “=”, “equal to”; and “< >”, “not equal to”.
The distance in the distance column 147 is a distance (in units of “words”) between a phrase and a numerical value.
In extracting a critical passage, a phrase, a numerical value, a unit a condition, and a distance stored in one record of the phrase-numerical value specifying search rule database 34 are always combined and are used as a single search key.
For example, a record on the third row of the phrase-numerical value specifying search rule database 34 has the phrase of “start current”, the numerical value of “400”, the unit of “A”, the condition of “≦”, and the distance of “17”. This means that a critical passage is searched from the RFP 1 using a search condition of [“start current” and “400 A” are present at a distance within “17” words].
A plurality of phrases and numerical values can be used as a single search key as described above.
<Phrase with Numerical Value Specifying Search Rule Database>
Next is described a phrase with numerical value specifying search rule database 35 with reference to
The phrase with numerical value specifying search rule database 35 stores therein, in association with a rule ID stored in a rule ID column 151: an applied flag in an applied flag column 152; a phrase in a phrase column 153; a numerical value in a numerical value column 154; and a condition in a condition column 155.
The rule ID in the rule ID column 151 is the same as that of
However, as described above, the rule ID used herein uniquely identifies a rule only in the phrase with numerical value specifying search rule database 35.
The applied flag in the applied flag column 152 is the same as that of
The phrase such as “AI” in the phrase column 153 is used as a search key and is described together with a certain numerical value.
The numerical value in the numerical value column 154 is used as a search key and is described together with a phrase such as the “AI”.
The condition in the condition column 155 is an applied condition of a corresponding numerical value. Meanings of “≧” or the like are as described above.
In extracting a critical passage, a phrase, a numerical value, and a condition stored in one record of the phrase with numerical value specifying search rule database 35 are always combined and are used as a single search key.
For example, a record on the first row of the phrase with numerical value specifying search rule database 35 has the phrase of “AI”, the numerical value of “20”, and the condition of “≧”. This means that a critical passage is searched from the RFP 1 with a search condition of [“20” or more numerical values are present immediately after “AI”].
A plurality of rules can be used as a single search key as described above.
The rule databases 32 to 35 may be collectively referred to as “third corresponding information”.
Next is described rule-knowhow corresponding information 36 with reference to
The rule-knowhow corresponding information 36 stores therein, in association with a rule group ID stored in a rule group ID column 161: a rule ID in a rule ID column 162; and a knowhow ID in a knowhow ID column 163.
The rule group ID in the rule group ID column 161 is the same as that of
The rule ID in the rule ID column 162 is the same as those of
The knowhow ID in the knowhow ID column 163 is an identifier which uniquely identifies a knowhow (to be described in detail hereinafter).
Next is described a knowhow database 37 with reference to
The knowhow database 37 stores therein, in association with a knowhow ID stored in a knowhow ID column 171, a knowhow in a knowhow column 172.
The knowhow ID in the knowhow ID column 171 is the same as that of
The knowhow in the knowhow column 172 is information which is useful for a user when the user recognizes a critical passage obtained from the RFP 1 as a search result. The knowhow does not assume to be outputted to the response document 2, unlike the response described above of the response document 2.
Note that the rule-knowhow corresponding information 36 and the knowhow database 37 can be combined into a single database. In this case, the rule-knowhow corresponding information 36 and the knowhow database 37 may be collectively referred to as “first corresponding information”.
Next is described a rule-template corresponding information 38 with reference to
The rule-template corresponding information 38 stores therein, in association with a rule group ID stored in a rule group ID column 181: a rule ID in a rule ID column 182; and a template ID in a template ID column 183.
The rule group ID in the rule group ID column 181 is the same as that of
The rule ID in the rule ID column 182 is the same as those of
The template ID in the template ID column 183 is an identifier which uniquely identifies a template (to be described in detail hereinafter).
Next is described a template database 39 with reference to
The template database 39 stores therein, in association with a template ID stored in a template ID column 191, a template in a template column 192.
The template ID in the template ID column 191 is the same as that of
The template in the template column 192 is a template for a response described in the response document 2.
Note that the rule-template corresponding information 38 and the template database 39 can be combined into a single database. In this case, the rule-template corresponding information 38 and the template database 39 may be collectively referred to as “second corresponding information”. The template may also be referred to as a “response example”.
<Relationship between Rule, Knowhow, and Template>
A combination of a rule group ID and a rule ID corresponds to a rule (which is a search key) in a one-to-one relationship. A combination of a rule group ID and a rule ID corresponds to a knowhow in a one-to-n relationship (n=1, 2, 3, . . . ). The combination of a rule group ID and a rule ID corresponds to a template in a one-to-m relationship (m=1, 2, 3, . . . ). That is, one or more knowhows and templates may or may not correspond to a critical passage searched by a single rule. To simplify description, however, a case in which n=m=1 is explained below.
For example, below is described a case in which a search is performed using a search key of [“SS” or “stainless steel”] which is a rule in the first row of the phrase specifying search rule database 32 of
Thus, if a user selects the rule of [“SS” or “stainless steel”] as a search key, the document preparation support apparatus 3 can display the knowhow of “SS is not easily available and expensive.” and the template of “SS is not necessary.” as a search result, in association with the [“SS” or “stainless steel”].
Next is described a buffer data 40 with reference to
The buffer data 40 stores therein, in association with a rule group ID stored in a rule group ID column 201: a rule ID in a rule ID column 202; a clause title in a clause title column 203; a critical passage in a critical passage column 204; a response in a response column 205; a knowhow in a knowhow column 206; and an edit status in an edit status column 207.
The rule group ID in the rule group ID column 201 is the same as that of
The rule ID in the rule ID column 202 is the same as those of
The clause title in the clause title column 203 is a clause title of the RFP 1.
The critical passage in the critical passage column 204 is a passage (a word, a numerical value, or a symbol, or a combination thereof) obtained as a search result if a search in the RFP 1 is performed using a rule as a search key. A user may specify a critical passage regardless of a search result (to be described in detail hereinafter). A critical passage may be stored with a word before and after the passage as a search result so as to help a user easily understand a context of the passage.
A response in the response column 205 is a response of the response document 2. The response may be prepared by editing a template. A template may be a response as it is without being edited. A response may be newly prepared not based on an existing template (to be described in detail hereinafter).
A knowhow in the knowhow column 206 is, as described above, the information which is useful for a user when the user recognizes a critical passage obtained from the RFP 1 as a search result. A knowhow in the buffer data 40 may be prepared by editing a knowhow in the knowhow database 37 or may be newly prepared not based on an existing knowhow (to be described in detail hereinafter).
The edit status in the edit status column 207 is information indicating an edit status of a record. The edit status is represented by any one of “edited”, “not edited”, “unnecessary”, and “added”.
The “edited” represents that a response and/or knowhow of a record is modified from when it was stored in the template database 39 and/or the knowhow database 37, by an edit of a user.
The “not edited” represents that a response and/or knowhow of a record is the same as when it was stored in the template database 39 and/or the knowhow database 37 without any edit of a user.
The “unnecessary” represents that a response and/or knowhow of a record is determined to be unnecessary by a user.
The “added” represents that a response and/or knowhow of a record is newly added by a user (that is, a record corresponding to the response and/or knowhow does not exist in the template database 39 and/or the knowhow database 37).
Next is described the output format 41 with reference to
The output format 41 stores therein, in association with a clause title stored in a section column 211: a critical passage in a requirement column 212; a response in a comment column 213.
The clause title in the section column 211 is the same as that of
The critical passage in the requirement column 212 is the same as that of
The response in the comment column 213 is the same as that of
Below are described processings and display windows displayed to a user via the output device 14 as steps of the processings advance.
The processings include: a critical passage extraction processing; a response document edit/preparation processing; and a knowledge edit/preparation processing, which are performed in this order.
The critical passage extraction processing is a processing in which the critical passage extract part 21 searches the RFP 1 using a rule as a search key and extracts a critical passage.
The response document edit/preparation processing is a processing in which the response document edit/preparation part 22 presents a template and a knowhow associated with the rule to a user and outputs the response document 2.
The knowledge edit/preparation processing is a processing in which the knowledge edit/preparation part 23 stores a knowhow and a template which are prepared by newly creating or by editing existing ones by a user.
Below are described three cases a) to c) of the response document edit/preparation processing in which: a) a user's selection of any of critical passages as search results is received; b) a user's selection of a passage to be newly taken as a critical passage from the RFP 1 is received; and c) a user's selection of neither a) nor b) is received.
After the response document edit/preparation processing is performed, at least one of a) to c) is selectively performed or two of a) to c) are successively performed.
Next is described a main window 51 with reference to
In
The critical passage view column 228 displays critical passages 232 to 234 searched using a rule, and clause titles 230, 231 of which clauses contain the critical passages. If there are a plurality of critical passages in one clause, a plurality of critical passages are displayed in association with the one clause title. The critical passages 232 to 234 are highlighted with an underline, a double underline, a boxed frame, or the like. Actually, the critical passages 232 to 234 are results searched using the rule as a search key. The critical passages 232 to 234 are highlighted in different ways because, in this case, rules used as search keys are different.
The RFP column 229 displays the RFP 1. The critical passages are highlighted also in the RFP column 229.
Also in
Next is described a rule group selection window 52 with reference to
A rule group selection window 52 appears if the rule edit button 224 of the main window 51 of
A user selects one or more check boxes 241 to 244 of one or more corresponding rule groups which the user wants to use. If the OK button 255 is pressed down, the selection becomes valid. If the cancel button 256 is then pressed down, the selection is cleared. A configuration is possible in which a result of a previous selection is stored, and, if the cancel button 256 is pressed down, the previous selection result becomes valid.
Note that the rule group select buttons 251 to 254 correspond to the respective rule databases 32 to 35 in a one-to-one relationship.
Next are described a rule edit window 53 and a rule edit subwindow 54 with reference to
Configurations of the rule edit window 53 and the rule edit subwindow 54 are almost similar to each other according to a selected rule group but are different in details. Thus, the terms of a rule edit window or subwindow are commonly used for all rule groups.
The rule edit window 53 of
The rule edit window 53 includes: a list 261; the add button 266; the edit button 267; a delete button 268; an OK button 269; and a cancel button 270.
The list 261 is similar to the phrase specifying search rule database 32 (
If the user places a checkmark in a check box of the rule ID column 262 in the list 261, a corresponding record becomes valid as a search key.
Then, if the user pressed down the add button 266, the rule edit subwindow 54 of
The user can enter a keyword, a synonym, and a relevant word in the keyword column 272, the synonym column 273, and the relevant word column 274, respectively, shown on the rule edit subwindow 54.
Upon a press down of the OK button 276a on the rule edit subwindow 54 by the user, the entered data is added to the list 261 as a new record. If the user presses down the cancel button 276b on the rule edit subwindow 54, the entered data is cleared.
Alternatively, if the user specifies a record in the list 261 (for example, by pointing a cursor to any part of the record) and presses down the edit button 267, the rule edit subwindow 54 of
The user can edit the keyword, the synonym, and the relevant word displayed on the rule edit subwindow 54.
Upon a press down of the OK button 275 on the rule edit subwindow 54 by the user, the edited data is overwritten on the specified record in the list 261. If the user presses down the cancel button 276b on the rule edit subwindow 54, the edited data is cleared.
Further alternatively, if the user specifies a record in the list 261 and presses down the delete button 268, the specified record is deleted from the list 261.
Finally, after the above described addition, edit, or deletion of the record is completed, if the user presses down the OK button 269 on the rule edit window 53, all records in the list 261 are overwritten and stored in the phrase specifying search rule database 32. If the cancel button 270 on the rule edit window 53 is pressed down, the edited data is cleared.
The rule edit window 53 of
The rule edit subwindow 54 of
As described above, according to a press-down of the rule group select buttons 251 to 254 on the rule group selection window 52, respective rule edit windows 53 and rule edit subwindows 54 of which configurations are somewhat different one another appear. However, descriptions of the windows 53 and the subwindow 54 of the other rule groups are omitted herefrom. A knowhow template button 275 on the rule edit subwindow 54 is to be described later.
Next is described a knowhow template edit window 55 with reference to
The knowhow template edit window 55 is used for editing a knowhow and a template. The knowhow template edit window 55 appears upon a press down of the knowhow template button 275 on the rule edit subwindow 54 (
A rule group ID column 278 shows a rule group ID of a rule group displayed on the rule edit window 53 at that time. A rule ID column 279 shows a rule ID displayed on the rule edit subwindow 53 at that time or “a maximum value of the rule ID+1”.
A template column 280 shows a template (
A knowhow column 281 shows a knowhow (
However, if the add button 266 on the rule edit window 53 is pressed down, and then, the knowhow template button 275 on the rule edit subwindow 54 is pressed down, the template column 280 and the knowhow column 281 are blank. This is because no corresponding knowhow and template exists yet. The user can herein enter a new template and knowhow in the template column 280 and the knowhow column 281, respectively.
Upon a press down of an OK button 282, the inputted template is stored in the template database 39 (
An input or an edit of either the template or the knowhow may be omitted.
Next is described a response document edit window 56 with reference to
A clause title column 284 shows a clause title of a clause which contains the selected critical passage. A critical passage column 285 shows the selected critical passage.
A knowhow column 286 shows a knowhow having a knowhow ID which is associated with a combination of a rule group ID and a rule ID for identifying a rule as a search key when the critical passage is extracted.
A response column 287 shows a template having a template ID which is associated with a combination of a rule group ID and a rule ID for identifying a rule as a search key when the critical passage is extracted.
Referring to the knowhow column 286 of
Similarly, referring to the response column 287, an underlined portion is added to a template which has been previously stored in the template database 39. The underlined portion is a data entered in the response column 287 by the user.
Upon a press down of a “to buffer data” button 288, information on the response document edit window 56 is stored as a record in the buffer data 40 (
Upon a press down of an OK button 289a, the buffer data 40 is stored in the auxiliary storage device 16. Upon a press down of a cancel button 289b, the buffer data 40 returns to its original state without reflecting the edit and is stored in the auxiliary storage device 16.
Next is described a new response input window 57 with reference to
When the new response input window 57 appears, a critical passage column 294 (
The user selects one of the rule groups in the rule group column 290 and presses down an add rule button 291, thus appearing the rule edit window 53.
After that, as described above, a new rule is added.
The rule ID column 292 of
The user inputs a knowhow in the knowhow column 295 and a response in the response column 296.
Upon a press down of a “to buffer data” button 297, information on the new response input window 57 is stored as a record in the buffer data 40 (
Upon a press down of an OK button 298, the buffer data 40 is stored in the auxiliary storage device 16. Upon a press down of a cancel button 299, the buffer data 40 returns to its original state without reflecting a result of the input and is stored in the auxiliary storage device 16.
Next is described a response list window 58 with reference to
The response list window 58 is used when the user looks at a list of a template and a knowhow associated with a critical passage, determines whether or not a response to the critical passage is necessary, and edits the response and the knowhow if necessary. The response list window 58 appears if the response document comment preparation button 225 on the main window 51 (
The response list window 58 is displayed based on part of the buffer data 40. A section column 301, a requirement column 302, a comment column 303, and a knowhow column 304 of the response list window 58 correspond to the clause title column 203, the critical passage column 204, the response column 205, and the knowhow column 206 of the buffer data 40, respectively. An edit column 300 includes an edit button 305 and a delete button 306 for each record.
When the response list window 58 appears, all of the columns 301 to 304 have already been filled.
Upon a press down of the edit button 305, the response document edit window 56 (
If the delete button 306 is pressed down, a corresponding record is deleted from the response list window 58. Another configuration is possible in which, upon a press down of the delete button 306, the edit column 300 of the corresponding record displays “Already Deleted”, and, upon a press down of a restore button (not shown), the “Already Deleted” record is restored.
If an end button 307 is pressed down, the response list window 58 is closed.
Next is described the critical passage extraction processing with reference to
Before starting steps of the processing, it is assumed that the main window 51 (
In step S401, the critical passage extract part 21 loads the RFP 1 in response to a press down of the RFP read button 221.
More specifically, the critical passage extract part 21 loads the RFP 1 via the input device 12 if the RFP 1 is in text format. If the RFP 1 is not in text format, for example, if it is printed on a paper medium, the RFP 1 is loaded via the read device 13 such as a scanner. The read device 13 is herein assumed to convert an image data into a text data. One or more RFPs 1 may be loaded. However, description herein is made assuming that one RFP 1 is loaded.
In step S402, the critical passage extract part 21 obtains a clause title in response to a press down of the clause extract button 222.
More specifically, the critical passage extract part 21 obtains all clause titles 311 (
In step S403, the critical passage extract part 21 determines a rule which is valid.
More specifically, firstly, the critical passage extract part 21 displays the rule group selection window 52 (
The user performs an addition, an edit, or a deletion of a record as necessary while looking at the list 261; places a checkmark in the rule ID column 262 of a record (a valid record) indicating a rule (a valid rule) which the user wants to make valid as a search key; and presses down the OK button 269.
Secondly, the critical passage extract part 21 sets, at “1”, an applied flag of a record in the rule group database 31 (
Thirdly, the critical passage extract part 21 stores the record shown in the list 261 as a record in the rule databases 32 to 35 (
In step S404, the critical passage extract part 21 extracts a critical passage in response to a press down of the critical passage search button 223.
More specifically, firstly, the critical passage extract part 21 obtains any one of valid records stored in step S403 and not yet subjected to the processing in all of the rule databases 32 to 35 and takes the obtained record as a search key. However, if the applied flag of the rule group database 31 for the rule databases 32 to 35 is “0”, the corresponding rule databases 32 to 35 are excluded from the processing. Secondly, the critical passage extract part 21 searches the RFP 1 loaded in step S401 using the search key and obtains a corresponding passage. Note that the corresponding passage may not exist.
In step S405, the critical passage extract part 21 determines whether or not a corresponding passage exists.
More specifically, if the critical passage extract part 21 has been able to obtain a corresponding passage in step S404 (if “Yes” in step S405), the processing advances to step S406. And, if not (if “No” in step S405), the processing returns to step S404.
In step S406, the critical passage extract part 21 obtains terms before and after the corresponding passage obtained in step S404.
More specifically, a range to be obtained as the terms before and after the passage can be previously set, for example, “three words before and after the corresponding passage”, “the other words in a sentence containing the corresponding passage”, and “the other words in a sentence containing the corresponding passage and one sentence before and after the sentence”.
In step S407, the critical passage extract part 21 extracts a clause title.
More specifically, the critical passage extract part 21 extracts a clause title of a clause containing the corresponding passage in step S404 from among the clause titles obtained in step S402.
In step S408, the critical passage extract part 21 generates an edit status of “not edited”.
In step S409, the critical passage extract part 21 creates the buffer data 40.
More specifically, firstly, the critical passage extract part 21 creates a new record of the buffer data 40.
Secondly, the critical passage extract part 21 stores a rule group ID and a rule ID of the valid record obtained in step S404, in the rule group ID column 201 and the rule ID column 202, respectively; stores the clause title extracted in step S407, in the clause title column 203; stores the corresponding passage in step S404 together with the terms before and after the corresponding passage obtained in step S406, in the critical passage column 204; and stores the “not edited” created in step S408, in the edit status column 207.
Note that the response column 205 and the knowhow column 206 of the record in the buffer data 40 remain blank.
In step S410, the critical passage extract part 21 determines whether or not all rules have been obtained.
More specifically, the critical passage extract part 21 determines that there is no valid record not yet subjected to the processing in the records stored in step S403 in all of the rule databases 32 to 35 (if “Yes” in step S410), the processing advances to step S411. And, if not (if “No” in step S410), the processing returns to step S404.
In step S411, the critical passage extract part 21 displays a critical passage.
More specifically, firstly, the critical passage extract part 21 displays the entire RFP 1 loaded in step S401, in the RFP column 229 on the main window 51 (
Secondly, the critical passage extract part 21 displays the corresponding passage in step S404 together with the terms before and after the corresponding passage obtained in step S406, in the critical passage view column 228 on the main window 51; and also displays the clause title extracted in step S407. At this time, the displayed corresponding passage in step S404 is highlighted.
The critical passage extraction processing then terminates.
Next is described a response document edit/preparation processing A with reference to
In step S421, the response document edit/preparation part 22 receives a critical passage as a search result.
More specifically, the response document edit/preparation part 22 receives a user's selection of a critical passage (a highlighted portion) displayed in the critical passage view column 228 (
In step S422, the response document edit/preparation part 22 determines whether or not the response document comment preparation button 225 is pressed down.
More specifically, the response document edit/preparation part 22 receives a press down of the response document comment preparation button 225 by the user (if “Yes” in step S422), the processing advances to step S423. And, if not (if “No” in step S422), the processing returns to step S421.
In step S423, the response document edit/preparation part 22 displays a response document edit window 56 (
More specifically, firstly, the response document edit/preparation part 22 displays the response document edit window 56 whose columns are all blank.
Secondly, the response document edit/preparation part 22 searches the rule-knowhow corresponding information 36 using a rule group ID and a rule ID for identifying a valid rule when the critical passage selected in step S421 is extracted, as search keys; obtains a knowhow ID of a corresponding record; searches the knowhow database 37 using the knowhow ID as a search key; obtains a knowhow of a corresponding record; and displays the obtained knowhow in the knowhow column 286.
Thirdly, the response document edit/preparation part 22 searches the rule-template corresponding information 38 using the rule group ID and the rule ID for identifying a valid rule when the critical passage selected in step S421 is extracted, as a search key; obtains a template ID of a corresponding record; searches the template database 39 using the template ID as a search key; obtains a template of the corresponding record; and displays the obtained template in the response column 287.
Fourthly, the response document edit/preparation part 22 displays the selected critical passage together with the terms before and after the selected critical passage, in the critical passage column 285; and displays a clause title of a clause containing the selected critical passage, in the clause title column 284.
Herein, the user can make an edit in the knowhow column 286 and the response column 287.
In step S424, the response document edit/preparation part 22 branches steps according to which button is pressed down.
More specifically, if “To buffer data” button 287 is pressed down (if “to buffer data” in step S424), the response document edit/preparation part 22 branches the processing to step S425. If the cancel button 289 is pressed down (if “Cancel” in step S424), the response document edit/preparation part 22 branches the processing to step S428. If the OK button 288 is pressed down (if “OK” in step S424), the response document edit/preparation part 22 branches the processing to step S429.
In step S425, the response document edit/preparation part 22 determines whether or not any edit has been made.
More specifically, if the user has edited at least one of the knowhow column 286 and the response column 287 (if “Yes” in step S425), the response document edit/preparation part 22 branches the processing to step S426. And, if not (if “No” in step S425), the processing returns to step S424.
In step S426, the response document edit/preparation part 22 generates the edit status of “edited”.
In step S427, the response document edit/preparation part 22 updates the buffer data 40 to a state after edited.
More specifically, the response document edit/preparation part 22 stores a knowhow and a response both after edited by the user, in the knowhow column 206 and in the response column 205, respectively, of the record in the buffer data 40 created in step S409 (Note that the response column 205 and the knowhow column 206 remain blank).
In step S428, the response document edit/preparation part 22 restores the buffer data 40 to a state before edited by the user and stores the restored buffer data 40 in the auxiliary storage device 16.
In step S429, the response document edit/preparation part 22 stores the buffer data 40 in the auxiliary storage device 16.
A series of step S421 to step S428 (or 5429) are repeated each time the user selects a new critical passage.
In step S430, the response document edit/preparation part 22 outputs the response document 2 in response to a press down of the response document output button 226 (
More specifically, the response document edit/preparation part 22 outputs the clause title column 203, the critical passage column 204, and the response column 205 of the buffer data 40 as the output format 41. At this time, the clause title, the critical passage (including terms before and after the passage), and the response are once stored in the section column 211, the requirement column 212, and the comment column 213 of the output format 41, respectively, and are then outputted.
Step S430 can be omitted according to an instruction by the user. This is because, if response document edit/preparation processings B and C to be described later are performed, it is convenient to output the response document 2 not at this time but after the processings B and C are performed (ditto with steps S451 and S469 to be described later).
The response document edit/preparation processing A then terminates.
Next is described the response document edit/preparation processing B with reference to
In step S441, the response document edit/preparation part 22 receives a new critical passage.
More specifically, the response document edit/preparation part 22 receives a user's selection of a portion of the RFP 1 displayed in the RFP column 229 (
In step S442, the response document edit/preparation part 22 determines whether or not the response document comment preparation button 225 is pressed down.
More specifically, if the response document edit/preparation part 22 determines that the user presses down the response document comment preparation button 225 (if “Yes” in step S442), the processing advances to step S443. And, if not (if “No” in step S442), the processing returns to step S441.
In step S443, the response document edit/preparation part 22 displays a new response input window 57 (
The response document edit/preparation part 22 displays the critical passage (that is, the passage 235) selected in step S441, in the critical passage column 294 and then displays a clause title of a clause containing the critical passage, in the clause title column 293. For example, in
The user then selects a rule group in the rule group column 290 and presses down the add rule button 291, which makes the rule edit window 53 and the rule edit subwindow 54 (
In step S444, the response document edit/preparation part 22 branches steps of the processing according to which button is pressed down.
More specifically, if the response document edit/preparation part 22 determines that the “to buffer data” button 297 is pressed down (if “To buffer data” in step S444), the processing advances to step S445; if the cancel button 299 (if “Cancel” in step S444), to step S449; and, if the OK button 298 (if “OK” in step S444), to step S450.
In step S445, the response document edit/preparation part 22 determines whether or not any input has been made.
More specifically, if the response document edit/preparation part 22 determines that the user has made an input at least one of the knowhow column 295 and the response column 296 (if “Yes” in step S445), the processing advances to step S446. And, if not (if “No” in step S445), the processing returns to step S444.
In step S446, the response document edit/preparation part 22 generates an edit status of “added”.
In step S447, the response document edit/preparation part 22 updates the buffer data 40 (
More specifically, firstly, the response document edit/preparation part 22 creates a new record in the buffer data 40.
Secondly, the response document edit/preparation part 22 stores the knowhow and the template inputted by the user in the knowhow column 295 and the response column 296 on the new response input window 57 (
Thirdly, the response document edit/preparation part 22 stores a rule ID of the rule group selected by the user in the rule group column 290, in the rule group ID column 201 and also stores a “maximum value of the rule ID+1” in the rule ID column 202.
Fourthly, the response document edit/preparation part 22 stores the critical passage received in step S441 together with the terms before and after the passage, in the critical passage column 204; a clause of a clause title containing the critical passage, in the clause title column 203; and the “added” in the edit status column 207.
In step S448, the response document edit/preparation part 22 updates the rule databases 32 to 35.
For example, assume that the user selects the “phrase specifying search” in the rule group column 290 on the new response input window 57 of
In step S449, the response document edit/preparation part 22 restores the buffer data 40 to a state before the input has been made by the user and stores the restored data in the auxiliary storage device 16.
In step S450, the response document edit/preparation part 22 stores the buffer data 40 in the auxiliary storage device 16.
A series of step S441 to step S449 (or 5450) are repeated each time the user selects a new critical passage.
In step S451, the response document edit/preparation part 22 outputs the response document 2 in response to a press down of the response document output button 226 (
Specific contents of this step are as described in step S430.
The response document edit/preparation processing B then terminates.
Next is described the response document edit/preparation processing C with reference to
In step S461, the response document edit/preparation part 22 receives a press down of the response document comment preparation button 225.
It is assumed herein that the user presses down the response document comment preparation button 225 without selecting any critical passage in the critical passage view column 228 on the main window 51 (
In step S462, the response document edit/preparation part 22 obtains a knowhow and a template.
More specifically, firstly, the response document edit/preparation part 22 searches the rule-knowhow corresponding information 36 using a combination of a rule group ID and a rule ID for identifying a rule when all critical passages displayed in the critical passage view column 228 on the main window 51 are extracted, as a search key; and obtains a knowhow ID of a corresponding record. Then the response document edit/preparation part 22 searches the knowhow database 37 using the obtained knowhow ID as a search key and obtains a knowhow of a corresponding record.
Secondly, the response document edit/preparation part 22 searches the rule-template corresponding information 38 using the combination of the rule group ID and the rule ID as a search key and obtains a template ID of a corresponding record. Then the response document edit/preparation part 22 searches the template database 39 using the obtained template ID as a search key and obtains a template of a corresponding record.
In step S463, the response document edit/preparation part 22 displays the response list window 58 (
More specifically, firstly, the response document edit/preparation part 22 displays the response list window 58 of which respective columns are blank.
Secondly, the response document edit/preparation part 22 displays all critical passages (including their before and after terms and highlights) shown in the critical passage view column 228 on the main window 51, in the requirement column 302 of each record and also displays a clause of a clause title containing the corresponding critical passage, in the section column 301.
Thirdly, the response document edit/preparation part 22 displays the knowhow and the template obtained in step S462, in the knowhow column 304 and the comment column 303, respectively. At this time, the response document edit/preparation part 22 displays a critical passage, a clause title, a knowhow, and a template each corresponding to the same combination of an identical rule group ID and an identical rule ID, in an identical record.
Fourthly, the response document edit/preparation part 22 displays the edit button 305 and the delete button 306 in each record.
In step S464, the response document edit/preparation part 22 branches steps of the processing according to which button is pressed down.
More specifically, if the response document edit/preparation part 22 determines that the edit button 305 is pressed down (if “Edit” in step S464), the processing advances to step S465. If the delete button 306 (if “Delete” in step S464), to step S467. And, if neither the edit button 305 nor the delete button 306 is pressed down (if “None” in step S464), to step S468.
In step S465, the response document edit/preparation part 22 displays the response document edit window 56 (
In step S466, the response document edit/preparation part 22 receives an edit.
More specifically, the response document edit/preparation part 22 performs steps similar to steps S424 to 5429 described in the response document edit/preparation processing A.
In step S467, the response document edit/preparation part 22 generates an edit status of “unnecessary”.
More specifically, the response document edit/preparation part 22 searches the buffer record 40 (
In step S468, the response document edit/preparation part 22 determines whether or not a press down of the end button 307 (
More specifically, if the response document edit/preparation part 22 has received a press down of the end button 307 on the response list window 58 (if “Yes” in step S468), the processing advances to step S469. And, if not (if “No” in step S468), the processing returns to step S464.
In step S469, the response document edit/preparation part 22 outputs the response document 2 in response to a press down of the response document output button 226 (
Specific contents of this step are as described in step S430.
The response document edit/preparation processing C then terminates.
Next is described a knowledge edit/preparation processing with reference to
In step S481, the knowledge edit/preparation part 23 loads a record from the buffer data 40.
More specifically, the knowledge edit/preparation part 23 loads any one record not yet subjected to the processing in the buffer data 40.
In step S482, the knowledge edit/preparation part 23 determines that an edit status of the record is any one of “edited”, “added”, or “not edited”.
More specifically, the knowledge edit/preparation part 23 determines that the edit status of the record loaded in step S481 is any one of “edited”, “added”, or “not edited” (if “Yes” in step S482), the processing advances to step S483. And, if not (if “No” in step S482), the processing returns to step S481.
In step S483, the knowledge edit/preparation part 23 updates the template database 39 and the knowhow database 37.
More specifically, firstly, the knowledge edit/preparation part 23 obtains a rule group ID, a rule ID, a response, and a knowhow of the record loaded in step S481.
Secondly, the knowledge edit/preparation part 23 creates a new record of the rule-knowhow corresponding information 36 (
Thirdly, the knowledge edit/preparation part 23 creates a new record of the rule-template corresponding information 38 (
In step S484, the knowledge edit/preparation part 23 determines whether or not all records in the buffer data 40 are subjected to the processing.
More specifically, if the knowledge edit/preparation part 23 determines that all records in the buffer data 40 are subjected to the processing (if “Yes” in step S484), the knowledge edit/preparation processing terminates. And, if not (if “No” in step S484), the processing returns to step S481.
Next are described a data sheet and a data sheet input window 59 with reference to
The RFP 1 is not necessarily described by sentences but may be described in tabular form. In the latter case, an input may be made in a data sheet of the document preparation support apparatus 3, instead of the RFP 1.
For example, the user looks at the data sheet in the tabular form on the data sheet input window 59 and inputs appropriate information in a requirement column 308. A check items column 307 corresponds to the clause title column 311 (
Referring back to
The embodiment according to the present invention has been explained as aforementioned. However, the embodiment of the present invention is not limited to those explanations, and those skilled in the art ascertain the essential characteristics of the present invention and can make the various modifications and variations to the present invention to adapt it to various usages and conditions without departing from the spirit and scope of the claims.
The present invention can provide a document preparation support apparatus and the like capable of supporting an efficient preparation of a contract document while utilizing information on previous contracts and knowhows and avoiding risks in contracts.
| Number | Date | Country | Kind |
|---|---|---|---|
| 2009-109795 | Apr 2009 | JP | national |
