JP2024074001A - Business improvement support device and program - Google Patents

Abstract

[Problem] The problem to be solved by the present invention is to provide a business improvement support device and program capable of supporting business improvement based on a business flow. [Solution] The business improvement support device of the embodiment comprises: a storage unit that associates a plurality of nodes related to the execution of a business with each of the nodes of a business flow that defines the order in which the business is performed, and stores attribute information including resources used in the business corresponding to the node; a creation means that creates a binary table based on the attribute information, in which business names of business executed at each node are arranged in one column in the order in which the business is performed, and resource names of all the resources included in the attribute information of each node are arranged in the other column, and in which specific information that can identify the resources used in the business is added for each business, and an output means that outputs information of the created binary table in a displayable manner. [Selected Figure] Fig. 13

Description

An embodiment of the present invention relates to a business improvement support device and program.

At sites where goods are produced or manufactured, or where products are received or inspected, for example, various tasks are carried out during the process. At such sites, in order to efficiently carry out various tasks sequentially, business flows are sometimes created that are written based on IPO notation (a chain of Input, Process, Output) such as BPMN (Business Process Model and Notation). For example, technology has been proposed that can automatically create business flows so that the input/output relationships between adjacent tasks are continuous.

By using the above-mentioned business flow, it is possible to confirm the procedure for performing each business and the relationships between the businesses. In addition, analyzing the relationship between each business and the resources used in that business is useful for improving business operations, as it can identify areas for improvement and lead to the formulation of business improvement measures. However, with conventional technology, it is not easy to analyze the relationship between the business operations in a business flow and the resources used in that business, and there is room for further improvement.

The problem that this invention aims to solve is to provide a business improvement support device and program that can provide business improvement support based on business flow.

The business improvement support device of the embodiment includes a storage unit that associates a plurality of nodes related to the execution of business with each of the nodes of a business flow that defines the order in which the business is performed, and stores attribute information including resources used in the business corresponding to the node; a creation means that creates a binary table in which, based on the attribute information, the business names of the business to be executed at each node are arranged in one column in the order in which the business is performed, and the resource names of all the resources included in the attribute information of each node are arranged in the other column, and the specific information that can identify the resources used in the business is added for each business, and an output means that outputs the information of the created binary table in a displayable manner.

FIG. 1 is a diagram illustrating an example of a configuration of a business improvement support system according to an embodiment. FIG. 2 is a diagram illustrating an example of a hardware configuration of a terminal device according to the embodiment. FIG. 3 is a diagram illustrating an example of a hardware configuration of a server device according to the embodiment. FIG. 4 is a diagram illustrating an example of a visualized business flow according to the embodiment. FIG. 5 is a diagram illustrating an example of a data configuration of the attribute storage unit according to the embodiment. FIG. 6 is a diagram illustrating an example of another data configuration of the attribute storage unit according to the embodiment. FIG. 7 is a diagram illustrating an example of a functional configuration of a terminal device and a server device according to the embodiment. FIG. 8 is a diagram showing an example of a binary table created according to the embodiment. FIG. 9 is a diagram showing another example of a binary table created according to the embodiment. FIG. 10 is a diagram illustrating an example of a data configuration of the attribute storage unit in a state in which information on task ratios and man-hours has been updated in the server device of the embodiment. FIG. 11 is a flowchart illustrating an example of a process related to attribute information creation executed by the server device according to the embodiment. FIG. 12 is a flowchart illustrating an example of a process related to automatic assignment of a process number executed by the server device of the embodiment. FIG. 13 is a flowchart illustrating an example of a process for creating and modifying a binary table executed by the server device according to the embodiment. FIG. 14 is a flowchart illustrating an example of a control process of the terminal device according to the embodiment.

The following describes the embodiments in detail with reference to the drawings. Note that the present invention is not limited to the embodiments described below.

Fig. 1 is a diagram showing an example of the configuration of a business improvement support system according to an embodiment. As shown in Fig. 1, the business improvement support system 1 has a terminal device 10 and a server device 20. The terminal device 10 and the server device 20 are connected to each other so as to be able to communicate with each other via a network N such as a LAN (Local Area network).

The terminal device 10 is a terminal device used by a user of the business improvement support system 1. The terminal device 10 executes various processes in response to user operations. For example, the terminal device 10 cooperates with the server device 20 to assist in the creation of a business flow (described below) and to display the business flow. The terminal device 10 can be realized, for example, by a stationary information processing device such as a PC (Personal Computer) or a portable information processing device such as a notebook PC, a tablet terminal, or a smartphone.

The server device 20 is an example of a business improvement support device. The server device 20 supports the creation and viewing of business flows. The server device 20 also provides the user with attribute information associated with the business flow and necessary for executing the business. The server device 20 also supports the creation of a binary table 90 (see Figures 8 and 9) described below.

In addition, the server device 20 provides the business flow, attribute information and binary table information (described later) to the terminal device 10 in response to a request from a user of the terminal device 10.

In this embodiment, an example in which the server device 20 is realized by a single device will be described, but this is not limiting, and the server device 20 may be realized by multiple devices, for example, using a technology such as cloud computing.

Next, the configuration of the terminal device 10 and server device 20 described above will be described.

Figure 2 is a diagram showing an example of the hardware configuration of the terminal device 10. As shown in Figure 2, the terminal device 10 has a computer configuration including a CPU (Central Processing Unit) 11, a ROM (Read Only Memory) 12, and a RAM (Random Access Memory) 13.

The CPU 11 is an example of a processor, and controls each part of the terminal device 10. The ROM 12 stores various programs. The RAM 13 is a workspace in which programs and various data are deployed.

The terminal device 10 also includes a display unit 14, an operation unit 15, a memory unit 16, and a communication unit 17.

The display unit 14 is composed of a display device such as an LCD (Liquid Crystal Display). The display unit 14 displays various information under the control of the CPU 11. The operation unit 15 has a keyboard, a pointing device, etc. The operation unit 15 outputs the operation content received from the user to the CPU 11. The operation unit 15 may be a touch panel provided on the display screen of the display unit 14.

The storage unit 16 is composed of storage media such as a hard disk drive (HDD) or flash memory, and maintains its stored contents even when the power is cut off. The storage unit 16 stores programs that the CPU 11 can execute and various setting information. For example, the storage unit 16 stores application programs such as a web browser that can access the server device 20 and display and operate various operation support screens provided by the server device 20.

The CPU 11 executes various processes by functioning as a functional unit by operating according to programs stored in the ROM 12 and memory unit 16 and deployed in the RAM 13.

The communication unit 17 is a communication interface that can be connected to the network N. The communication unit 17 communicates with external devices such as the server device 20 via the network N.

Figure 3 is a diagram showing an example of the hardware configuration of the server device 20. As shown in Figure 3, the server device 20 has a computer configuration including a CPU 21, a ROM 22, and a RAM 23.

The CPU 21 is an example of a processor, and controls each part of the server device 20. The ROM 22 stores various programs. The RAM 23 is a workspace in which programs and various data are deployed.

The server device 20 also includes a display unit 24, an operation unit 25, a memory unit 26, and a communication unit 27.

The display unit 24 is composed of a display device such as an LCD. The display unit 24 displays various information under the control of the CPU 21. The operation unit 25 has a keyboard, a pointing device, etc. The operation unit 25 outputs the operation content received from the user to the CPU 11. The operation unit 25 may be a touch panel provided on the display screen of the display unit 24.

The memory unit 26 is an example of a storage device. The memory unit 26 is composed of a storage medium such as a HDD or flash memory, and maintains the stored contents even when the power is cut off. The memory unit 26 stores programs that the CPU 21 can execute and various setting information. For example, the memory unit 26 stores web application programs, etc. The CPU 21 executes various processes by functioning as various functional units according to the programs stored in the ROM 22 or the memory unit 26 and deployed in the RAM 23.

The memory unit 26 also stores a business flow DB 261 and a table memory unit 262. The business flow DB 261 is a database for storing and managing business flows. The business flow DB 261 has a business flow memory unit 2611 and an attribute memory unit 2612.

The business flow storage unit 2611 stores information about business flows. Here, a business flow is a data file in which the business executed at each node related to the performance of the business and the execution contents executed in the business are described as a series of procedures. For example, a business flow describes the execution contents and procedures executed by a business related to the acceptance, inspection, and storage of goods and parts. The information stored in the business flow storage unit 2611 will be described later in FIG. 4. The attribute storage unit 2612 stores attribute information related to multiple businesses executed sequentially in a business flow. The attribute information stored in the attribute storage unit 2612 will be described later in FIG. 5 and FIG. 6.

Fig. 4 is a diagram showing an example of a state in which a business flow is visualized based on the business flow information stored in the business flow storage unit 2611. As shown in Fig. 4, the business flow storage unit 2611 stores information on business flows that can be visualized. Note that in this embodiment, as an example, it is assumed that information on business flows related to the reception and storage of goods or products is stored in the business flow storage unit 2611.

As shown in FIG. 4, the business flow storage unit 2611 stores the pool names of pools that indicate business areas in which a series of business operations are divided at a predetermined granularity, and nodes that indicate the types of business operations executed within the pools for each pool. Here, the pool names are a higher-level concept than the node names (business names), and in the example shown in FIG. 4, the pool names correspond to "receiving inspection" and "storage" of goods, articles, parts, products, etc. Also, in the example of FIG. 4, the following nodes are stored as business operations performed in the pool name "receiving inspection", including node Aa for the business "delivery", node Ab for the business "delivery note confirmation", node Ac for the business "lot, item, and quantity check", node Ad for the business "specification search", node Ae for the business "sampling inspection work", and node Af for the business "inspection completion".

In addition, the following nodes are stored as nodes for tasks performed in the pool named "storage": node Ba for task "inspected item", node Bb for task "check storage instructions and print list", node Bc for task "find shelf number and store", node Bd for task "enter storage quantity on list", node Be for task "put list in completion box", and node Bf for task "storage complete". Note that "Delivery", "Confirm delivery note", "Check lot/item/quantity", "Search specifications", "Sampling inspection", "End of inspection", "Inspected item", "Check storage instructions and print list", "Find shelf number and store", "Enter storage quantity on list", and "storage complete" are the node names of each node.

The business flow storage unit 2611 also stores information indicating the order in which business operations are performed at each node. For example, in FIG. 4, it is stored that business operations are performed in the following order: Node Aa → Node Ab → Node Ac → Node Ad → Node Ae → Node Af → Node Ba → Node Bb → Node Bc → Node Bd → Node Be → Node Bf. The order in which business operations are performed at each node is determined, for example, by displaying the nodes that perform the business operations on a screen and connecting the nodes with arrows in the order in which the business operations are performed, so that the business operations are performed in order from the upstream side to the downstream side of the arrow. Note that determining the order in which business operations are performed in this manner can be performed using a known method for creating business flows, such as a flowchart or BPMN (Business Process Modeling Notation).

Each node is associated with attribute information related to the node's business. The attribute storage unit 2612 stores attribute information related to the business of each node in association with each node stored in the business flow storage unit 2611. For example, the attribute information includes information necessary to execute the business of each node.

Attribute information related to "Delivery" of node Aa shown in FIG. 4 is illustrated in FIG. 5. The attribute information related to "Delivery" includes node name 26121, process number 26122, resource information 26123, Input node 26124, Output node 26125, pool name 26126, and analysis 26127. Node name 26121 is information indicating the node name of the node associated with the attribute information. Process number 26122 is information indicating the execution order of the tasks executed by the node in the pool to which the node belongs. Resource information 26123 is information indicating the resources used in executing the tasks of the node. The resources include physical resources and human resources. Input node 26124 is a process number indicating the execution order of the tasks of the node executed immediately before the node. Output node 26125 is a process number indicating the execution order of the tasks of the node executed immediately after the node. Pool name 26126 is information indicating the name of the pool to which the node's business belongs. Analysis 26127 is information indicating whether or not work is involved in executing the node's business. If work is involved, it is written as "target", and if no work is involved, it is written as "not target". Whether the analysis is target or not can be set on a pool name basis or on a node basis.

Attribute information related to "Delivery" shown in FIG. 5 is stored as node name 26121, with "Delivery" information stored as process number 26122 indicating the "Delivery" node. Also, as resource information 26123 (physical resource "Facilities") of the resources used to execute the task at the "Delivery" node, "Supplier", "EDI system", and "Parts warehouse" information are stored, and as resource information 26123 (human resource "Executor"), "Warehouse staff" is stored. Also, since there is no node that executes the task immediately before the "Delivery" node, a blank is stored in Input node 26124, which is the process number indicating the execution order of the task at the node where the task is executed immediately before the node. Also, "A002" is stored as Output node 26125, which is the process number indicating the execution order of the task at the node where the task is executed immediately after the "Delivery" node (i.e., the "Delivery note confirmation" node). Additionally, as analysis 26127, "not applicable" information is stored, indicating that the node does not involve any work related to the business.

Attribute information related to "Delivery Note Check" is illustrated in FIG. 6. The attribute information related to "Delivery Note Check" is stored as node name 26121, which is "Delivery Note Check". Also, "A002" is stored as process number 26122, which indicates the "Delivery Note Check" node. Also, "Inspection Department" and "Part-time Worker" are stored as resource information 26123 (human resource "Executor") of the resources used to execute the task at the "Delivery Note Check" node, and "EDI System", "Scanner", and "Multifunction Printer" are stored as (physical resource "Equipment"). Also, input node 26124 stores "A001", which is the process number of the "Delivery" node, which is the node that executed the task immediately before the "Delivery Note Check" node. Also, output node 26125 stores "A003", which is the process number of the "Lot, Item, and Quantity Check" node, which is the node that executes the task next to the "Delivery Note Check" node. Additionally, as analysis 26127, "target" information is stored, indicating that the node involves work related to the business.

The business flow and attribute information are created by the business flow creation support unit 211, which is realized by cooperation between the CPU 21 and the application program stored in the memory unit 26. The user can create business flows and attribute information by using the creation support function of the business flow creation support unit 211, for example, by accessing the server device 20 via the terminal device 10 (for example, the user can set the creation and execution order of nodes while operating the visualized business flow). The created business flow and attribute information are stored in association with each other. The memory unit may also store business flows and attribute information created by another terminal device 10.

Returning to the explanation of FIG. 3, the table storage unit 262 stores information on a binary table 90 (see FIG. 8 and FIG. 9) that is automatically created by the server device 20 based on the attribute information stored in the attribute storage unit 2612. The binary table 90 is, for example, a table formed in a matrix shape with a horizontal axis (X axis) and a vertical axis (Y axis), in which node names indicating the contents of a task are arranged in the order of task execution in one column (e.g., along the X axis), and resources used in the task are arranged in the other column (e.g., along the Y axis), thereby showing the relationship between the task and the resources used in the task. Details of the binary table 90 will be described later with reference to FIG. 8 and FIG. 9.

Next, the functional configuration of the terminal device 10 and the server device 20 will be described with reference to FIG. 7. FIG. 7 is a diagram (functional block diagram) showing an example of the functional configuration of the terminal device 10 and the server device 20.

As shown in FIG. 7, the terminal device 10 has a display control unit 111 and an operation reception unit 112 as functional units.

Some or all of the functional units of the terminal device 10 may be software configurations realized by cooperation between the CPU 11 of the terminal device 10 and a program stored in a memory (e.g., the ROM 12, the storage unit 16). Also, some or all of the functional units of the terminal device 10 may be hardware configurations realized by a dedicated circuit or the like mounted on the terminal device 10.

The display control unit 111 of the terminal device 10 controls the display unit 14 to display various screens on the display unit 14. For example, the display control unit 111 displays various operation support screens provided by the server device 20 on the display unit 14. A user can access the server device 20 via the terminal device 10, for example, obtain information on an input screen for business flows and attribute information from the server device 20, and display the information on the display unit 14 to create and modify business flows and attribute information.

The operation reception unit 112 of the terminal device 10 receives user operations via the operation unit 15. For example, when the operation reception unit 112 receives an operation on the operation assistance screen displayed on the display unit 14, it notifies the server device 20 of the content of the operation.

On the other hand, as shown in FIG. 7, the server device 20 has a business flow creation support unit 211, a binary table creation unit 212, and a transmission unit 213 as functional units.

Some or all of the functional units of the server device 20 may be software configurations realized by cooperation between the CPU 21 of the server device 20 and a program stored in a memory (e.g., the ROM 22, the storage unit 26). Also, some or all of the functional units of the server device 20 may be hardware configurations realized by a dedicated circuit or the like mounted on the server device 20.

The business flow creation support unit 211 of the server device 20 provides an operation support screen to assist in creating (or editing) and viewing business flows.

For example, the business flow creation support unit 211 provides an operation support screen on which drawing parts and the like corresponding to the notation rules of BPMN are arranged. Furthermore, when the business flow creation support unit 211 receives an operation to create a business flow via the operation support screen, the business flow creation support unit 211 creates a data file representing the business flow according to the content of the operation, and stores the data file in the business flow storage unit 2611.

When a business flow to be displayed or edited is specified from among the business flows stored in the business flow DB 261, the business flow creation support unit 211 reads the specified business flow and creates information that can be displayed on the terminal device 10 with the flow diagram of the business flow visualized.

The method of selecting a business flow is not particularly limited. For example, the flow names of business flows stored in business flow DB261 may be displayed as a list, and the selection of a business flow may be accepted from the displayed list. Also, for example, the flow diagrams represented by each business flow stored in business flow DB261 may be displayed as a list using thumbnails or the like, and the selection of a business flow may be accepted from the displayed list.

The business flow creation support unit 211 also automatically assigns a process number to each node related to the created business flow in the order in which the business is performed. The method of assigning the process number can be any known method, and there is no particular restriction.

The business flow creation support unit 211 also supports the creation of attribute information. For example, when a node is selected, the business flow creation support unit 211 displays a creation support screen for inputting attribute information related to the business of the node.

The display unit 14 of the terminal device 10 displays the node name, process number, input node, output node, pool name, etc. of the selected node as a creation support screen, and resource information, analysis, etc. can be input.

In addition, the business flow creation support unit 211 associates the node to which the process number has been assigned with the stored attribute information by storing the assigned process number in the attribute storage unit 2612 as attribute information of the node (storing it as process number 26122).

The business flow creation support unit 211 also displays part of the associated attribute information at the node related to the visualized business flow. The part of the information can be selectively set from the attribute information; for example, the "node name" can be selected. When the "node name" is selected, the node name representing the node is displayed together with the node as part of the business flow (see FIG. 4).

The binary table creation unit 212 is an example of a creation means. Based on the nodes set in the business flow and attribute information related to the nodes, the binary table creation unit 212 creates a binary table 90 in which the node names (business names) 92 of each node are arranged in one column (e.g., the X-axis direction) in the order of process numbers, and the resource names 95 of all resources related to the business executed at each node are arranged in the other column (e.g., the Y-axis direction). In addition, the binary table creation unit 212 clearly indicates the relationship between the business and the resource by attaching a mark (specific information) to the intersection of the arranged node name and the resource name 95 of the resource used in the business of the node name in the created binary table 90.

Specifically, the binary table creation unit 212 arranges the pool names, process numbers, and node names related to each node in one column (e.g., horizontal column) in the order in which the tasks are performed in the business flow (i.e., in the order of the process numbers assigned to each node), and arranges the resource names of the resources used by each node to perform the tasks in the other column (e.g., vertical column) in pairs of physical resources and human resources. That is, a binary table 90 is created in which the node names and resource names are arranged in a matrix. Then, the binary table creation unit 212 marks the intersection of the arranged node names with the resource names (physical resources and human resources) used to perform the tasks at the node in question, based on the attribute information, in the created binary table 90. The created binary table 90 is stored in the table storage unit 262.

Figure 8 is an example of a binary table 90 created by the binary table creation unit 212. In the binary table 90, pool names 91 ("receiving inspection" and "storage" in Figure 8 (these pool names are examples)) that are business area names are arranged in the horizontal direction (X-axis direction). In addition, in association with each pool name 91, node names 92 ("delivery", "confirm delivery note", "check lot/item/quantity", "search specifications", "sampling inspection work", "inspection completed", "inspection completed item", "check storage instruction sheet and print list", "find shelf number and store", "enter storage quantity in list", "storage completed") that are included in the pool name 91 are arranged in the order of business execution, and process numbers 93 assigned to each node ("A001" to "A006" and "B001" to "B006" in Figure 8) are arranged in the order of business execution. The process numbers are automatically assigned from "A001" to "B006" in the order of business execution.

In addition, in the binary table 90, business area names 94 (in FIG. 8, "resource 1" (physical resource), "resource 2" (human resource), and "worker") are arranged in the vertical direction (Y-axis direction). In addition, in the binary table 90, in correspondence with each business area name 94, resource names 95 included in each business area name 94 (in FIG. 8, "supplier," "EDI system," "production system," "scanner," "multifunction printer," "handy terminal," "parts warehouse," and "completed box" (all of which are physical resources), "inspection department staff," "warehouse staff," and "part-time staff" (all of which are human resources) (these resource names are just examples)) are arranged.

In other words, the binary table creation unit 212 creates a binary table 90 in which the pool name 91, node name 92, and process number 93 are arranged along the X-axis, and the business area name 94 and resource name 95 are arranged along the Y-axis.

In addition, in FIG. 8, the created binary table 90 has an "*" mark (an example of identifying information, an example of identifying information) added to the column of the intersection between the node name 92 and the resource name 95 of the resource used to execute the task at each node based on the created attribute information. That is, in each node name 92, identifying information that can identify the resource used in the task indicated by the node name 92 is added. For example, in the node with the task name "Delivery", an "*" mark is added to the intersection with the resources used, "Supplier", "EDI system", "Parts warehouse", and "Warehouse staff", based on the "resource information" included in the attribute information shown in FIG. 5.

The binary table 90 also has each task area name 94 of "worker" in the column direction (Y-axis direction). In the binary table 90, "inspection department staff", "warehouse staff", "part-time worker", "man-hours", and "task subtotal by pool" (these resource names are examples) are arranged as resource names 95 included in each task area name 94 in association with each task area name 94 of "worker". In the resource name 95 "inspection department staff", "warehouse staff", and "part-time worker" related to "worker", a task ratio (%) indicating the ratio of time the worker engages in the task related to the node name 92 written on the horizontal axis is entered. Since "inspection department staff", "warehouse staff", and "part-time worker" each have their own post, the task ratio for each may differ. In the resource name 95 "man-hours" column, the average time the worker engages in the task is entered. In the "task subtotal by pool", the total time entered in the process column is entered.

The binary table 90 created in this way can be displayed on the display unit 14 in response to a request from the terminal device 10. For example, a user of the terminal device 10 can look at the binary table 90 shown in FIG. 8 and check the resources marked with an "*" by node name. This makes it possible to consider business improvements, such as reviewing the resources used in the business. The binary table 90 supports such business improvements.

Returning to the explanation of FIG. 7, the transmission unit 213 is an example of an output means. The transmission unit 213 outputs information about the created binary table 90 in a displayable manner. In an embodiment, the transmission unit 213 transmits (outputs) information about the binary table 90 created by the binary table creation unit 212 to the terminal device 10 that has requested display, in a manner that the terminal device 10 can display it.

The display control unit 111 of the terminal device 10 that has received the information related to the binary table 90 displays, for example, the binary table 90 shown in FIG. 8 on the display unit 14 based on the received information. In this state, the terminal device 10 is able to input information from the operation unit 15. For example, a user of the terminal device 10 can input information related to task ratios and man-hours into the worker column 97 of the displayed binary table 90. The information related to task ratios and man-hours is input by a person operating the operation unit 15. The operation reception unit 112 of the terminal device 10 receives the input information related to task ratios and man-hours. The information of the binary table 90 that has been changed based on the information received by the operation reception unit 112 is transmitted from the terminal device 10 to the server device 20.

The server device 20 updates the information of the binary table 90 stored in the table storage unit 262 based on the change information received from the terminal device 10. The information of the relevant portion of the associated attribute information stored in the attribute storage unit 2612 is also updated. Note that in the example of Figure 8, the area 96 shown in black is set to "not applicable" in analysis 26127, and input is not possible because no work is required by the operator.

Figure 9 shows an example of a binary table 90 in an updated state in which the operation reception unit 112 receives input of information related to business ratios and information related to man-hours, the terminal device 10 transmits binary table change information in which the binary table 90 has been modified, the server device 20 receives the binary table change information, and the binary table creation unit 212 stores and updates the binary table 90 in the table storage unit 262.

As shown in Figure 9, the worker column 97 corresponding to each node contains the work ratio by type of worker at each node (e.g., the percentage of time involved in the work of that node). In Figure 9, the work ratios involved by workers in the inspection department are 5% for node A001 "Confirm delivery note", 10% for node A003 "Check lot, item, and quantity", 25% for node "Search specifications", and 60% for sampling inspection work.

Also, as shown in FIG. 9, the updated binary table 90 stores the man-hours that indicate the time required to execute a task at each node.

The binary table creation unit 212 highlights, for example, the point (intersection) with the highest task ratio in the information on task ratios and man-hours in the updated binary table 90. The highlighting is performed, for example, by hatching the area of the intersection or by making the background color different from that of the other intersections (making it stand out), so that the intersection can be displayed in a recognizable manner that distinguishes it from the other intersections. In FIG. 9, the intersection 98 between node A005 of "sampling inspection work" and the inspection department worker, the intersection 99 between node B003 of "find shelf number and store" and the warehouse worker, and the intersection 100 between node B003 of "find shelf number and store" and the part-time worker have a higher ratio than the task ratios of the other intersections, and are therefore stored so as to be able to be highlighted.

In addition, the information on the task ratio and man-hours entered on the terminal device 10 is reflected in the attribute information associated with the binary table 90 and stored in the attribute storage unit 2612 as the binary table 90 is updated.

Figure 10 is an example of attribute information stored in the attribute storage unit 2612 for node A002 of "Delivery note confirmation" reflecting the inputted work ratio. As shown in Figure 10, after the resource information "Inspection department", the information "5%" is updated (stored) as the inspection department's work ratio for that task, and after "Part-time worker", the information "10%" is updated (stored) as the part-time worker's work ratio for that task.

The information of the binary table 90 thus updated and stored can be displayed on the terminal device 10. For example, when looking at the binary table 90 shown in FIG. 9, it can be determined that the highlighted intersections (intersection 98, intersection 99, intersection 100) are tasks that have a high task ratio and place a heavy burden on the worker, executed at the node. For this reason, it is possible to consider improving the task, for example by reviewing the resources used in the task. The binary table 90 supports such task improvements.

For example, the workload ratio of the inspection department staff for the task of "sampling inspection search" is high at 60%. Currently, the physical resource used for the task "sampling inspection search" is a scanner, but it is possible to consider whether it is possible to reduce the workload ratio by changing this scanner to another (or new) resource. Additionally, currently, the human resource used for the task "sampling inspection search" is an inspection department staff member, but it is possible to consider whether it is possible to reduce the workload ratio by changing the inspection department staff member to another person or by increasing the number of inspection department staff members.

Next, the control process of the server device 20 will be described. FIG. 11 is a flowchart showing an example of a process related to the creation of attribute information executed by the server device 20 of the embodiment. As shown in FIG. 11, the CPU 21 of the server device 20 calls up attribute information related to a specified node from the attribute storage unit 2612. The CPU 21 then displays the called up attribute information on the display unit 24 (S11). For the displayed attribute information, the person in charge operates the operation unit 25 to input information related to the node name 26121, resource information 26123, pool name 26126, and analysis 26127. The process number 26122, Input node 26124, and Output node 26125 are automatically input with an automatically assigned process number, which will be described later in FIG. 12.

Next, the CPU 21 determines whether information has been input for the displayed attribute information (S12). This determination is made, for example, based on whether the person in charge has operated an input end button (not shown). The CPU 21 waits until information has been input (No in S12), and if it determines that information has been input for the displayed attribute information (Yes in S12), the CPU 21 stores attribute information including the input information in the attribute storage unit 2612, and updates the storage of the attribute information (S13). The CPU 21 then ends the process. In this state, the attribute information stores a process number, thereby associating each node with the attribute information, which is information about that node.

Note that when a display request for attribute information is made from the terminal device 10 and attribute information is input in the terminal device 10, FIG. 11 should be read as follows. That is, in S11, the CPU 21 transmits the attribute information called from the attribute storage unit 2612 to the terminal device 10. The CPU 11 of the terminal device 10 displays the received attribute information on the display unit 14. Then, in the terminal device 10, the user operates the operation unit 15 to input information related to the node name 26121, resource information 26123, pool name 26126, and analysis 26127. The CPU 11 transmits attribute information including the input information to the server device 20. The server device 20 determines whether attribute information has been received from the terminal device 10 (S12), and if it is determined that attribute information has been received (Yes in S12), stores the attribute information in the attribute storage unit 2612 and updates the storage of the attribute information (S13). Even in this case, the process number 26122, the input node 26124, and the output node 26125 are automatically stored in the attribute storage unit 2612 as automatically assigned process numbers, which will be described later in FIG. 12.

Next, the automatic assignment of process numbers will be described. FIG. 12 is a flowchart showing an example of a process related to the automatic assignment of process numbers executed by the server device 20 of the embodiment. As shown in FIG. 12, the CPU 21 judges whether an instruction to assign a process number to the created business flow has been given (S21). This instruction is issued, for example, when an operation to assign a process number to the created business flow is performed, or automatically when the business flow is created. If it is judged that an instruction to assign a process number has been given (Yes in S21), the CPU 21 assigns a process number to each node in the created business flow in the order of business execution (S22). Then, the assigned process number is stored in each node of the business flow stored in the business flow storage unit 2611 and in the process number 26122 of the attribute information stored in the attribute storage unit 2612 in association with each node (S23), the process number one before the process number is stored in the Input node 26124 (S23), and the process number one after the process number is stored in the Output node 26125 (S23). The CPU 21 then ends the process.

Also, if it is determined in S21 that the instruction is not to assign a process number (No in S21), it is determined whether the business flow stored in the business flow storage unit 2611 has been changed, such as whether some nodes have been deleted, or new nodes have been added, or whether some nodes have been deleted and new nodes have been added (S24). The business flow is changed, for example, by the terminal device 10. The CPU 21 determines whether the business flow has been changed based on whether there has been an instruction to change from the terminal device 10. If it is determined that the business flow has been changed (Yes in S24), the CPU 21 reassigns a new process number to the entire business flow after the change (S25). In the process of S25, a process is performed to store the new process number in the attribute information. Then, the CPU 21 ends the process.

If it is determined that there is no change in the business flow (No in S24), the CPU 21 ends the process.

When a control flow is created in this way, the CPU 21 assigns a process number to each node in the created business flow in the order in which the business is performed. The assigned process numbers are stored as attribute information. Then, when the business flow is changed, the CPU 21 assigns a new process number to the changed business flow. The assigned process numbers are stored as attribute information for each node.

Next, the control of creating the binary table 90 based on the attribute information stored in the attribute storage unit 2612 in the server device 20 will be described. FIG. 13 is a flowchart showing an example of the process related to the creation and modification of the binary table 90 executed by the server device 20 of the embodiment. As shown in FIG. 13, the CPU 21 judges whether an instruction to create the binary table 90 has been received (S31). The instruction to create the binary table 90 is issued by performing an operation to specify a business flow from the operation unit 25 of the server device 20. Alternatively, the instruction to create the binary table 90 is issued by receiving an instruction signal to create a binary table related to the business flow from the terminal device 10 in association with the specification of the business flow specified from the operation unit 15 of the terminal device 10.

When it is determined that an instruction to create a binary table 90 has been issued (Yes in S31), all attribute information for the specified business flow is read from the attribute storage unit 2612 (S32). Then, the binary table creation unit 212 (creation means) creates a binary table 90 based on the read attribute information (S33). Then, the binary table creation unit 212 assigns specific information to the resource name 95 used in correspondence with the business of each node name 92 in the binary table 90 created based on the read attribute information. That is, the binary table creation unit 212 creates a binary table 90 in which an * is added to the intersection with the resource name 95 used in correspondence with the business of each node name 92 in the binary table 90 created based on the read attribute information. Then, the CPU 21 stores the information of the created binary table 90 in the table storage unit 262 (S34). Then, the CPU 21 ends the process. Then, the CPU 21 ends the process.

Also, if it is determined that the instruction is not to create a binary table 90 (No in S31), the CPU 21 determines whether information of a request to display the created binary table 90 has been received from the terminal device 10 (S41). If it is determined that information of a request to display the binary table 90 has been received from the terminal device 10 (Yes in S41), the transmission unit 213 transmits information of the binary table 90 stored in the table storage unit 262 (information that allows the terminal device 10 to display the binary table 90) to the terminal device 10 (S42). Then, the CPU 21 ends the process.

Also, if it is determined that the request is not a display request for the binary table 90 from the terminal device 10 (No in S41), the CPU 21 determines whether binary table change information has been received from the terminal device 10 (S51). When the terminal device 10 inputs information on the business ratio or the process into the binary table 90 displayed on the terminal device 10, the terminal device 10 receives binary table change information, which is information on the binary table 90 reflecting the information on the business ratio or the process. If it is determined that the binary table change information has been received from the terminal device 10 (Yes in S51), the binary table creation unit 212 stores the binary table change information received from the terminal device 10 in the table storage unit 262 (S52). The binary table creation unit 212 also updates the attribute information stored in the attribute storage unit 2612 based on the received binary table change information (S52). That is, the binary table creation unit 212 stores new attribute information reflecting the information on the business ratio or the process input on the terminal device 10 in the attribute storage unit 2612 (S52).

Next, the binary table creation unit 212 extracts the task with the largest workload for each worker type from the stored task ratios in the updated binary table 90, and highlights the intersection with the extracted node with the largest workload (S53). Then the CPU 21 ends the process.

Next, the control process of the terminal device 10 will be described. FIG. 14 is a flowchart showing an example of the control process of the terminal device 10 of the embodiment. As shown in FIG. 14, the CPU 11 of the terminal device 10 judges whether a display request operation has been made to display the binary table 90 on the terminal device 1 (S61). The display request operation of the binary table 90 is performed, for example, by operating the operation unit 15. If it is determined that a display request operation of the binary table 90 has been made (Yes in S61), the CPU 11 transmits information indicating a display request for the binary table 90 to the server device 20 (S62).

Next, the CPU 11 judges whether the information of the binary table 90 has been received from the server device 20 (S63). The CPU 11 waits until the information of the binary table 90 has been received (No in S63), and if it judges that the information of the binary table 90 has been received from the server device 20 (Yes in S63), the CPU 11 displays the binary table 90 on the display unit 14 based on the received information of the binary table 90 (S64).

Next, the CPU 11 determines whether the contents of the displayed binary table 90 have been changed (S65). If either or both of the task ratio information and the labor-hour information have been entered into the displayed binary table 90, the CPU 11 determines that the contents of the binary table 90 have been changed.

When the contents of the binary table 90 are changed, the CPU 11 transmits binary table change information, which is information on the binary table 90 including the changed information (either or both of the input business ratio information and labor-hour information), to the server device 20 (S66). Then, the CPU 11 ends the process.

If it is determined in S61 that the operation is not a request to display the binary table 90 (No in S61), the CPU 11 proceeds to S65, and if it is determined that the contents of the binary table 90 have not been changed (No in S65), the CPU 11 ends the process.

Such a terminal device 10 again requests display of a binary table 90 including either or both of the task ratio information and the labor-hour information in step S61, and displays the binary table 90 shown in FIG. 9 in step S64. Therefore, a user who sees the display can determine which tasks have a high task ratio and a heavy burden among the tasks executed at each node. Therefore, for example, it is possible to consider improving the tasks by reviewing the resources used in the tasks.

As described above, the server device 20 of the embodiment includes a storage unit 26 that associates multiple nodes related to the execution of tasks with each of the nodes of a task flow that defines the order in which the tasks are performed, and stores attribute information including resources used in the tasks corresponding to the nodes; a creation means 212 that creates a binary table 90 in which, based on the attribute information, node names 92 of tasks executed at each node are arranged in one column in the order in which the tasks are performed, and resource names 95 of all the resources included in the attribute information of each node are arranged in the other column, and in which specific information that can identify the resources used in each task is added for each task; and an output means 213 that outputs the information of the created binary table 90 in a displayable manner.

The binary table 90 created by the server device 20 in this embodiment allocates the resources used in each task, and for each node, specific information is attached that identifies the resources used in the task executed at that node. By outputting this binary table 90 in a displayable manner, the output destination can visually grasp the resources used for each task. Therefore, it is possible to review the resources available for the tasks executed at each node, and it becomes possible to provide support for task improvement based on the task flow, such as considering whether task improvement can be performed to reduce the time required to execute the task.

In addition, the server device 20 of the embodiment outputs a binary table 90 including either or both of task ratio information and labor-hour information, allowing the output destination to visually grasp the resources used for each task and determine which tasks executed at each node have a high task ratio and/or a large labor-hour count and are therefore a heavy burden. In other words, the relationship between the time required to execute a task and the resources used can be seen. Therefore, for example, by reviewing the resources used in the task, it is possible to consider improvements to the task, such as whether the time required to execute the task can be reduced. This makes it possible to provide support for task improvement based on the task flow.

Although an embodiment of the present invention has been described above, this embodiment is presented as an example and is not intended to limit the scope of the invention. These new embodiments and their modifications can be implemented in various other forms, and various omissions, substitutions, and modifications can be made without departing from the gist of the invention. These embodiments and their modifications are included in the scope and gist of the invention, and are included in the scope of the invention and its equivalents described in the claims.

For example, in the embodiment, the server device 20 has been described as an example of a business improvement support device. However, this is not limited to the above, and for example, the terminal device 10 may be the business improvement support device. Furthermore, a system including the server device 20 and the terminal device 10 may be the business improvement support device.

In the embodiment, information on task ratios and man-hours is input to the binary table 90. However, this is not limited to this, and only task ratio information or only man-hour information may be input.

In the embodiment, the server device 20 transmits information about the binary table 90 to the terminal device 10, and business improvement is considered based on the binary table 90 displayed on the terminal device 10. However, the present invention is not limited to this, and the server device 20 may display information about the binary table 90 on its own display unit 24, and business improvement may be considered based on the binary table 90 displayed on the display unit 24.

In the embodiment, a "*" mark is marked at the intersection of the node name 92 and the resource name 95 of the resource used in the business related to the node name 92 as an example of specific information. However, this is not limiting, and specific information other than the "*" mark may be marked. Furthermore, the resource name 95 of the resource used in the business related to the node name 92 may be identified by a method other than marking specific information at the intersection of the node name 92 and the resource name 95.

1 Business improvement support system 10 Terminal device 11 CPU
14 Display unit 15 Operation unit 16 Storage unit 20 Server device 21 CPU
24 Display unit 25 Operation unit 26 Storage unit 91 Pool name 92 Node name 93 Process number 94 Business area name 95 Resource name 97 Column 98 Intersection 99 Intersection 100 Intersection 111 Display control unit 112 Operation reception unit 211 Business flow creation support unit 212 Binary table creation unit 213 Transmission unit 261 Business flow DB
262 table storage section 2611 business flow storage section 2612 attribute storage section 26121 node name 26122 process number 26123 resource information 26126 pool name

JP 2014-235470 A

Claims (6)

a storage unit that associates a plurality of nodes related to the execution of a task with each of the nodes of a task flow defined in the order of task execution, and stores attribute information including resources used in the task corresponding to the node;
a creation means for creating a binary table in which, based on said attribute information, task names of tasks executed at each node are arranged in one column in the order in which the tasks are performed, and resource names of all the resources included in said attribute information of each node are arranged in another column, and specific information for identifying the resources used in each task is added;
an output means for outputting the information of the created binary table in a displayable manner;
A business improvement support device equipped with the above. The specific information is mark information attached to the intersection of each arranged business name and the resource name of the resource used in the business of the business name.
The business improvement support device according to claim 1. The resources include physical resources indicating the type of equipment for performing the tasks and human resources indicating the type of workers performing the tasks, and further include at least one of task ratio information indicating the ratio of the tasks that the workers were involved in and man-hour information indicating the time that the workers were involved in the tasks for each task.
3. The business improvement support device according to claim 1. The task ratio and the man-hours can be input for each task in the created binary table,
The input information on the business ratio is reflected in the attribute information stored in the storage unit.
The business improvement support device according to claim 3. The process numbers are automatically assigned to the nodes in the order in which the tasks are performed.
The business improvement support device according to claim 1. A computer as a business improvement support device, which is provided with a storage unit that stores, for each node, a process number indicating the order in which the business is performed at the node and attribute information including resources used to perform the business, in order to execute a business flow in which the plurality of nodes related to the execution of the business are defined in the order in which the business is performed;
a creation means for creating a binary table in which, based on said attribute information, task names of tasks executed at each node are arranged in one column in the order in which the tasks are performed, and resource names of all the resources included in said attribute information of each node are arranged in another column, and specific information for identifying the resources used in each task is added;
an output means for outputting the information of the created binary table in a displayable manner;
A program to make it function as such.

Images