JP5415910B2 - Business management device - Google Patents

Description

  The present invention relates to a data processing technique, and more particularly to a technique for managing the progress of work.

  Some business operations are required to be implemented based on documents, and some are required to leave the implementation results in documents or records. Documents and records to be held in a company may be digitized and stored in a database or the like.

JP 2001-31422 A

  Multiple documents may need to be created or revised to perform a task. Furthermore, there are cases where a plurality of processes, such as an approval process and an education process, should be completed before new documents are created or revised. In such operations, progress management from the setting of the execution plan to the completion of the execution has been complicated.

  The present invention has been made in view of these problems, and a main purpose thereof is to provide a technique for supporting progress management for a business execution plan.

  In order to solve the above-described problems, a business management apparatus according to an aspect of the present invention defines a plurality of tasks to be performed by a business execution plan, and each task defines one or more processes necessary for the execution. If so, the plan registration unit that accepts the registration of the execution plan, the progress management unit that manages the progress of the process defined by each of the multiple tasks as the progress status of the execution plan, and each of the multiple tasks And a progress display unit for displaying on the predetermined display device that the execution of the execution plan has been completed on condition that all of the prescribed processes have been completed.

  It should be noted that any combination of the above-described constituent elements and a representation of the present invention converted between an apparatus, a method, a system, a program, a recording medium storing the program, and the like are also effective as an aspect of the present invention.

  ADVANTAGE OF THE INVENTION According to this invention, the progress management with respect to the implementation plan of work can be supported, and the burden of the user required for the progress management can be reduced.

It is a figure which shows the structure of the information system of embodiment. It is a block diagram which shows the function structure of the work management apparatus of FIG. It is a figure which shows the display image of a theme list screen. It is a figure which shows the display image of a task list screen. It is a flowchart which shows operation | movement of a business management apparatus. It is a flowchart which shows operation | movement of a business management apparatus. It is a flowchart which shows operation | movement of a business management apparatus. It is a figure which shows typically the cooperation of each apparatus in an information system.

Before describing the embodiment of the present invention, an outline will be described first.
In order to ensure safety and reliability in the pharmaceutical industry, there are many regulations such as the Pharmaceutical Affairs Law, which regulate the operations of pharmaceutical companies. The regulated business is implemented based on a document called SOP (Standard Operating Procedures), and it is necessary to leave a document and a record indicating the result of the implementation. Document management is therefore a very important factor in the pharmaceutical industry. Also, companies other than pharmaceutical companies are now required to thoroughly enforce compliance and corporate governance, and the importance of document management is increasing.

  In general, a business execution plan (hereinafter, also referred to as “theme”) is drawn up, and the business is executed in accordance with the theme. Some themes may require work such as new creation or revision of a plurality of documents (hereinafter also referred to as “tasks”). Further, each task is completed through one or more processes such as an approval process by a predetermined department, an education process for related persons, an effective process for validating a document, and a distribution process to related persons. The entire process is completed for all tasks, and the theme is completed.

  For example, in the theme of introducing a new inspection device in a pharmaceutical company, a task for establishing a plurality of SOP documents, applications for GQP (Good Quality Practice), and the like is necessary. And it is necessary to go through the various processes described above for each task.

  Even for tasks associated with the same theme, the required process may differ depending on the task, and the progress of the process also differs. Some processes also take a long time to complete. Therefore, it is complicated to manage the progress of each of the plurality of tasks, and it is also difficult to manage the progress of the entire theme.

  Therefore, the business management apparatus proposed in this embodiment automates the progress management for each task process that subdivides the theme, and supports the progress management of the theme. The user can efficiently grasp the progress of the theme, and can promptly perform various reports, response when progress is delayed, and the like.

  FIG. 1 shows a configuration of an information system according to an embodiment. The information system 100 is an information processing system built in a company, and includes a business management apparatus 10 and a first department terminal 12a, a second department terminal 12b, and a quality assurance section terminal 12c, which are collectively referred to as a person-in-charge terminal 12. Prepare. The business management apparatus 10 and the person-in-charge terminal 12 are interconnected via an intranet 14 constructed using various communication networks such as LAN, WAN, and the Internet.

  Each of the first department terminal 12a and the second department terminal 12b is a PC terminal installed in the first department and the second department of the company, and is operated by a person in charge of each department. The business management device 10 is an information processing device that manages and supports the business execution of the person in charge of each department.

  FIG. 2 is a block diagram showing a functional configuration of the business management apparatus 10 of FIG. The business management apparatus 10 includes a document management unit 20, a workflow processing unit 30, and a theme management unit 40. Each block shown in the block diagram of the present specification can be realized in terms of hardware by an element such as a CPU of a computer or a mechanical device, and in terms of software, it can be realized by a computer program or the like. The functional block realized by those cooperation is drawn. Therefore, those skilled in the art will understand that these functional blocks can be realized in various forms by a combination of hardware and software. For example, each functional block may be stored in a recording medium as a computer program, installed on the hard disk of the business management apparatus 10, and appropriately read into the main memory of the business management apparatus 10 and executed by the CPU.

  The document management unit 20 accepts registration of a document and holds the data of the document in a predetermined storage area. When a document acquisition request is received, the document data is provided to the request source. Of course, the user's access authority to the document may be held, and whether to provide the document may be determined according to the access authority.

  The workflow processing unit 30 is a workflow engine that executes a process defined in a task such as document revision. For example, in the execution of a certain process, a document is circulated to the person in charge of the process, and when a notification indicating the end of work of the process is received from the person in charge of execution, the next process is executed. It goes without saying that information specifying the processing procedure of the process (hereinafter also referred to as “workflow”) such as the circulation order of the document may be further received and the process executed according to the procedure. In addition, when no particular restriction is provided, the workflow processing unit 30 may execute each of a plurality of tasks in parallel, or may execute a plurality of processes in one task in parallel.

  The theme management unit 40 manages the progress of the theme. For convenience of explanation, first, a user interface for presenting the progress of the theme to the user will be described, and then the functional configuration of the theme management unit 40 will be described.

  FIG. 3 shows a display image of the theme list screen. The theme list screen displays a list of the progress of each of a plurality of themes. The theme ID column indicates the ID of a theme for uniquely specifying the theme. The status column indicates whether the theme has been completed or not completed. The registration date column indicates the date when the theme is registered in the business management apparatus 10, and the corresponding due date column indicates the time limit for completing the theme. The response completion date column indicates the date when the theme has been completed, and is not set if the theme has not been completed.

  FIG. 4 shows a display image of the task list screen. The task list screen displays a list of the progress of tasks defined in the theme specified by the user among the themes displayed on the theme list screen. The task ID column indicates a task ID for uniquely identifying the task. The task name column indicates work to be performed in the theme, for example, new creation, revision, validation, etc. of a document. The version column indicates the version number of the document. The approval, education, effective, distribution, and validation check columns in the figure indicate the names of processes that should be performed in the task. In the process to be managed, information indicating the completion date is set when the process is completed or not completed. The completion date column indicates the date on which the task has been completed, and is not set if the task has not been completed.

  Returning to FIG. 2, the theme management unit 40 includes a data holding unit 42 that is a storage area for holding various types of data, and a data processing unit 52 that executes various types of data processing. The data holding unit 42 includes a template holding unit 44, a theme holding unit 46, a task holding unit 48, and a process holding unit 50. The data processing unit 52 includes a template registration unit 54, a theme registration unit 56, a document registration unit 58, a progress information acquisition unit 60, a progress information update unit 62, and a progress information display unit 64.

  The template holding unit 44 holds data of a registration form (hereinafter also referred to as “template”) that can be reused by a user when registering a theme. This template defines a combination of a plurality of processes. For example, a combination of approval, education, effect, and distribution is defined. On the other hand, templates do not specify tasks. The task to be executed in the theme is set by the user when the theme is registered. By using the registered template at the time of theme registration, the user basically has only to add a task to the template, and it becomes easy to set the contents of the theme efficiently.

  The theme holding unit 46 holds data related to the theme itself for the theme registered by the user. Specifically, the data shown in FIG. 3 is held. The task holding unit 48 holds data related to the task defined by the theme for the theme registered by the user. Specifically, the task number, task name, document name, version, and completion date data shown in FIG. 4 are held together with the theme ID. The task may include not only a task related to the document but also a task not related to the document such as a validation operation.

  The process holding unit 50 holds data related to the process defined by each task for the theme registered by the user. Specifically, the process ID, management presence / absence, and status data shown in FIG. 4 are held together with the task ID and the sequence number indicating the execution order of the processes in the task.

  The template registration unit 54 displays a template registration screen on the person-in-charge terminal 12 and stores the template data set by the user on the registration screen in the template holding unit 44. On the template setting screen, the user sets a combination mode of a plurality of processes, an execution order, a name of each process, and the like.

  The theme registration unit 56 displays a theme registration screen on the person-in-charge terminal 12, and obtains theme data set by the user on the registration screen from the person-in-charge terminal 12. Then, the data is stored in the data holding unit 42. As a result, the task management apparatus 10 starts progress management for the theme.

  Specifically, on the theme registration screen, first, a registered template held in the template holding unit 44 is displayed, and a user selects a template to be used for theme registration from the registered templates. Subsequently, the user appropriately edits the selected template and inputs items other than the status and completion date among the information items shown in FIGS. 3 and 4. On the theme registration screen, the user can arbitrarily add a process that has not been set in the template. The theme registration unit 56 stores the data relating to the theme itself in the theme holding unit 46, the data relating to the task in the task holding unit 48, and the data relating to the process of each task in the process holding unit 50 among the input data to the registration screen. .

  The document registration unit 58 displays on the person-in-charge terminal 12 a document registration screen for registering a document to be worked on in a task, that is, a document to be newly created or revised, and is set by the user on the registration screen. Document data is acquired from the person-in-charge terminal 12. The data is stored in the document management unit 20. Hereinafter, a document that is accepted from the person-in-charge terminal 12 and is a work target in a task is also referred to as a “registered document”.

  The progress information acquisition unit 60 sequentially acquires information indicating that each process of the task has been completed from the workflow processing unit 30. The progress information update unit 62 reflects the progress status of each process of the task to the process holding unit 50. Specifically, the status of each process such as approval and education is updated. Further, the progress status of the task is determined according to the progress status of the process, and the status of the task held in the task holding section 48 is updated. Also, the progress of the theme is determined according to the progress of the task, and the status of the theme held in the theme holding unit 46 is updated.

  The progress information display unit 64 acquires data indicating the progress status of each theme, task, and process from the data holding unit 42 and displays the data on an external display. For example, a progress status display request regarding a registered theme may be received from an external device such as the person-in-charge terminal 12. Then, the progress status may be displayed on the external device by transmitting data indicating the progress status to the external device.

The operation of the above configuration will be described below.
FIG. 5 is a flowchart showing the operation of the business management apparatus 10. This figure shows the operation until the progress management of the theme is started. The template registration unit 54 stores the template data received from the person-in-charge terminal 12 via the template registration screen in the template holding unit 44 in advance. The theme registration unit 56 provides the person-in-charge terminal 12 with the template selected for editing on the theme registration screen (S10). Then, the setting information of the theme registered by the user is acquired from the person-in-charge terminal 12 and stored in the data holding unit 42 (S12). The document registration unit 58 acquires the data of the registered document set by the user on the document registration screen from the person-in-charge terminal 12 and stores it in the document management unit 20 (S14). The workflow processing unit 30 receives a workflow for executing a process from the person-in-charge terminal 12, and notifies a process execution instruction to the person-in-charge terminal 12 in a predetermined department according to the order defined in the workflow (S16).

  FIG. 6 is a flowchart showing the operation of the task management apparatus 10. This figure shows the operation when updating the progress of the theme. When the workflow processing unit 30 detects the completion of the process defined by each task (Y in S20), the workflow processing unit 30 sequentially notifies the progress information acquisition unit 60 accordingly. When the progress information acquisition unit 60 receives a process completion notification from the workflow processing unit 30, the progress information acquisition unit 60 updates the status of the process to completion (S22). When the statuses of all processes defined by a certain task are completed (Y in S24), the progress information update unit 62 sets data for the completion date of the task (S26). Further, when the completion dates of all tasks defined in a certain theme are set (Y in S28), the progress information update unit 62 sets the completion date data of the theme (S30). If some tasks have not been completed for the theme (N in S28), S30 is skipped. In addition, when only a part of processes is finished for a certain task and there is an incomplete process (N in S24), the workflow processing unit 30 notifies the execution terminal of the next process to the person in charge terminal 12 of the predetermined department. Then, the flow of this figure is ended (S32). If the completion of the process is not detected (N in S20), the subsequent flow is skipped and the flow of this figure is terminated.

  FIG. 7 is a flowchart showing the operation of the task management apparatus 10. This figure shows the operation when presenting the progress of the theme to the user. When the progress information display unit 64 receives an acquisition request for the theme list screen (Y in S40), the progress information display unit 64 acquires the progress status of each theme under progress management from the theme holding unit 46, and the data of the theme list screen is displayed in the person-in-charge terminal 12 To be displayed (S42). When a specific theme is selected by the user on the theme list screen (Y in S44), the progress status of each task specified by the theme is acquired from the task holding unit 48, and each process specified by each task is acquired. The progress status is acquired from the process holding unit 50. Then, the data of the task list screen is transmitted to the person-in-charge terminal 12 and displayed (S46). If a specific theme is not selected on the theme list screen (N in S44), S46 is skipped. If there is no acquisition request for the theme list screen (N of S40), S42 to S46 are skipped, and the flow of this figure ends.

  FIG. 8 schematically shows how the devices in the information system 100 are linked. This figure shows an example in which a task for revising an SOP document (hereinafter also referred to as “SOP revision task”) in which three processes of approval, education, and distribution are defined is executed. In addition, blocks indicated by dotted lines in the figure mainly indicate functions of the theme management unit 40, blocks indicated by alternate long and short dash lines mainly indicate functions of the workflow processing unit 30, and blocks indicated by two-dot chain lines mainly indicate document management units. 20 functions are shown.

  First, the first department terminal 12a registers the theme including the SOP revision task in the business management apparatus 10, and the business management apparatus 10 starts progress management of the theme. Subsequently, the first department terminal 12 a registers the revised version SOP and its approval process workflow in the business management apparatus 10. The business management apparatus 10 circulates the revised version SOP in the order of the second department terminal 12b and the quality assurance section terminal 12c in accordance with the registered workflow. When it is accepted from the second department terminal 12b that the approval of the revised SOP has been approved, the business management apparatus 10 updates the status of the approval process for the SOP revision task according to the approval approval. The business management apparatus 10 notifies the first department terminal 12a of the approval result of the revised version SOP. If rejected, the revised SOP is modified and the approval process is performed again.

  When the revised version SOP is approved, the first department terminal 12 a registers the workflow of the education process in the business management apparatus 10. The business management apparatus 10 provides the revised version SOP to the second department terminal 12b according to the registered workflow. When it is accepted from the second department terminal 12b that training has been completed, the business management apparatus 10 completes the status of the education process of the SOP revision task and notifies the quality assurance section terminal 12c to that effect.

  When the completion of the education process is notified, the quality assurance section terminal 12c registers the workflow of the distribution process in the business management apparatus 10. The business management apparatus 10 provides the revised SOP to the first department terminal 12a and the second department terminal 12b according to the registered workflow. When the fact that the revised SOP has been received is received from the first department terminal 12a and the second department terminal 12b, the business management apparatus 10 completes the status of the distribution process of the SOP revision task. At the same time, since the entire process of the SOP revision task is completed, the completion date is set with the status of the SOP revision task as completion.

  As described above, it is necessary to execute various processes such as approval, education, distribution, etc. for various newly created documents and revised documents based on the business execution plan (theme). Also, various human tasks need to be performed based on the theme. Conventionally, it has been complicated to centrally manage these, and the progress of the whole theme has been apt to be unclear. According to the business management apparatus 10 of the present embodiment, in cooperation with the document management unit 20, the workflow processing unit 30, and the theme management unit 40, in each hierarchy from the upper hierarchy to the lower hierarchy of business such as themes, tasks, and processes. Progress management is automated. Thereby, it is possible to assist the user in confirming the progress of the theme efficiently and easily.

  The present invention has been described based on the embodiments. This embodiment is an exemplification, and it will be understood by those skilled in the art that various modifications can be made to combinations of the respective constituent elements and processing processes, and such modifications are also within the scope of the present invention. is there. A modification is shown below.

  A first modification will be described. Although not described in detail in the above embodiment, common tasks may be set in different themes. For example, a plurality of themes whose task is revision of the same SOP document may be registered from the person-in-charge terminal 12 to the business management apparatus 10 and the progress of each theme may be executed. In this case, the progress information acquisition unit 60 receives the progress status of the process of the common task from the workflow processing unit 30, and the progress information update unit 62 updates the progress status of the common task set for each of the plurality of themes at a time. Also good. According to this modification, since a many-to-many relationship is allowed between the theme and the task, the degree of freedom of the task combination mode in each theme is improved. In addition, progress management of each of the themes can be realized efficiently.

  A second modification will be described. Although not described in detail in the above embodiment, document management may be performed in the business management apparatus 10. For example, the document management unit 20 of the business management apparatus 10 may hold document data that is distinguished for each version even for documents having the same name. In this case, for the task of revising the document, it is desirable that the revised document version is not determined at the time of theme registration, and it is desirable that the version be determined at the time of document registration. This is because a time lag may occur between theme registration and document registration, and the version of the document may be changed during the execution of another theme during that time. In this modification, the document registration unit 58 determines the version of the revised document based on the latest version at the time of document registration, and sets the version number in the task holding unit 48. At the same time, the version number and the revised document data are associated with each other and stored in the document management unit 20. According to this modification, document version management can be appropriately performed even when a plurality of themes are performed concurrently.

  Any combination of the above-described embodiments and modifications is also useful as an embodiment of the present invention. The new embodiment generated by the combination has the effects of the combined embodiment and the modified examples.

  It should also be understood by those skilled in the art that the functions to be fulfilled by the constituent elements described in the claims are realized by the individual constituent elements shown in the embodiments and the modification examples or by their cooperation.

  DESCRIPTION OF SYMBOLS 10 Business management apparatus, 20 Document management part, 30 Workflow processing part, 40 Theme management part, 44 Template holding part, 46 Theme holding part, 48 Task holding part, 50 Process holding part, 54 Template registration part, 56 Theme registration part, 58 document registration unit, 60 progress information acquisition unit, 62 progress information update unit, 64 progress information display unit, 100 information system.

Claims (2)

When a business execution plan specifies a plurality of tasks to be performed, and each task specifies one or more processes necessary for the execution,
A plan registration unit that accepts registration of the execution plan of the business of the pharmaceutical industry ;
A plurality of tasks specified in the implementation plan, each of which is an approval process, an education process, an effective process for validating a document, and a document creation task or a document revision task including a distribution process. A document registration unit that accepts registration of a document,
A document management unit that holds the document data received by the document registration unit in association with version information;
As the progress status of the execution plan, a progress management unit that manages the progress status of the process defined by each of the plurality of tasks;
A progress display unit that displays on a predetermined display device that the execution of the execution plan is completed on condition that all of the processes defined by each of the plurality of tasks are completed;
The document registration unit, when accepting registration of a target document in a task to revise a document, determines version information after revision based on the version information of the document at that time,
The document management unit stores a document that is received by the document registration unit and that is a target of a document revision task in association with version information determined by the document registration unit. Management device. The plan registration unit accepts registration of a plurality of execution plans each including a common task,
The business management apparatus according to claim 1, wherein the progress management unit acquires a progress status of a process defined by the common task and updates a progress status of each of the plurality of execution plans.

Images