JP7503665B2 - Business management device, business management method, and business management program - Google Patents

Description

The present invention relates to a management control device, a management control method, and a management control program.

Manufacturers and other companies manage indicators that are directly related to on-site production on a daily basis, and also manage key performance indicators (KPIs) that relate to the entire company, for example on an annual basis. By sharing the impact that fluctuations in on-site indicators have on KPIs across the entire company, a sense of unity is fostered within the company, and KPIs naturally improve.

The data analysis device in Patent Document 1 simulates the production process after an event such as a temporary machine stop occurs, based on the time elapsed between the time the event is detected and an action taken, and calculates the simulated results as KPIs. The production plan evaluation system in Patent Document 2 inputs an order into a model that pre-stores the factory operation schedule, and receives simulated production results and their evaluation points from the model. The evaluation points are a weighted evaluation of cost, delivery date, operation rate, etc.

JP 2018-36917 A JP 2002-366219 A

The indicators that on-site managers manage on a daily basis often do not match the indicators that top management explains to external stakeholders (shareholders, creditors, licensing authorities, etc.). Therefore, when reviewing on-site indicators with the aim of improving company-wide management indicators, on-site managers must convert the on-site indicators into management indicators and explain them to top management. This type of conversion requires not only in-depth knowledge across various fields such as manufacturing, labor, and finance, but also a correct understanding of the business flow of each individual company.

The data analysis device in Patent Document 1 uses the time elapsed until an event is detected as an explanatory variable and the KPI as a target variable. Other on-site indicators such as operation rate are not considered as explanatory variables. The production plan evaluation system in Patent Document 2 does not distinguish between indicators required for the on-site and those required for management as the indicators to be evaluated.
Therefore, an object of the present invention is to convert fluctuations in on-site indicators into fluctuations in management indicators.

The business management device of the present invention comprises an input processing unit which receives on-site indicators from the field, an index management unit which converts the received on-site indicators into management indicators necessary for management decisions, and an output processing unit which displays the converted management indicators to a manager , wherein the index management unit calculates a cost for each event, which is an unpredictable defect that occurs or is discovered at the field, and calculates a cost for each process included in the occurrence conditions corresponding to each of the events, and the output processing unit displays the cost for each event and the cost for each process .
Other means will be described in the description of the embodiment of the invention.

According to the present invention, fluctuations in on-site indicators can be converted into fluctuations in management indicators.

FIG. 2 is a diagram illustrating the configuration and environment of a business management device. 1 is an example of factory information. 4 is an example of vehicle information. 11 is an example of line information. 11 is an example of personnel information. 13 is an example of unit information. 13 is an example of product unit price information. 1 is an example of product cost breakdown information. This is an example of management information. This is an example of management information. 13 is an example of inter-index relationship information. 1 is an example of event information. 13 is a flowchart of a processing procedure. 13 is an example of an event-specific cost display screen. 13 is an example of a process-by-process cost display screen. 13 is an example of an influence display screen. 13 is an example of an influence display screen.

Hereinafter, a form for implementing the present invention (referred to as the "present embodiment") will be described in detail with reference to the drawings, etc. This embodiment is an example in which a computer at an automobile manufacturer converts fluctuations in on-site indicators into fluctuations in management indicators. However, the present invention is also applicable to manufacturers in other fields, and further, to business types other than manufacturers with on-site operations, such as electricity, communications, warehousing, transportation, and traffic.

(Configuration and environment of business management apparatus)
1 is a diagram explaining the configuration and environment of the business management device 1. The business management device 1 is a general computer, and comprises a central control device 11, an input device 12 such as a keyboard or a touch panel, an output device 13 such as a display, a main memory device 14, an auxiliary memory device 15, and a communication device 16. These are interconnected by a bus. The auxiliary memory device 15 stores field information 31, business information 32, index relationship information 33, and event information 34 (described in detail below). The auxiliary memory device 15 may be configured independent of the business management device 1.

The input processing unit 21, output processing unit 22, event detection unit 23, and index management unit 24 in the main memory device 14 are programs. The central control unit 11 reads these programs from the auxiliary memory device 15 and loads them into the main memory device 14, thereby realizing the functions of each program (described in detail below).

At the head office 2, the manager uses one or more portable or fixed manager terminal devices 5. The multiple sites 3 are, for example, factories with production lines. At the sites 3, the site managers use one or more portable or fixed site terminal devices 6. The manager terminal devices 5 and the site terminal devices 6 are connected to the business management device 1 via the network 4.

(On-site information)
2 to 8 are examples of the site information 31 (31a to 31g). In this embodiment, the factory information 31a (FIG. 2), vehicle information 31b (FIG. 3), line information 31c (FIG. 4), personnel information 31d (FIG. 5), basic unit information 31e (FIG. 6), product unit price information 31f (FIG. 7), and product cost structure information 31g (FIG. 8) are collectively referred to as site information 31. The specific content of the site information 31 varies greatly depending on the site 3.

2 shows an example of the factory information 31a. Numeric values are stored in a numerical value column 102 in association with the items stored in the item column 101.
The items in the item column 101 are the number of lines, which indicates the number of production lines in a series, and the number of shifts, which indicates the number of shifts (morning, afternoon, etc.) for personnel working on the line.
The numerical values in the numerical value column 102 are specific numerical values for each item.

3 is an example of the vehicle information 31b. Numeric values are stored in the numerical value column 112 in association with the items stored in the item column 111.
The items in item column 111 are the number of vehicle models, which indicates the number of vehicle models (sedan, hardtop, wagon, etc.) manufactured, the number of models, which indicates the number of models (grades, environmental specifications, etc.) manufactured, the number of options, which indicates the number of options adopted (additional options such as interior, auxiliary equipment, etc.), and the number of colors, which indicates the number of body paint colors.
The numerical values in the numerical value column 112 are specific numerical values for each item.

4 shows an example of the line information 31c. Numeric values are stored in the numerical value column 122 in association with the items stored in the item column 121. The line information 31c exists for each line.
The items in item column 121 are the line's minimum takt time (seconds/unit), the line's current takt time (seconds/unit), WBS (White Body Storage, storage for unpainted vehicles) capacity, and PBS (Painted Body Storage, storage for painted vehicles) capacity. Note that takt time is the reciprocal of the production speed and indicates the production capacity of the line. The smaller the takt time, the greater the production capacity. Therefore, the minimum takt time is the line's maximum production capacity. The WBS capacity and PBS capacity are temporary storage capacities immediately before and after the painting process, respectively.
The numerical values in the numerical value column 122 are specific numerical values for each item.

5 is an example of the personnel information 31d. A personnel number field 132 stores a numerical value associated with the process stored in the process field 131.
The processes in the process column 131 are processes for manufacturing a vehicle as a finished product. Each process may be located upstream or downstream of the same line, or may be located on a different line.

The number of personnel in the number of personnel column 132 is the number of personnel for each process, and the breakdown is stored in the sub-columns of "number of direct personnel," "number of semi-direct personnel," and "number of indirect personnel." The number of direct personnel is the number of personnel engaged in the actual work in each process. For example, direct personnel in a welding process operate the welding robot that welds parts. The number of semi-direct personnel is the number of personnel engaged in the maintenance of equipment used in each process. For example, semi-direct personnel in a welding process inspect the welding robot at night, etc. The number of indirect personnel is the number of personnel engaged in clerical work, etc. in the back office on-site.

6 is an example of the basic unit information 31e. In association with the items stored in the item column 141, amounts are stored in the amount column 142.
A plurality of items showing labor costs and energy costs by process are stored in the item column 141. Labor costs may be further divided into "direct" costs and the like, and overtime may be a separate item.
The amount in the amount column 142 is the labor cost per hour (per person) or the energy cost value.

7 shows an example of the product price information 31f. In association with the items stored in the item column 151, amounts are stored in the amount column 152.
Each item in item column 151 indicates that the "selling price" (the price at which consumers purchase) is calculated by adding the "expected factory profit,""selling and administrative expenses," and "retailer expenses" to the "sales cost" (factory cost).
The amount in the amount column 152 is a value per number of units corresponding to each item.

8 shows an example of the product cost structure information 31g. In association with the items stored in the item column 161, amounts are stored in the amount column 162.
The items in the item column 161 are "factory cost" and its breakdown.
The amount in the amount column 162 is a value per number of units corresponding to each item.

(Management Information)
9 and 10 are examples of the management information 32 (32a and 32b). In this embodiment, the balance sheet 32a (FIG. 9) and the profit and loss statement 32b (FIG. 10) are collectively referred to as the management information 32. The management information 32 is a so-called financial statement, and has a format that is almost common throughout all companies (although it differs slightly depending on the industry). The balance sheet is also called "BS" (Balance Sheet), and the profit and loss statement is also called "PL" (Profit and Loss statement). The balance sheet 32a and the profit and loss statement 32b in this embodiment also have a general format for the manufacturer, so detailed explanations are omitted. Although not shown, the management information 32 may include "attached explanations". The attached explanations explain industry-specific values that cannot be expressed by BS and PL.

(Relationship between on-site information and management information)
The management information 32 is used by company managers to explain the business performance of the current period to external stakeholders such as shareholders. The site information 31 is used by site managers to manage the operation status of the site, and is also basic data when the management information 32 is created.

(index)
An indicator is a value used when managing and evaluating corporate activities, and in many cases is the numerical value of each item in the field information 31, the numerical value of each item in the management information 32, or a numerical value resulting from processing these (such as performing arithmetic operations).

(Information on relationships between indicators)
11 is an example of the inter-index relationship information 33. In association with the index ID stored in the index ID column 171, a category is stored in the category column 172, an index name is stored in the index name column 173, a management information name is stored in the management information name column 174, a responsible site name is stored in the responsible site name column 175, and an inter-index relationship is stored in the index relationship column 176.

The index ID in the index ID column 171 is an identifier that uniquely identifies the index.
The category in the category column 172 is either “management” indicating that the indicator belongs to management information 32 , or “site” indicating that the indicator belongs to site information 31 .
The index name in the index name column 173 is the name of the index described above. An index with the "management" category is also called a "management index" and is an index necessary for management decisions. An index with the "field" category is also called a "field index" and is an index necessary for field management. "ROA" is return on assets.

It is up to the user to decide whether to categorize an indicator as a management indicator or a field indicator. The business management device 1 accepts the user's flexible setting of categories according to the origin of each indicator's value, the job responsibilities of the manager and field manager, etc. In FIG. 11, for example, "direct labor cost (K05)" is a management indicator. This reflects the manager's desire to know changes in the total amount. On the other hand, the "direct labor cost" of the same name in FIG. 8 is the unit price per product, and the manager does not need to know this for the time being.

The management information name in the management information name column 174 is the specific name of the management information (document) related to the indicator, and is at least one of “PL”, “BL”, and “attached instructions”. In the corresponding column of a record whose category is “on-site”, “-” (not applicable) is stored.
The responsible site name in the responsible site name column 175 is the name of the site that has practical responsibility for the indicator. "-" is stored in the relevant column for records whose classification is "management".
The inter-index relationship in the inter-index relationship column 176 is a formula for calculating the index based on other indexes (described in detail below).

(Relationships between indicators)
When one looks at each record in FIG. 11, for example, the following can be seen.
- The record with index ID "K01" stores "Sales = _F01 (K _## , G _## , ...)". This indicates that the value of "Sales" is calculated based on multiple management indexes and/or field indexes other than "Sales". "F" stands for a function.
- "Sales volume = _F02 (K _## , G _## , ...)" is stored in the record with index ID " _K02 ". This also indicates that the value of "Sales volume" is calculated based on multiple management indexes and/or field indexes other than "Sales volume". However, the explanatory variables "K _## " and "G _## " of function F02 may be the same as the explanatory variables "K _## " and "G _## " of function _F01 , or may be different.

The record with the index ID "K04" stores "direct material cost = _F04 ( _G11 , _G12 , _G13 , ...)". This indicates that the value of "direct material cost" is calculated based on "line stoppage cost", "operational error cost", "parts shortage cost", and others.
"Direct labor cost = F ₀₅ (G ₁₁ , G ₁₂ , G ₁₃ , ...)" is stored in the record with the index ID "K05". This also indicates that the value of "direct labor cost" is calculated based on "line stoppage cost", "operational error cost", "parts shortage cost", and others. "F ₀₅ " is a different function from "F ₀₄ ". Therefore, even if the values of the input explanatory variables are the same, the values of the output objective variables will be different.

"Line stoppage cost = _F11 (production quantity, unit cost, occurrence probability)" is stored in the record of index ID "G11". This indicates that the value of "line stoppage cost" is calculated based on "production quantity", "unit cost" and "occurrence probability".
"Operation error cost = _F12 (production quantity, unit cost, occurrence probability)" is stored in the record of index ID "G12". This also indicates that the value of "operation error cost" is calculated based on "production quantity", "unit cost" and "occurrence probability". " _F12 " is a different function from " _F11 ". Therefore, even if the input explanatory variable value is the same, the output objective variable value will be different. The "production quantity", "unit cost" and "occurrence probability" will be described later.

"Takt time = _F14 (G _## , G _## , ...)" is stored in the record with index ID "G14". This indicates that the value of "Takt time" is calculated based on multiple site indexes other than "Takt time".
- "Total operation time = _F15 (G _## , G _## , ...)" is stored in the record of index ID "G15". This indicates that the value of "total operation time" is calculated based on multiple site indexes other than "total operation time". However, the explanatory variable "G _## " of function _F15 may be the same as the explanatory variable "G _## " of function _F14 , or it may be different.

Looking at the inter-index relationship column 176 in FIG. 11 as a whole, the following can be seen.
Management indicators and on-site indicators are interrelated, and when the value of one changes, the value of at least one other management indicator and on-site indicator also changes.
The business management device 1 can calculate the effect that a change in the value of one index caused by a chance event has on the value of another index.
Similarly, the business management device 1 can calculate the effect of a simulated change in the value of one index by the user on the values of other indexes.

(Event Information)
12 is an example of the event information 34. In association with an event ID stored in an event ID column 181, an event column 182 stores an event, a condition ID column 183 stores a condition ID, an occurrence condition column 184 stores an occurrence condition, a production quantity column 185 stores a production quantity, a unit cost column 186 stores a unit cost, an occurrence probability column 187 stores an occurrence probability, and a cost column 188 stores a cost.

The event ID in the event ID column 181 is an identifier that uniquely identifies an event. An event is an unpredictable malfunction that occurs or is discovered in the field.
The events in the event column 182 are the events described above, and in this case, in particular, "line stoppage,""workerror,""partsshortage," etc. These correspond to the "line stoppage cost" etc. in the site index in FIG.
The condition ID in the condition ID column 183 is an identifier that uniquely identifies the occurrence condition of an event. The occurrence condition is the cause when the result of a causal relationship is an event, or the result when the cause of a causal relationship is an event.

The production quantity in the production quantity column 185 is the quantity of parts or products produced on the line.
The unit cost in the unit cost column 186 is the manufacturing cost per part or product.
The occurrence probability in the occurrence probability column 187 is a conditional probability that an event will occur when an occurrence condition is satisfied. The occurrence probability is calculated in advance based on past cases.
The cost in the cost column 188 is the total amount of damage expected when an event occurs. Note that the formula "cost = production quantity x unit cost x occurrence probability" is established. The cost in this column corresponds to the "line stoppage cost" in FIG. 11, etc.

Looking at FIG. 12, for example, the following can be seen.
When the occurrence condition C01 “The current takt time is more than twice the minimum takt time” is satisfied, the events “line stop”, “operational error”, and “parts shortage” occur with a probability of “10%, “15%, and “20%”, respectively.
As a result, line stoppage causes "line stoppage cost = # ₁ x ## ₁ x 10%". At the same time, operational errors cause "operational error cost = # ₂ x ## ₂ x 15%", and parts shortages cause "parts shortage cost = # ₃ x ## ₃ x 20%".

When the occurrence condition C02 "The number of semi-direct personnel in the □□ process is □ or more" is satisfied, the event "line stop" occurs with a probability of "20%". As mentioned above, when the number of semi-direct personnel increases, there is a high possibility that a malfunction requiring special maintenance has occurred in that process.
・As a result, the line stoppage causes "line stoppage cost = # ₁ x ## ₁ x 20%". However, there are no costs caused by "operational mistakes" and "parts shortage". This is because the □□ process affects the line stoppage but does not affect operational mistakes or parts shortages.

(Processing Procedure)
13 is a flowchart of the processing procedure. In the explanation of FIG. 13, reference will be made to FIGS. 14 to 17 as appropriate.
In step S201, the input processing section 21 of the business management device 1 acquires the site information 31 (31a to 31g, FIGS. 2 to 8). Specifically, the input processing section 21 acquires the site information 31 from the input device 12, the site terminal device 6, or any other device (not shown) operated by the site manager, and stores it in the auxiliary storage device 15. Each time a change occurs in the numerical value, amount, etc. of the site information 31, the input processing section 21 acquires the changed numerical value, amount, etc. As a result, the input processing section 21 always keeps the values of the site information 31 in the auxiliary storage device 15 up to date.

In step S202, the input processing unit 21 acquires management information 32 (32a and 32b, Figures 9 and 10). Specifically, the input processing unit 21 acquires management information 32 from the input device 12, the manager's terminal device 5, or any other device (not shown) operated by the finance department, etc., and stores it in the auxiliary storage device 15. Each time a change occurs in the amount, etc. of the management information 32, the input processing unit 21 acquires the changed amount, etc. As a result, the input processing unit 21 always maintains the value of the management information 32 in the auxiliary storage device 15 in an up-to-date state.

In step S203, the input processing unit 21 acquires the inter-index relationship information 33 ( FIG. 11 ). Specifically, the input processing unit 21 accepts the inter-index relationship information 33 input by the user via the input device 12.
In step S204, the input processing unit 21 acquires the event information 34 ( FIG. 12 ). Specifically, the input processing unit 21 accepts the event information 34 input by the user via the input device 12.

In step S205, the event detection unit 23 of the business management device 1 monitors changes in the site information 31, etc. Specifically, the event detection unit 23 starts to monitor whether the changes in the site information 31 and the business information 32 satisfy the occurrence conditions of the event information 34 (FIG. 12). The changes are classified into the following two types.
<Type 1> A change in an index caused by a malfunction that occurred accidentally on-site <Type 2> A change in an index caused intentionally by a user for the purpose of simulation

In step S206, the event detection unit 23 determines whether or not an event has been detected. Specifically, if the changes in the site information 31 and management information 32 satisfy the occurrence condition of the event information 34 (step S206 "Yes"), the event detection unit 23 proceeds to step S207, and otherwise (step S206 "No"), the event detection unit 23 returns to step S205. For ease of explanation, it is now assumed that the event detection unit 23 detects that the occurrence condition C01 in FIG. 12 is satisfied. As described above, this example is an example in which line stoppage costs, operational error costs, and part shortage costs occur simultaneously (but type 1). Other examples will be described later.

In step S207, the index management unit 24 of the business management device 1 calculates the cost for each event. Specifically, the index management unit 24 calculates the line stop cost, the operational error cost, and the part shortage cost based on the event information 34, as described above in the explanation of FIG.
In step S208, the output processing unit 22 of the business management device 1 displays and records the cost for each event. Specifically, the output processing unit 22 displays an event-specific cost display screen 41 (FIG. 14) on the output device 13 or the manager terminal device 5. The output processing unit 22 then stores the displayed screen as a snapshot in the auxiliary storage device 15. The explanation will now move to FIG. 14.

Figure 14 is an example of an event-specific cost display screen 41. The output processing unit 22 displays the cost per event (daily, monthly, and annual amounts) and a bar graph of the cost per event (daily amount). Return to Figure 13 for explanation.

In step S209, the index management unit 24 of the business management device 1 calculates the cost for each process. Specifically, the index management unit 24 recalculates the cost for each event calculated in step S207 into the cost for each process. In the event information 34 (Figure 12), at least two process names (such as "□□ process", "□■ process") are stored in the occurrence conditions corresponding to each event. Therefore, the index management unit 24 redistributes the total cost calculated in step S207 to each process, for example using the occurrence probability.

In step S210, the output processing unit 22 of the business management device 1 displays and records the cost for each process. Specifically, the output processing unit 22 displays the process-by-process cost display screen 42 (Figure 15) on the output device 13 or the manager terminal device 5. Furthermore, the output processing unit 22 stores the screen displayed at this time as a snapshot in the auxiliary storage device 15. The explanation will now move to Figure 15.

Figure 15 is an example of a process-by-process cost display screen 42. The output processing unit 22 displays the cost per process (daily, monthly, and annual) and a bar graph of the cost per process (daily). Refer back to Figure 13 for explanation.

In step S211, the index management unit 24 of the business management device 1 calculates the management indexes after the occurrence of the event. Specifically, the index management unit 24 assigns the values of the line stoppage cost, operational error cost, and part shortage cost calculated in step S207 to the explanatory variables of the inter-index relationship (function) in Figure 11. The index management unit 24 then obtains the value of the objective variable output by the function. For ease of explanation, it is assumed here that the index management unit 24 obtains the values of "direct material cost" and "direct labor cost" as management indexes. The explanation will now move to Figure 16.

Figure 16 is an example of the impact display screen 51. The impact display screen 51 displays an indicator tree 52, a site image 53, a cost column by event 54, and an indicator relationship arrow 55. The indicator tree 52 expresses the indicator relationship in Figure 11 as a tree diagram with "ROA" as the apex node. Each node (bold rectangle) of the indicator tree 52 displays an indicator name and its value. The site image 53 is a diagram of a natural image of the site. The site image diagram 53 displays a character string such as "line stop" indicating a malfunction (event) occurring at the site. The event cost column 54 displays the cost for each event. The indicator relationship arrow 55 connects the explanatory variable (starting point) and the target variable (ending point) of the indicator relationship in Figure 11. Let's return to Figure 13 for an explanation.

In step S212, the output processing unit 22 of the business management device 1 displays and records the business indicators after the occurrence of the event. Specifically, first, the output display unit 22 creates an indicator tree 52 based on the inter-indicator relationships in Fig. 11, and creates character strings for the event-specific cost column 54 and the site image diagram 53 based on the costs for each event calculated in step S207.
Secondly, the output processing unit 22 displays the effect display screen 51 (FIG. 16) on the output device 13 or the manager terminal device 5. Furthermore, the output processing unit 22 stores the displayed screen as a snapshot in the auxiliary storage device 15. Thereafter, the processing procedure is terminated.

(Another example of a processing procedure)
In step S206, the event detection unit 23 of the business management device 1 detects that the user has changed the current takt time from "60 seconds/unit" to "64 seconds/unit", and as a result, the occurrence condition C01 in FIG. 12 is satisfied. At this time, the user wants to know how the business indicators will change by slightly slowing down the production speed. As mentioned above, this example is also an example in which the line stoppage cost, operational error cost, and part shortage cost occur simultaneously (but type 2). In this example, in "second" of step S212, the output processing unit 22 of the business management device 1 displays the effect display screen 51 (FIG. 17). The explanation will now move to FIG. 17.

Fig. 17 is also an example of the effect display screen 51. The configuration of the effect display screen 51 in Fig. 17 is the same as that in Fig. 16. The differences between Fig. 17 and Fig. 16 are as follows.
・The takt time has changed to "64 seconds/unit." This change will have an impact on cost reduction and production volume reduction.
In terms of cost reduction, there has been a reduction in part shortages, line stoppages, and work errors due to the creation of more leeway in on-site work. The character string "reduced part shortages" in the on-site image 53 indicates this. As a result, the amounts in the event-specific cost column 54 have decreased. Furthermore, direct material costs and direct labor costs have decreased.

・Regarding the decrease in production volume, the production volume is decreasing due to the slowdown in production speed.
・The "profit margin," an indicator where the two directions converge, has increased slightly. As a result, "ROA" has also increased slightly.
· From the management's perspective, in order to at least maximize the ROA, it would be better to change the takt time to "64 seconds/unit."

(Effects of this embodiment)
The business management device of this embodiment has the following advantages.
(1) The business management device can convert field indicators into business indicators.
(2) The business management device can extract events that cause changes in on-site indicators.
(3) The business management device can calculate the impact that a defect at a manufacturing site has on a company's finances.
(4) The business management device can calculate business indicators based on the probability of an event occurring.
(5) The business management device can display the relationships between indicators in a tree diagram.
(6) The business management device can simulate how business indicators change.

The present invention is not limited to the above-described embodiments, but includes various modified examples. For example, the above-described embodiments have been described in detail to make the present invention easier to understand, and are not necessarily limited to those having all of the configurations described. It is also possible to replace part of the configuration of one embodiment with the configuration of another embodiment, and it is also possible to add the configuration of another embodiment to the configuration of one embodiment. It is also possible to add, delete, or replace part of the configuration of each embodiment with other configurations.

LIST OF SYMBOLS 1 Business management device 2 Head office 3 Work site 4 Network 5 Manager's terminal device 6 Work site terminal device 11 Central control device 12 Input device 13 Output device 14 Main memory device 15 Auxiliary memory device 16 Communication device 21 Input processing unit 22 Output processing unit 23 Event detection unit 24 Index management unit 31 Work site information 31a Factory information 31b Vehicle information 31c Line information 31d Personnel information 31e Basic unit information 31f Product unit price information 31g Product cost structure information 32 Management information 32a Balance sheet 32b Profit and loss statement 33 Inter-index relationship information 34 Event information 41 Event-specific cost display screen 42 Process-specific cost display screen 51 Impact display screen

Claims (8)

an input processing unit that receives on-site indicators from the site;
an index management unit that converts the received field indexes into management indexes necessary for management decisions;
an output processing unit that displays the converted management index to a manager;
Equipped with
The index management unit
Calculating the cost for each event that is an unpredictable defect that occurs or is discovered at the site, and calculating the cost for each process included in the occurrence conditions corresponding to each of the events;
The output processing unit includes:
Displaying the cost for each of the events and displaying the cost for each of the steps;
A business management device comprising: an event detection unit that detects an event that changes the on-site index among the events that are the unpredictable malfunctions ;
The index management unit
Calculating the management index based on the on-site index related to the detected event;
2. The business management device according to claim 1 . The management indicators are:
It is an indicator related to corporate finances;
3. The business management device according to claim 2, The index management unit
multiplying a production quantity, which is the quantity of parts or products produced on the line, by a unit cost, which is the production cost per part or product, and further multiplying it by the probability that the detected event will occur when the occurrence condition is satisfied , thereby calculating a cost caused by the detected event as a site index related to the detected event , and calculating the management index based on the calculated cost;
4. The business management device according to claim 3. The output processing unit includes:
Displaying the relationships between a plurality of on-site indicators and management indicators in a tree diagram to the manager;
storing the displayed tree diagram;
5. The business management device according to claim 4. The event detection unit is
detecting when a user has changed the scene indicator as a simulation;
6. The business management device according to claim 5, The input processing unit of the business management device includes:
Accepting on-site indicators from the field,
The index management unit of the business management device includes:
Converting the received on-site indicators into management indicators necessary for management decisions;
The output processing unit of the business management device
Displaying the converted management indicators to the manager;
The index management unit further
Calculating the cost for each event that is an unpredictable defect that occurs or is discovered at the site, and calculating the cost for each process included in the occurrence conditions corresponding to each of the events;
The output processing unit further includes:
Displaying the cost for each of the events and displaying the cost for each of the steps;
A management method for a management device comprising the steps of: Computer,
an input processing unit that receives on-site indicators from the site;
an index management unit that converts the received field indexes into management indexes necessary for management decisions;
an output processing unit that displays the converted management index to a manager;
A management program for making the company function as a
The index management unit further
Calculating the cost for each event that is an unpredictable defect that occurs or is discovered at the site, and calculating the cost for each process included in the occurrence conditions corresponding to each of the events;
The output processing unit further includes:
Execute a process of displaying the cost for each of the events and the cost for each of the steps.
Business Administration Program for.

Images