This application claims the benefit of Japanese Patent Application No. 2007-298992 filed on Nov. 19, 2007, the disclosure of which is incorporated herein by reference.
1. Field of the Invention
The present invention relates to a procedure generation apparatus and a procedure generation method.
2. Description of the Related Art
There has been known a technique of guiding work procedures in a routine work such as a general business process, in which a specific work flow is defined as a premise, and then, various work procedures according to the work flow or management of an examination and approval procedure following results of conducting the work are supported.
In a commercially-available work flow management system, for example, a unit of a work called a “task” or an “activity” in a business process is represented in a form of a block. A plurality of blocks are connected with arrowed lines, which represents an anteroposterior relationship in the process. If a problem resulting from conducting a work occurs in an examination and approval procedure, the process returns to a previous procedure. This can be represented by a loop or a conditional branching.
Japanese Laid-Open Patent Application, Publication No. 2004-126681 (paragraphs 0013 to 0032 and
In a nonroutine work such as designing and development of a product, however, it is not always easy to define a specific work flow which is a premise in the conventional technique. This is because cause and effect relationships between procedures in the nonroutine work are often deeply intertwined or go around in circles. For example, a result of one procedure influences another, whose result then influences yet another which is present prior to the one procedure.
Japanese Laid-Open Patent Application, Publication No. 2004-126681 has an advantageous effect on a reduction in man-hours for modifying a work flow. However, the patent application cited above is used exclusively for a routine business process and can hardly adapt to a change of a start point or of an order of procedures depending on situations, which often occurs in procedures of a nonroutine work.
To solve the problems described above, the present invention has been made in an attempt to provide a procedure generation apparatus and a procedure generation method capable of guiding work procedures and reducing the number of man-hours for creating a work flow or conducting its maintenance, even in nonroutine work procedures in which a start point or an order of procedures changes, such as designing and development of a product.
A procedure generation apparatus according to the present invention has, in a storage unit thereof, a database in which a name of input information and a name of output information are stored, associated with a name of a work. The procedure generation apparatus retrieves one or more candidate work names associated with an input information name from the database, displays the retrieved one or more work names, receives a selection of a work name from among the displayed one or more work names, retrieves one or more candidate output information names associated with the selected work name from the database, displays the retrieved one or more output information names, receives a selection of an output information name from among the displayed output information names, retrieves one or more candidate input information names each having a similar name to the selected output information name, from the database, and displays the retrieved input information name.
Next is described an embodiment of the present invention. The present invention is not, however, limited to the embodiment described below.
<Configuration of Hardware and Others>
A procedure generation apparatus 1 is a commonly-used computer. The procedure generation apparatus 1 includes a central control unit (which may be referred to as a control unit) 11, an input unit 12, an output unit 13, a main storage unit (which may be referred to as a storage unit) 16, an auxiliary storage unit (which may also be referred to as a storage unit) 14, and a network interface 15, all of which are connected to each other via a bus. The procedure generation apparatus 1 is accessible from a terminal unit 3 via a network 2. The terminal unit 3 is also a commonly-used computer. One terminal unit 3 is shown in
The procedure generation apparatus 1 has an input information name/procedure name/output information name definition unit 17, an input information name-querying procedure retrieval unit 18, a procedure name-querying information retrieval unit 19, an output information name-querying similar name input information retrieval unit 20, an input information determination unit 21, and a retrieved result display/select unit 22.
Each of the units 17 to 22 referred to above is a program. To simplify description, it is assumed herein that the units 17 to 22 directly perform their respective functions. Actually, however, it is the central control unit 11 that reads and loads the units 17 to 22 from the auxiliary storage unit 14 into the main storage unit 16, and executes the functions written in the units 17 to 22.
The procedure generation apparatus 1 also has an input information name/procedure name/output information name relational database 23 and a synonym dictionary 24. The input information name/procedure name/output information name relational database 23 is a database in which an input information name and an output information name are stored, associated with a procedure name (to be described hereinafter). The synonym dictionary 24 is a reference database in which a synonym of the output information name is stored (to be described in detail hereinafter).
<Input Information Name/Procedure Name/Output Information Name Relational Database 23>
The input information name/procedure name/output information name relational database 23 (which may also be referred to as a relational database or, simply, a database) stores, associating with a procedure name stored at a procedure name 31 in
The procedure name is composed of a character or characters representing contents of a given procedure and may also be referred to as a work name.
The input information name is composed of a character or characters representing information to be inputted as necessary for conducting the procedure.
The output information name is composed of characters representing information generated and outputted by conducting the procedure.
The number of the input information names associated with one procedure name may be one or more. The number of the output information names associated with the one procedure name may also be one or more. The number of the input information names associated with a given procedure name may be or may not be the same as the number of the output information name associated with the same procedure name. The numbers of a plurality of input information names associated with respective procedure names may be or may not be the same. The number of a plurality of output information names may be or may not be the same as the number of respective procedure names associated with the plurality of output information names.
In
An input (or output) information name associated with a procedure name may by chance coincide with another input (or output) information name associated with another procedure name. For example, in
An output (or input) information name associated with a procedure name may by chance coincide with another output (or input) information name associated with another procedure name. For example, in
The relational database 23 may be divided into two as shown in
<Operation Screen 40>
Rectangular nodes (a node herein is shown as a graphic) designated at reference numerals 43, 44, and 45 are Works W1, W2, and W3, respectively. Works W1, W2, and W3 correspond to the procedure names in
How the work flow 41 is displayed in phases from left to right on the operation screen 40 as shown in
If Work W143 is selected with the pointer 51, the input information name-querying procedure retrieval unit 18 uses the procedure name as a query and retrieves the relational database 23 using Work W1 as a retrieval key. The input information name-querying procedure retrieval unit 18 then acquires an input information name which has the procedure name of Work W1, other than Data A. (It is assumed herein that the input information name-querying procedure retrieval unit 18 also has a function of acquiring a data, serving more than its name indicates.) The retrieved result display/select unit 22 then displays the acquired input information name.
As described above, in this embodiment, nodes can be displayed on the operation screen 40 in an order of the input information name, procedure name, and output information name. In addition, the nodes can be displayed in a reverse order to the above, namely, the output information name, procedure name, and input information name. Moreover, nodes in any number of prescribed rows can be displayed in relation to a node selected by the user. For example, the user selects a node and then selects the number of rows to be displayed at a column rightward or leftward of the selected node.
<Procedures>
Next are described procedures according to this embodiment. The procedures include a procedure of relational database creation and a procedure of work flow creation. The procedure of work flow creation is performed only after the procedure of relational database creation is completed.
<Procedure of Relational Database Creation>
In step S61, the input information name/procedure name/output information name definition unit 17 displays a screen for creating a relational database.
More specifically, the input information name/procedure name/output information name definition unit 17 responds to a click of a relational database creation button (not shown) on the output unit 13, which is performed by a user via the input unit 12 such as a mouse, and then displays the relational database creation screen. It is assumed herein that
In step S62, the input information name/procedure name/output information name definition unit 17 receives a procedure name.
More specifically, the name definition unit 17 receives an input of the procedure name by the user via the input unit 12 such as a keyboard.
In step S63, the input information name/procedure name/output information name definition unit 17 receives one or more input information names.
More specifically, the name definition unit 17 receives an input of the one or more input information names by the user via the input unit 12 such as a keyboard, associating with the procedure name received in step S62.
In step S64, the input information name/procedure name/output information name definition unit 17 receives one or more output information names.
More specifically, the name definition unit 17 receives an input of the one or more output information names by the user via the input unit 12 such as a keyboard, associating with the procedure name received in step S62.
In step S65, the input information name/procedure name/output information name definition unit 17 registers the input information name, procedure name, and output information name.
More specifically, the name definition unit 17 stores the input information name and the output information name inputted in step S63 and S64, respectively, associating the input and output information names with the procedure name, in the relational database 23. This terminates the procedure of relational database creation.
It is to be noted that steps S62 to S64 may be conducted in any order. Further, instead of receiving a manual input by a user according to the aforementioned procedure of relational database creation, the input information name/procedure name/output information name definition unit 17 may receive an input of the relational database 23 previously inputted and stored in a recording medium, via the input unit.
<Procedure of Work Flow Creation>
<Determination of Input Information Name and Others>
The procedure of work flow creation begins with either an input of the input information name or the procedure name which is performed by a user.
An input information name may be inputted directly or may be selected from among the input information names stored in the relational database 23. Further, an input information name may be selected from a plurality of candidate input information names. In the latter case, the number of the candidates is narrowed down using a retrieval key composed of characters or using some specific characters. Herein, the selection of one input information name is referred to as a determination of the input information name. Similarly, one procedure name is determined in the procedure.
A user tends to have a difficulty in newly thinking of the input information name to start the procedure of work flow creation. In this embodiment, however, the procedure can be started off with an easy determination of the input information name. For example, below is a description making use of a difference between a specification requested by a customer and that of an existing product.
It is assumed herein that the customer requests a specification of a product by order, for example, with a horsepower of 100 hp, a weight of 1000 kg, and a noise of 70 dB. A user inputs an item “horsepower”, its requested numerical values, and so on, via the input unit 12.
It is also assumed that a specification of an existing product of the same type as the product by order is known to have the horsepower of 90 hp, the weight of 950 kg, and the noise of 70 dB, and those data are stored in the main and auxiliary storage units 14, 16.
Then, the input information determination unit 21 calculates a rate of deviation of the values for each specified items of the ordered product relative to those of the existing product. The calculation finds that the item “horsepower” has the largest rate of deviation ((100−90)/90=11.1%), which determines the item “horsepower” as the input information name. Alternatively, the item “noise” having the smallest rate of deviation may be determined as the input information name.
In step S71, the retrieved result display/select unit 22 displays the operation screen 40 (see
More specifically, the retrieved result display/select unit 22 displays the operation screen 40 in response to a click of a work flow creation button (not shown) on the output unit 13 by the user via the input unit 12 such as a mouse.
It is to be noted that, after step S71 is completed, the work flow 41 is not yet displayed on the operation screen 40. Four vertical dotted lines in
In step S72, the input information determination unit 21 determines and displays the input information name.
More specifically, the input information determination unit 21 determines the input information name in any of the ways described above.
Then the input information determination unit 21 displays the determined input information name on the operational screen 40 (see a node of Data A 42 in
In step S73, the procedure generation apparatus 1 retrieves and displays the procedure name to the user, and receives a selection of the procedure name by the user.
More specifically, in a first substep of step S73, the input information name-querying procedure retrieval unit 18 retrieves the relational database 23 using the input information name determined in step S72 or the input information name received in step S76 (if “Yes” in step S76) as a retrieval key and acquires all the procedure names retrieved by the retrieval key.
In a second substep, the retrieved result display/select unit 22 displays all the procedure names acquired in the first step on the operational screen 40 (see nodes of Works W1 to W343 to 45 in
In a third substep, the retrieved result display/select unit 22 receives the procedure name selected by the user via the input unit 12 from among the procedure names displayed in the second substep. A selection of the procedure name may be made by operating the input unit 12, for example, by placing the pointer 51 over a desired node and clicking a mouse there (selections hereinafter the same). After the selection, only the selected node may be displayed or highlighted.
In step S74, the procedure generation apparatus 1 retrieves and displays the output information name to the user, and receives a selection of the output information name by the user.
More specifically, in a first substep of step S74, the procedure name-querying procedure retrieval unit 19 retrieves the relational database 23 using the procedure name determined in the third substep of step S73 as a retrieval key and acquires all the output information names retrieved by the retrieval key.
In a second substep, the retrieved result display/select unit 22 displays all the output information names acquired in the first step on the operational screen 40 (see a node of Data C 46 in
In a third substep, the retrieved result display/select unit 22 receives the output information name selected by the user via the input unit 12 from among the output information names displayed in the second substep. After the selection, only the selected node may be displayed or highlighted.
In step S75, the procedure generation apparatus 1 retrieves and displays a name similar to the input information name to the user.
Details of this step will be described later.
<Similar Name>
In steps S72 to S74, the procedure generation apparatus 1 displays a series of nodes (which may also be collectively referred to as a unit) from the input information name through the procedure name to the output information name, to the user. Such a unit allows the user to precisely know the input information name required to conduct a work and the output information name created and outputted after conducting the work.
A user generally requests a further display of the unit until the user finds all desired information in the displayed output information name. One unit and a subsequent unit thereto are desirably linked to each other with an identical information name for an accurate linkage. That is, the output information name of one unit is desirably identical to the input information name of a subsequent unit thereto. However, even if two units are not linked with the identical information name, a pseudo linkage with similar information names is also useful. In some cases, two information names are apparently different but have very similar contents. Or, information on an output information name in one unit may be manually processed, to thereby create certain information on an input information name in a subsequent unit thereto.
In step S75, the procedure generation apparatus 1 thus retrieves and displays a name similar to the input information name so as to enable such a pseudo linkage.
In step S76, the retrieved result display/select unit 22 receives a determination whether a selection of the input information name is accepted or not.
More specifically, if the retrieved result display/select unit 22 receives the selection made by the user from among the input information names displayed in step S75 (if “Yes” in step S76), the procedure returns to step S73. After the selection, only the selected node may be displayed or highlighted. Alternatively, if the retrieved result display/select unit 22 receives a click of a quit button (not shown) made by the user via the input unit 12 (if “No” in step S76), the procedure of work flow creation terminates.
<Procedure Beginning with Determination of Procedure Name>
The aforementioned procedure of work flow creation begins with the determination of the input information name. However, the procedure may begin with a determination of the procedure name as previously stated.
The latter case is similar to the former except two points as follows. First, step S72 is omitted. And second, if “No” in step S73, the input information name-querying procedure retrieval unit 18 determines the procedure name, instead of performing the first to third substeps of step S73. It is assumed herein that the input information name-querying procedure retrieval unit 18 also has a function of determining the procedure name, serving more than its name indicates. Then, the retrieved result display/select unit 22 displays the determined procedure name. Meanwhile, if “Yes” in step S76 and the procedure returns to step S73, there is no change in step S73.
<Retrospective Display of Input Information Name>
At any time after the user selects the procedure name in step S73, the input information name that is associated with the procedure name but is not presently displayed (for example, a node of Data B 50 in
<Display in Order of Frequency so Far Selected>
In steps S73, S74 and S75 in the procedure of work flow creation, the retrieved result display/select unit 22 can display the retrieved procedure name, output information name, and similar input information name in descending order of frequency, that is, how many times each of those names is selected so far. More specifically, each time a selection of those names by the user is received in steps S73, S74 and S76, the numbers of selections by those names are counted and recorded. Thus, if there is, for example, a plurality of the procedure names to be displayed, the procedure names can be displayed in descending order placing a procedure name having the largest number first. This facilitates the user to make a selection.
<Substeps of Step S75 in Procedure of Work Flow Creation>
In step S751, the output information name-querying similar name input information retrieval unit 20 analyzes morpheme of the output information name and retrieves a synonym of the morphologically-analyzed output information name from a synonym dictionary 24.
More specifically, the output information name-querying similar name input information retrieval unit 20 analyzes morpheme of the output information name received in the third substep of step S74. It is assumed herein that the output information name is broken down into a plurality of constituent words.
For example, the output information name “rotating shaft material” is broken into three constituent words, “rotating”, “shaft” and “material”.
The synonym dictionary 24 is then retrieved by each of the constituent words as a retrieval key to obtain a synonym (including an identical word) thereof. Any number of synonyms to be obtained by each retrieval key can be set. For example, if two synonyms by each retrieval key are set to be obtained, “rotating” and “rotary” are obtained by the retrieval key “rotating”; “shaft” and “axis”, by “shaft”; and “material” and “substance”, by “material”.
In step S752, the output information name-querying similar name input information retrieval unit 20 creates a term vector of the synonym.
More specifically, the output information name-querying similar name input information retrieval unit 20 combines the synonyms obtained in step S751. This creates eight (2×2×2) synonyms of the output information name such as “rotating shaft material”, “rotating shaft substance”, “rotating shaft material”, “rotating axis material”, and the like.
Then the output information name-querying similar name input information retrieval unit 20 creates a term vector of each of the created eight synonyms.
In step S753, the output information name-querying similar name input information retrieval unit 20 creates a term vector of the input information name in the relational database 23.
More specifically, the output information name-querying similar name input information retrieval unit 20 analyzes morpheme of all the input information names stored in the relational database 23 and creates term vectors thereof. For example,
In step S754, the output information name-querying similar name input information retrieval unit 20 calculates an inner product of the term vector.
More specifically, the output information name-querying similar name input information retrieval unit 20 calculates an inner product of the term vector created in step S752 and the term vector created in step S753. As a result, 8×11 inner products are obtained.
In step S755, the output information name-querying similar name input information retrieval unit 20 displays the input information names in descending order of inner products.
More specifically, the output information name-querying similar name input information retrieval unit 20 displays, on the operational screen 40, the input information names subjected to the calculation of inner products in step S754 in descending order placing the procedure name having the largest inner product first. The number of the input information names displayed may be set in advance.
Completion of step S755 terminates step S75 in the procedure of work flow creation, and the procedure advances to step S76.
The procedure of relational database creation and the procedure of work flow creation may be performed by a plurality of users in parallel or intermittently, via the input and output units 12, 13 of the procedure generation apparatus 1 and input and output units (not shown) of the terminal unit 3.
The embodiment according to the present invention has been explained as aforementioned. However, the embodiment of the present invention is not limited to the explanation, and those skilled in the art ascertain the essential characteristics of the present invention and can make 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.
Number | Date | Country | Kind |
---|---|---|---|
2007-298992 | Nov 2007 | JP | national |
Number | Name | Date | Kind |
---|---|---|---|
5604910 | Kojima et al. | Feb 1997 | A |
5748973 | Palmer et al. | May 1998 | A |
6065009 | Leymann et al. | May 2000 | A |
6092048 | Nakaoka | Jul 2000 | A |
6523026 | Gillis | Feb 2003 | B1 |
6546364 | Smirnov et al. | Apr 2003 | B1 |
6571230 | Parida | May 2003 | B1 |
6772407 | Leymann et al. | Aug 2004 | B1 |
6799314 | Beniyama et al. | Sep 2004 | B2 |
6826568 | Bernstein et al. | Nov 2004 | B2 |
6853974 | Akifuji et al. | Feb 2005 | B1 |
7184967 | Mital et al. | Feb 2007 | B1 |
7299244 | Hertling et al. | Nov 2007 | B2 |
7533008 | Mangino et al. | May 2009 | B2 |
7809822 | Gotta et al. | Oct 2010 | B2 |
7869984 | Mangino et al. | Jan 2011 | B2 |
7870012 | Katz et al. | Jan 2011 | B2 |
20020032692 | Suzuki et al. | Mar 2002 | A1 |
20020078432 | Charisius et al. | Jun 2002 | A1 |
20020188597 | Kern et al. | Dec 2002 | A1 |
20030120651 | Bernstein et al. | Jun 2003 | A1 |
20030236689 | Casati et al. | Dec 2003 | A1 |
20040010505 | Vishnubhotla | Jan 2004 | A1 |
20040034857 | Mangino et al. | Feb 2004 | A1 |
20040111430 | Hertling et al. | Jun 2004 | A1 |
20040230636 | Masuoka et al. | Nov 2004 | A1 |
20040254768 | Kim et al. | Dec 2004 | A1 |
20060020931 | Clarke | Jan 2006 | A1 |
20060074730 | Shukla et al. | Apr 2006 | A1 |
20070162324 | Suzuki et al. | Jul 2007 | A1 |
Number | Date | Country |
---|---|---|
2004-126681 | Apr 2004 | JP |
Number | Date | Country | |
---|---|---|---|
20090132532 A1 | May 2009 | US |