Check support system and check support method

Abstract

In order to achieve an efficient check, the present invention comprises: a design matter extraction unit (103) that extracts design matter information together with tag information by searching a design information model DB (200); a check item content conversion unit (104) that generates an output check item sentence by converting elements of a check item sentence, which is a check item sentence used by a user in the past, by the design matter information on the basis of information pertaining to the check item sentence and retrieved from a check item sentence DB (300); and an output processing unit (105) that outputs the output check item sentence to an input / output unit (101). The check item content conversion unit (104) converts the elements of the check item sentence by the design matter information on the basis of tag information associated with the elements of the check item sentence and the tag information associated with the design matter information extracted by the design matter extraction unit (103).

Description

Check support system and check support method

[0001] The present invention relates to a technology for a check support system and a check support method.

[0002] Checking the content of specified work is a daily practice. However, there is a problem in such checks, where the number of check items increases every time a defect occurs, and the number of design check items becomes enormous. Another problem is that it is not easy to reduce the number of check items once they have been set.

[0003] Patent Documents 1 and 2 disclose techniques relating to such work content checks.

[0004] Patent Document 1 discloses a design support method, a design support program, and a design support system that is "suitable for industries that manufacture one or a small number of products to order, and includes a design status confirmation step S26 that confirms the design status of a product designed using a CAD system 10, a task confirmation step S22 that checks a production management database 21 to confirm a task corresponding to the design status, a knowledge comparison step S12 that checks a design knowledge base 30 that corresponds to the design status and the task, a presented information narrowing down step S24 that narrows down presented information by comparing and taking the task into consideration with respect to the design status, and an information provision step S25 that provides narrowed down presented information that corresponds to the design status" (see abstract).

[0005] Furthermore, Patent Document 2 discloses a design support method and program which "includes the steps of providing a library in which importance levels are set in association with inspection items, and displaying the inspection items and importance levels extracted from the library, and when the importance level for the displayed inspection item is higher than a predetermined value and an OK check result is input, requesting approval from an authority, and setting the item as resolved if approved, or recording an unresolved issue and setting the item as unresolved if not approved, or setting the item as unresolved if an NG check result is input, and on the other hand, setting the item as resolved or unresolved depending on the input check result if the importance level is lower than a predetermined value" (see abstract).

[0006] JP 2021-56860 A JP 2003-296523 A

[0007] Since frequent checks are inefficient, checks are often performed collectively using phase gates. However, when checks are performed collectively using phase gates, the number of check items often becomes too large. When this happens, if there are check expressions that the user is not familiar with (check expressions that the subject has not checked in the past), there is a problem that each item is not checked thoroughly. The technologies described in Patent Documents 1 and 2 cannot solve this problem.

[0008] The present invention has been made in view of the above background, and an object of the present invention is to realize an efficient check.

[0009] In order to solve the above-mentioned problems, the present invention includes a design item extraction unit that, based on input information, searches a design information model DB in which a design information model linking tag information and design item information related to the input information is stored, and extracts the design item information related to the input information along with the tag information; a check item content conversion unit that, based on information about first check item sentences that are check item sentences used in the past by the user, generates third check item sentences by converting, with the design item information, elements of second check item sentences that have elements corresponding to check items and for which tag information is associated with each of the elements; and an output processing unit that outputs the third check item sentences to an output unit, wherein the check item content conversion unit converts the elements of the second check item sentences with the design item information, based on the tag information associated with the elements of the second check item sentences and the tag information associated with the design item information extracted by the design item extraction unit. Other solutions will be described as appropriate in the embodiments.

[0010] According to the present invention, an efficient check can be realized.

[0011] FIG. 1 is a functional block diagram showing an example of the configuration of a check support system according to a first embodiment. FIG. 2 is a diagram showing an example of the configuration of hardware of a computer that constitutes the check support system. FIG. 3 is a diagram showing an example of a design information model used in the first embodiment. FIG. 4 is a diagram showing an example of check item sentence information stored in a check item sentence DB. FIG. 5 is a diagram showing an example of usage information stored in a check item result DB. FIG. 6 is a flowchart showing the procedure of a check support method according to a first embodiment. FIG. 7 is a diagram showing an example of output check item sentences. FIG. 8 is a diagram showing an example of target product information. FIG. 9 is a diagram showing an example of a process flow. FIG. 10 is a diagram showing an example of a design information model that is output to an input / output unit. FIG. 11 is a flowchart showing the procedure of a check support method according to a second embodiment.

[0012] Next, a mode for carrying out the present invention (referred to as an "embodiment") will be described in detail with reference to the drawings as appropriate.

[0013] <First embodiment> [Check support system 1] Fig. 1 is a functional block diagram showing an example of the configuration of a check support system 1 according to the first embodiment. Fig. 1 describes an overview of the processes performed by the input / output unit 101 to the output processing unit 105, and the design information model DB 200 to the check item result DB 400 in the check support system 1. Details of the processes performed by the input / output unit 101 to the output processing unit 105, and the design information model DB 200 to the check item result DB 400 will be described later.

[0014] The check support system 1 includes an input / output unit 101, which is an output unit, an input processing unit 102, a design item extraction unit 103, a check item content conversion unit 104, and an output processing unit 105. The check support system 1 also includes a design information model DB 200, which is a memory unit, a check item sentence DB 300, and a check item performance DB 400, which are memory units.

[0015] The design information model DB 200 stores a design information model 210 (see FIG. 3 ), which is a model in which tag information 213 and design item information 211 (see FIG. 3 ) are linked. The design item information 211 is information about design items, such as "entrance / exit" and "welding," and can be used as a check item. The tag information 213 is information associated with each piece of design item information 211 and indicates the classification of the design item indicated by the design item information 211, such as "task" or "functional part." The check item sentence DB 300 stores check item sentence information 310 (see FIG. 4 ). The check item sentence information 310 stores check item sentences 311 (see FIG. 4 ) used in the past by various users. In other words, the check item sentence information 310 stores multiple check item sentences 311. The check item record DB 400 stores usage information 410 (see FIG. 5 ), which is information about first check item sentences used by users in the past. The usage information 410 will be described in detail later.

[0016] The input processing unit 102 acquires information input via the input / output unit 101. The design item extraction unit 103 extracts design item information 211 (see FIG. 3 ) corresponding to the check item from the design information model 210 stored in the design information model DB 200. The check item content conversion unit 104 converts elements 312 (see FIG. 4 ) of check item sentences 311 stored in the check item sentence DB 300 using the design item information 211 extracted by the design item extraction unit 103. Specific examples of the elements 312 of the check item sentences 311 will be described later, but they correspond to the check items in the check item sentences 311. In this case, the check item content conversion unit 104 selects the check item sentence 311 (see FIG. 4 ), which is the second check item sentence, based on the usage information 410 (see FIG. 5 ) stored in the check item performance DB 400. In this way, the check item content conversion unit 104 converts the check item into an expression that is familiar to the user. As a result, an output check item sentence 511 (see FIG. 7) which is the third check item sentence is generated.

[0017] The output processing unit 105 outputs the output check item sentence 511 output from the check item content conversion unit 104 to the input / output unit 101 .

[0018] The input / output unit 101 may be configured as a terminal device (not shown), and the input processing unit 102 to the output processing unit 105 and the design information model DB 200 to the check item result DB 400 may be configured as a server (not shown). Alternatively, the input / output unit 101 to the output processing unit 105 and the design information model DB 200 to the check item result DB 400 may be mounted on a single terminal (not shown). Alternatively, the design information model DB 200 to the check item result DB 400 may be stored in a database server (not shown) separate from the server (not shown) on which the input processing unit 102 to the output processing unit 105 are mounted.

[0019] 2 is a diagram showing an example of the hardware configuration of a computer C that constitutes the check support system 1. The computer C is a server (not shown) or the like that executes the input processing unit 102 to the output processing unit 105.

[0020] The computer C includes a memory 111 including a RAM or the like, an arithmetic unit 112 including a CPU, a GPU or the like, and a storage device 113 including a HDD, an SSD or the like. The computer C also includes an input device 114 including a keyboard, a mouse or the like, an output device 115 including a display, a printer or the like, and a communication device 116. The input device 114 and the output device 115 correspond to the input / output unit 101 in FIG. 1 .

[0021] Then, the program stored in the storage device 113 is loaded into the memory 111. The loaded program is then executed by the arithmetic unit 112. This embodies the input processing unit 102, design item extraction unit 103, check item content conversion unit 104, and output processing unit 105 shown in FIG.

[0022] The design information model DB 200, check item sentence DB 300, and check item performance DB 400 shown in FIG. 1 may correspond to the storage device 113 in FIG. 2, or may be configured as a DB separate from the storage device 113.

[0023] (Design Information Model 210) FIG. 3 is a diagram showing an example of the design information model 210 used in the first embodiment. The design information model 210 stores nodes 212 corresponding to design item information 211 and tag information 213 corresponding to each node 212 (design item information 211). Each node 212 corresponds to the design item information 211, such as "production design" or "welding." The nodes 212 are connected by edges to form a graph structure. As described above, the tag information 213 stores information related to the classification of design items, such as "task" or "part."

[0024] 3, each piece of design item information 211 is a node 212, and the nodes 212 are connected by edges to form a graph structure, but this is not limiting. For example, the relationships between the design item information 211 and the relationships between the design item information 211 and the tag information 213 may be expressed in a format similar to a relational database.

[0025] In this way, the design information model 210 contains a plurality of pieces of design item information 211, and tag information 213 is assigned to each piece of design item information 211. The design information model 210 stores each piece of design item information 211 in association with other pieces of design item information 211.

[0026] In the example of the design information model 210 shown in Fig. 3, the side of the node 212 corresponding to the design item information 211 of "production design" or "manufacturing" is defined as the upstream side. Also, in the example of the design information model 210 shown in Fig. 3, the side of the node 212 to which the tag information 213 of "threshold value" such as "distance 55 mm or more" is assigned is defined as the downstream side.

[0027] (Check Item Sentence Information 310) FIG. 4 is a diagram showing an example of check item sentence information 310 stored in the check item sentence DB 300. The check item sentence information 310 stores a plurality of check item sentences 311. Each check item sentence 311 has been used in the past by a plurality of users. As shown in FIG. 4, each check item sentence 311 is divided into elements 312 corresponding to the check items checked in the check item sentence 311. Each element 312 is associated with tag information 313. The tag information 313 is similar to the tag information 213.

[0028] (Usage Information 410) Figure 5 is a diagram showing an example of usage information 410 stored in the check item results DB 400. The usage information 410 stores multiple check item sentences 411 that a user has used in the past to generate output check item sentences 511 (Figure 7). The check item sentences 411 are preferably stored in order of frequency of use. Such usage information 410 is generated for each user.

[0029] In the example shown in Fig. 5, the check item sentences 411 themselves are stored in the usage information 410, but this is not limited to this. For example, if an ID or the like is assigned to the check item sentences 311 stored in the check item sentence information 310 shown in Fig. 4, the ID may be stored in the usage information 410. In addition, in the example shown in Fig. 5, the check item sentences 411 are stored in order of frequency of use, but this is not limited to this. Information related to the check item sentences 411 (such as the check item sentences 411 themselves or the IDs assigned to the check item sentences 311) may be stored in association with the number of times they have been used.

[0030] It is also desirable that the design information model 210, the check item text information 310, and the usage information 410 are each created by an administrator or the like.

[0031] [Flowchart] FIG. 6 is a flowchart showing the steps of the check support method according to the first embodiment. Reference will be made to FIGS. 1, 3, 4, 5, and 6 as appropriate. Specific and detailed content of each process in FIG. 6 will be described later. FIG. 7 is a diagram showing an example of an output check item sentence 511. First, the input processing unit 102 acquires target product information, task information, and user information, which are information about the product (target product) to be checked, input via the input / output unit 101 (S1). The target product information, task information, and user information constitute input information. Thus, the input information includes information about tasks. Next, the design feature extraction unit 103 extracts design feature information 211 from the design information model 210 based on the target product information and task information (S2: design feature extraction step). The design feature extraction unit 103 then references the design information model 210 and determines whether a downstream node exists (S3). A downstream node is a node 212 located downstream of the node 212 corresponding to the design feature information 211 being processed in step S2.

[0032] If a downstream node exists (S3 → Yes), the design item extraction unit 103 returns to step S2 and extracts design item information 211 corresponding to the downstream node. If a downstream node does not exist (S3 → No), the check item content conversion unit 104 selects check item sentences 311 from the check item sentence information 310 (S4). This selection is made based on the user information entered in step S1. At this time, the check item content conversion unit 104 also selects check item sentences 311 that the user has used in the past from the check item sentence information 310 stored in the check item sentence DB 300.

[0033] Then, the check item content conversion unit 104 converts (replaces) the element 312 of the selected check item sentence 311 with the design item information 211 extracted in step S2 (S5: conversion step).

[0034] As a result of steps S2 to S5, the check support system 1 extracts design item information 211 linked to the target product and task information from the design information model 210. Then, the check support system 1 converts elements 312 of check item sentences 311 with a history of use with the extracted design item information 211. As a result, the check support system 1 generates output check item sentences 511 (see FIG. 7) that have expressions with a history of use.

[0035] Then, the output processing unit 105 outputs the output check item sentence 511 (see FIG. 7) and the design information model 210 as a result of step S5 to the input / output unit 101 (S6: output processing step).

[0036] (Specific Example) Next, the specific content of each process performed in FIG. 6 will be described with reference to FIGS. 1, 3, 4, and 7 to 9. In the following description, step numbers refer to the step numbers shown in FIG. 6. First, in step S1, the input processing unit 102 acquires target product information, task information, and user information input via the input / output unit 101. The target product information may be input as information such as that shown in FIG. 8. In FIG. 8, information regarding entrances and exits is input as the target product information. Note that in the example shown in FIG. 8, information regarding "functional parts" ("entrances and exits"), contents ("number of items," "width"), "old," and "new" is input. In this embodiment, the input processing unit 102 acquires only information regarding the "functional parts" ("entrances and exits"). For example, when a user selects the "functional parts" ("entrances and exits") of the target product information via the input / output unit 101, the input processing unit 102 acquires only information regarding the "functional parts" ("entrances and exits"). Incidentally, in FIG. 8, "old" means before renovation, and "new" means after renovation, etc.

[0037] 9 shows an example of a process flow 600. In step S1, the user selects "production design" (reference numeral 601) in the process flow 600 via the input / output unit 101, causing the input processing unit 102 to acquire information on "production design" as task information. The fact that "production design" is task information can be determined by the process flow 600 being set in advance as information on task information, or by the user inputting information indicating that "production design" is task information.

[0038] 8 and 9 are merely examples, and any input may be made. Also, in step S1, it is sufficient to input information that enables processing in step S2 and subsequent steps, and it is not necessary to input all of the target product information, task information, and user information.

[0039] In step S2, the design matter extraction unit 103 extracts design matter information 211 including the check target. Specifically, the design matter extraction unit 103 searches the design information model 210 shown in FIG. 3 using the target product and task information input in step S1 as keys. Referring to FIG. 3, an example is shown in which "entrance / exit" is input as the target product and "welding" is input as the task information in step S1. The design matter extraction unit 103 searches the design information model 210 and extracts nodes 212 having design matter information 211 for "entrance / exit" and "welding." In the example of FIG. 3, node 212a corresponds to the "entrance / exit" node 212, and node 212b corresponds to the "welding" node 212.

[0040] Then, the design feature extraction unit 103 sequentially extracts nodes 212 (downstream nodes) located downstream of the extracted node 212 (S2, S3).

[0041] In this case, the design matter extraction unit 103 extracts downstream nodes according to the following conditions: (A1) When multiple nodes 212 are extracted as downstream nodes of a certain node 212 and the same tag information 213 is assigned to them, the design matter extraction unit 103 assigns priorities to the two nodes 212. (A2) The more common nodes 212 selected upstream, the higher the priority of the target node 212. (A3) Even under the condition (A2), if the design matter extraction unit 103 cannot set a high or low priority, the highest priority is assigned to the node 212 that has been used by the user the most in the past. (A4) When downstream nodes of a node 212 to which a priority has been assigned are extracted, the node 212 with the highest priority is extracted first.

[0042] In (A1), a case will be described in which two nodes 212 are extracted as downstream nodes of a certain node 212. In the example shown in FIG. 3, a "weld line" node 212c and a "weld bead" node 212d exist as downstream nodes corresponding to a "weld" node 212b. Both the "weld line" node 212c and the "weld bead" node 212d have tag information 213 of "part." In this case, priorities are assigned to both the "weld line" node 212c and the "weld bead" node 212d in accordance with the condition in (A1).

[0043] Meanwhile, downstream nodes of the "weld bead" node 212d are the "end face" node 212e and the "distance 50 mm or more" node 212f. However, the tag information 213 assigned to node 212e is "part," while the tag information 213 assigned to node 212f is "threshold." In this way, if a node 212 has a common downstream node but different tag information 213, no priority is assigned.

[0044] The following is a specific example of (A2). Assume that "entrance / exit" is input as the target product information and "welding" is input as the task information in step S2. In this case, the "entrance / exit" node 212a and the "welding" node 212b are extracted in step S2.

[0045] Then, after "Yes" is selected in step S3, downstream nodes of the "entrance / exit" node 212a and the "welding" node 212b are selected in step S2. At this time, the "welding bead" node 212d is extracted as the downstream node of the "entrance / exit" node 212a. Meanwhile, the "welding line" node 212c and the "welding bead" node 212d are extracted as the downstream nodes of the "welding" node 212b. Here, the downstream node common to the "entrance / exit" node 212a and the "welding" node 212b is the "welding bead" node 212d. Therefore, the design feature extraction unit 103 sets the priority of the "welding bead" node 212d higher than that of the "welding line" node 212c.

[0046] Specific examples of (A3) will be omitted, and specific examples of (A4) will be described later.

[0047] The "production design" node 212g will be described later in the second embodiment.

[0048] Then, "Yes" is selected in step S3, and further downstream nodes are extracted in the next step S2. At this time, based on the condition (A4) described above, between "weld line" node 212c and "weld bead" node 212d, "weld bead" node 212d, which has the (highest) priority, is extracted. Then, "end face" node 212e, which is a downstream node of "weld bead" node 212d, and "distance 50 mm or more" node 212f are extracted.

[0049] Then, the design feature extraction unit 103 determines whether or not a downstream node exists (S3). In step S3, the design feature extraction unit 103 determines whether or not a downstream node exists for the most downstream node 212 among the extracted nodes 212. In the example shown in Fig. 3, there is no downstream node for node 212f, which is the extracted most downstream node 212 with a "distance of 50 mm or more", so the determination in step S3 is "No."

[0050] When extracting the node 212 (i.e., the design matter information 211), the design matter extraction unit 103 also acquires the tag information 213 associated with the node 212. In this way, the design matter extraction unit 103 searches the design information model 210 based on the input information, thereby extracting the design matter information 211 related to the input information together with the tag information 213.

[0051] The conditions (A1) to (A4) for extracting downstream nodes in step S3 are merely examples. The contents of the conditions for extracting downstream nodes in step S3 are set appropriately based on the structure of the design information model 210, the configuration of the check item sentences 311, etc.

[0052] For example, it is possible to assign a level of importance to each piece of design item information 211 stored in the design information model 210. This level of importance can also be set for each phase (task content) of the process flow 600 (see FIG. 9 ). For example, if a user makes a mistake in the size of a screw hole in the first phase of the process flow 600, it is difficult to correct the mistake in subsequent phases. For such design items, the level of importance of the design item information 211 is set high in the first phase of the process flow 600, but is set low in subsequent phases of the process flow 600.

[0053] Next, the check item content conversion unit 104 selects, as the second check item sentence, a check item sentence 311 that the user has used in the past (S4: check item sentence selection step). The selection in step S4 is made based on the user information input in step S1 of FIG. 6, the usage information 410, and the check item performance DB 400.

[0054] In the example shown in Figure 4, it is assumed that check item sentence 311a has been selected. If the user has used more than one of the check item sentences 311 stored in the check item sentence information 310, multiple check item sentences 311 may be selected. In this case, the sentences may be selected in descending order of the number of times the user has used them, or the check item sentence 311 that has been used the most may be selected. The check item sentences 411 that the user has used in the past are stored in the check item record DB 400.

[0055] In this way, the check item content conversion unit 104 selects a check item sentence 311 from the plurality of check item sentences 311 stored in the check item sentence information 310 based on the usage information 410 .

[0056] Next, the check item content conversion unit 104 converts the element 312 of the selected check item sentence 311 with the design item information 211 of the node 212 extracted in step S202 (S5). As shown in FIG. 3, tag information 213 is assigned to each of the nodes 212 in the design information model 210. Therefore, tag information 213 is also assigned to the node 212 extracted in step S2. Referring to FIG. 3, the tag information 213 of "part" is assigned to the "weld bead" node 212d extracted in step S2. Similarly, the tag information 213 of "part" is assigned to the "end face" node 212e extracted in step S202, and the tag information 213 of "part" is assigned to the "distance of 50 mm or more" node 212f.

[0057] On the other hand, as described above in Fig. 4, check item sentence 311 has elements 312. In the example shown in Fig. 4, check item sentence 311a has elements 312 such as "weld bead," "bolt hole," and "distance 20 mm or more." As shown in Fig. 4, each of the elements 312 is assigned tag information 313. For example, the "weld bead" element 312 in check item sentence 311a is assigned tag information 313 of "part." Similarly, in check item sentence 311a, the "bolt hole" element 312 is assigned tag information 313 of "part," and the "distance 20 mm or more" element 312 is assigned tag information 313 of "threshold."

[0058] In step S5, the check item content conversion unit 104 converts (replaces) the element 312 of the check item sentence 311 with the design item information 211 of the node 212 extracted in step S2, based on the tag information 213, 313. If there is no design item information 211 that matches the element 312, the check item content conversion unit 104 leaves that element 312 blank, etc.

[0059] In step S4, it is assumed that the check item sentence 311a shown in Fig. 4 is selected. The check item content conversion unit 104 replaces the "weld bead" element 312a, which has the tag information 313 of "part" attached, in the check item sentence 311a shown in Fig. 4. In this case, the check item content conversion unit 104 replaces the element 312a with the design item information 211 of "weld bead," which has the tag information 213 of "part" attached, from among the nodes 212 extracted in step S202 (see Fig. 7).

[0060] Similarly, the check item content conversion unit 104 replaces the "bolt hole" element 312b, which has the "part" tag information 313, in the check item sentence 311a shown in Fig. 4. In this case, the check item content conversion unit 104 replaces the element 312b with the "end face" design item information 211, which has the "part" tag information 213, from the node 212 extracted in step S202 (see Fig. 7).

[0061] The check item content conversion unit 104 then replaces the element 312c, "distance 20 mm or more," which has been assigned the tag information 313 of "threshold" in the check item sentence 311a shown in Fig. 4. In this case, the check item content conversion unit 104 replaces the element 312c with the design matter information 211, "distance 50 mm or more," which has been assigned the tag information 213 of "threshold," from among the extracted nodes 212 (see Fig. 7). As a result, the output check item sentence 511 shown in Fig. 7 is generated.

[0062] In this way, the check item content conversion unit 104 converts the elements 312 (312a to 312c) of the check item sentence 311 (311a) selected in step S4 with the design item information 211. The conversion is performed based on the tag information 313 associated with the elements 312 of the check item sentence 311 and the tag information 213 associated with the design item information 211 extracted by the design item extraction unit 103.

[0063] By the processing of steps S1 to S5, an output check item sentence 511 containing expressions familiar to the user is output. As shown in FIG. 7, elements 512 and tag information 513 are output to the output check item sentence 511.

[0064] Then, in step S6, the output processing unit 105 displays the generated output check item sentences 511 and the design information model 210. When displaying the output check item sentences 511, the output processing unit 105 also displays elements 512 of the output check item sentences 511 and tag information 513, as shown in Fig. 7. That is, in addition to the output check item sentences 511, the output processing unit 105 outputs the tag information 213 associated with the design item information 211 extracted by the design item extraction unit 103 to the input / output unit 101 as tag information 513.

[0065] Furthermore, the output processing unit 105 displays information about the nodes 212 extracted in step S2 from the design information model 210. Displaying information about the nodes 212 extracted in step S2 means that the output processing unit 105 displays only the nodes 212 extracted in step S2 from the design information model 210. Alternatively, as shown in FIG. 10 , the output processing unit 105 highlights the nodes 212 extracted in step S2 from the design information model 210. That is, in addition to the output check item sentence 511, the following information is output. That is, the design item information 211 extracted by the design item extraction unit 103 from the design item information 211 (nodes 212) stored in the design information model 210 is output to the input / output unit 101.

[0066] As described above, in the first embodiment, the check support system 1 presents the output check item sentences 511. To present the output check item sentences 511, the design information model 210, which links the tag information 213 and design item information 211 related to the target product, is stored in the design information model DB 200. Also, the check item sentences 311 used in the past by various users are stored in the check item sentence DB 300. Furthermore, information related to the check item sentences 411 used in the past by a certain user is stored in the check item record DB 400.

[0067] When target product information, task, and user information are input, the check support system 1 narrows down the design item information 211 stored in the design information model 210 according to the user. The check support system 1 then converts the elements 312 of the check item sentences 311 using the narrowed down design item information 211. Furthermore, the check support system 1 displays the output check item sentences 511 that are the results of the conversion.

[0068] In this way, it is possible to generate and display output check item sentences 511 that are composed of expressions that the user has used in the past, that is, expressions that the user is familiar with. This allows the user to focus on checking.

[0069] Furthermore, according to the first embodiment, information is stored at the design item level in the design information model 210, making it possible to handle it as a module. This makes it possible to generate the output check item sentence 511 simply by replacing the element 312 of the check item sentence 311.

[0070] 7, when the output check item sentence 511 is displayed, the elements 512 of the output check item sentence 511 and tag information 513 are also displayed. Also, as shown in FIG. 10, the output processing unit 105 displays information about the node 212 extracted in step S2 from the design information model 210. This allows the user to confirm how the output check item sentence 511 was generated and output. As shown in FIG. 7, when the output check item sentence 511 is displayed, the user may be able to select whether or not to display the elements 512 of the output check item sentence 511 and tag information 513. Similarly, as shown in FIG. 10, the user may be able to select whether or not to display information about the node 212 extracted in step S2 from the design information model 210.

[0071] Second Embodiment [Flowchart] FIG. 11 is a flowchart showing the steps of a check support method according to the second embodiment. In step S1A, in addition to the target product and user information, information on a task currently in progress (ongoing) is input. This step differs from step S1 shown in FIG. 6 in that in addition to the target product and user information, the information on the task in progress is input. In other words, the information on the task is information on the task currently in progress. Incidentally, the task information input in step S1 shown in FIG. 6 is not necessarily information on the task in progress. Furthermore, in step S1A, if the information on the task in progress includes the target product and user information, only the information on the task in progress may be input.

[0072] The processing from step S2 onwards is the same as in the first embodiment, and therefore the description of the second embodiment will be omitted.

[0073] According to the second embodiment, it is possible to generate and output the output check item sentence 511 based on the information of the task currently in progress.

[0074] The present invention is not limited to the above-described embodiments and includes various modifications. For example, the above-described embodiments have been described in detail to clearly explain the present invention, and the present invention is not necessarily limited to those having all of the described configurations. Furthermore, it is possible to replace part of the configuration of one embodiment with the configuration of another embodiment, and it is also possible to add the configuration of another embodiment to the configuration of one embodiment. Furthermore, it is possible to add, delete, or replace part of the configuration of each embodiment with other configurations.

[0075] In this embodiment, generation of the output check item sentence 511 is initiated when target product information, task information, and user information are input via the input / output unit 101, but this is not limiting. For example, generation of the output check item sentence 511 may be initiated when CAD information is changed. In this case, the input information is a signal indicating the change in CAD information, information about the part indicated by the CAD information, etc.

[0076] Furthermore, the design information model 210, the check item text information 310, etc. may be set for each task.

[0077] Furthermore, some or all of the above-described components, functions, input / output unit 101 to output processing unit 105, design information model DB 200, check item sentence DB 300, and check item performance DB 400 may be implemented in hardware, for example, by designing them as integrated circuits. As shown in FIG. 2 , the above-described components, functions, and the like may be implemented in software by a processor such as a CPU interpreting and executing a program that implements each function. Information such as the programs, tables, and files that implement each function can be stored on a hard disk or in a recording device such as memory 111 or an SSD, or on a recording medium such as an IC (Integrated Circuit) card, an SD (Secure Digital) card, or a DVD (Digital Versatile Disc).

[0078] In addition, in each embodiment, the control lines and information lines shown are those that are considered necessary for explanation, and not all control lines and information lines in the product are necessarily shown. In reality, it can be considered that almost all components are interconnected.

[0079] 1 Check support system 101 Input / output unit (output unit) 102 Input processing unit 103 Design item extraction unit 104 Check item content conversion unit 105 Output processing unit 111 Memory 112 Arithmetic unit 113 Storage device 114 Input device 115 Output device 116 Communication device 200 Design information model DB (storage unit) 210 Design information model 211 Design item information 212 Node 212a Node 212b Node 212c Node 212d Node 212e Node 212f Node 212g Node 213 Tag information 300 Check item sentence DB (storage unit) 311 Check item sentence 311a Check item sentence (second check item sentence) 312 Element 313 Tag information 400 Check item achievement DB 410 Usage information (information related to the first check item sentence) 411 Check item sentence 511 Output check item sentence (third check item sentence) 600 Process flow 601 Code C Computer S2 Extraction of design item information (design item extraction step) S5 Conversion (conversion step) S6 Output (output processing step)

Claims

1. A check support system comprising: a design item extraction unit that, based on input information that is input, searches a design information model DB in which a design information model linking tag information and design item information related to the input information is stored, and extracts the design item information related to the input information together with the tag information; a check item content conversion unit that generates a third check item sentence by converting, based on information about a first check item sentence that is a check item sentence used in the past by a user, elements of a second check item sentence that has elements corresponding to check items and has tag information associated with each of the elements, using the design item information; and an output processing unit that outputs the third check item sentence to an output unit, wherein the check item content conversion unit converts the elements of the second check item sentence with the design item information, based on the tag information associated with the elements of the second check item sentence and the tag information associated with the design item information extracted by the design item extraction unit.

2. The check support system described in claim 1, characterized in that the output processing unit outputs to the output unit, in addition to the third check item sentence, the tag information associated with the design item information extracted by the design item extraction unit.

3. The check support system according to claim 1, characterized in that the output processing unit outputs the tag information associated with the element of the third check item sentence when outputting the third check item sentence to the output unit.

4. The check support system according to claim 1, characterized in that the input information includes information regarding a task.

5. The check support system according to claim 4, characterized in that the information relating to the task is information relating to a task currently in progress.

6. A check support method in which a check support system executes the following steps: a design item extraction step in which, based on input information that is input, a design information model DB in which a design information model linking tag information and design item information related to the input information is stored, and the design item information related to the input information is extracted together with the tag information; a conversion step in which, based on information about a first check item sentence that is a check item sentence used in the past by a user, the elements of a second check item sentence that has elements corresponding to check items and has tag information associated with each of the elements are converted with the design item information based on the tag information associated with the elements and the tag information associated with the design item information, thereby generating a third check item sentence; and an output processing step in which the third check item sentence is output to an output section.

Images