Management device, management method, and management program

Abstract

To facilitate management across the states of a plurality of jobs.SOLUTION: A management device 100 manages a workflow including information on business of a predetermined granularity as an object. The management apparatus 100 receives an input of information related to a task of a predetermined granularity. The management device 100 associates a parent object, which is a management subject, with a child object, which represents a state of a task of a predetermined granularity by being associated with the parent object, based on the input information related to the task of the predetermined granularity. The management device 100 outputs a workflow in which the parent object and the child object are associated with each other.SELECTED DRAWING: Figure 4

Description

[Technical Field]

[0001] The present invention relates to a management device, a management method, and a management program. [Background technology]

[0002] In companies and other organizations, various activities are carried out for the continuation of business activities. For example, in sales activities, activities are carried out for each task of a predetermined granularity, such as business negotiations, submission of estimates, orders, delivery of deliverables, inspection, billing, etc. In order to smoothly proceed with the above-mentioned tasks of a predetermined granularity, it is necessary to manage the status of the tasks, such as the implementation status, history, and next actions.

[0003] Therefore, conventional techniques are known that are used to manage the status of the above-mentioned tasks at a predetermined granularity. For example, a function that displays fields for inputting predetermined information and a technique that links the input information and stores it as a hierarchical structure are known (see, for example, Non-Patent Document 1). The status of tasks at a predetermined granularity that are input using the above-mentioned conventional techniques can be managed for each granularity. [Prior art documents] [Non-patent literature]

[0004] [Non-Patent Document 1] kintone,<URL:https: / / kintone.cybozu.co.jp / > ,<Search date: June 28, 2020> Summary of the Invention [Problem to be solved by the invention]

[0005] However, with the above-mentioned conventional technology, it is not easy to manage the status of a plurality of tasks across the board.

[0006] For example, conventional technologies can manage the status of tasks at a specific granularity based on information management using a hierarchical structure. However, when attempting to manage a comprehensive series of tasks that span multiple tasks (hereinafter sometimes referred to as a "workflow"), conventional technologies require that information for each task be appropriately associated to build a hierarchical structure, which requires specialized knowledge and experience. Therefore, it is not easy to manage a workflow that spans multiple tasks, rather than just a single task, using conventional technologies. [Means for solving the problem]

[0007] In order to solve the above problems and achieve the objectives, the management device of the present invention is a management device that manages a workflow that includes information about work of a specified granularity as an object, and is characterized by comprising: an input receiving unit that receives input of information about the work of the specified granularity; a structural control unit that associates a parent object, which is the management entity, with a child object that represents the state of the work of the specified granularity by being associated with the parent object based on the input information about the work of the specified granularity; and a display output unit that outputs the workflow in which the parent object and the child object are associated. [Effects of the Invention]

[0008] The present invention has the effect of facilitating management across the states of a plurality of tasks. [Brief explanation of the drawings]

[0009] [Figure 1] FIG. 1 is a diagram illustrating workflow management according to the reference technology. [Figure 2] FIG. 2 is a diagram illustrating an outline of processing by the management device according to the embodiment. [Figure 3] FIG. 3 is a diagram illustrating an example of processing by the management device according to the embodiment. [Figure 4] FIG. 4 is a diagram illustrating an example of the configuration of a management device according to the embodiment. [Figure 5]FIG. 5 is a table diagram illustrating an example of a parent object according to the embodiment. [Figure 6] FIG. 6 is a table diagram illustrating an example of a child object according to the embodiment. [Figure 7] FIG. 7 is a table showing an example of processing conditions according to the embodiment. [Figure 8] FIG. 8 is a diagram illustrating an example of processing by the structure control unit according to the embodiment. [Figure 9] FIG. 9 is a diagram illustrating an example of processing by the structure control unit according to the embodiment. [Figure 10] FIG. 10 is a diagram illustrating an example of processing by the structure control unit according to the embodiment. [Figure 11] FIG. 11 is a flowchart showing an example of a management procedure according to the embodiment. [Figure 12] FIG. 12 is a flowchart showing an example of a management procedure according to the embodiment. [Figure 13] FIG. 13 is a flowchart illustrating an example of a management procedure according to the embodiment. [Figure 14] FIG. 14 is a hardware configuration diagram illustrating an example of a computer that realizes the functions of the management device according to the embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0010] Hereinafter, a detailed description will be given of a management device, a management method, and a management program according to the present invention (hereinafter referred to as an "embodiment") with reference to the drawings. Note that the management device, the management method, and the management program according to the present invention are not limited to the present embodiment. Furthermore, the same components in the following embodiments are designated by the same reference numerals, and redundant description will be omitted.

[0011] <Introduction> In companies and other organizations, tasks are carried out according to predetermined procedures. Therefore, it is necessary to appropriately manage the status of each task, including its progress, history, and next actions. Therefore, a reference technology is known that manages tasks at a predetermined granularity by managing input information based on a hierarchical structure.

[0012] Here, a method for managing a workflow according to the reference technology will be described with reference to Fig. 1. Fig. 1 is a diagram for explaining workflow management according to the reference technology.

[0013] In this embodiment, an "object" is information about various business operations in an organization grouped together into a single unit at a predetermined granularity. Using the object, information about various business operations in an organization grouped together at a predetermined granularity (hereinafter, sometimes referred to as "information about business operations at a predetermined granularity") is managed.

[0014] For example, in this embodiment, the objects include "Business Partner" which compiles information about business partners, "NDA" which compiles information about the work of concluding an NDA (Non-Disclosure Agreement), "Quote" which compiles information about the work of submitting a quote to a customer, "Contract" which is work related to concluding a business contract with a customer, and "Billing Payment" which is information about the work of billing for value provided.

[0015] The reference technology constructs a hierarchical structure of objects (for example, a four-level data structure as shown in (1) of Figure 1) based on the correspondence between each input task of a specified granularity, thereby realizing status management for each task and management of a workflow that bundles tasks of a specified granularity.

[0016] For example, in Figure 1 (1), objects from the first level to the fourth level are shown in correspondence. Specifically, "NDA (object in the second level) ((1-2) in Figure 1)" is associated with "Customer (object in the first level) ((1-1) in Figure 1)." Also, "Quote (object in the second level) ((1-3) in Figure 1)" is associated with "Customer (object in the first level) ((1-1) in Figure 1)."

[0017] Furthermore, "Estimate (object at second level) ((1-3) in Figure 1)" is associated with "Contract (object at third level) ((1-4) in Figure 1)". Furthermore, "Contract (object at third level) ((1-4) in Figure 1)" is associated with "Bill Payment (object at fourth level) ((1-5) in Figure 1)".

[0018] In the four-level data structure shown in (1) of Figure 1 above, the status of business operations can be managed at a specified granularity by adding / updating information for each object shown in (1-1) to (1-5) of Figure 1 and managing the status of each object. Also, by associating objects shown in (1-1) to (1-5) of Figure 1, the entire business can be managed as a series of flows (workflows), such as "Business Partner (developing business partners, etc.)" → "NDA (signing an NDA, etc.)" → "Quote (presenting a quote, etc.)" → "Contract (receiving an order for a project, etc.)" → "Billing and Payment (billing for expenses, etc.)."

[0019] However, with the above-mentioned reference technology, it is not easy to manage multiple task states as a comprehensive workflow. For example, each single task, such as "NDA," "quote," or "invoice," can be further broken down into work steps. In other words, each single task also contains a workflow, and the progress of each task is managed.

[0020] Therefore, in order to manage the status management of multiple tasks as a workflow by bundling them using the reference technology, it is necessary to manage information indicating the status of a single task in a linked manner between tasks. For this reason, it is necessary to set appropriate input items for each task of a predetermined granularity, design correspondence between tasks of a predetermined granularity, and build an appropriate hierarchical structure.

[0021] However, in order to properly construct the above-mentioned hierarchical structure, it is necessary to understand the complex relationships between data and to properly associate them, which requires specialized knowledge and experience, and this can sometimes create challenges.For example, in an environment where many non-engineer employees work together, it can become impossible to communicate information between those who can understand the complex hierarchical structure and those who cannot, which can make it difficult to communicate the necessary business purposes.

[0022] (Overview of management device 100) Therefore, the management device 100 of this embodiment solves the above-mentioned problem by limiting the multi-layer hierarchical structure as shown in (1) of Figure 1 to "two layers" and managing objects in the first layer and objects in the second layer in association with each other.

[0023] The above-mentioned first-level objects are objects that are the main subjects of management (hereinafter simply referred to as "parent objects"). The second-level objects are objects that represent the status of business operations at a predetermined level of granularity by being associated with parent objects (hereinafter simply referred to as "child objects"). For example, the business status of a child object is expressed depending on which of multiple parent objects the child object is associated with.

[0024] From here, an overview of the processing of the management device 100 according to this embodiment will be explained using Fig. 2. Fig. 2 is a diagram showing an overview of the processing by the management device 100 according to this embodiment. The management device 100 shown in Fig. 2 is a device that manages a workflow in which information related to a task of a predetermined granularity is included as an object, and is an example of a computer that provides a technology for displaying the status of an object in a workflow by changing the correspondence between objects.

[0025] 2, the management device 100 receives input of an object including information about a business of a predetermined granularity ((1) in FIG. 2). Next, the management device 100 associates a parent object (an object in the first layer) with a child object (an object in the second layer) based on the input information about the business of the predetermined granularity.

[0026] For example, the management device 100 associates the received object as a child object with a first parent object ((2-1) in FIG. 2). Furthermore, the management device 100 moves the child object associated with the first parent object so that it is associated with a second parent object ((2-2) and (2-3) in FIG. 2).

[0027] Then, the management device 100 outputs the workflow in which the parent object and the child object are associated with each other via a display unit or a terminal device operated by a user ((3) in FIG. 2).

[0028] The above-described process enables management device 100 to display the state of the input child object more simply than before. Here, the process of management device 100 shown in Fig. 2 will be described in more detail using an example with reference to Fig. 3.

[0029] Fig. 3 is a diagram showing an example of processing by the management device 100 according to the embodiment. Fig. 3 (1) shows an example in which each object shown in Fig. 1 (1) is expressed based on a two-level data structure. Specifically, a "Customer (first parent object) (Fig. 3 (1-1))" in the first level is associated with an "NDA (child object) (Fig. 3 (1-2))" in the second level and a "Quote (child object) (Fig. 3 (1-3))" in the second level.

[0030] The "contract" object is managed as a first-level object (second parent object) rather than a third-level object ((1-4) in FIG. 3). However, if the data structure were simply two levels, the correspondence between "customer" and "contract," and between "quote" and "contract," which was associated in the conventional four-level data structure, would be broken. Therefore, the management device 100 manages information that identifies objects so that "contract" is associated with "customer."

[0031] As described above, the management device 100 can manage the status of a task as a two-tier data structure by associating parent objects with child objects. In other words, while conventionally managing the status of multiple tasks would require a complex data structure such as parent (first tier), child (second tier), grandchild (third tier), great-grandchild (fourth tier), etc., the management device 100 enables easier management based on a simple "two-tier" data structure.

[0032] Furthermore, the management apparatus 100 expresses a change in the status of a task related to a child object by changing the child object so that the child object is associated with a different parent object.

[0033] For example, the management device 100 associates the input "quote (child object) ((1-3) in FIG. 3)" with the "customer (first parent object) ((1-1) in FIG. 3)." This allows the management device 100 to express the status of the "quote" task, for example, that "the quotation has only been issued and sent, but no order has been received."

[0034] Also, for example, the management device 100 moves the "quote (child object) ((1-3) in FIG. 3)" associated with the "customer (first parent object) ((1-1) in FIG. 3)" so that it is associated with the "contract (second parent object) ((1-4) in FIG. 3)" (for example, (1-5) in FIG. 3). This allows the management device 100 to express, for example, the status of the "quote" task as "order has been received."

[0035] In addition, the object "Bill Payment (child object) ((1-6) in Figure 3)" undergoes processes such as object registration and association with the target parent object in the same way as "Estimate (child object) ((1-3) in Figure 3)".

[0036] In this way, the management device 100 realizes management of a workflow that bundles the states of multiple tasks by changing the association state between the first-level object (parent object) and the second-level object (child object) according to the state of the task.

[0037] <Explanation of Management Device 100> Next, detailed functions of the management device 100 according to this embodiment will be described. Fig. 4 is a diagram showing an example of the configuration of the management device 100 according to this embodiment. As shown in Fig. 4, the management device 100 has a communication unit 110, an input unit 120, a display unit 130, a storage unit 140, and a control unit 150.

[0038] (Communication unit 110) The communication unit 110 performs communication related to input of information related to business operations relating to objects and output of workflows in which parent objects and child objects are associated. The communication unit 110 is realized by, for example, a network interface card (NIC). The communication unit 110 is connected to a predetermined network via wired or wireless connection, and performs transmission and reception of information between, for example, the management device 100 and the terminal device 200.

[0039] (input unit 120) The input unit 120 is configured with a keyboard, a touch panel, etc., and can accept input of predetermined information from a user who uses the management device 100, etc.

[0040] (Display section 130) The display unit 130 is configured with a display, a printer, etc., and displays information generated based on the management process to the user of the management device 100, etc.

[0041] (Regarding the storage unit 140) The storage unit 140 is realized by, for example, a semiconductor memory element such as a RAM (Random Access Memory) or a flash memory, or a storage device such as a hard disk or an optical disk. The storage unit 140 stores data and programs used for various processes by the control unit 150. As shown in FIG. 4 , the storage unit 140 has an object storage unit 141 and a processing condition storage unit 142.

[0042] (Object storage unit 141) The object storage unit 141 stores information about a business at a predetermined granularity as an object. Specifically, the object storage unit 141 stores a parent object 141a and a child object 141b.

[0043] First, an example of a parent object 141a stored in the object storage unit 141 will be described with reference to Fig. 5. Fig. 5 is a table diagram showing an example of a parent object according to the embodiment.

[0044] The object storage unit 141 stores the parent object as identification information or information indicating the contents of the parent object, in association with the name of each item ("item name" in FIG. 5), the contents of the item ("item contents" in FIG. 5), and the information actually input ("input value" in FIG. 5).

[0045] The object storage unit 141 can store information for each of a plurality of objects in a table format as shown in Fig. 5. The object storage unit 141 can also store a plurality of parent objects as shown in Fig. 5.

[0046] For example, taking the item name "Details," the object storage unit 141 associates the item content "Customer Details" and the input value "ABC..." with the "Details" and stores them as the parent object 141a. Note that the input value "ABC..." above indicates a legend for the input value. In reality, the input value includes information such as text, numbers, and symbols related to items such as [Customer Type], [Representative Name], [Postal Code], [Address], [Telephone Number], [Capital], [Expected Transaction Details], and [Expected Annual Transaction Amount], as shown in FIG. 5(1).

[0047] Next, an example of a child object 141b stored in the object storage unit 141 will be described with reference to Fig. 6. Fig. 6 is a table diagram showing an example of a child object according to the embodiment.

[0048] The object storage unit 141 stores child objects as identification information or information indicating the contents of the parent object, in association with the name of each item ("item name" in FIG. 6), the content of the item ("item content" in FIG. 6), and the information actually input ("input value" in FIG. 6).

[0049] The object storage unit 141 can store information for each of a plurality of objects in a table format as shown in Fig. 6. The object storage unit 141 can also store a plurality of child objects as shown in Fig. 6.

[0050] For example, taking the item name "Details," the object storage unit 141 associates the item content "Project Details" and the input value "abc..." with the "Details" and stores them as a child object 141b. Note that the input value "abc..." above indicates a legend for the input value. In reality, the input value includes information such as text, numbers, and symbols related to items such as [Project Classification], [Customer], [Bank Transfer Fee], [Email Address], [Customer Representative], [Project Name], [Delivery Date], [Payment Terms], [Billing Timing], [Implementation Period], [Billing Details], [Contract Amount], and [Remarks], as shown in (1) of FIG. 6.

[0051] (Processing condition storage unit 142) Returning to Fig. 4, the explanation will be continued. The processing condition storage unit 142 stores information (processing conditions 142a) relating to the execution conditions of processing by the structure control unit 152, which will be described later. An example of the processing conditions 142a stored in the processing condition storage unit 142 will now be described with reference to Fig. 7. Fig. 7 is a table diagram showing an example of processing conditions according to the embodiment.

[0052] The processing condition storage unit 142 associates a "condition" that is a trigger for processing execution with "processing content" that is the content of the processing to be executed when the condition is met, and associates it with "No," which is information that identifies individual data of the processing condition, and stores them as processing condition 142a.

[0053] For example, the processing condition storage unit 142 stores the condition "item includes customer status" and the processing content "set type to customer (parent object)" in association with No. "1." Note that actual processing based on the conditions and processing content shown in No. "1" and No. "2 to 6" will be explained in the following sections.

[0054] (control unit 150) The control unit 150 is realized by a CPU, an MPU (Micro Processing Unit), or the like executing various programs stored in a storage device inside the management device 100 using RAM as a work area. The control unit 150 is also realized by an integrated circuit such as an ASIC (Application Specific Integrated Circuit) or an FPGA (Field Programmable Gate Array). As shown in FIG. 4, the control unit 150 has an input receiving unit 151, a structure control unit 152, and a display output unit 153.

[0055] (Input reception unit 151) The input receiving unit 151 receives information about a task of a predetermined granularity related to a parent object or a child object, and transmits the received information about the task of the predetermined granularity to the structure control unit 152, which will be described later.

[0056] (Structure Control Unit 152) Based on information about a business operation of a predetermined granularity sent from the input receiving unit 151, the structure control unit 152 updates information about parent or child objects, performs processing to associate parent objects with each other, and performs processing to associate child objects.

[0057] Next, details of the processing of the structure control unit 152 will be described with reference to Fig. 8 to Fig. 10. Fig. 8 to Fig. 10 are diagrams showing an example of the processing of the structure control unit 152 according to the embodiment.

[0058] (First example) First, as a first example, an example of "registration and association processing of a new object" will be described with reference to Fig. 8. Fig. 8 shows an example in which a newly input object is determined to be a parent object or a child object, and based on the determination result, the object is registered and the objects are associated with each other.

[0059] The example shown in Figure 8 is a case where a parent or child object has not been registered and an object is newly input. Note that a case where a parent or child object has already been registered and information is updated as an object is input will be explained in the second example.

[0060] First, the structure control unit 152 determines whether the input object is a parent object or a child object ((1) in FIG. 8). Specifically, the structure control unit 152 uses at least one of a character string, a numerical value, and identification information (for example, the information shown in FIG. 5 or FIG. 6) included in the item information of the input object to identify whether the object is a parent object or not.

[0061] For example, the structure control unit 152 executes processing based on the processing conditions shown in Fig. 7. Specifically, for an object that satisfies the condition "item includes 'customer status'" identified by No. "1" shown in Fig. 7, the processing content "set 'type' to 'customer'" is executed. As a result, the structure control unit 152 determines that the input object is a "parent object" (Yes in (1) of Fig. 8).

[0062] The structure control unit 152 registers the object determined to be the parent object ((2-1) in FIG. 8). As an example, the structure control unit 152 accepts the item content "ABC..." included in the object determined to be the parent object. Then, the structure control unit 152 associates the accepted item content "ABC..." with the item name "Details" and stores them in the object storage unit 141 as parent object 141a.

[0063] Furthermore, if a first parent object has already been registered, the structure control unit 152 registers the input new parent object (second parent object) and executes a process of associating the first parent object with the second parent object. Specifically, if the first parent object (e.g., "Customer") and the second parent object (e.g., "Contract") are corresponding objects, the structure control unit 152 adds information identifying the first parent object to the item information of the second parent object and associates them ((2-2) in FIG. 8).

[0064] As an example, when a first parent object (business partner) identified by ID "1001" has already been registered and a second parent object (contract) (ID: 1002) is entered as an additional parent object, the structure control unit 152 enters the information "1001" into the item name "related object (ID of related object)" of the second parent object.

[0065] On the other hand, if the input object is determined to be a "child object" (No in (1) of FIG. 8), the structure control unit 152 registers the child object.

[0066] As an example, the structure control unit 152 accepts the item content "abc..." included in the object determined to be a child object. Then, the structure control unit 152 associates the accepted item content "abc..." with the item name "Details" and stores them in the object storage unit 141 as child object 141b.

[0067] Furthermore, the structure control unit 152 can determine the type of child object based on the item information. Specifically, the structure control unit 152 identifies the type of business related to the child object by using at least one of a character string, a numerical value, and identification information included in the item information of the input child object (for example, "quote"). Then, the structure control unit 152 adds information related to the identified type of business to the child object.

[0068] For example, the structure control unit 152 executes processing based on the processing conditions shown in Fig. 7. Specifically, for an object that satisfies the condition "item includes 'quote creation status'" identified by No. "2" shown in Fig. 7, the processing content "set 'type' to 'quote'" is executed. Then, the structure control unit 152 sets the item name "type" of the object determined to be a child object to "quote." As a result, the structure control unit 152 determines that the input object is a "child object" (No. of (1) in Fig. 8).

[0069] Furthermore, the structure control unit 152 uses information included in the child object to identify the corresponding parent object. Specifically, when the input object is determined to be a child object, the structure control unit 152 uses the item information of the child object to identify the first parent object (for example, "Customer") to which the child object is to be associated ((3-1) in FIG. 8).

[0070] Specifically, when at least one of the character string, numerical value, and identification information included in the item information for each object satisfies the association condition between the child object and the parent object, the structure control unit 152 identifies the parent object as an association target for the child object. Then, the structure control unit 152 associates the identified first parent object with the child object ((3-2) in FIG. 8).

[0071] As an example, if the input child object satisfies the condition "'Quote creation status' is 'Quote sending' or 'Quote sent'" identified by No. "3" shown in Fig. 7, the structure control unit 152 sets the parent object of the child object to the target business partner. Then, the structure control unit 152 associates "NDA (child object)" with "business partner (parent object)".

[0072] The structure control unit 152 prohibits the process of associating child objects with each other. Specifically, the structure control unit 152 performs the process of associating a child object with an object related to a "parent object."

[0073] As described above, in the first example, the management device 100 performs parent-child determination of the object and appropriate association processing between the objects based on information included in the input object. Note that, although the first example describes that the determination processing is performed as described above, in reality, when the object to be input is designated by a user or the like, the determination processing may be skipped.

[0074] (Second example) Next, as a second example, an example of "adding or updating an object, changing a correspondence target (moving a child object)" will be described with reference to Fig. 9. Fig. 9 shows an example in which, when information about an object that has already been registered is input, the input information is used to update information about the object, and the child object is moved based on the updated information.

[0075] 9 shows an example where a "Customer (first parent object)", a "Contract (second parent object)", an "NDA (child object)", and a "Quote (child object)" are registered. The "Contract (second parent object)" is associated with the "Customer (first parent object)" based on the information in the item name "Related Object".

[0076] First, the structure control unit 152 determines whether the input object is a parent object or a child object ((1) in FIG. 9). Note that this determination process is the same as the determination process in the first example described above, and therefore a description thereof will be omitted in the second example. Also, although the second example describes that the determination process is performed as described above, in reality, when the object to be input is designated by the user or the like, the determination process may be skipped.

[0077] If the input object is a "parent object" (Yes in (1) of FIG. 9), the structure control unit 152 updates the information included in the target parent object (for example, (2) of FIG. 9). On the other hand, if the input object is a "child object" (No in (1) of FIG. 9), the structure control unit 152 updates the information included in the target child object (for example, (3) of FIG. 9).

[0078] Then, if the input object is determined to be a child object ("quote (child object)") associated with a first parent object ("customer (first parent object)") and the status of the child object is updated, the structure control unit 152 uses the item information of the child object to identify the second parent object ("contract (second parent object)") with which the child object is to be associated.

[0079] For example, when the estimate creation status included in the child object "Estimate" is changed to "Estimate Confirmed," the structure control unit 152 sets the parent object to the target contract based on the condition identified by No. "4" in Fig. 7. Then, the structure control unit 152 specifies "Contract (second parent object)" as the object to be associated ((4-1) in Fig. 9).

[0080] Next, the structure control unit 152 cancels the association between the child object ("quote (child object)") and the first parent object ("customer (first parent object)") ((4-2) in FIG. 9). Then, the structure control unit 152 associates the child object ("quote (child object)") whose association has been canceled with the identified second parent object ("contract (second parent object)") ((4-3) in FIG. 9).

[0081] That is, the structure control unit 152 can represent a change in the state of the "quote (child object)" (for example, "before order received" to "received order") by moving the "quote (child object)" associated with the "customer (first parent object)" so that it is associated with the "contract (second parent object)."

[0082] (Third example) Next, as a third example, an example of "error determination for input that ignores the execution order of tasks defined in a workflow" will be explained using Fig. 10. Fig. 10 shows an example in which an error determination is output when a new child object is input and there is no child object corresponding to the previous step of the task related to the input child object.

[0083] The example shown in Figure 10 is a case where a "Customer (first parent object)" and a "Contract (second parent object)" are registered. The "Contract (second parent object)" is associated with the "Customer (first parent object)" based on the information in the field name "Related Object." As a prerequisite, when a "Quote (first child object)" is registered in the workflow, the "NDA (second child object)" in the previous step must be registered.

[0084] First, the structure control unit 152 determines whether the input object is a parent object or a child object ((1) in FIG. 10). Note that this determination process is the same as the determination process in the first example described above, and therefore a description thereof will be omitted in the third example. Also, although the third example describes that the determination process is performed as described above, in reality, if the object to be input is designated by the user or the like, the determination process may be skipped.

[0085] If the input object is a "parent object" (Yes in (1) of FIG. 10), the structure control unit 152 updates the information included in the target parent object (for example, (2) of FIG. 10). On the other hand, if the input object is a "child object" (No in (1) of FIG. 10), the structure control unit 152 registers the target child object (for example, (3) of FIG. 10).

[0086] Here, the structure control unit 152 can determine whether or not the input child object violates a workflow. Specifically, when the input object is determined to be a child object and, based on the execution steps of the preset objects, there is no second child object located in a step earlier than the input first child object, the structure control unit 152 determines that the input of the first child object is an error.

[0087] As an example, when "quote (first child object)" is input, the structure control unit 152 determines whether or not the condition "the item includes 'quote creation status' and there is no corresponding child object" identified by No. "6" in Fig. 7 is satisfied. That is, the structure control unit 152 determines whether or not there is an "NDA (second child object)" that corresponds to the child object of the previous step of "quote (first child object)" ((4-1) in Fig. 10).

[0088] If the condition is met, the structure control unit 152 outputs an error because a child object registration violation has occurred ((4-2) in FIG. 10). Note that if the condition is not met, the structure control unit 152 does not execute the error output process (error determination).

[0089] In addition to the above-mentioned determination between child objects, the structure control unit 152 can also determine whether or not there is a workflow violation based on whether or not a target parent object exists (not shown in FIG. 10). Specifically, when the structure control unit 152 determines that an input object is a child object and there is no parent object to which the input first child object is associated, it determines that the input of the child object is an error.

[0090] For example, when "quote (first child object)" is input, the structure control unit 152 determines whether or not the condition "the item includes 'quote creation status' and there is no corresponding parent object" identified by No. "5" in Fig. 7 is satisfied. In other words, the structure control unit 152 determines whether or not there is a "customer (first object)" that corresponds to the parent object to which "quote (first child object)" is to be associated.

[0091] If the condition is met, the structure control unit 152 outputs an error because a registration violation of the child object has occurred. Note that if the condition is not met, the structure control unit 152 does not execute the error output process (error determination).

[0092] As described above, in the third example, the management device 100 outputs an error to an object that violates a condition determined based on the correspondence between objects, thereby enabling appropriate workflow management.

[0093] (Display output unit 153) Returning to FIG. 4, the explanation will be continued. The display output unit 153 outputs a workflow in which parent objects and child objects are associated with each other. For example, the display output unit 153 can output a list in which parent objects and child objects are displayed in a list format. Furthermore, the display output unit 153 can display a diagram in which parent objects and child objects are displayed in a format such as a block diagram, as shown in FIGS. 8 to 10.

[0094] (Terminal device 200) The terminal device 200 is a predetermined information processing terminal device operated by a user. The terminal device 200 receives input of an object from the user and transmits it to the management device 100, and displays to the user a workflow or the like output from the management device 100. The terminal device 200 may be a PC (Personal Computer), a notebook PC, a desktop PC, a smartphone, a PDA (Personal Digital Assistant), or the like, and the type of the information processing terminal device is not particularly limited.

[0095] (Processing Procedure) From here, a management procedure by the management device 100 according to the embodiment will be described with reference to Fig. 11 to Fig. 13. Fig. 11 to Fig. 13 are flowcharts showing an example of the management procedure according to the embodiment.

[0096] (Overall flow of management procedures) First, the overall flow of the management procedure will be described with reference to Fig. 11. The management device 100 waits for processing until an object is input by a user or the like (No in S101).

[0097] When the input receiving unit 151 receives the input of an object (Yes in S101), the structure control unit 152 determines whether the input object is a parent object or a child object (S102).

[0098] If the input object is a parent object (Yes in S102), the structure control unit 152 executes processing related to the parent object (S103). Details of the "processing related to the parent object" will be described later with reference to FIG. 12.

[0099] On the other hand, if the input object is a child object (No in S102), the structure control unit 152 executes a process related to the child object (S104). Details of the "process related to the child object" will be described later with reference to FIG. 13.

[0100] The display output unit 153 outputs the workflows associated by the processes of S103 and S104 (S105). Then, the management device 100 ends the process.

[0101] (Processing related to parent object) Next, the flow of processing related to the parent object in the management procedure will be described with reference to Fig. 12. Fig. 12 is a flowchart illustrating the details of the processing of S103 in Fig. 11.

[0102] The administration device 100 waits for the execution of the process related to the parent object (No in S1031). Then, when the process related to the parent object has been executed (Yes in S1031), the structure control unit 152 compares the information related to the parent object stored in the object storage unit 141 with the information related to the input object (S1032).

[0103] If a parent object corresponding to the input object exists (Yes in S1033), the structure control unit 152 updates information related to the registered parent object (S1034). On the other hand, if a parent object corresponding to the input object does not exist (No in S1033), the structure control unit 152 newly registers the parent object (S1035). Then, the management device 100 ends the process.

[0104] (Processing related to child objects) Next, the flow of processing related to child objects in the management procedure will be described with reference to Fig. 13. Fig. 13 is a flowchart illustrating the details of the processing of S104 in Fig. 11.

[0105] The administration device 100 waits for the execution of the process related to the child object (No in S1041). Then, when the process related to the child object is executed (Yes in S1041), the structure control unit 152 compares the information related to the child object stored in the object storage unit 141 with the information related to the input object (S1042).

[0106] If a child object corresponding to the input object exists (Yes in S1043), the structure control unit 152 updates the information related to the registered child object (S1044).

[0107] If the association destination of the parent object is changed due to an update of information related to the child object, etc. (Yes in S1045), the structure control unit 152 identifies a second parent object (S1046). Next, the structure control unit 152 releases the association with the first parent object (S1047). Next, the structure control unit 152 executes association with the second parent object (S1048). Then, the management device 100 ends the process.

[0108] On the other hand, if the association destination of the parent object is not changed (No in S1045), the structure control unit 152 skips the processes from S1046 to S1048, and the management device 100 then ends the process.

[0109] On the other hand, if there is no parent object corresponding to the input object (No in S1043), the structure control unit 152 determines whether or not there is a target parent object (S1049).

[0110] If the target parent object exists (Yes in S1049), the structure control unit 152 newly registers the input child object (S1050). Next, the structure control unit 152 identifies the parent object to which the newly registered child object is to be associated (S1051). Next, the structure control unit 152 executes association with the parent object (S1052). Then, the management device 100 ends the process.

[0111] On the other hand, if the target parent object does not exist (No in S1049), the structure control unit 152 outputs an error (S1053), and the management device 100 then ends the process.

[0112] (effect) Next, we will explain the effects of the management device 100 according to this embodiment. In order to realize a workflow that bundles the status management of multiple tasks using conventional technology, specialized knowledge and experience are required to build a complex hierarchical structure, which can make it difficult to realize.

[0113] Therefore, the input receiving unit 151 of the management device 100 according to this embodiment receives input of information relating to a task at a predetermined granularity. The structure control unit 152 of the management device 100 associates parent objects with child objects based on the input information relating to the task at the predetermined granularity. Then, the display output unit 153 of the management device 100 outputs a workflow in which the parent objects and child objects are associated with each other.

[0114] As described above, the management device 100 manages the input object as a parent object or a child object. The management device 100 then associates the child object with a parent object according to the business status, thereby representing changes in the business status of the child object.

[0115] Therefore, it is possible to visualize changes in the business status of an object that is a single business, the current status, etc. As a result, the management device 100 of this embodiment has the effect of facilitating management across the statuses of multiple businesses.

[0116] The effects of each functional unit will be described in the following items. When the input object is determined to be a child object, the structure control unit 152 uses the item information of the child object to identify a first parent object to be associated with the child object. The structure control unit 152 associates the identified first parent object to be associated with the child object.

[0117] Through the above-described processing, the management device 100 can appropriately associate the input child object with the target parent object, thereby enabling an easy construction of a workflow.

[0118] Furthermore, the structure control unit 152 identifies a parent object as a target for association with a child object if at least one of the character string, numerical value, and identification information contained in the item information for each object satisfies the association condition between the child object and the parent object.

[0119] Conventionally, a user must identify a parent object to which a child object is to be associated, but the above-described process enables the management device 100 to automate the process of identifying a parent object that corresponds to an input child object, thereby achieving the effect of enabling efficient object association.

[0120] Furthermore, the structure control unit 152 identifies the type of business related to the child object by using at least one of a character string, a numerical value, and identification information included in the item information of the input child object. The structure control unit 152 adds information related to the identified type of business to the child object.

[0121] By the above-described process, the management device 100 can automatically identify which business the input child object is related to. As a result, the management device 100 reduces the input load of objects and improves the efficiency of the entire business.

[0122] When the structure control unit 152 determines that the input object is a child object associated with a first parent object and the status of the child object has been updated, the structure control unit 152 uses the item information of the child object to identify a second parent object with which the child object is to be associated. The structure control unit 152 releases the association between the child object and the first parent object. The structure control unit 152 associates the released child object with the identified second parent object.

[0123] By performing the above-described processing, the management device 100 moves the child object so as to correspond to the parent object according to the state of the child object, thereby enabling the user to easily understand the current state of the child object.

[0124] If the input object is determined to be a child object and, based on the preset execution steps of the object, there is no second child object located at a step earlier than the input first child object, the structure control unit 152 determines that the input of the first child object is an error.

[0125] The above-described process enables the management device 100 to determine an error, such as that the work is not being performed according to the proper procedure, when a second child object that should exist in the previous step of the input first child object does not exist. Furthermore, the management device 100 can prevent the user from violating the workflow by outputting the error determination to the user.

[0126] The structure control unit 152 prohibits processing to associate child objects with each other. Through the above-described processing, the management device 100 can limit the hierarchical structure of data to two levels, which is simpler than conventional hierarchical structures. Therefore, in an environment where many non-engineer employees work together, the management device 100 can improve the work efficiency of the entire organization by enabling the construction of easy workflows, even in a situation where people who can understand complex hierarchical structures coexist with people who cannot.

[0127] When the first parent object and the second parent object are corresponding objects, the structure control unit 152 adds information for identifying the first parent object to the item information of the second parent object and associates them.

[0128] By using a two-tier data structure instead of the conventional multi-tier data structure, the correspondence between the main parent objects is broken, but by performing the above-described processing, the management device 100 makes it possible to associate related parent objects with each other.

[0129] The structure control unit 152 registers or updates the information of an object determined to be a parent object. That is, if the input object is a parent object, the structure control unit 152 updates the information if the target parent object exists, and registers the object as a parent object if the target parent object does not exist. As a result, the management device 100 reduces the object input load and achieves the effect of improving the efficiency of the entire business.

[0130] <Modification> The following describes modified examples realized by the management device 100 according to this embodiment.

[0131] (Data, etc.) The objects, parent objects, child objects, business partners, NDAs, estimates, contracts, billing and payments, names of functional parts of the management device 100, steps, processes, names of steps or processes, etc. used in the description of the above embodiments are merely examples and can be changed as desired.

[0132] (Information stored in storage unit 140) The storage unit 140 according to this embodiment has been described as having an object storage unit 141 and a processing condition storage unit 142, and each individual storage unit stores the information shown in FIGS. 5 to 7, but is not limited to this.

[0133] For example, the object storage unit 141 can store, without limitation, item names and item contents other than those shown in Figures 5 and 6. Furthermore, the processing condition storage unit 142 can store, without limitation, conditions and processing contents other than those shown in Figure 7.

[0134] (Processing related to parent object by structure control unit 152) It has been explained that the structure control unit 152 according to this embodiment determines that an input object is a parent object by using the character string, numerical value, identification information, etc. included in the parent object 141a shown in Fig. 5. For example, the structure control unit 152 can execute the process of determining whether or not an input object is a parent object by using an item other than the "customer status" explained in this embodiment.

[0135] For example, the structure control unit 152 can determine that an input object is a parent object when a specific company name is included in the title field "Client Company Name." The structure control unit 152 can determine that an input object is a parent object when information about a specific company is included in the details field "Client Details." Furthermore, the structure control unit 152 can determine that an input object is a parent object when a specific person in charge name is included in the person in charge field "Person in Charge." Furthermore, the structure control unit 152 can determine that an input object is a parent object when a specific department name is included in the category field "Related Department Name."

[0136] (Processing related to child objects by structure control unit 152) As described above, the structure control unit 152 according to this embodiment performs a process of associating an input child object with a target parent object and a process of identifying the type of work, using the character string, numerical value, identification information, etc. included in the child object 141b shown in Fig. 6. For example, the structure control unit 152 can perform the above-described process of associating and identifying using an item other than the "quote creation status" described in this embodiment.

[0137] For example, the structure control unit 152 can perform a process of associating with the target parent object and a process of identifying the type of work using information about the estimate included in the title field "Estimate Name." The structure control unit 152 can also perform a process of associating with the target parent object and a process of identifying the type of work using information about the case included in the details field "Case Details." The structure control unit 152 can also perform a process of associating with the target parent object and a process of identifying the type of work based on a specific person's name included in the person in charge field "Person in Charge" or a specific department name included in the category field "Related Department Name."

[0138] (Regarding processing by management device 100) In the present embodiment, the management device 100 is described as automatically performing a process of associating an input object with a target parent object and a process of identifying a business type based on the item information included in the input object, but the present invention is not limited to this. For example, the management device 100 can receive a user instruction for associating an input object with a target parent object and an instruction for a business type, and perform processing based on the instruction.

[0139] For example, the management device 100 (structure control unit 152) can associate the input child object with the target parent object based on a predetermined instruction from the user such as "associate the input child object with the first parent object."

[0140] Furthermore, the management device 100 (structure control unit 152) can associate a child object associated with a first parent object with a second parent object, which is the target parent object, based on a predetermined instruction from the user, such as "associate a child object associated with a first parent object with a second parent object."

[0141] Note that the above-mentioned user's designations such as "associate the input child object with the first parent object" and "associate the child object associated with the first parent object with the second parent object" are merely examples. The management device 100 can receive user designations for the execution of various other processes and execute the processes based on the designations.

[0142] (Flowcharts, etc.) The steps in the flowcharts may be interchanged as long as there is no contradiction, and some steps may not be performed. In addition, conjunctions such as "next," "continue," "further," "at this time," and "on this occasion" used in the explanation of the flowcharts do not limit the order or timing of the execution of the processes in the flowcharts.

[0143] (others) Furthermore, among the processes described in each of the above embodiments, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically using known methods. In addition, the information including the processing procedures, specific names, various data, and parameters shown in the above documents and drawings can be changed as desired unless otherwise specified. For example, the various information shown in each drawing is not limited to the information shown in the drawings.

[0144] Furthermore, the components of each device shown in the figure are conceptual functional components and do not necessarily have to be physically configured as shown in the figure. In other words, the specific form of distribution and integration of each device is not limited to that shown in the figure, and all or part of them can be functionally or physically distributed and integrated in any unit depending on various loads, usage conditions, etc.

[0145] Furthermore, the above-described embodiments can be combined as appropriate within the scope of not causing any contradiction in the processing content. Furthermore, the effects described in this specification are merely examples and are not intended to be limiting, and other effects may also be obtained.

[0146] Although some embodiments of the present invention have been described in detail above with reference to the drawings, these are merely examples, and the present invention can be embodied in other forms that include various modifications and improvements based on the knowledge of those skilled in the art, including the forms described in the Disclosure of the Invention section.

[0147] Furthermore, the aforementioned "section, module, unit" can be read as "means" or "circuit," etc. For example, a selection section can be read as a selection means or a selection circuit.

[0148] <Hardware configuration> The management device 100 described above is realized, for example, by a computer 1000 configured as shown in Fig. 14. The following description will be given using the management device 100 as an example. Fig. 14 is a hardware configuration diagram showing an example of a computer that realizes the functions of the management device 100 according to the embodiment.

[0149] The computer 1000 includes a CPU 1100, a RAM 1200, a ROM 1300, a HDD 1400, a communication interface (communication I / F) 1500, an input / output interface (input / output I / F) 1600, and a media interface (media I / F) 1700.

[0150] The CPU 1100 operates and controls each unit based on programs stored in the ROM 1300 or the HDD 1400. The ROM 1300 stores a boot program executed by the CPU 1100 when the computer 1000 starts up, programs that depend on the hardware of the computer 1000, and the like.

[0151] The HDD 1400 stores programs executed by the CPU 1100, data used by the programs, etc. The communication interface 1500 receives data from other devices via a predetermined network NW and sends the data to the CPU 1100, and transmits data generated by the CPU 1100 to other devices via the predetermined network NW.

[0152] The CPU 1100 controls output devices such as a display and a printer, and input devices such as a keyboard and a mouse, via the input / output interface 1600. The CPU 1100 acquires data from the input devices via the input / output interface 1600. The CPU 1100 also outputs generated data to the output devices via the input / output interface 1600.

[0153] Media interface 1700 reads a program or data stored in recording medium 1800 and provides it to CPU 1100 via RAM 1200. CPU 1100 loads the program or data from recording medium 1800 onto RAM 1200 via media interface 1700 and executes the loaded program. Recording medium 1800 is, for example, an optical recording medium such as a DVD (Digital Versatile Disc) or a PD (Phase Change Rewritable Disc), a magneto-optical recording medium such as an MO (Magneto-Optical disk), a tape medium, a magnetic recording medium, or a semiconductor memory.

[0154] For example, when the computer 1000 functions as the management device 100, the CPU 1100 of the computer 1000 executes programs loaded onto the RAM 1200, thereby realizing the functions of the control unit 150. The CPU 1100 of the computer 1000 reads and executes these programs from the recording medium 1800, but as another example, the CPU 1100 may obtain these programs from another device via a predetermined network NW. [Explanation of symbols]

[0155] 100 Management device 110 Communications Department 120 Input section 130 Display section 140 Storage section 141 Object Storage 142 Processing condition memory unit 150 control section 151 Input reception unit 152 Structural Control Section 153 Display output unit 200 Terminal Device

Claims

1. A management device for managing a workflow including information about a business operation of a predetermined granularity as an object, an input receiving unit that receives input of information related to the business of the predetermined granularity; a structure control unit that associates a parent object, which is a management entity, with a child object that represents the status of a task of the predetermined granularity by being associated with the parent object based on the input information about the task of the predetermined granularity; a display output unit that outputs the workflow in which the parent object and the child object are associated with each other; A management device comprising:

2. The structural control unit includes: If the input object is determined to be the child object, Identifying a first parent object to be associated with the child object using item information of the child object; Associating the identified first parent object with the child object; The management device according to claim 1 .

3. The structural control unit includes: When the input object is determined to be the child object associated with a first parent object, and the status of the child object is updated, Identifying a second parent object to be associated with the child object using the item information of the child object; Disassociating the child object from the first parent object; Associating the child object whose association has been cancelled with the identified second parent object; The management device according to claim 1 .

4. The structural control unit includes: If the input object is determined to be the child object, and if there is no second child object located in a step before the input first child object based on the execution steps of the preset object, determining that the input of the first child object is an error; 4. The management device according to claim 2 or 3.

5. The structural control unit includes: prohibiting the process of associating the child objects with each other; 4. The management device according to claim 1, wherein the management device is a management device for managing a plurality of data.

6. The structural control unit includes: If at least one of a character string, a numerical value, and identification information included in the item information for each of the objects satisfies a matching condition between the child object and the parent object, the parent object is identified as a matching target for the child object.

4. The management device according to claim 2 or 3.

7. The structural control unit includes: Identifying the type of business related to the child object using at least one of a character string, a numerical value, and identification information included in the item information of the input child object; Adding information about the identified type of business to the child object; 4. The management device according to claim 2 or 3.

8. The structural control unit includes: If the first parent object and the second parent object are corresponding objects, adding information for identifying the first parent object to the item information of the second parent object and associating the information with the second parent object; 4. The management device according to claim 2 or 3.

9. The structural control unit includes: registering or updating information about the object determined to be the parent object; 3. The management device according to claim 1 or 2.

10. A management method executed by a management device that manages a workflow that includes information about a business of a predetermined granularity as an object, comprising: an input receiving step of receiving input of information about the business of the predetermined granularity; a structure control step of associating a parent object, which is a management entity, with a child object, which represents the status of a business of the predetermined granularity by being associated with the parent object, based on the input information on the business of the predetermined granularity; a display output step of outputting the workflow in which the parent object and the child object are associated with each other; A management method comprising:

11. A management program executed by a management device that manages a workflow that includes information about a business of a predetermined granularity as an object, an input receiving step of receiving input of information about the business of the predetermined granularity; a structure control procedure for associating a parent object, which is a management entity, with a child object, which represents the status of a business of the predetermined granularity by being associated with the parent object, based on the input information on the business of the predetermined granularity; a display output step of outputting the workflow in which the parent object and the child object are associated with each other; A management program comprising:

Images