JP2009237736A - Work support device, task management method, and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a work support device, a method, and a program capable of coping with respect to an unknown task in a flexible manner. <P>SOLUTION: It is determined whether a work document with a description requesting predetermined work has been viewed, based on the document identification information operated by each user. A work content common to a plurality of users is determined from the content of each user's work performed, after the work document has been viewed, and the common work content is associated with the document identification information of the work document related to this task, and managed as a common task which is imposed on a plurality of users. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to a work support apparatus, a task management method, and a program.

  Conventionally, the work (task) related to a specific business and the work actually performed by the user are performed by manually inputting a work state for each task. Moreover, in patent document 1, the rule (task determination rule) for determining the operation | work relevant to a task among the operations which a user actually performs is defined beforehand, and the operation | work which adapts to this task determination rule is detected. Thus, a technique for managing the progress of tasks by managing them is disclosed. Patent Document 2 discloses a technique for accumulating an operation history from each client terminal to shared information, and presenting a dependency relationship between users as a data flow based on the operation history. .

JP 2004-244620 A JP 2003-132192 A

  However, the above-described manual management method has a problem that it is inefficient because the load for inputting the work procedure is large and the input of the work procedure becomes more complicated as the task becomes more complicated. Further, in the technique described in Patent Document 1, since task determination is performed according to the task determination rule described above, it is a case where work contents common to a plurality of users are instructed, and the task determination rule is set for each user. Since it is necessary to define it explicitly, there is a problem that it is not possible to flexibly cope with an unknown task.

  Moreover, in the technique described in Patent Document 2, every time an operation is performed on shared information from each user, it is possible to present a change transition (data flow) of the shared information. In order to manage, a business flow that explicitly defines the contents of the task is required separately. Therefore, like Patent Document 1, there is a problem that an unknown task cannot be flexibly handled.

  The present invention has been made in view of the above, and an object of the present invention is to provide a work support apparatus, method, and program capable of flexibly handling unknown tasks.

  In order to solve the above-described problems and achieve the object, the present invention includes a first storage means for storing a work document in which a text requesting a predetermined work is described in association with document identification information, and a plurality of users The work contents of the documents operated by each are stored in the second storage means and the second storage means for sequentially storing the document identification information of the documents and the work history associated with the user identification information of the operated user. The work history including the same document identification information as the work document stored in the first storage means, the browsing work determination means for judging that the work document is the browsing work, and the browsing work after the browsing work Of the work histories stored in the second storage means, related work detection means for detecting a work history including the same user identification information as the browsing work as a related work related to the browsing work; Third storage means for storing the work content included in the continuous work and the same user identification information as the browsing work in association with the document identification information included in the browsing work related to the related work, and the third storage Among the related work stored in the means, common work determination means for judging common work contents from related work having the same document identification information and different user identification information, and the common work contents to a plurality of users As a common task that is imposed, a management unit that manages in association with document identification information of a work document related to the task is provided.

  Further, the present invention is a task management method executed by a work support device, wherein the work support device stores a work document in which a text requesting a predetermined work is described in association with document identification information. And a second storage control unit that stores the work contents of the document operated by each of a plurality of users as a work history associated with the document identification information of the document and the user identification information of the operated user. Document identification information identical to the work document stored in the first storage means out of the work history stored in the second storage means by the second storage step that is sequentially stored in the second storage means and the browsing work determination means The browsing work determination step of determining the work history including the browsing work of the work document, and the related work detection means, among the work histories stored in the second storage means after the browsing work, the browsing work The related work detection step of detecting a work history including the same user identification information as a related work related to the browsing work, and the third storage control means are the same as the work content and the browsing work included in the related work A third storage step of storing the user identification information in the third storage means in association with the document identification information included in the browsing work related to the related work, and the common work determination means is stored in the third storage means A common work determination step for determining a common work content from related work having the same document identification information and different user identification information, and the management means assigns the common work content to a plurality of users. And a management step of managing in association with the document identification information of the work document related to the task.

  According to the present invention, a computer including a first storage unit that stores a work document in which a text requesting a predetermined work is described in association with document identification information is stored in a document operated by each of a plurality of users. Second storage control means for sequentially storing the contents in the second storage means as work history associated with the document identification information of the document and the user identification information of the operated user, and the work stored in the second storage means Of the histories, a browsing work determination unit that determines that a work history including the same document identification information as the working document stored in the first storage unit is a browsing work of the working document, and the second and subsequent browsing works. Among the work histories stored in the storage means, related work detection means for detecting a work history including the same user identification information as the browsing work as a related work related to the browsing work, Third storage control means for storing the work content included in the continuous work and the same user identification information as the browsing work in association with the document identification information included in the browsing work related to the related work in the third storage means And common work determination means for judging common work contents from related work having the same document identification information and different user identification information among the related work stored in the third storage means, and the common work As a common task assigned to a plurality of users, the content is made to function as a management unit that manages the content in association with document identification information of a work document related to the task.

  According to the present invention, the common work content is determined for each work document from the work content of each user performed after the work document browsing work, and the work content is determined as a common task assigned to a plurality of users. It is managed in association with the document identification information related to the contents. This makes it possible to determine that the work content imposes work common to multiple users without specifying the work content required by the work document, so there is no need to explicitly define a task for each user. It is possible to respond flexibly to these tasks.

  DESCRIPTION OF EXEMPLARY EMBODIMENTS Hereinafter, exemplary embodiments of a work support device, a task management method, and a program will be described in detail with reference to the accompanying drawings. In the embodiment described below, an example in which the present invention is applied to a server device (work support server) will be described, but the target to be applied is not limited to this aspect.

[First Embodiment]
FIG. 1 is a block diagram showing a configuration of a work support system including a work support server 200 according to the first embodiment. As shown in the figure, the work support system includes a plurality of user terminals 100 and a work support server 200, and each device is connected to be communicable via a network N such as the Internet or an intranet. Yes. Note that the number of user terminals 100 connected to the network N is not particularly limited.

  FIG. 2 is a block diagram showing functional configurations of the user terminal 100 and the work support server 200 shown in FIG. Hereinafter, functional units of each device will be described.

  The user terminal 100 is a terminal device such as a PC (Personal Computer) or a portable terminal operated by the user. By operating an input device (not shown) such as a mouse or a keyboard provided in the user terminal 100, the user can perform operations such as browsing and creating documents and browsing Internet sites. In addition, the user terminal 100 can exchange e-mail with an external device or access a shared document published on the network N according to an operation from the user.

  As shown in FIG. 2, the user terminal 100 includes a user ID input unit 11, a work content recording unit 12, and a work support information presentation unit 13. Note that each of the user terminals 100 illustrated in FIG. 1 has the configuration illustrated in FIG.

  The user ID input unit 11 receives a user ID input from the user of the user terminal 100 and outputs it to the work content recording unit 12. Here, the “user ID” is identification information for uniquely identifying each user, and is given in advance for each user. In addition, although it is possible to set arbitrary character strings etc. to a user ID, this embodiment demonstrates the aspect using an e-mail address.

  Each time the user terminal 100 is operated by the user, the work content recording unit 12 records the work content performed by the operation. Specifically, the work content recording unit 12 includes the user ID input from the user ID input unit 11, the date and time when the work was started (work start date and time), and the date and time when the work was finished (work end). Date and time) and sequentially transmitted to the work support server 200 as a user-specific work history. Note that the time information serving as an index for the work start date and time and the work end date and time is obtained from a date and time measurement device (not shown) that measures the date and time.

  Here, the “work content” can include arbitrary information. For example, the name of the application in which the operation was performed (active application), the name and URL of the document targeted for the operation, the title of the mail (operation target), and the like can be given. When the screen is displayed as a window, the title of the window displayed by the user's operation (window title) and information indicating whether or not the scroll operation has been performed in this window (scroll presence / absence) are used as work contents. It may be recorded. If a document ID (to be described later) is assigned to the operation target document, the document ID is included in the work content and recorded. Of the above-described information, the operation target and the document ID function as document identification information for uniquely identifying the document operated by the user.

  The work support information presentation unit 13 displays the work support information provided from the work support server 200 on a display device such as a liquid crystal display (LCD) (not shown). The display form is not particularly limited. For example, a user interface such as a text message or an icon may be displayed.

  Next, the work support server 200 will be described. The work support server 200 is a server device that manages the work history of each user who operates the user terminal 100 and provides work support information described later to each user.

  As shown in FIG. 2, the work support server 200 includes a user-specific work history storage unit 21, a work document storage unit 22, a related work determination processing unit 23, a work deadline acquisition unit 24, and a task registration unit 25. A task work time calculation unit 26, a task management unit 27, and a work support notification processing unit 28.

  The user-specific work history storage unit 21 is a database for storing and managing data, and sequentially stores the user-specific work history transmitted from each of the user terminals 100.

  FIG. 3 is a diagram illustrating an example of a user-specific work history stored in the user-specific work history storage unit 21. As shown in the figure, the user-specific work history is composed of a plurality of items, and each row represents one user-specific work history.

  Among the plurality of items, “user ID” stores the user ID of the user who performed the operation on the user terminal 100. The “work start date” and “work end date” are items corresponding to the work start date and the work end date recorded by the work content recording unit 12, respectively, and the date when the work was started on the user terminal 100. The date and time when the work is completed are stored.

  The “active application” is an item corresponding to the active application recorded in the work content recording unit 12 and stores the name of the application on which the operation was performed. The “operation target” is an item corresponding to the operation target recorded by the work content recording unit 12, and stores the name of the document, URL, e-mail title, and the like as the operation target. “Window title” is an item corresponding to the window title recorded by the work content recording unit 12, and stores the title of the window displayed on the user terminal 100. “Scroll presence / absence” is an item corresponding to the presence / absence of scrolling recorded by the work content recording unit 12 and stores information indicating whether or not a scroll operation has been performed.

  The “document ID” is an item corresponding to the document ID recorded by the work content recording unit 12 and stores a document ID (described later) assigned to the operation target document. If no document ID is assigned, this item is null.

  Returning to FIG. 2, the work document storage unit 22 is a database or the like that stores and manages data, and is a document that requests (requests) a predetermined work transmitted from a specific user to the user of the user terminal 100. Accumulate. Hereinafter, a document stored in the work document storage unit 22 is referred to as a “work document”.

  Various methods can be used to store the work document in the work document storage unit 22. For example, it is good also as an aspect which accumulate | stores the electronic mail which requests the predetermined | prescribed work transmitted by the mailer as a work document. In this case, it is assumed that an e-mail transmitted to each user is separately transmitted to the work support server 200, and the work document storage unit 22 stores the received e-mail as a work document. In the configuration of the present embodiment, the work document storage unit 22 extracts and stores predetermined items from the header information and the text that make up the e-mail.

  The e-mail serving as the work document may be explicitly transmitted to the work support server 200, but is not limited thereto. For example, by making the work support server 200 function as a mail server or a mail proxy, The work support server 200 may be provided on a communication path for sending and receiving electronic mail. Moreover, it is good also as an aspect which transmits an email directly from the work support server 200.

  Alternatively, a message for requesting a predetermined work transmitted as IM (Instant Messenger) may be stored as a work document. In this case, similarly to the electronic mail, the IM transmitted to each user is separately transmitted to the work support server 200, and the work document storage unit 22 stores the received IM as a work document.

  The work document storage unit 22 may be linked to the electronic bulletin board function, scheduler function, workflow function, etc. of the groupware. In this case, the work document storage unit 22 is registered in the electronic bulletin board, schedule table, or the like. Article contents are stored as work documents. Note that the device serving as the groupware server may be the work support server 200 or another device.

  Alternatively, the work document storage unit 22 may be disclosed on the network N, and a document for requesting a predetermined work shared as a shared document from the user terminal 100 may be stored as a work document. In the case of this aspect, the person who is requested to work by the work document is not specified.

  Hereinafter, in the configuration of the present embodiment, an aspect in which electronic mail is used as a work document will be described. FIG. 4 is a diagram illustrating an example of a work document stored in the work document storage unit 22. As shown in the figure, the work document is composed of a plurality of items, and each line represents one work document.

  Among the plurality of items, “document ID” includes identification information for document management (hereinafter referred to as document) automatically assigned to the work document storage unit 22 when the work document is stored in the work document storage unit 22. ID) is stored. When an e-mail is transmitted via the work support server 200, the work document storage unit 22 adds a document ID to the e-mail and then transfers the e-mail to the user terminal 100. .

  Further, in the “message ID”, the message ID of the electronic mail given at the time of transmission of the electronic mail is stored as identification information. The “sender” stores the email address of the sender of the email, that is, the user who is the requester of the work execution. The “destination” stores the mail address of the user who is the destination of the e-mail, that is, the user who is the work destination. “Subject” stores the subject (Subject) of the e-mail. In the “text”, a text requesting a predetermined work described in the text of the e-mail is stored. Of the above-described information, the document ID, subject, and text function as document identification information that uniquely identifies a work document.

  Returning to FIG. 2, the related work determination processing unit 23 detects a common work content from the work history for each user after browsing the work document stored in the work history storage unit 21 for each user, and the work content is detected by a plurality of users. Are managed in association with the document ID of the corresponding work document.

  Here, as illustrated in FIG. 2, the related work determination processing unit 23 includes a work document browsing determination unit 231, a document related work detection unit 232, a document related work storage unit 233, and a work target person acquisition unit 234. The common work determination unit 235 is provided.

  The work document browsing determination unit 231 sequentially refers to the user-specific work history stored in the user-specific work history storage unit 21 in chronological order, and based on the work contents included in the user-specific work history, It is determined whether or not each user has browsed any work document (e-mail) stored in the work document storage unit 22. Hereinafter, a user-specific work history including work contents related to work document browsing is referred to as “browsing work”.

  Specifically, the work document browsing determination unit 231 includes identification information for identifying an operation target such as a document ID and a title included in the user-specific work history, a document ID of the work document, and a title described in the text. Are compared with the identification information for identifying the work document, and if both the identification information match, the user-specific work history is determined as the browsing work.

  Note that the condition for determining whether or not browsing has been performed is not limited to the above example. For example, “active application: mailer” is active for a predetermined time (for example, 5 minutes) or longer, and a document having the same document ID or subject (title) as the work document stored in the work document storage unit 22 is “document ID”. Alternatively, a user-specific work history that is “work target” and that is “scroll presence / absence: yes” may be used as a determination condition for viewing work. Here, the active application active time is a value calculated from the difference between the work end date and time and the work start date and time.

  When the document ID is not described in the user-specific work history determined as the browsing work, the work document browsing determination unit 231 reads the document ID of the work document corresponding to the browsing work from the work document storage unit 22 and browses it. It is good also as an aspect registered into the item of "document ID" which comprises work.

  The document-related work detection unit 232 extracts a user-specific work history that conforms to a predetermined condition from user-specific work histories accumulated after the browsing work, and as a work content related to the browsing work, The document ID is registered in the document related work storage unit 233 in association with the document ID.

  Specifically, the document related work detection unit 232 includes a browsing history storage unit 2321, a new work detection unit 2322, and a confirmation work detection unit 2323, and the operations of the new work detection unit 2322 and the confirmation work detection unit 2323. The number of browsing of the work document serving as the index is counted for each document ID and user ID, and is registered in the browsing history storage unit 2321 in association with the work start date and time at the first time.

  The browsing history storage unit 2321 is a database or the like that stores data, and associates the document ID registered from the document related work detection unit 232 with the user ID, the work start date and time, and the number of times of browsing. Accumulate as history.

  FIG. 5 is a diagram illustrating an example of a browsing history stored in the browsing history storage unit 2321. As shown in the figure, the browsing history is composed of items of document ID, user ID, work start date and time, and the number of browsing times, and each row represents one browsing history.

  Returning to FIG. 2, the new work detection unit 2322 is based on the work contents of the user-specific work history located before and after the first-time browsing work among the user-specific work histories stored in the user-specific work history storage unit 21. The user-specific work history of the work contents performed for the first time after the browsing work is extracted for each user. Here, the determination as to whether or not the browsing operation is the first time is performed based on the number of browsing times included in the browsing history.

  Also, the new work detection unit 2322 registers the extracted user-specific work history in the document related work storage unit 233 as a related work related to the browsing work in association with the document ID of the work document related to the browsing work.

  FIG. 6 is a diagram for explaining the operation of the new work detection unit 2322, and schematically shows user-specific work histories for three users (Suzuki, Takahashi, Yamada). In the figure, the passage of time is shown from the top to the bottom of the drawing. Each rectangular area indicated by A to C represents the work content represented by each user's work history, and the symbols A to C represent the type of work content. Here, it is assumed that the work content of B is a browsing work, and this work content is represented as a browsing work B. The work contents of A and C are represented as work A and work C, respectively.

  In FIG. 6, focusing on “user name: Suzuki”, it can be seen that the work is not performed before the browsing work B and the work C is performed after the browsing work B. In this case, the new work detection unit 2322 determines the work performed for the first time after the browsing work B as the work C, and extracts the user-specific work history corresponding to the work C from the user-specific work history storage unit 21 as a related work. . Similarly, regarding “user name: Yamada”, it is determined that the work A is the work that was performed for the first time after the browsing work B, and the user-specific work history corresponding to the work A is used as the related work, and the user-specific work history storage unit 21. Extract from

  On the other hand, when attention is paid to “user name: Takahashi”, it is understood that the work A is performed before and after the browsing work B, and the work C is performed thereafter. In this case, since the work located before and after the browsing work B has the same work content, the new work detection unit 2322 excludes the work A before and after the browsing work B and starts the subsequent work C after the browsing work B for the first time. Judged as work done. Then, the new work detection unit 2322 extracts the user-specific work history corresponding to the work C from the user-specific work history storage unit 21 as related work.

  The new work detection unit 2322 continues to extract new work after the browsing work B until a predetermined time (new work detection time) elapses. The new work detection time can be arbitrarily set, and for example, 1 hour, 3 hours, 6 hours, or the like can be set. In addition, the number of user-specific work histories extracted as related work can be arbitrarily set.

  Returning to FIG. 2, when the browsing operation for the same document ID and user ID is performed a predetermined number of times, the confirmation work detection unit 2323 determines that the predetermined number of browsing operations is a work document confirmation operation, and this predetermined operation is performed. The user-specific work history accumulated after the number of browsing work is extracted as a related work for each user. In addition, although the numerical value (for example, 3 times etc.) used as the index | index of browsing frequency determination shall be predetermined, arbitrary values can be set.

  Also, the confirmation work detection unit 2323 registers the extracted user-specific work history in the document related work storage unit 233 as work contents related to the work document of the browsing work in association with the document ID of the work document related to the browsing work. .

  Note that the confirmation work detection unit 2323 continues the above-described processing until a predetermined time (confirmation operation detection time) elapses after the first browsing work. The confirmation operation detection time can be arbitrarily set. For example, 1 hour, 3 hours, 6 hours, or the like can be set. In addition, the number of user-specific work histories extracted as related work can be arbitrarily set.

  The document-related work storage unit 233 is a database or the like for storing and managing data, and associates a combination of the document ID extracted from the document-related work detection unit 232 with the user-specific work history, and browses the document ID. Accumulate as work related to documents related to work.

  FIG. 7 is a diagram showing an example of document related work stored in the document related work storage unit 233. As shown in the figure, the document-related work is composed of a document ID and a user-specific work history, and each row represents one document-related work. Of the items constituting the document-related work, “user ID”, “work start date / time”, “work end date / time”, “active application”, “operation target”, “window title”, “scroll presence / absence” This is the same as each item of the user-specific work history extracted by the document-related work storage unit 233, but “document ID” is the document ID of the work document related to the browsing work detected when this user-specific work history is extracted. It has become.

  The work target person acquisition unit 234 acquires, for each work document stored in the work document storage unit 22, the user ID of the work target person who is requested to work on the work document. In this embodiment, an application example related to electronic mail is described. In this case, the mail address stored in “destination” is acquired from each work document (see FIG. 4).

  When a work document other than e-mail is used, or when the transmission destination of the work document cannot be specified, the work for the same work document can be performed by using the user-specific work history stored in the user-specific work history storage unit 21. The identification information of the target user can be acquired. Specifically, the same work document is specified from the “work target” and “document ID” included in each user's work track, and the e-mail address is determined from the “user ID” of the user work track related to this work document. By acquiring, the identification information of the work target user is acquired.

  The common work determination unit 235 corresponds to a combination of the document ID of the work document acquired by the work target person acquisition unit 234 and the user ID of the work target person from the document related work stored in the document related work storage unit 233. Each of the document-related work including the item to be specified is specified. Specifically, the common work determination unit 235 refers to the user ID and document ID included in each document-related work, and the document relation that matches the set of the document ID and user ID acquired by the work target person acquisition unit 234. Identify work.

  In addition, the common work determination unit 235 performs the work contents for each user ID based on the work contents of the specified document-related work (“active application”, “operation object”, “window title”, “scroll presence”, etc.). Is determined for each identical document ID. Hereinafter, the common work content is referred to as “common work”.

  Here, it is possible to arbitrarily set an index for determining whether or not it is a common work. For example, it may be determined as common work when active applications are common, or may be determined as common work when active applications are common and operation targets are common.

  Even if it is determined that the work is a common work, if the work time derived from the difference between the work end date and the work start date is within one minute, such as a work time is not realistic, the common work May be excluded. Note that the work time serving as an index of work to be excluded can be arbitrarily set.

  Moreover, it is good also as determining whether it is common work by the number of users (user ID) with whom work is common. For example, if 3 out of 5 tasks are common, it indicates that 60% is common, but if the threshold is set to 80% or more, the common work determination unit 235 indicates that the work is not common. judge. When 50% or more is set as the threshold, the common work determination unit 235 determines that the work is common. The threshold value can be set arbitrarily.

  Further, in a work document in which a user having a job title or age of a certain level or more is a work target person, it is necessary to specify a document-related work that satisfies this condition. In this case, by separately storing a table in which the information indicating the job title and age of each user and the user ID are associated with each other in the document-related work storage unit 233, the job title, age, and the like of each user can be stored from this table. Can be determined. Moreover, as another aspect, it is good also as an aspect comprised so that the title, age, etc. of each user may be input from the user ID input part 11. FIG. Moreover, when there are many users of a certain post or age among the users who have specified the post or age, the common work may be determined by excluding users under the post or age.

The work deadline acquisition unit 24 detects a date pattern such as “yyyy / MM / dd” or “MM month dd day” by parsing the body text of the work document stored in the work document storage unit 22,
Acquired as the work deadline for the work requested in this work document. “Yyyy” represents the year, “MM” represents the month, and “dd” represents the day.

  Further, the work deadline acquisition unit 24 outputs the work deadline acquired for each work document to the task registration unit 25 in association with the document ID of the corresponding work document. When the work deadline acquisition unit 24 fails to obtain the work deadline or determines that the work deadline is inappropriate compared to the current date, the predetermined date is set as the work deadline. It may be configured. Note that the work deadline date can be arbitrarily set. For example, it may be set three days or seven days after the current date.

  The task registration unit 25 uses the common task assigned to a plurality of users as the work content represented by the document related work for each document ID determined as the common work by the related work determination processing unit 23 (common work determination unit 235). Each determination is made, and the document ID and the work content are associated with each other and registered in the task management unit 27.

  The task registration unit 25 registers the work deadline for each document ID input from the work deadline acquisition unit 24 in the task management unit 27 in association with the corresponding document ID.

  Based on each document ID registered in the task management unit 27, the task work time calculation unit 26 refers to the document related work related to the document ID from the document related work storage unit 233, and starts the task (work). The work time required until the end is calculated for each document ID.

  Specifically, the task work time calculation unit 26 calculates the difference between the “work end date and time” and the “work start date and time” from the document related work related to the document ID for each document ID, and calculates the average of the calculated values. The value is derived as work time. Here, the average value of the calculated values is used as the work time. However, the present invention is not limited to this, and the calculated value having the longest time (or the shortest time) may be used as the work time.

  Further, the task work time calculation unit 26 registers the calculated work time for each document ID in the task management unit 27 in association with the corresponding document ID.

  The task management unit 27 is a database or the like that stores and manages data, and includes a document ID registered from the task registration unit 25, work contents, and work deadline, and a work time registered from the task work time calculation unit 26. Are stored as task information.

  FIG. 8 is a diagram illustrating an example of task information accumulated in the task management unit 27. As shown in the figure, the task information is composed of a plurality of items, and each row represents one task information.

  Among the plurality of items, “task ID” stores task management information (T001, etc.) automatically assigned by the task management unit 27 when task information is accumulated in the task management unit 27. . Further, items registered as work contents by the task registration unit 25 are stored in “document ID”, “active application”, “operation target”, “window title”, and “scroll presence / absence”. The “work time” stores the work time calculated by the task work time calculation unit 26. The “work deadline” stores the work deadline registered by the task registration unit 25.

  Returning to FIG. 2, the work support notification processing unit 28 is a functional unit that notifies the user terminal 100 (work support information presentation unit 13) of work support information related to the work document, and the work support information notification determination unit 281. And a work support information notifying unit 282.

  The work support information notification determination unit 281 determines a non-worker of a task (work content) included in the task information, and the work support information notification unit 282 indicates the user ID of the non-worker and the document ID related to the task. Output to.

  Specifically, the work support information notification determination unit 281 imposes on each work target person based on the combination of the work document (document ID) acquired by the work target person acquisition unit 234 and the work target person (user ID). The specified task is identified from the task information stored in the task management unit 27.

  In addition, the work support information notification determination unit 281 includes a user-specific work history stored in the user-specific work history storage unit 21 and a browsing of each work target detected by the work document browsing determination unit 231. Based on the work, it is determined whether or not there is a work history for each user whose work content matches the task after the browsing work of the document ID related to the task of each work subject. As a result of the determination, when it is determined that the user-specific work history having the work content matching the task does not exist in the user-specific work history storage unit 21, the work support information notification determination unit 281 performs the work target related to the user-specific work history. The task management unit 27 identifies the task information related to this task.

  In addition, the work support information notification determination unit 281 acquires the work time and the work deadline from the task information specified from the task management unit 27, and the result of adding the work time to the current date and time is approximately equal to or exceeds the work deadline. If it is determined that the user ID of the unworked person is associated with the document ID associated with the task, the user ID is output to the work support information notification unit 282.

  When the work support information notification unit 282 generates the work support information from the task information corresponding to the document ID based on the combination of the user ID and the document ID input from the work support information notification determination unit 281, the user ID Or to the user terminal 100 operated by the user having the user ID.

  Here, it is assumed that the work support information includes all or a part of each item included in the task information. The work document having the document ID included in the task information is read from the work document storage unit 22. Alternatively, it may be transmitted as work support information.

  Note that the work support information providing method from the work support information notifying unit 282 to the user terminal 100 can have various modes. For example, the work support information may be transmitted to the mail address of the user ID input from the work support information notification determination unit 281. Further, when groupware is operating on the work support server 200 or another device, the scheduler function provided by the groupware is used to determine the user ID input from the work support information notification determination unit 281. It is good also as an aspect which registers work assistance information in a schedule.

  On the other hand, in the user terminal 100 that has received the work support information, the work support information presenting unit 13 displays the work support information on a display device (not shown), thereby presenting the work support information to a user who is not yet working.

  FIG. 9 is a diagram illustrating an example of work support information displayed by the work support information presenting unit 13. Here, the work support information is presented in the area A1 located at the right end of the desktop screen. FIG. 10 is a diagram showing a display screen when work support information is provided using groupware, and shows an example of a schedule screen displayed by the work support information presenting unit 13. In this case, work support information is presented as the schedules Sc1 to Sc4 of each user (Nishimura, Kato, Imai). In addition, the presentation form of work assistance information shall not be limited to the example of FIG. 9, FIG.

  Hereinafter, the operation of the work support server 200 will be described. FIG. 11 is a diagram illustrating a procedure of work support information provision processing executed by each function unit of the work support server 200. As a premise of this process, it is assumed that the work document is stored in the work document storage unit 22 in advance. In addition, the processing related to the work target acquisition unit 234 and the work deadline acquisition unit 24, that is, the processing directly related to the work document storage unit 22, is performed in advance when the work document is stored in the work document storage unit 22. It shall be.

  First, when the user ID is input in the user terminal 100 and the operation of the user terminal 100 is started, the user-specific work history accumulation unit 21 sequentially accumulates the user-specific work history transmitted from the user terminal 100 (step S11). ).

  Subsequently, the work document browsing determination unit 231 sequentially refers to the user-specific work histories stored in the user-specific work history storage unit 21 in chronological order, and browses the work documents based on the work contents of each user-specific work history. Is determined (step S12). Here, when the browsing work cannot be confirmed (step S12; No), the work document browsing determination unit 231 refers to the next user-specific work history and repeats the process of step S12.

  On the other hand, every time the work document browsing determination unit 231 determines that the browsing work is executed in Step S12 (Step S12; Yes), the document related work detection unit 232 executes a document related work detection process (Step S13). . Note that the work document browsing determination unit 231 operates independently of the document related task detection unit 232, and thus repeats the operation of step S12 even when the browsing task is determined. Hereinafter, the document related work detection process in step S13 will be described with reference to FIG.

  FIG. 12 is a flowchart showing the procedure of the document related work detection process. First, the document-related work detection unit 232 determines whether or not the number of times of browsing work detection, that is, the number of times of browsing is the first time, for the combination of document ID and user ID included in the browsing work (step S131). Here, the determination of whether or not it is the first time may be performed based on the presence or absence of the browsing history.

  If it is determined in step S131 that it is the first time (step S131; Yes), the document related work detection unit 232 displays the number of times of browsing N (N Is an integer) and is registered in the browsing history storage unit 2321 as the browsing history of this browsing work (step S132). In step S132, “1” is set as the number of times of browsing N representing the first time.

  Subsequently, the new work detection unit 2322 executes a new work detection process (step S133). Hereinafter, the new work detection process in step S133 will be described with reference to FIG.

  FIG. 13 is a flowchart showing the procedure of the new work detection process. First, when the new work detection unit 2322 detects that a new browsing history (browsing count N = 1) is stored in the browsing history storage unit 2321 (step 1331), the user ID and the work included in the browsing history are recorded. Based on the start date and time, the browsing work corresponding to the browsing history is specified from the user-specific work history storage unit 21 (step S1332).

  Subsequently, the new work detection unit 2322 waits until the user-specific work history having the same user ID as the browsing work is accumulated in the user-specific work history accumulation unit 21 after the browsing work specified in step S1332 (step S1332). S1333; No). Here, when the new work detection unit 2322 confirms that a new user-specific work history has been stored in the user-specific work history storage unit 21 (step S1333; Yes), the user-specific work history is read in chronological order ( Step S1334).

  Next, the new work detection unit 2322 compares the work start date and time included in the browsing history detected in step S1331 with the work start date and time included in the user-specific work history read in step S1334 (step S1335), and this difference Is within a preset time (step S1336). Here, when it is determined that the difference between the two dates exceeds a preset time (step S1336; No), the process proceeds to step S12 in FIG.

  On the other hand, if it is determined in step S1336 that the difference between the two dates is within a preset time (step S1336; Yes), the new work detection unit 2322 is the same as the user ID included in the browsing work specified in step S1332. The user-specific work history stored immediately before the browsing work is specified from the user-specific work history storage unit 21 (step S1337).

  Subsequently, the new work detection unit 2322 determines whether or not the work content of the user-specific work history read in step S1334 is different from the work content of the user-specific work history specified in step S1337 (step S1338).

  If it is determined in step S1338 that the two work contents match (step S1338; No), the process returns to step S1333 again. If it is determined in step S1338 that the contents of both tasks are different (step S1338; Yes), the new work detection unit 2322 includes the user-specific work history read in step S1334 in the browsing history detected in step S1331. The document ID is stored in the document-related work storage unit 233 in association with the document ID (step S1339), and the process proceeds to step S12 in FIG.

  Returning to FIG. 12, when it is determined in step S131 that the number of times of browsing work detection is the first or more (step S131; No), the document-related work detection unit 232 browses corresponding to the document ID and user ID of this browsing work. The number of browsing times N included in the history is incremented by 1 (step S134).

  Subsequently, the confirmation work detection unit 2323 executes confirmation operation detection processing for the browsing work detected in step S12 (step S135). Hereinafter, the confirmation work detection process in step S135 will be described with reference to FIG.

  FIG. 14 is a flowchart showing the procedure of the confirmation work detection process. First, when the confirmation work detection unit 2323 detects that one of the browsing histories stored in the browsing history storage unit 2321 is updated among the browsing histories having the browsing count N of 2 or more (step) 1351), the browsing work related to the browsing history detected this time in step S12 is specified from the user-specific work history storage unit 21 (step S1352).

  Next, the confirmation work detection unit 2323 compares the work start date and time included in the browsing history detected in step S1351 with the work start date and time of the user-specific work history specified in step S1352 (step S1353). It is determined whether or not the difference is within a preset time (step S1354). Here, if it is determined that the difference between the two dates exceeds a preset time (step S1354; No), the process immediately proceeds to step S12 in FIG.

  On the other hand, when it is determined in step S1354 that the difference between both dates and times is within a preset time (step S1354; Yes), the confirmation work detection unit 2323 has a value of the number of browsing times N included in the browsing history detected in step S1351. It is determined whether or not the number exceeds a preset number (step S1355). Here, when it is determined that the value of the browsing count N is equal to or less than the preset count (step S1355; No), the process proceeds to step S12 in FIG.

  If it is determined in step S1355 that the value of the browsing count N exceeds the preset count (step S1355; Yes), the confirmation work detection unit 2323 is included in the browsing work read in step S1352. The user-specific work history that is the same as the user ID and accumulated after the browsing work is extracted from the user-specific work history storage unit 21 (step S1356).

  Next, the confirmation work detection unit 2323 stores the user-specific work history extracted in step S1356 in the document-related work storage unit 233 in association with the document ID included in the browsing history detected in step S1351 (step S1357). The process proceeds to step S14 in FIG.

  Returning to FIG. 11, the common work determination unit 235 includes a document-related work including items corresponding to a combination of the work document (document ID) acquired by the work target person acquisition unit 234 and the work target person (user ID). Is identified from the document-related work accumulation unit 233 (step S14).

  Subsequently, the common work determination unit 235 determines the common work contents (common work) for each user ID based on the work contents (active application, operation target, window title, etc.) of each document-related work specified in step S14. A determination is made for each identical document ID (step S15).

  Next, the task registration unit 25 registers the common work for each document ID determined in step S15 in the task management unit 27 in association with the work deadline for each document ID input from the work deadline acquisition unit 24 (step S16). ).

  Next, the task work time calculation unit 26 calculates the work time required for the task for each document ID based on the work start date and time and the work end date and time of the document related work related to each document ID stored in the task management unit 27. (Step S17), the work time is associated with the corresponding document ID and registered in the task management unit 27 (step S18).

  Subsequently, the work support information notification determination unit 281 executes a work support information notification determination process based on the task information accumulated in the task management unit 27 (step S19). Hereinafter, the work support information notification determination process in step S19 will be described with reference to FIG.

  FIG. 15 is a flowchart showing the procedure of the work support information notification determination process. First, the work support information notification determination unit 281 receives each work target from the task management unit 27 based on the combination of the work document (document ID) acquired by the work target person acquisition unit 234 and the work target person (user ID). Task information related to the person is specified (step S191).

  Next, the work support information notification determination unit 281 starts the work for each document ID and user ID included in the browsing history, the work history for each user stored in the work history storage unit 21 for each user, and the browsing history. Based on the date and time, each work person in charge identifies each browsing work in which the work document related to his / her task has been browsed (step S192).

  Subsequently, the work support information notification determination unit 281 has a user-specific work history including work contents that match the tasks assigned to each work person after the browsing work specified for each work person in step S192. It is determined whether or not to do. (Step S193) Here, regarding the user-specific work histories of all work subjects, if the existence of work content that matches the task is confirmed (Step S193; Yes), the process returns to Step S12 in FIG.

  On the other hand, when it is determined in step S193 that there is no work content that matches the task in the user-specific work history of any work subject (step S193; No), the work support information notification determination unit 281 When the target person is set as a non-worker (step S194), task information corresponding to the task assigned to the non-worker is read from the task management unit 27 (step S195).

  Next, when the work support information notification determination unit 281 adds the current date and time to the work time included in the task information read in step S195 (step S196), the addition result is substantially the same as the work deadline, or the work deadline. Is determined (step S197). If it is determined that the work deadline has not been reached (step S197; No), the process returns to the process of step S12 in FIG.

  On the other hand, when it is determined in step S197 that the work deadline is substantially the same or exceeds the work deadline (step S197; Yes), the work support information notification determination unit 281 determines the unworked worker set in step S193. The user ID and the document ID included in the task information read in step S195 are output as notification targets to the work support information notification unit 282 (step S198), and the process proceeds to step S20 in FIG.

  Returning to FIG. 11, when the combination of the user ID to be notified and the document ID is input from the work support information notification determination unit 281 in the process of step S19, the work support information notification unit 282 performs a task corresponding to the document ID. Work support information is generated from the information (step S20). Next, the work support information notifying unit 282 transmits the generated work support information to the notification target user ID input from the work support information notification determining unit 281 (step S21), and then ends the process.

  As described above, according to the first embodiment, a common work content is determined for each work document from the work content of each user performed after the work document is browsed, and this work content is imposed on a plurality of users. The common task is managed in association with the document ID of the work document. This makes it possible to determine that the work content imposes work common to multiple users without specifying the work content required by the work document, so there is no need to explicitly define a task for each user. It is possible to respond flexibly to these tasks.

  In addition, since work support information is sent to unworked workers who are not performing tasks among the work subjects, it is possible to notify the task non-workers of the existence of the task, and the execution of the task has not been performed. The operator can be encouraged. In addition, work support information is sent only for tasks that are determined to be approximately equivalent to or exceeding the work deadline based on the work time required for task execution. The presence of a task can be notified.

[Second Embodiment]
Next, the work support server 300 according to the second embodiment will be described. In addition, about the structure similar to 1st Embodiment mentioned above, the same code | symbol is provided and the description is abbreviate | omitted.

  FIG. 16 is a block diagram illustrating a functional configuration of the user terminal 100 and the work support server 300 according to the second embodiment. As shown in the figure, the work support server 300 includes a user-specific work history storage unit 21, a work document storage unit 22, a related work determination processing unit 23, a task registration unit 31, a task management unit 32, A work status determination unit 33 and a work support notification processing unit 34 are provided.

  The task registration unit 31 registers the common work (task) for each document ID detected by the related work determination processing unit 23 (common work determination unit 235) in the task management unit 32 in association with the corresponding document ID. The task registration unit 31 registers the work target person (user ID) for each work document (document ID) acquired by the work target person acquisition unit 234 in the task management unit 32 in association with the corresponding document ID.

  The task management unit 32 is a database or the like for storing and managing data, and stores the document ID, task (common work), and work target person registered from the task registration unit 31 as task information. In the present embodiment, the task information accumulated in the task management unit 32 deletes the items “working time” and “working period” from the task information shown in FIG. This is a configuration in which an item “work target person” is added. Here, the “work target person” stores the user ID of the work target person for each document ID acquired by the work target person acquisition unit 234. The other items are the same as those in FIG.

  The work status determination unit 33 monitors the user-specific work history stored in the user-specific work history storage unit 21, and checks whether the work content included in the user-specific work history matches the task stored in the task management unit 32. Determine whether or not.

  Specifically, when the work status determination unit 33 acquires the user ID and the work content from the user-specific work history stored in the user-specific work history storage unit 21, the task that matches the combination of the user ID and the work content. It is determined whether or not the information is registered in the task management unit 32. Note that the determination method of the match between the work content of the user-specific work history and the task information task (work content) is the same as the determination method in the common work determination unit 235.

  When the work status determination unit 33 determines that the task information corresponding to the task management unit 32 is registered, the work status determination unit 33 includes the user ID of the work target included in the task information and is included in the user-specific work history. The user ID is deleted, and the document ID and the remaining user ID included in the task information are output to the work support notification processing unit 34 as notification targets.

  The work support notification processing unit 34 is a functional unit that notifies the user terminal 100 (work support information presenting unit 13) of work support information related to a work document, and includes a work support information notification unit 341.

  Here, the work support information notification unit 341 sends a work document corresponding to the document ID from the work document storage unit 22 based on the combination of the document ID to be notified and the user ID input from the work situation determination unit 33. Obtained and transmitted to this user ID or to the user terminal 100 operated by the user of the user ID.

  In the present embodiment, only the work document is transmitted. However, the present invention is not limited to this. The task included in the task information related to the document ID to be notified is read from the task management unit 32 and is combined with the work document. It is good also as a mode which transmits.

  Hereinafter, the operation of the work support server 300 will be described. FIG. 18 is a diagram illustrating a procedure of work support information provision processing executed by each function unit of the work support server 300. As a premise of this processing, it is assumed that work documents are stored in the work document storage unit 22 in advance. Further, it is assumed that the process related to the work target person acquisition unit 234, that is, the process directly related to the work document storage unit 22, is performed in advance when the work document is stored in the work document storage unit 22. Moreover, since the process of step S31-S35 is the same as the process of step S11-S15 mentioned above, description is abbreviate | omitted.

  The task registration unit 31 associates the task (common work) for each document ID detected in step S35 with the work target (user ID) for each document ID acquired by the work target person acquisition unit 234. 32 (step S36).

  Subsequently, when the work status determination unit 33 sequentially acquires the user ID and the work content from each user work history stored in the user-specific work history storage unit 21 (step S37), the user ID and the work content. It is determined whether or not the task information that matches the combination of these is stored in the task management unit 32 (step S38).

  Note that the user-specific work history that is the acquisition target of the user ID and work content in step S37 is preferably a user-specific work history accumulated after the work start date and time of the browsing history accumulated in the browsing history accumulation unit 2321. . In this case, as in the first embodiment described above, the first browsing work can be specified based on the user ID and the work start date and time included in the browsing history.

  If it is determined in step S38 that the corresponding task information has not been accumulated (step S38; No), the process returns to step S37 again.

  On the other hand, when it is determined in step S38 that task information that matches the combination of the user ID and the work content has been accumulated (step S38; Yes), from the user ID of the work subject included in the task information. The user ID included in the user-specific work history acquired in step S37 is deleted (step S39).

  Subsequently, the work status determination unit 33 outputs the document ID included in the task information and the remaining user ID as notification targets to the work support notification processing unit 34 (step S40).

  When the combination of the user ID to be notified and the document ID is input from the work status determination unit 33 in the process of step S40, the work support information notification unit 341 uses the task information corresponding to the document ID and the work document. Work support information is generated (step S41). Next, the work support information notifying unit 282 transmits the generated work support information to the user ID input from the work status determining unit 33 (step S42), and then ends this process.

  As described above, according to the second embodiment, the common work content is determined for each work document from the work content of each user performed after the work document is browsed, and this work content can be imposed on a plurality of users. As a common task, management is performed in association with the document ID of the work document. This makes it possible to determine that the work content imposes work common to multiple users without specifying the work content required by the work document, so there is no need to explicitly define a task for each user. It is possible to respond flexibly to these tasks.

  In addition, since work support information is sent to unworked workers who do not perform tasks among the work target persons, it is possible to notify the task non-workers of the existence of the tasks and prompt the execution of the tasks. be able to.

[Third Embodiment]
Next, the work support server 400 of the third embodiment will be described. In addition, about the structure similar to 1st Embodiment mentioned above, the same code | symbol is provided and the description is abbreviate | omitted.

  FIG. 19 is a block diagram illustrating a functional configuration of the user terminal 100 and the work support server 400 according to the third embodiment. As shown in the figure, the work support server 400 includes a user-specific work history storage unit 21, a work document storage unit 22, a related work determination processing unit 23, and a work support notification processing unit 41.

  The work support notification processing unit 41 is a functional unit that notifies the work support information presenting unit 13 of the user terminal 100 of work support information, and includes a work support information notification unit 411.

  If the work support information notification unit 411 determines that the common work determined by the common work determination unit 235 is a task assigned to a plurality of users, the work document having the document ID is based on the document ID corresponding to the task. Is read from the work document storage unit 22. Also, the work support information notification unit 411 parses the body text of the read work document and performs work work for which the work document requires a date pattern such as “yyyy / MM / dd” or “MM month dd day”. Get as a deadline.

  In addition, when the work support information notification unit 411 acquires the work target person for the work document read from the work document storage unit 22 from the work target person acquisition unit 234, the work support information notification unit 411 is directed to the user ID of the work target person or the user of the user ID A part or all of the items included in the work document and the work deadline are transmitted as work support information to the user terminal 100 operated by. In this case, a scheduler function provided by the groupware may be used to register a part or all of the items included in the work document on the work deadline date.

  Hereinafter, the operation of the work support server 400 will be described. FIG. 20 is a diagram illustrating a procedure of work support information provision processing executed by each function unit of the work support server 400. As a premise of this processing, it is assumed that work documents are stored in the work document storage unit 22 in advance. Further, it is assumed that the process related to the work target person acquisition unit 234, that is, the process directly related to the work document storage unit 22, is performed in advance when the work document is stored in the work document storage unit 22. Moreover, since the process of step S51-S55 is the same as the process of step S11-S15 mentioned above, description is abbreviate | omitted.

  The work support information notifying unit 411 reads out the work document with this document ID from the work document storage unit 22 based on the document ID of the document-related work determined as the common work by the common work determination unit 235 (step S56).

  Subsequently, the work support information notification unit 411 acquires the date pattern as the work deadline by parsing the work document read in step S56 (step S57).

  Next, when the work support information notifying unit 411 acquires the work target person for the work document read out in step S56 from the work target person acquiring unit 234 (step S58), the work support information notifying unit 411 includes a part or all of the items included in the work document. Then, the work deadline acquired in step S57 is transmitted to the user ID of the work target person as work support information (step S59), and this process ends.

  As described above, according to the third embodiment, the common work content is determined for each work document from the work content of each user performed after the work document browsing operation, and this work content is imposed on a plurality of users. The common task is managed in association with the document ID of the work document. This makes it possible to determine that the work content imposes work common to multiple users without specifying the work content required by the work document, so there is no need to explicitly define a task for each user. It is possible to respond flexibly to these tasks.

  In addition, by sending part or all of the items included in the work document and the work deadline to the work target person as work support information, the existence of the task and the work deadline can be notified. The work subject can be prompted to execute the task.

[Hardware configuration of work support server]
FIG. 21 is a block diagram illustrating a hardware configuration of the work support server according to each of the first to third embodiments. As shown in FIG. 20, the work support server includes a CPU (Central Processing Unit) 51, an operation unit 52, a display unit 53, a ROM (Read Only Memory) 54, a RAM (Random Access Memory) 55, A storage unit 56 and a communication unit 57 are provided, and each unit is connected by a bus 58.

  The CPU 51 uses the predetermined area of the RAM 55 as a work area, executes various processes in cooperation with various control programs stored in advance in the ROM 54 or the storage unit 56, and comprehensively controls the operation of each part constituting the work support server. To do.

  In addition, the CPU 51 realizes each functional unit of the work support server according to the first to third embodiments described above in cooperation with a predetermined program stored in advance in the ROM 54 or the storage unit 56.

  The operation unit 52 includes various input keys, receives information input from the user as an instruction signal, and outputs the instruction signal to the CPU 51.

  The display unit 53 includes a display unit such as an LCD, and displays various information based on a display signal from the CPU 51. In addition, the display part 53 is good also as an aspect which comprises a touchscreen integrally with the operation part 52. FIG.

  The ROM 54 stores, in a non-rewritable manner, programs and various setting information for controlling the work support server.

  The RAM 55 is volatile storage means such as SDRAM, and functions as a work area for the CPU 51 and serves as a buffer.

  The storage unit 56 has a magnetically or optically recordable storage medium, and stores rewritable programs and various setting information for controlling the work support server. The storage unit 56 serves as the above-described user-specific work history storage unit 21, work document storage unit 22, browsing history storage unit 2321, document-related work storage unit 233, task management unit 27, and task management unit 32. .

  The communication unit 57 is an interface that performs communication with the user terminal 100 through a network. Specifically, the communication unit 57 receives a user-specific work history transmitted from the user terminal 100 and transmits work support information to the user terminal 100.

  Although the embodiments of the invention have been described above, the present invention is not limited to these embodiments, and various modifications, substitutions, additions, and the like can be made without departing from the spirit of the present invention.

  For example, in the above embodiment, the relationship between the user terminal 100 and the work support servers 200, 300, and 400 is a server / client type configuration. However, the present invention is not limited to this, and a P2P (Peer to Peer) type communication mode is also possible. Good.

  In addition, the program executed by the work support server of the above embodiment is provided by being incorporated in advance in the ROM 54, the storage unit 56, or the like, but is not limited thereto, and is in an installable format or an executable format. You may comprise so that a file may record and provide on computer-readable recording media, such as CD-ROM, flexible disk (FD), CD-R, DVD (Digital Versatile Disk).

  In addition, the program may be stored on a computer connected to a network such as the Internet and provided by being downloaded via the network, or provided or distributed via a network such as the Internet. May be.

It is the figure which showed the structure of the work assistance system. It is the figure which showed the functional structure of the user terminal concerning 1st Embodiment, and a work assistance server. It is the figure which showed an example of the work according to user accumulate | stored in the work log | history accumulation part according to user of FIG. It is the figure which showed an example of the work document accumulate | stored in the work document storage part of FIG. It is the figure which showed an example of the browsing history accumulate | stored in the browsing history storage part of FIG. It is a figure for demonstrating operation | movement of the new work detection part of FIG. FIG. 3 is a diagram illustrating an example of document-related work stored in a document-related work storage unit in FIG. 2. FIG. 3 is a diagram illustrating an example of task information accumulated in a task management unit 27 in FIG. 2. It is the figure which showed the example of a display of work assistance information. It is the figure which showed the example of a display of work assistance information. It is the flowchart which showed the procedure of the work assistance information provision process concerning 1st Embodiment. It is the flowchart which showed the procedure of the document related work detection process. It is the flowchart which showed the procedure of the new work detection process. It is the flowchart which showed the procedure of confirmation work detection. It is the flowchart which showed the procedure of the work assistance information notification determination process. It is the figure which showed the functional structure of the user terminal and work assistance server concerning 2nd Embodiment. It is the figure which showed an example of the task information accumulate | stored in the task management part of FIG. It is the flowchart which showed the procedure of the work assistance information provision process concerning 2nd Embodiment. It is the figure which showed the functional structure of the user terminal concerning 3rd Embodiment, and a work assistance server. It is the flowchart which showed the procedure of the work assistance information provision process concerning 2nd Embodiment. It is the figure which showed the hardware constitutions of the work assistance server.

Explanation of symbols

DESCRIPTION OF SYMBOLS 100 User terminal 11 User ID input part 12 Work content recording part 13 Work support information presentation part 200 Work support server 21 User-specific work history storage part 22 Work document storage part 23 Related work discrimination | determination process part 231 Work document browsing determination part 232 Document relation Work detection unit 2321 Browsing history storage unit 2322 New work detection unit 2323 Confirmation work detection unit 233 Document related work storage unit 234 Work target person acquisition unit 235 Common work determination unit 24 Work deadline acquisition unit 25 Task registration unit 26 Task work time calculation unit 27 Task management unit 28 Work support notification processing unit 281 Work support information notification determination unit 282 Work support information notification unit 300 Work support server 31 Task registration unit 32 Task management unit 33 Work status determination unit 34 Work support notification processing unit 341 Work support information Notification unit 400 Work support server 1 work support notification processing unit 411 work support information notification unit 51 CPU
52 Operation section 53 Display section 54 ROM
55 RAM
56 storage unit 57 communication unit 58 bus

Claims (9)

First storage means for storing a work document in which a text requesting a predetermined work is described in association with document identification information;
Second storage means for sequentially storing work contents of a document operated by each of a plurality of users as document identification information of the document and work history associated with the user identification information of the operated user;
Among the work histories stored in the second storage means, a browsing work determination means for determining a work history including the same document identification information as the work document stored in the first storage means as a browsing work for the work document. When,
Related work detection means for detecting a work history including the same user identification information as the browsing work among the work histories stored in the second storage means after the browsing work as a related work related to the browsing work; ,
Third storage means for storing the work content included in the related work and the same user identification information as the browsing work in association with the document identification information included in the browsing work related to the related work;
Of the related work stored in the third storage means, common work determination means for determining common work contents from related work having the same document identification information and different user identification information;
A management means for managing the common work content in association with document identification information of a work document related to the task as a common task assigned to a plurality of users;
A work support apparatus comprising:   The related work detection means includes a work history including work contents different from a work history stored immediately before the browsing work among work histories stored in the second storage means after the browsing work. The work support apparatus according to claim 1, wherein the work support apparatus is detected as a related work.   When the related work detection means detects again the browsing work that includes the same document identification information as the browsing work and includes the user identification information after the browsing work, the related work history is stored in the related work history. The work support apparatus according to claim 1, wherein the work support apparatus is detected as a work. A work target person specifying means for specifying the user identification information described in the work document as a work target person of the work document;
The work support apparatus according to claim 1, wherein the common work determination unit determines common work contents from related work including the work target person. Generating means for generating work support information from the work document and / or the task related to the work document;
Providing means for providing the work support information to a work target person of the work document;
The work support apparatus according to claim 4, further comprising: Among the work histories including the document identification information of the same work document stored in the second storage means, the user identification of the work history including the work target person of the work document and not including the task related to the work document. A non-worker determination means for determining information as a non-worker of the task;
Further comprising
The generation means generates work support information from a task related to the unworked person and / or a work document related to the task,
The work support apparatus according to claim 5, wherein the providing unit provides work support information to the unworked person. The work document includes information indicating a work due date of the work, and the work content includes at least a work start date and time when the user started work and a work end date and time when the work is finished,
A work due date obtaining means for obtaining a work due date from the work document;
Work time calculation means for calculating the work time required for the task from the difference between the work start date and time and the work end date and time included in the work content that matches the task,
Providing control means for controlling whether or not to provide the work support information according to a difference between a date and time obtained by adding the current date and time to the work time and the work due date acquired from a work document related to the task;
The work support apparatus according to claim 6, further comprising: A task management method executed by a work support device,
The work support device includes first storage means for storing a work document in which a text requesting a predetermined work is described in association with document identification information,
The second storage control means sequentially stores the work contents of the document operated by each of the plurality of users in the second storage means as the work history associated with the document identification information of the document and the user identification information of the operated user. A second storage step to perform,
The browsing work determination means uses a work history including the same document identification information as the work document stored in the first storage means among the work histories stored in the second storage means as a browsing work of the work document. A browsing operation determination process for determining,
The related work detection means detects a work history including the same user identification information as the browsing work among the work histories stored in the second storage means after the browsing work as a related work related to the browsing work. Related work detection process to
Third storage control means associates the work content included in the related work and the same user identification information as the browsing work with the document identification information included in the browsing work related to the related work. A third storage step stored in
A common work determination step of determining a common work content from related work including the same document identification information and different user identification information among the related work stored in the third storage means;
A management step in which the management means manages the common work content as a common task imposed on a plurality of users in association with document identification information of a work document related to the task;
A task management method comprising: A computer having first storage means for storing a work document in which a text requesting a predetermined work is described in association with document identification information;
Second storage control means for sequentially storing work contents of a document operated by each of a plurality of users in the second storage means as document identification information of the document and work history associated with the user identification information of the operated user; ,
Among the work histories stored in the second storage means, a browsing work determination means for determining a work history including the same document identification information as the work document stored in the first storage means as a browsing work for the work document. When,
Related work detection means for detecting a work history including the same user identification information as the browsing work among the work histories stored in the second storage means after the browsing work as a related work related to the browsing work; ,
Third storage control for storing the work content included in the related work and the same user identification information as the browsing work in association with the document identification information included in the browsing work related to the related work in the third storage unit Means,
Of the related work stored in the third storage means, common work determination means for determining common work contents from related work having the same document identification information and different user identification information;
A management means for managing the common work content in association with document identification information of a work document related to the task as a common task assigned to a plurality of users;
A task management program characterized by making it function.

Images