Business information search system and business information search method

Abstract

To provide a business information retrieval system and a business system retrieval method capable of providing a retrieval result matching business that all workers and each worker of a sales staff are going to perform from now.SOLUTION: A business information retrieval system includes: a full-text retrieval unit that performs full-text retrieval using a word selected by a worker as a retrieval key, and extracts a document containing business information that includes the retrieval key; and a latest-scheduled-work retrieval unit that retrieves the latest scheduled work contents ahead of a current time of the worker. The system also includes: a document topic estimation unit that estimates related work indicated by a browsed document being viewed by the worker; and an estimation job order sorting unit that sorts, from the related work indicated by the work contents retrieved by the latest-scheduled-work retrieval unit and the related work indicated by the browsed document, retrieval results extracted in the full-text retrieval unit.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a business information search system and a business information search method. [Background technology]

[0002] Infrastructure equipment such as generators, elevators, mining and construction equipment have become indispensable in society. These equipment undergoes model changes to meet the diverse needs of society, and their configurations become more complex. For this reason, a large amount of specialized equipment knowledge is required not only in the design and manufacturing process of the equipment, but also when maintaining and selling the equipment.

[0003] For this reason, maintenance companies and sales companies for the above-mentioned infrastructure facilities provide specialized training for personnel who perform maintenance work and sales. However, there is a shortage of instructors to provide training, and an increasing number of company departments are unable to provide sufficient training and guidance. Therefore, there is a need for a system that allows personnel to efficiently acquire specialized knowledge about infrastructure facilities.

[0004] Patent Document 1 discloses a method for a maintenance worker support system that supports maintenance workers, in which the skill level of a worker is estimated from past data such as the training that the worker has received, work history, and last work date, and a maintenance manual appropriate for the worker's level is provided. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] JP 2007-34712 A Summary of the Invention [Problem to be solved by the invention]

[0006] In this way, in Patent Document 1, information to be provided to a worker is estimated from past information such as the worker's work history. However, the technical information required by a worker differs not only depending on the skill level but also on the work that the worker is going to perform using the information. Therefore, in a system in which information to be provided to a worker is estimated from the skill level and past work history, etc., there is a risk that incorrect information will be provided if the work content that the worker is going to perform differs from the work content in the past. For this reason, if the worker is transferred or the work tendency changes due to the change of period, etc., there are cases in which the technical information required by the worker for the work to be performed cannot be provided.

[0007] Therefore, the present invention provides a task information search system and a task system search method that can provide search results that match the task that each worker, such as a maintenance worker or a sales representative, is about to perform. [Means for solving the problem]

[0008] In order to solve the above problems and achieve the object of the present invention, the task information search system of the present invention comprises a full-text search unit that performs a full-text search using a word selected by a worker as a search key and extracts documents containing task information including the search key.The system also comprises an upcoming scheduled task search unit that searches for task content scheduled in the near future ahead of the worker's current time, and a document topic estimation unit that estimates related tasks indicated by the documents being viewed by the worker.The system also comprises an estimated task order sorting unit that sorts the search results extracted by the full-text search unit from the related tasks indicated by the task content searched by the upcoming scheduled task search unit and the related tasks indicated by the documents being viewed.

[0009] The task information search method of the present invention performs a full-text search using a word selected by a worker as a search key to extract documents containing task information including the search key. It also searches for work content scheduled immediately ahead of the worker's current time to estimate related tasks indicated by the documents being viewed by the worker. It also sorts the documents extracted by the full-text search based on the related tasks indicated by the searched task content and the related tasks indicated by the viewed documents. Effect of the Invention

[0010] According to the present invention, it is possible to provide search results that are suited to the work that each worker is about to perform. [Brief description of the drawings]

[0011] [Figure 1] 1 is a schematic configuration diagram of a business information search system according to an embodiment of the present invention; [Diagram 2] FIG. 2 is a diagram showing Table A and Table B constituting a human resources management DB. [Diagram 3] FIG. 13 is a diagram showing a table C constituting the schedule DB. [Figure 4] FIG. 13 is a diagram showing a table D constituting a document DB. [Diagram 5] FIG. 13 is a diagram showing table E constituting a business master DB. [Figure 6] 3 is a flow chart showing a main routine of a business information search method according to an embodiment of the present invention. [Figure 7] FIG. 11 is a diagram showing an example of a screen displayed on the display unit 105 in step S1 and viewed by a worker. [Figure 8] FIG. 13 is a diagram showing an example of a table F created from the data acquired in step S3 and stored in the temporary storage unit. [Figure 9] 13A and 13B are diagrams showing examples of tables G, H, and I created from the data acquired in step S4 and stored in the temporary storage unit. [Figure 10] FIG. 13 is a diagram showing an example of a table created from the data acquired in step S6 and stored in the temporary storage unit. [Figure 11] FIG. 13 is a diagram showing an example of a table M created from the data acquired in step S7 and stored in the temporary storage unit. [Figure 12] 13 is a diagram showing an example of a screen when related tasks are displayed on a display unit according to the order determined by an estimated task order sorting unit; FIG. [Figure 13]FIG. 11 is a diagram showing an example of a screen showing the search results sorted in step S10 and displayed on the display unit. [Figure 14] This is the flow of subroutine 01. [Figure 15] This is the flow of subroutine 02. [Figure 16] This is the flow of subroutine 03. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] An example of a business information search system and a business information search method according to an embodiment of the present invention will be described below with reference to the drawings. Note that the present invention is not limited to the following example. In each of the drawings described below, the same reference numerals are used to designate common members.

[0013] <Configuration of business information search system> First, a business information search system according to an embodiment of the present invention will be described with reference to the drawings. Fig. 1 is a schematic configuration diagram of a business information search system 1 according to an embodiment of the present invention (hereinafter, referred to as this embodiment).

[0014] As shown in FIG. 1, the business information search system 1 of this embodiment is composed of a personal terminal 100 operated by a technician such as a maintenance worker or sales representative (hereinafter collectively referred to as "worker 102"), and a center-side system 130 installed in a management company, a maintenance office, etc.

[0015] [Personal device] The personal terminal 100 is preferably a mobile phone terminal, a smartphone, or a tablet terminal that is easy for the worker 102 to carry when moving to the work site. In this embodiment, the personal terminal 100 and the center-side system 130 are configured separately so that the worker 102 carries the personal terminal and searches for information as necessary. However, the personal terminal 100 may be a personal computer operated by an administrator at a management company or the like, or may be configured to be incorporated into the center-side system 130.

[0016] The personal terminal 100 includes a display unit 105, an input unit 120, and a communication unit 125. The display unit 105 is, for example, a monitor configured with an LCD (Liquid Crystal Display) or the like, and displays the results of processing performed by the business information search system 1. The input unit 120 is a part where operations are input by the worker 102, and is configured with, for example, a keyboard, a mouse, a touch sensor, etc. Furthermore, the display unit 105 and the input unit 120 may be configured as an integrated touch panel.

[0017] The communication unit 125 transmits and receives information to and from a communication unit 190 of the center-side system 130 in response to an operation from the input unit 120. The display unit 105, the input unit 120, and the communication unit 125 are controlled and processed under the control of a terminal-side control unit (not shown). The terminal-side control unit includes, for example, a CPU (Central Processing Unit), a ROM (Read Only Memory), a RAM (Random Access Memory), and a non-volatile storage, each of which is connected to a bus.

[0018] The CPU reads out the program code of the software that realizes each function according to the present embodiment from the ROM, expands it into the RAM, and executes it in the personal terminal 100. The terminal control unit may include a processing device such as an MPU (Micro-Processing Unit) instead of the CPU. Variables, parameters, etc. that are generated during the calculation process are temporarily written to the RAM.

[0019] Examples of non-volatile storage that can be used include a hard disk drive (HDD), a solid state drive (SSD), a flexible disk, an optical disk, a magneto-optical disk, a CD-ROM, a CD-R, a magnetic tape, and a non-volatile memory card. In addition to an operating system (OS) and various parameters, programs for operating the terminal-side control unit are recorded in the non-volatile storage. The programs may be stored in a ROM.

[0020] The program is stored in the form of a computer-readable program code, and the CPU sequentially executes operations according to the program code. In other words, a ROM or non-volatile storage is used as an example of a computer-readable non-transitory recording medium that stores a program to be executed by a computer.

[0021] The worker 102 can log in to the center-side system 130 by inputting the worker ID into the personal terminal 100 .

[0022] [Center system] The center-side system 130 is a system for providing optimal information to the worker 102 in response to input from the personal terminal 100 owned by the worker 102. Specifically, the center-side system 130 estimates the task information intended (desired to be searched) by the worker 102 based on the worker ID input via the personal terminal 100 at the time of login.

[0023] The center-side system 130 includes a full-text search unit 137, an implementation task narrowing-down unit 140, a near-term scheduled task search unit 150, a document topic estimation unit 160, and an estimated task order sort unit 170. The center-side system 130 also includes a temporary storage unit 135, a human resources management database (DB) 145, a schedule database (DB) 155, a document database (DB) 165, and a task master database (DB) 175.

[0024] The full-text search unit 137 is a full-text search engine that performs a full-text search of the document DB 165 (described later) based on a "search key." The full-text search engine applied to the full-text search unit 137 can be an existing engine that has been used conventionally. Here, the search key is a phrase (including a word) selected by the worker 102 from within the text of the document that the worker is viewing. Therefore, the full-text search unit 137 performs a full-text search of the data accumulated in the document DB 165 using the phrase selected by the worker 102 viewing the document using the personal terminal 100 as the search key, and extracts documents containing business information including the search key as search results.

[0025] The performed work narrowing down unit 140 has a function of referring to information stored in a human resources management DB 145 (described later) based on the worker ID input by the worker 102 from the input unit 120 of the personal terminal 100, and extracting the qualification information held by the worker 102. The performed work narrowing down unit 140 has a function of narrowing down the search results by the full-text search unit 137 to those related to the work that the worker 102 can perform, based on the qualification information held by the worker 102.

[0026] The upcoming scheduled work search unit 150 has the function of searching for and extracting related work indicated by the work content that the worker 102 is scheduled to perform in the future by referring to the schedule DB 155 described later and extracting the work date and time and work content of the worker 102.

[0027] The document topic estimation unit 160 has a function of extracting the topic of a document currently being viewed by the worker 102 (hereinafter referred to as the viewed document) from the frequency of occurrence of words contained in the document, and estimating and extracting related tasks indicated by the viewed document. The document topic estimation unit 160 also extracts the topic of each document extracted by the full-text search unit 137 from the frequency of occurrence of words contained in each document searched by the full-text search unit 137. The document topic estimation unit 160 also has a function of estimating and extracting related tasks indicated by each document.

[0028] The estimated task order sorting unit 170 has the function of sorting the search results of the full-text search unit 137 in order of the frequency of occurrence of words indicating related tasks extracted by the upcoming scheduled task search unit 150 and related tasks of the viewed document extracted by the document topic estimation unit 160.

[0029] The communication unit 190 transmits and receives information to and from the communication unit 125 of the personal terminal 100 in response to an operation from the input unit 120 of the personal terminal 100 .

[0030] The temporary storage unit 135 temporarily stores data that is temporarily generated during the processing performed by the full-text search unit 137, the performed task narrowing down unit 140, the upcoming scheduled task search unit 150, the document topic estimation unit 160, the estimated task order sorting unit 170, and the communication unit 190. The configuration of the data generated in the temporary storage unit 135 will be described later.

[0031] The human resource management DB 145 is a database that accumulates information on the work content that each worker can perform for each qualification held by the worker, and information on the qualification held by each worker. Table A and Table B that constitute the human resource management DB 145 are shown in FIG.

[0032] Table A is a table that shows, in association with a qualification, a task that a worker 102 who holds the qualification can perform, and has items of "qualification" and "task". In the "qualification" item, a name indicating the qualification, for example, Class A, Class B, Class C, etc., is stored. In the "task" item, the name of the task that a worker 102 who holds the corresponding qualification can perform is stored. For example, when the "qualification" is Class A, four tasks, namely, defect response, periodic inspection, final inspection, and statutory inspection, are stored in the "task" item. In addition, when the "qualification" is Class B, three tasks, namely, defect inspection, periodic inspection, and final inspection, are stored in the "task" item.

[0033] Table B is a table indicating which qualifications each worker 102 holds, and has the fields "Worker ID" and "Qualification." The "Worker ID" field stores a worker ID that identifies each worker 102, such as W01, W02, W03, etc. The "Qualification" field stores the qualification held by the worker 102 identified by the corresponding worker ID. For example, the first row of Table B indicates that the worker 102 with worker ID W01 holds a Class A qualification.

[0034] Therefore, the task narrowing-down unit 140 can extract tasks that can be performed by each worker 102 by integrating table A and table B in the human resources management DB 145.

[0035] The schedule DB 155 is a database that stores the schedule of each worker 102. Table C that constitutes the schedule DB 155 is shown in FIG.

[0036] Table C is a table showing the worker ID that identifies the worker 102 in association with the work schedule of the worker 102, and has the items of "worker ID", "date and time", and "work content". The "worker ID" item is the same as the "worker ID" item in Table B. The "date and time" item stores the scheduled work date and time of the worker 102 identified by the corresponding worker ID. The "work content" item records the work content that the worker 102 is scheduled to perform for each corresponding "worker ID" and "date and time". For example, according to the first row of Table C, it is recorded that the worker 102 with the worker ID W01 will "respond to a malfunction in Building X from 13:00 to 17:00 on August 27, 2021".

[0037] The document DB 165 is a database that stores information about the document addresses where the document files are stored and the contents of the documents.

[0038] Table D is a table showing the documents placed at each document address, and has the fields "Document Address" and "Document Content." The "Document Address" field stores the address where the document is stored. The "Document Content" field stores the text data of the document linked to the corresponding document address. Full-text search unit 137 refers to document DB 165 to perform a full-text search of the "Document Content" text data, thereby extracting document addresses and documents based on the search key as search results.

[0039] The job master DB 175 is a database that accumulates the job contents that may be performed by the worker 102. Table E that constitutes the job master DB 175 is shown in FIG.

[0040] Table E is a table showing a list of task IDs that identify individual tasks and the names of the task contents that the task IDs indicate, and has the fields "task ID", "task name 1", "task name 2", ..., "task name S". The "task ID" field stores IDs for identifying individual tasks, and for each task, for example, 01, 02, 03, ..., etc. are stored. The fields "task name 1" to "task name S" store different names for the tasks that are indicated by the corresponding task IDs. Depending on the circumstances, each task may be abbreviated or called by a different name, such as "final inspection" for "complete inspection". In this way, there are often multiple names for one task. Therefore, in table E, task name 1 to task name S can be defined so that a maximum of S types of names can be defined for one task. Although S is a design value, it is preferable to set it to as large a value as possible, such as 100.

[0041] In the above-mentioned center-side system 130, the full-text search unit 137, the performed task narrowing down unit 140, the upcoming scheduled task search unit 150, the document topic estimation unit 160, the estimated task order sorting unit 170, and the communication unit 190 are controlled and processed under the control of a center-side control unit (not shown). The center-side control unit includes, for example, a CPU (Central Processing Unit), a ROM (Read Only Memory), a RAM (Random Access Memory), and a non-volatile storage, each of which is connected to a bus. Here, the RAM constitutes the temporary storage unit 135.

[0042] The CPU reads out the program code of the software that realizes each function according to the present embodiment from the ROM, expands it into the RAM, and executes it in the center-side system 130. The terminal-side control unit may include a processing device such as an MPU (Micro-Processing Unit) instead of the CPU. Variables, parameters, etc. generated during the calculation process are temporarily written to the temporary storage unit 135.

[0043] Examples of non-volatile storage that can be used include a hard disk drive (HDD), a solid state drive (SSD), a flexible disk, an optical disk, a magneto-optical disk, a CD-ROM, a CD-R, a magnetic tape, and a non-volatile memory card. In addition to an operating system (OS) and various parameters, programs for operating the terminal-side control unit are recorded in the non-volatile storage. The programs may be stored in a ROM.

[0044] The program is stored in the form of a computer-readable program code, and the CPU sequentially executes operations according to the program code. In other words, a ROM or non-volatile storage is used as an example of a computer-readable non-transitory recording medium that stores a program to be executed by a computer.

[0045] <How to search for business information> Next, a description will be given of a business information search method in the business information search system 1 of this embodiment. Fig. 6 is a flow chart showing a main routine of the business information search method of this embodiment.

[0046] [Main routine] First, the worker 102 logs in to the center side system 130 from the personal terminal 100 using his / her worker ID. Then, the worker 102 inputs the document address of the document he / she wishes to view, and text data of the corresponding document address is displayed on the display unit 105 of the personal terminal 100 (step S1). Fig. 7 shows an example of a screen displayed on the display unit 105 in step S1 and viewed by the worker 102. Fig. 7 shows a screen 1410 of viewer software for viewing documents on the personal terminal 100, and on this screen 1410, text data 1420 is displayed based on the document address input by the worker 102.

[0047] In step S1, information on the worker ID and document address entered via the input unit 120 of the personal terminal 100 is sent to the center-side system 130 via the communication unit 125. As a result, the full-text search unit 137 refers to the document DB 165 and extracts the text data placed at the corresponding document address. The extracted text data is then sent to the personal terminal 100 via the communication units 190 and 125 and displayed on the display unit 105.

[0048] Next, the worker 102 selects any phrase (including a word) from the document being viewed (viewed document) based on the point the worker 102 is unsure about or the matter he or she wishes to investigate in detail in relation to the work (step S2). For example, in the text data 1420 of FIG. 7, if the worker wants to know more about "connector", the worker 102 operates the input unit 120 to select "connector". Information on the selected phrase is transmitted to the center-side system 130 via the communication units 125 and 190.

[0049] Next, in the center side system 130, the full-text search unit 137 performs a full-text search using the text transmitted from the personal terminal 100 in step S2 as a search key (step S3). The full-text search unit 137 checks the search key against the "document address" and "document content" stored in the document DB 165 to extract and acquire the record line containing the search key. The document information containing the record line acquired in step S3 is stored in the temporary storage unit 135.

[0050] FIG. 8 shows an example of table F created from the data acquired in step S3 and stored in temporary storage unit 135. As shown in FIG. 8, table F, which is configured from the data extracted in step S, has the fields "Document Address", "Document Content", "1st Related Task", "2nd Related Task", and "3rd Related Task". The "Document Address" field records a document address where text data including the search key is placed. "Document Content" is text data placed in the "Document Address", which is text data including the search key. The fields "1st Related Task", "2nd Related Task", and "3rd Related Task" are scheduled to be created later, and are blank "-" at the stage of step S3.

[0051] Next, the document topic estimation unit 160 estimates the document topic of each document that includes the search key acquired in step S3, and calculates 1 to N jobs that are closely related to the "document content" (related jobs) (step S4). In step S4, the document topic estimation unit 160 estimates the document topic by counting the job names that appear in the text data of the "document content" with reference to table F shown in Fig. 8. The details of the process in step S4 will be described in detail in subroutine 01 using Fig. 14.

[0052] 9 shows examples of tables G, H, and I created from the data acquired in step S4 and stored in temporary storage unit 135. Tables G and H are tables created in subroutine 01, which will be described later, and therefore these tables G and H will be described later. In step S4, table I in FIG. 9 is finally obtained. As shown in FIG. 9, table I, which is finally created from the data extracted in step S4, is a table in which the items "related task No. 1," "related task No. 2," and "related task No. 3" of table F shown in FIG. 8 are written.

[0053] As shown in Table I, "Related Task No. 1" records the task name that appears most frequently among words related to the task name that appeared in the text data of "Document Content" and the number of times it appeared. "Related Task No. 2" records the task name that appears second most frequently among words related to the task name that appeared in the text data of "Document Content" and the number of times it appeared. "Related Task No. 3" records the task name that appears third most frequently among words related to the task name that appeared in the text data of "Document Content" and the number of times it appeared. Note that while FIG. 9 shows up to "Related Task No. 3" as an example, it is possible to configure the field to include up to "Related Task No. N". In the following explanation, "Related Task No. 1" to "Related Task No. N" may simply be referred to as "Related Task".

[0054] Next, the performed work narrowing down unit 140 narrows down the search results by the work that the logged-in worker 102 can perform among the "related works" obtained in step S4 (step S5). In step S5, the performed work narrowing down unit 140 refers to table B configured in the human resources management DB 145 to extract the qualification information of the logged-in worker ID, and then refers to table A to extract the work that the qualified worker can perform. In this way, the performed work narrowing down unit 140 extracts the work that the worker 102 having the corresponding worker ID can perform. After that, the performed work narrowing down unit 140 refers to table I in FIG. 9, which is the search result detected by the full-text search unit 137, searches for all "related works" that include the work that the worker 102 can perform based on the qualifications he holds, and extracts the "document addresses" and "document contents" linked to those "related works".

[0055] In this embodiment, the table created from the data of "document address" and "document content" extracted by the performed work narrowing down unit 140 is the same as table G shown in Fig. 9. In this way, in step S5, the full-text search unit 137 narrows down the search results obtained by the full-text search using the search key to those related to the work that the worker 102 can perform based on the qualifications held by the worker 102.

[0056] Next, the upcoming scheduled work search unit 150 refers to table C stored in the schedule DB 155 to search for work content that the logged-in worker 102 is scheduled to perform in the future in ascending order of time to the current time, and adds information on related work to the schedule of the worker 102 (step S6). The processing content of step S6 will be described in detail in the explanation of subroutine 02 using FIG. 15.

[0057] FIG. 10 shows an example of a table created from the data acquired in step S6 and stored in temporary storage unit 135. Tables J and K are tables obtained by subroutine 02, and will be described in detail later. In step S6, table L is finally obtained. As shown in FIG. 10, table L has the fields "worker ID," "date and time," "task content," and "related work." "Worker ID," "date and time," and "task content" are the same as table C in FIG. 3. The "related work" field is an item added in step S6, and stores the name of a related work that is determined to be highly related to the "task content."

[0058] Next, the document topic estimation unit 160 estimates the topic of the document that was displayed on the display unit 105 in step S1 and was being viewed by the worker 102, and estimates and extracts related tasks (step S7). In step S7, similar to step S4, estimation and extraction of related tasks are performed in the same manner as the explanation of subroutine 01 using FIG. 14.

[0059] 11 shows an example of table M created from the data acquired in step S7 and stored in temporary storage unit 135. As shown in Fig. 11, table M has the items "Document address", "Document content", "Related business No. 1", "Related business No. 2", and "Related business No. 3". These items are the same as those of table F shown in Fig. 9.

[0060] Next, the estimated task order sorting unit 170 calculates the MRR (Mean Reciprocal Rank) score of each related task using the results of steps S6 and S7, ranks and rearranges the related tasks in descending order of MRR score, and transmits the rearranged results to the personal terminal 100 via the communication units 190, 125 (step S8). The display unit 105 displays the search results transmitted from the estimated task order sorting unit 170.

[0061] The following describes a method for calculating the MRR score in the estimated task order sorting unit 170. First, the first score is calculated by dividing the reference point 1 by the ranking of each related task, using the ranking of the "related tasks" extracted in step S7 and constituting table M. In this embodiment, as shown in table M in FIG. 11, "completion inspection" is ranked first, "installation work" is ranked second, and "defect response" is ranked third. Therefore, in this case, the first score of "completion inspection" is 1 / 1, the first score of "installation work" is 1 / 2, and the first score of "defect response" is 1 / 3.

[0062] Next, the "related tasks" extracted in step S6 and constituting table L in Fig. 10 are ranked in order of proximity to the current time. Then, using the ranking, the second score is calculated by dividing the reference point 1 by the ranking of each related task. In this embodiment, as shown in table L in Fig. 10, when ranked in order of proximity to the current time, "defect response" is ranked first, "final inspection" is ranked second, and "regular inspection" is ranked third. Therefore, in this case, the second score of "defect response" is 1 / 1, the second score of "final inspection" is 1 / 2, and the second score of "regular inspection" is 1 / 3.

[0063] In addition, in calculating the first score, "regular inspection" is not listed as a related task, and in calculating the second score, "installation work" is not listed as a related task. In this case, the first score for "regular inspection" is 0, and the second score for "installation work" is 0.

[0064] Then, by adding the calculated first score and second score, the final MRR score for each related business is calculated, as shown below. MRR score for "Completion Inspection" = 1 / 1 + 1 / 3 = 3 / 4 "Installation" MRR score = 1 / 2 + 0 = 1 / 2 MRR score for "defect resolution" = 1 / 3 + 1 / 1 = 4 / 3 MRR score for "Regular Inspection" = 0 + 1 / 3 = 1 / 3

[0065] If the related tasks mentioned above are ranked in descending order of MRR score, they are ranked as follows: 1st place "Completion inspection", 2nd place "Defect response", 3rd place "Installation work", and 4th place "Regular inspection". Note that when the MRR scores are the same, such as for "Completion inspection" and "Defect response", the order may be determined randomly. After calculating the MRR scores of the related tasks and determining the order of the related tasks as described above, the estimated task order sorting unit 170 transmits the results to the personal terminal 100 via the communication units 190 and 125.

[0066] Fig. 12 is an example of a screen 1410 when related tasks are displayed on the display unit 105 according to the ranking determined by the estimated task order sorting unit 170. As shown in Fig. 12, in this embodiment, a related task selection unit 1510 is displayed on the screen 1410, and four related task groups 1515 are displayed in the related task selection unit 1510 in the order ranked by the estimated task order sorting unit 170. In this embodiment, four related task groups 1515 are displayed, but if there are a large number of related tasks, the display unit 105 may be configured to display only the top several.

[0067] As described above, in step S8, the estimated task order sorting unit 170 ranks the related tasks based on the results of steps S6 and S7, and the display unit 105 displays the ranked related tasks based on the results.

[0068] Next, the worker 102 operates the input unit 120 to select a task of interest (one that he / she wishes to research) from among the related task group 1515 in the related task selection section 1510 of the display screen 1410 shown in Fig. 12 (step S9). In this embodiment, it is assumed that the worker 102 selects "deal with malfunctions" in the second row from the top in the related task selection section 1510 of Fig. 12. Information on the related task selected by the worker 102 is transmitted to the center-side system 130 via the communication units 125, 190.

[0069] Next, the estimated task order sorting unit 170 again sorts the search results in FIG. 9 based on the information on the related tasks selected and transmitted by the worker 102 ("defect handling" in this embodiment), and the personal terminal 100 displays the sorted search results on the display unit 105 (step S10). In step S10, first, the estimated task order sorting unit 170 sorts the search results shown in table I in FIG. 9 in descending order of the frequency of occurrence of the name of the selected related task. The sorting of the search results in step S10 will be described in [Subroutine 03] using FIG. 16. Thereafter, the estimated task order sorting unit 170 transmits the sorted search results to the personal terminal 100 via the communication units 190 and 125. The personal terminal 100 displays the transmitted search results on the display unit 105.

[0070] Fig. 13 is an example of a screen showing the search results rearranged in step S10 and displayed on the display unit 105. As shown in Fig. 13, the search results 1620 displayed on the screen 1410 display the "document addresses" and their "document contents" rearranged in descending order of the frequency of occurrence of "defect handling" selected by the worker 102. In this embodiment, when the worker 102 appropriately selects a plurality of related tasks displayed in the selection bar 1630 at the top of the screen 1410 shown in Fig. 13, the "document addresses" and their "document contents" are rearranged again by the processing of step 10 according to the selected related task.

[0071] This is the end of the main routine of the transaction search method. Next, a subroutine that is executed in a predetermined step of the main routine will be described.

[0072] [Subroutine 01] First, a description will be given of subroutine 01 called in step S4 of the main routine. A flow of subroutine 01 is shown in Fig. 14. Subroutine 01 is a process for finding the most closely related tasks (related tasks) from 1 to N for each record in the search result acquired in step S4, and creating table I in Fig. 9.

[0073] First, as a preparation, the document topic estimation unit 160 loads a list of business names constituting a table E stored in the business master DB 175 (step S11).

[0074] Next, the document topic estimation unit 160 loads the text data of "Document Content" for each "Document Address" in table F shown in FIG. 8, line by line (step S12). After that, the document topic estimation unit 160 counts the number of times the task name appears in the text data for each task name (step S13). The count results of the task names are stored in the temporary storage unit 135 in the format shown in table G in FIG. 9. In the "Task ID" field of table G, the task name stored in "Appearing Task Name" and the task ID assigned to each task name in table E stored in the task master DB 175 are stored. In addition, in the "Appearing Task Name" field, the task name that appears in the text data is stored. As mentioned above, task names are often written in abbreviations, so the document topic estimation unit 160 is configured to extract all the multiple task names stored in the task master DB 175.

[0075] Furthermore, in step S13, the document topic estimation unit 160 counts the number of occurrences of the task name for each task ID based on table G. The counting results are stored in the temporary storage unit 135 in the format shown in table H. The "task ID" in table H is the same as the "task ID" in table E, and the "number of occurrences" field stores the number of times the task name is counted for each "task ID." For example, since "completion inspection" and "complete inspection" shown in table G have the same task ID, table H stores the value obtained by adding up the respective numbers of occurrences in table G (20+2=22).

[0076] Next, the document topic estimation unit 160 stores the related tasks indicated by the task IDs with the top N number of occurrences (third in this embodiment) shown in table H for each "document address" in table I (step S14). For example, the related task corresponding to the task ID with the highest number of occurrences is stored in "related task No. 1", the related task corresponding to the task ID with the second highest number of occurrences is stored in "related task No. 2", and the related task corresponding to the task ID with the third highest number of occurrences is stored in "related task No. 3". In this embodiment, the name of "task name 1" out of the task IDs is stored as an example, but it is also possible to store the task ID, the task name associated with it, or both. In this way, related tasks are estimated and extracted for each document address.

[0077] Next, the document topic estimation unit 160 judges whether or not the related tasks indicated by all documents included in the search result have been estimated (step S15). If the result in step S15 is "NO", that is, if the result is that the related tasks indicated by all documents have not been estimated, steps S12 to S15 are performed again. If the result in step S12 is "YES", that is, if the result is that the related tasks indicated by all documents have been estimated, the process returns to the main routine.

[0078] In step S7 of Fig. 6, related work is also estimated and extracted using subroutine 01 described with reference to Fig. 14. In step S7, related work is estimated and extracted only based on the document content of the document address of the document viewed by the worker 102, as shown in table M of Fig. 11.

[0079] [Subroutine 02] Next, a description will be given of the subroutine 02 called in step S6 in Fig. 6. Fig. 15 shows the flow of the subroutine 02. The subroutine 02 is a process of searching for tasks that the worker 102 is planning to perform in the order of proximity to the current time, and linking each task with its task ID.

[0080] First, the upcoming scheduled work search unit 150 searches table C stored in the schedule DB 155 using the worker ID (in this embodiment, W01) as a search key (step S21). Next, from the search result acquired in step S21, X items (>N items) of scheduled contents are extracted from the schedule of the corresponding worker ID in order of proximity to the current time (step S22). The results extracted in step S22 are stored in the temporary storage unit 135 in the form of table J in FIG. 10. Here, the scheduled number X is a design value and can be changed in various ways, but it is preferable to set it to 100 items, etc., which is sufficiently larger than the number N of tasks (3 items in this embodiment) finally presented to the worker 102.

[0081] Next, the upcoming scheduled task search unit 150 loads a list of task names from table E stored in the task master DB 175 (step S23).

[0082] Next, the upcoming scheduled work search unit 150 extracts the work names included in the work contents of each of the X tasks acquired in step S22 based on the loaded list of work names (step S24). Here, if the work contents include a work name, the work name is added to the "related work" field as shown in table K in FIG. 10. If the work contents do not include a work name, a blank "-" is stored. Furthermore, in step S24, the upcoming scheduled work search unit 150 deletes records in table K in which a blank "-" is stored in the "related work" field, and creates a new table L as shown in FIG. 10.

[0083] Thereafter, the upcoming scheduled task search unit 150 judges whether extraction of N task names has been completed (step S25). If the judgment in step S25 is "NO", that is, if extraction of N task names has not been completed, the process returns to step S22. On the other hand, if the judgment in step S25 is "YES", that is, if extraction of N task names has been completed, the extraction result is returned to the main routine as the result of subroutine 02, and the process returns to the main routine.

[0084] [Subroutine 03] Next, a description will be given of subroutine 03 called in step S10 of Fig. 6. Fig. 16 is a flow diagram showing subroutine 03. Subroutine 03 is a process for sorting and displaying the search results (document addresses and document contents) obtained in step S5 in descending order of the frequency of occurrence of the task name selected by the worker.

[0085] First, the estimated task order sorting unit 170 extracts only search results in which the related task name selected by the worker 102 in the related task selection section 1510 on the screen 1410 in step S9 of Fig. 6 is included in the 1st to Nth ranked related tasks (step S31). In this embodiment, if the worker 102 selects "dealing with malfunctions", documents that do not include "dealing with malfunctions" in "related tasks" in table I of Fig. 9 are excluded from the search results.

[0086] Next, the estimated task order sorting unit 170 sorts the search results extracted in step S31 in descending order of the frequency of occurrence of the related task selected by the operator 102 (in this embodiment, "dealing with malfunctions") (step S32).

[0087] The search results sorted in step S32 are then transmitted to the personal terminal 100 via the communication units 190 and 125, and the display unit 105 displays the search results (step S33). After the display unit 105 displays a screen 1410 shown in Fig. 13, the process returns to the main routine.

[0088] As described above, in this embodiment, the multiple documents searched and extracted by the full-text search unit can be rearranged using the related tasks indicated by the document being viewed by the worker and the related tasks indicated by the work content that the worker is planning to perform in the future. This makes it possible to efficiently provide the worker with documents containing work information suitable for future work that the worker may perform in the future. As a result, even if the future work content of the worker changes from the previous work content, documents suitable for the work scheduled in the future can be provided to the worker.

[0089] Furthermore, in this embodiment, the task narrowing unit extracts tasks that can be performed by the worker based on the qualifications he or she holds, and eliminates documents that include task information that is not related to the tasks that the worker can perform from the search results. This makes it possible to provide the worker with documents that correspond to the qualifications he or she holds.

[0090] The above-mentioned embodiment has been described in detail to clearly explain the present invention, and is not necessarily limited to having all of the configurations described. For example, it is possible to replace a part of the configuration of the embodiment with another configuration, and it is also possible to add another configuration to the configuration of the embodiment. Also, it is possible to add, delete, or replace a part of the configuration of the embodiment with another configuration. [Explanation of symbols]

[0091] 1...Business information search system, 100...Personal terminal, 102...Worker, 105...Display unit, 120...Input unit, 125...Communication unit, 130...Center side system, 135...Temporary storage unit, 137...Full text search unit, 140...Implemented work narrowing unit, 145...Human resources management database, 150...Right-up scheduled work search unit, 155...Schedule database, 160...Document topic estimation unit, 165... document database, 170... estimated task order sorting section, 175... task master DB, 190... communication section, 145... human resources management DB, 155... schedule DB, 165... document DB, 175... task master DB

Claims

1. In a work information search system that provides work information to workers, a full-text search unit that performs a full-text search using a word selected by an operator as a search key and extracts documents that contain business information that includes the search key; an immediate scheduled work search unit that searches for work content that is scheduled in the immediate future and is ahead of the worker's current time; a document topic estimation unit that estimates a related task indicated by a document being viewed by the worker; an estimated task order sorting unit that sorts search results extracted by the full-text search unit from related tasks indicated by the task contents searched for by the immediately upcoming scheduled task search unit and related tasks indicated by the document to be viewed; Business information search system.

2. A business master database is provided that contains data in which a plurality of business names are set for each related business; The document topic estimation unit refers to the task master database, and estimates the related tasks indicated by the viewed document by counting the number of occurrences of task names that appear in the text data of the viewed document based on task names set for each related task.

2. A business information search system according to claim 1.

3. A business master database is provided that contains data in which a plurality of business names are set for each related business; The immediately scheduled task search unit refers to the task master database, and estimates related tasks indicated by the task contents from task names included in the task contents based on task names set for each related task.

3. A business information search system according to claim 1 or 2.

4. A business master database is provided that contains data in which a plurality of business names are set for each related business; The document topic estimation unit refers to the task master database, and counts the number of occurrences of task names that appear in the text data of each document extracted by the full-text search unit based on task names set for each related task, thereby estimating related tasks indicated by each document from top 1 to top N.

2. A business information search system according to claim 1.

5. The estimated task order sorting unit Among the multiple related tasks indicated by the document to be viewed, the multiple related tasks are ranked in order of the number of occurrences of the task name and the task indicated by the work content scheduled for the closest time to the current time among the multiple related tasks indicated by the scheduled work content. The business information search system according to claim 3.

6. The estimated task order sorting unit sorts the documents extracted by the full-text search unit in order of the frequency of occurrence of task names related to the related tasks selected by the worker from among the ranked related tasks.

6. A business information search system according to claim 5.

7. and an operation narrowing unit that extracts operations that can be performed by the worker and extracts documents related to the operations that can be performed from the documents extracted by the full-text search unit based on the extracted operations that can be performed by the worker.

2. A business information search system according to claim 1.

8. A full-text search is performed using the word selected by the worker as a search key to extract documents containing business information including the search key; Search for work content scheduled in the near future that is ahead of the worker's current time, Estimate the related work indicated by the documents being viewed by the worker, The documents extracted by the full-text search are sorted based on the related tasks indicated by the searched work contents and the related tasks indicated by the viewed documents. How to search for business information.

Images