JP2007213519A - Management information output method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To output a KPI (Key Performance Indicator) in response to an indication from a user. <P>SOLUTION: A computer stores management numerical values being numerical values relating to management, into a memory and calculates a summed-up value resulting from summing up management numerical values stored in the memory and outputs the calculated summed-up value to an output device in response to the indication from the user. Various kinds of pieces of management information is displayed on a screen so that the user can recognize the numerical values relating to management, such as sales, gross profit, and profit and loss from various viewpoints and can recognize the schedule of cash collection and can recognize levels of budget achievement and business forecast per subject, whereby the user can take management measures quickly. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a management information output method.

Conventionally, there is a high need for managers to understand key performance indicators (KPIs) such as sales, gross profit, and profit / loss. Patent Document 1 discloses a mechanism in which monthly data of each department is stored in a database and shared on the Web.
JP 2004-302839 A

  However, in the system described in Patent Document 1, since data is shared on a monthly basis, managers cannot grasp KPIs until the end of the month and cannot make management decisions in a timely manner. It was.

  The present invention has been made in view of such a background, and an object thereof is to provide a method capable of outputting a KPI in accordance with an instruction from a user.

  A main invention of the present invention for solving the above-described problem is a method for outputting management information of a company, wherein a computer stores a management value that is a numerical value related to the management in a memory, and according to an instruction from a user A total value obtained by totaling the management numerical values stored in the memory is calculated, and the calculated total value is output to an output device.

  According to the present invention, a KPI can be output in response to an instruction from a user.

  Hereinafter, a management information display system according to an embodiment of the present invention will be described in detail with reference to the drawings.

  In the management information display system of the present embodiment, the user grasps (1) numerical values related to management such as sales, gross profit, profit and loss (hereinafter referred to as KPI numerical values) from various viewpoints, and (2) cash collection Various management information is displayed on the screen so that the schedule can be grasped, and (3) the budget achievement level and the business performance forecast for each project (project) can be grasped. The user can quickly implement management measures by monitoring the display of the management information display system of the present embodiment and performing management analysis with reference to the displayed management information.

== System configuration ==
FIG. 1 is a diagram showing the overall configuration of the management information display system of the present embodiment. As shown in the figure, the management information display system of this embodiment includes a client device 10 and a management information providing device 20. The client device 10 and the management information providing device 20 are connected via a communication network 30. The communication network 30 is, for example, the Internet, a LAN (Local Area Network), a WAN (Wide Area Network), or the like, and is constructed by Ethernet (registered trademark), a public telephone line, a wireless communication path, or the like.

  The client device 10 is a computer operated by a user, and the management information providing device 20 is a computer that provides management information to the user. In the present embodiment, it is assumed that the management information providing apparatus 20 provides management information to the user in the form of a Web application. Therefore, the user can browse the management information provided by the management information providing device 20 by operating the client device 10 and accessing the management information providing device 20 in accordance with HTTP (Hyper Text Transfer Protocol).

  In the present embodiment, the management information providing apparatus 20 displays data as page data described in HTML (HyperText Markup Language) in response to a request from the client apparatus 10, JPEG, PNG, GIF, or the like. The creation of image data of the format

== Hardware configuration ==
FIG. 2 is a diagram illustrating a hardware configuration of the management information providing apparatus 20. As shown in the figure, the management information providing device 20 includes a CPU 201, a memory 202, a storage device 203, and a communication interface 204. The storage device 203 is, for example, a hard disk drive, a CD-ROM drive, or a flash memory that stores programs and data. The CPU 201 implements various functions by reading a program stored in the storage device 203 into the memory 202 and executing it. The communication interface 204 is an interface for connecting to the communication network 30. As the communication interface 204, for example, an adapter for connecting to Ethernet (registered trademark), a modem for connecting to a public telephone line network, or the like can be adopted.

== Software configuration ==
FIG. 3 is a diagram illustrating a software configuration of the management information providing apparatus 20. As shown in the figure, the management information providing apparatus 20 includes a drill-down display unit 211, a tabulated display unit 212, a collection information registration unit 213, a collection information display unit 214, a case accuracy information registration unit 215, and an order accuracy display unit. 216, a case list display unit 217, a budget database 251, a performance database 252, a product management database 253, a collection information database 254, a case accuracy database 255, a case budget database 256, and a case performance database 257. Each of the functional units 211 to 217 is realized by the CPU 201 of the management information providing apparatus 20 reading out the program stored in the storage device 203 to the memory 202 and executing it. The databases 251 to 257 are each realized as a storage area provided by the memory 202 or the storage device 203 of the management information providing device 20.

  The functional units 211 to 217 and the databases 251 to 257 are (1) related to display of KPI numerical values in various ways, (2) related to display of a cash collection schedule, and (3) related to matters. It is divided into those related to the display of information. Hereinafter, each of the three groups will be described in detail.

== (1) Display of KPI numerical value ==
The drill-down display unit 211, the hierarchical total display unit 212, the budget database 251 and the performance database 252 relate to the KPI numerical value display processing.

  The budget database 251 stores, for example, information related to the company's accounting budget (hereinafter referred to as budget information) acquired from the company's financial results, and the results database 252 is acquired from the accounting data such as the company's financial data. Information related to the accounting performance of the company (hereinafter referred to as performance information) is stored. 4 and 5 are diagrams showing examples of the configuration of the budget information stored in the budget database 251 and the record information stored in the record database 252, respectively. As shown in FIGS. 4 and 5, the budget information and the result information have the same configuration. Budget information and performance information include levels 1 to 4 and KPI values (sales, gross profit, profit and loss) using date as a key. For the sake of simplicity in the following description, the KPI figures refer to sales, gross profit, and profit / loss. However, the KPI figures are not limited to these, and any information can be used as a management index. It may be a numerical value. Each of the hierarchies 1 to 4 is an aggregation item of KPI numerical values. In the present embodiment, levels 1 to 4 are a company branch, a sales market, a category of sold products, and names of sold products, respectively.

  Budget information and performance information can be acquired as transaction data from an external accounting system or the like.

== Drill down ==
The drill-down display unit 211 aggregates and displays KPI numerical values for each hierarchy designated by the user. The flow of the KPI numerical value display process by the drill-down display unit 211 is shown in FIG. The drill-down display unit 211 receives designation of whether to display budget information or performance information from the user (S401), and from the budget database 251 or the performance database 252 according to the designation from the user, the levels 1 to The KPI numerical values are totaled for each of the four and tree-structured data (hereinafter referred to as tree data) corresponding to the hierarchy is created from the total values (S402).

  A configuration example of the created tree data 300 is shown in FIG. As shown in the figure, the drill-down display unit 211 uses the total value of sales, gross profit, and profit / loss for all records as a route, by branch, branch and sales market, branch, sales market, The tree data 300 is created by calculating the total values of the KPI values for each product category and for each branch, sales market, product category, and product name.

  The drill-down display unit 211 receives designation of KPI to be displayed among sales, gross profit, or profit / loss (hereinafter referred to as KPI) and designation of elements constituting the tree data 300 from the user (S403). FIG. 8 shows an example of a screen displayed for the drill-down display unit 211 to accept the element designation. In the example of FIG. 8, on the screen 310, the drill-down display unit 211 sets the designation of the KPI numerical value to “sales”, the total sales total, that is, the name of the root element of the tree data 300, and the root element “650”, which is sales corresponding to The user selects one of sales, gross profit, and profit / loss from the selection column 311 and clicks “650”, which is the total sales total, to specify the KPI and the element. Similarly, on the screen 320, by clicking the sales “590” of “Branch A”, the element “/ Branch A” one level below the route is selected.

The drill-down display unit 211 performs the KPI numerical value display process shown in FIG. 9 using the root element as an argument (S404).
The drill-down display unit 211 uses the element specified as an argument as a processing element (S421), and the hierarchy to which the element received from the user in (S403) (hereinafter referred to as a specified element) belongs and the processing element belongs. When the hierarchy is the same (S422: YES), if the specified element is the same as the processing element (S423: YES), the KPI value of the child element is set for each of the elements that are children of the processing element. It is displayed (S424).

On the other hand, when the hierarchy of the processing element is different from the hierarchy of the designated element (S422: NO), the drill-down display unit 211 displays the name of the child element for each element that is a child of the processing element (S425). ). If the processing element is an ancestor of the specified element (S426: YES), the drill-down display unit 211 recursively executes KPI numerical value display processing using the processing element as an argument (S427).
Next, the drill-down display unit 211 displays the KPI value of the processing element (S429).

  In this way, as shown in FIG. 8, by clicking the KPI numerical value of each layer and designating elements of the tree data 300, the KPI numerical value of the lower layer is displayed, so-called drill-down KPI. It is possible to display numerical values and KPI numerical values by so-called drill-up, in which KPI numerical values of higher layers are displayed. In the example of FIG. 8, the sales total for the root element (entire) is displayed on the screen 310, the sales total for each branch corresponding to the breakdown of the total sales is displayed on the screen 320, and the branch is displayed on the screen 330. Total sales by sales market in A are displayed. That is, on the screens 310 to 330, KPI numerical values are displayed by drill-down. Here, for example, when “650”, which is the entire KPI numerical value, is selected on the screen 330, the screen returns to the screen 310, and the KPI numerical value is displayed by drill-up.

  As described above, according to the drill-down display unit 211 of this embodiment, it is possible to easily perform analysis by drill-up or drill-down in online analysis only by selecting an element with a mouse or the like. Therefore, since the user can easily try various analysis methods, the opportunity for analyzing the KPI numerical value can be increased for the user. The user can accurately grasp the management status by browsing the KPI numerical values from various perspectives.

== Display of total by hierarchy ==
The hierarchical total display unit 212 accepts designation of total items from the user, and displays the total KPI values for each designated item. FIG. 10 shows the flow of the hierarchical total display process by the hierarchical total display unit 212.

  When receiving the designation of the year and month that is the period to be aggregated, the hierarchy that is the aggregation item, and the KPI that is the aggregation target (S441), the hierarchical aggregation display unit 212 receives the specified year and month (hereinafter, Each KPI of the performance information corresponding to the designated date is summed for each value of the designated hierarchy (hereinafter, designated hierarchy) (S442). The tabulation display unit 212 displays the total values corresponding to each value of the specified layer and each of the KPIs in a table format (S443), and specifies a specified KPI (hereinafter, specified) for each value of the specified layer. The total value of KPI) is displayed in a bar graph format (S444).

  FIG. 11 shows an example of a screen that displays KPIs in the table format and bar graph format displayed in this way. The screen 340 includes a pull-down list 341 for specifying a hierarchy and a pull-down list 342 for specifying a KPI. In the display column 343, the sum of each KPI value for each value of the specified hierarchy is displayed as a table 345, and the sum of the KPI values of the specified KPI is displayed as a bar graph type graph 344 at the top of the table 345. The display field 343 also displays a total value 346 of all KPI values. In Table 345, the underlined KPI numerical value indicates that the value is for the KPI selected from the pull-down list 342 for specifying the KPI.

  Here, when receiving the input from the user (S445), the hierarchical display display unit 212 determines whether the value of the designated hierarchy is selected from the graph 344 (S446).

  When the value of the designated hierarchy is selected from the graph 344 (S446: YES), the hierarchical total display unit 212 displays the history information corresponding to the designated date and the value of the selected designated hierarchy from the achievement database 252. The respective KPI numerical values are summed for each value of the hierarchy one level below the designated hierarchy (hereinafter referred to as the lower hierarchy) (S447). The hierarchical total display unit 212 displays the sum of the corresponding KPI numerical values for each of the lower hierarchical values in a table format (S448), and displays the KPI numerical values for the designated KPI in a bar graph format (S449).

  An example of the screen 340 in this case is shown in FIG. The screen 340 shown in FIG. 12 is displayed when “product A” as the value of “hierarchy 3” is selected by clicking the profit / loss 347 of “product A” on the screen 340 of FIG. It is what is displayed. When “product A” is selected in the example of FIG. 11, the hierarchical display unit 212 displays the year / month / day from the result database 252 as the designated date and the hierarchy 3 is “product A”. The result information is displayed in the display column 343 by summing up the KPI numerical values for the values “A1” and “A2” of “hierarchy 4” which is the lower hierarchy of “hierarchy 3”.

  On the other hand, when the value and KPI of the designated hierarchy are designated from the table 345 (S446: NO), the aggregation display unit 212 by hierarchy selects the achievement information corresponding to the selected designated hierarchy value from the achievement database 252. The KPI numerical values of the KPIs are summed for each year up to the designated date (S450). The hierarchical total display unit 212 displays the total of the KPI values corresponding to the values of each lower layer in a tabular format for each year and month up to the specified date (S451), and also displays it in a line graph format (S452). ).

  An example of the screen 340 in this case is shown in FIG. The screen 340 shown in FIG. 13 is displayed when the sales 348 of “Product C” is selected from the table 345 on the screen 340 of FIG. 11. When “sales” of “product C” is selected from the table 345, the tabulated display unit 212 for each layer displays “tier 4” which is a lower layer of “tier 3” to which “product C” belongs from the results database 252. For each of the values “C1” and “C2”, the sum of the KPI values for each year and month is calculated, and the calculated KPI values are displayed in the graph 344 and the table 345. As shown in the example of FIG. 13, the table 352 may also display the sum of the KPI values for the selected “product C”.

== Modification ==
In the above description, the level-specific total display unit 212 performs totalization for one layer (total item), but may perform totalization for two layers. FIG. 14 shows an example of a screen 350 when KPI numerical values are aggregated for two layers.

  The screen 350 includes two selection columns for selecting a hierarchy, a pull-down list 351 and a pull-down list 353. When the first hierarchy is selected from the pull-down list 351, the aggregation display unit 212 for each hierarchy acquires the value of the item indicated by the first hierarchy from the result database 252 without duplication and registers it in the pull-down list 352. When a value is selected from the pull-down list 352 and the second hierarchy is selected from the pull-down list 353, the hierarchical display unit 212 selects the item indicated by the first hierarchy from the pull-down list 352 from the performance database 252. Each KPI numerical value of the performance information which is the obtained value is summed for each value of the item indicated by the second hierarchy selected from the pull-down list 353. The tabulated display unit 212 displays the total KPI numerical values as a table 356 in the display field 355, and also displays a bar graph 357 for those selected from the pull-down list 354. Further, the hierarchical total display unit 212 displays the total value 358 of the entire KPI numerical values displayed as the bar graph 357.

  When the second hierarchy is changed from the pull-down list 353 on the screen 350, the KPI numerical value of the performance information in which the hierarchy 3 is “product A” is changed to the value of the hierarchy 2 as shown in FIG. "Domestic" and "Asia" are aggregated and displayed.

  As shown in the examples of FIGS. 14 and 15, according to the management information providing apparatus 20 of the present embodiment, the performance information whose hierarchy 3 is “product A” is displayed from the performance database 252 by branch (see FIG. 14) It is possible to easily change the tabulation items such as display by market (FIG. 15). Therefore, the user can analyze the KPI numerical value from various points of view and grasp an accurate management state.

== (2) Cache collection schedule display processing ==
Next, display processing of information related to a cache collection schedule (hereinafter referred to as collection information) will be described.

  The merchandise management database 253 stores information (hereinafter referred to as merchandise management information) that indicates the status of inventory and margin transactions for merchandise. FIG. 16 shows the configuration of product management information stored in the product management database 253. As shown in the figure, the product management information includes the number of products in stock, the amount of inventory, the amount of accounts receivable, and the amount of accounts payable in association with the year and month.

  The collection information database 254 stores information (hereinafter referred to as collection information) relating to collection of cash for the product. FIG. 17 shows a configuration example of the collection information stored in the collection information database 254. As shown in the figure, the collection information includes the number of days in stock, the number of accounts receivable, the number of accounts payable, and the number of working capital days in association with the year and month.

The inventory holding days is a predicted value of the days until the inventory amount is converted into sales. The stock holding days are calculated from “inventory amount ÷ sales × business days” or “inventory quantity ÷ sales quantity × business days”.
Accounts receivable days are the predicted values for the number of days until the accounts receivable amount is converted into cash deposits, and the accounts payable days are the estimated values for the number of days for the accounts payable amount to be converted into cash withdrawals. Accounts receivable days are calculated from “Accounts receivable ÷ Sales × Business days”, and Accounts payable days are calculated from “Accounts payable ÷ Purchase × Business days”.
The number of working capital days is a predicted value of the number of days from purchase of goods to sales and cashing. The number of working capital days is calculated from “inventory holding days + number of accounts receivable days−number of accounts payable days”.

  The collection information registration unit 213 creates collection information based on the product management information, and registers the created collection information in the collection information database 254. FIG. 18 shows the flow of registration processing of collection information by the collection information registration unit 213.

  The collection information registration unit 213 receives the designation of the product from the user (S501), and reads the record information that matches the value of the specified product and the level 3 from the record database 252 (S502). The collection information registration unit 213 refers to the date of the read performance information, and performs the following processing using the date from the oldest date to the newest date as the processing date.

The collection information registration unit 213 identifies the number of business days included in the processing date (S503). The number of business days can be obtained, for example, by subtracting the number of days that will be Saturday, Sunday, and a holiday from the processing date. The collection information registration unit 213 sums the sales of the performance information corresponding to the processing date to obtain the sales (S504), and totals the sales of the performance information corresponding to the processing date minus the gross profit. It is set as the amount of money (S505).
The collection information registration unit 213 reads the product management information corresponding to the product designated by the user (hereinafter referred to as the processed product) and the processing date from the product management database 253 (S506), and stores the product management information. The quotient obtained by dividing the stock amount by the sales amount is multiplied by the number of business days to calculate the stock holding days (S507). The collection information registration unit 213 calculates the number of days of accounts receivable by multiplying the quotient obtained by dividing the sales amount of the product management information by the sales amount by the number of business days (S508), and divides the payable amount of the product management information by the purchase amount. The number of working days is calculated by multiplying the quotient by the number of business days (S509). The collection information registration unit 213 calculates the working capital days by adding the number of accounts receivable days to the inventory holding days and subtracting the accounts payable days (S510).
The collection information registration unit 213 registers the processing date, the processed product, the inventory holding days, the accounts receivable holding days, the accounts payable holding days, and the working capital days in the collection information database 254 (S511).

  By repeatedly performing the above processing, the collection information registration unit 213 can calculate the collection information based on the product management information and register it in the collection information database 254.

  The collection information display unit 214 displays collection information and performance information. An example of the screen on which the record information and the collection information are displayed is shown in FIGS.

  FIG. 19 is a diagram illustrating an example of a screen 610 that displays information related to inventory. When a product is selected from the pull-down list 621 on the screen 610 shown in FIG. 19, the collection information registration unit 213 registers the collection information in the collection information database 254. In the following description, it is assumed that the collection information for the product selected from the pull-down list 611 is registered in the collection information database 254.

  The collection information display unit 214 reads the performance information corresponding to the product selected in the pull-down list 611 from the performance database 252 and displays the sales transition of the read performance information as a line graph 612. Further, the collection information display unit 214 reads out the product management information and the collection information corresponding to the current date and the above-mentioned products from the product management database 253 and the collection information database 254, and stores the stock amount of the product management information and the stock of the collection information. According to the number of holding days, the prediction of the sales transition of the next month is displayed as a line graph 613.

  Here, even if the stock amount has increased to the amount 615, if the sales amount has increased to the amount 616, the change in the sales will be as indicated by the dotted line 617, which is a problem on the cash collection schedule. I understand that there is no. On the other hand, when the stock amount is constant and the number of days in stock extends to the period 618, the sales trend is as indicated by the dotted line 619, indicating that the sales are decreasing. Therefore, the user can recognize the necessity of considering countermeasures such as sales promotion.

  FIG. 20 is a diagram illustrating an example of a screen 620 that displays information related to accounts receivable. The collection information display unit 214 reads the performance information corresponding to the product selected in the pull-down list 611 from the performance database 252 and displays the sales transition of the read performance information as a line graph 621. In addition, the collection information display unit 214 reads out the product management information and the collection information corresponding to the current date and the above-mentioned product from the product management database 253 and the collection information database 254, and the sales amount of the product management information and the sale of the collection information. In accordance with the number of days on hand, the prediction of the change in sales for the next month is displayed as a line graph 622.

  Here, even if the amount of accounts receivable increases to the amount of money 623, if the sales amount increases to the amount of money 624, the transition of the sales becomes a dotted line 625, and there is a problem in the cash collection schedule. I understand that there is no. On the other hand, when the amount of accounts receivable is constant and the number of days of accounts receivable extends to the period 626, the trend of sales becomes as indicated by the dotted line 627, indicating that sales are decreasing. Therefore, the user can recognize the necessity of considering the credit analysis of the seller and the measures for shortening the deposit site.

  FIG. 21 is a diagram illustrating an example of a screen 630 that displays information related to accounts payable. The collection information display unit 214 reads the performance information corresponding to the product selected in the pull-down list 611 from the performance database 252, and shows a transition of the purchase amount obtained by subtracting the gross profit from the sales of the read performance information as a line graph 631. indicate. Further, the collection information display unit 214 reads out the product management information and the collection information corresponding to the current date and the above-mentioned product from the product management database 253 and the collection information database 254, and pays the amount of the product management information and the purchase of the collection information. The forecast of the purchase amount of the next month is displayed as a line graph 632 according to the number of days on hand.

  Here, even if the amount of accounts payable increases to an amount of money 633, if the amount of purchase increases to an amount of money 634, the purchase amount changes as indicated by the dotted line 635, and the accounts payable is cleared. It turns out that there is no problem on the schedule. On the other hand, when the amount of accounts payable is constant and the number of days of accounts payable is extended to the period 636, the transition of the purchase amount is as shown by the dotted line 637, and it can be seen that the withdrawal is reduced. Therefore, the user can recognize the necessity of analyzing the payee and considering the extension plan of the payment site.

  FIG. 22 is a diagram illustrating an example of a screen 640 that displays changes in the number of working capital days by year and month. The collection information display unit 214 reads the collection information corresponding to the product selected in the pull-down list 611 from the collection information database 254, and displays the transition of the working capital days of the read collection information as a line graph 641. In addition, the collection information display unit 214 also displays changes in the number of days of inventory holding, the number of accounts receivable on hand, the number of accounts payable on hand, and the number of working capital days as a table 642.

  The user can grasp the overall fund status at a glance by referring to the transition of the working capital days, which is the number of days from purchase of goods to sales and cashing, with reference to the screen 640. . The user can determine that the borrowing of funds is necessary when the working capital days is positive, and that the self-financing is possible when the working capital days are negative. In addition, when the number of working capital days is significantly increased, it is possible to grasp that there is a possibility that a problem such as difficulty in raising cash is occurring on the cash collection schedule. In addition, the user can perform advance management regarding cash flow by grasping the transition of the overall cash flow and grasping the schedule until cash collection. As a result, the user can formulate an optimal investment plan, and is expected to prevent an opportunity loss of the investment plan and realize an optimal cash flow.

== (3) Matter management information output processing ==
Next, display processing of information related to a case (project) (hereinafter referred to as case information) will be described.

  The case accuracy database 255 stores information related to a case such as an expected probability (accuracy) of receiving a case (hereinafter referred to as case accuracy information). FIG. 23 shows the configuration of the case accuracy information stored in the case accuracy database 255. As shown in the figure, the case accuracy information includes a scenario number, a customer name, an order amount, accuracy, and a situation. The scenario NO is a number assigned to a series of matters, for example, assigned for each in-house sales group, for each manager, for each person in charge. The customer name is the name of the customer who sells the product. The accuracy is information indicating the possibility of receiving an order with an order amount. In the present embodiment, the accuracy is expressed in four stages “A” to “D”. The status is information indicating the status of the item.

  The case accuracy information registration unit 215 receives input of information regarding the accuracy of the case, and registers the case accuracy information in the case accuracy database 255. FIG. 24 shows a flow of registration processing of case accuracy information. FIG. 25 shows an example of an input screen 810 used for registration processing of case accuracy information.

  The case accuracy information registration unit 215 displays the screen 810 and accepts input of check items related to the accuracy of the case (S701). The screen 810 includes a scenario number input field 811, a customer name input field 812, a check item input field 813, an order amount input field 814, and an information input field 815 indicating the status of the case. Check items to be entered in the input field 813 include, for example, whether the customer's reaction is good or bad and the person in charge knows the request for proposal (RFP) that is a request from the customer. It shows whether budgeting is in progress.

  When input is made in each field of the screen 810 and the OK button 816 is pressed, the case accuracy information registration unit 215 counts the number of “◯” among the check item values input in the input field 813 ( In step S702, a quotient obtained by dividing the number of counted “o” by the number of check items input in the input field 813 is set as a determination value (S703).

  The case accuracy information registration unit 215 sets the accuracy to “A” if the determination value is 0.8 or more (S704: 0.8 or more) (S705), and if the determination value is 0.6 to 0.8. (S704: 0.6 to 0.8), the accuracy is “B” (S706), and if the determination value is 0.3 to 0.6 (S704: 0.3 to 0.6), the accuracy is “ C ”(S707), and if the determination value is less than 0.3 (S704: less than 0.3), the accuracy is set to“ D ”(S708).

  The case accuracy information registration unit 215 includes the scenario number input in the input field 811 of the screen 810, the customer name input in the input field 812, the order amount input in the input field 814, the accuracy determined above, and the input field 815. Item accuracy information is set in which the status of the item input to is set, and the generated item accuracy information is registered in the item accuracy database 255 (S709).

As described above, the order accuracy of a case can be determined by inputting check items, and the case accuracy database 255 can be updated. In general, the order receipt accuracy of a case is often determined based on intuition based on the experience of the person in charge. However, according to the management information providing apparatus 20 of this embodiment, the order receipt accuracy of a case is determined from a plurality of check items. It becomes possible. Therefore, it is possible to determine the accuracy with high accuracy without being influenced by the years of experience of the person in charge. Further, it is possible to quantitatively calculate the order receipt accuracy while minimizing the difference between the persons in charge of each case.
Furthermore, by managing the order receipt accuracy from the person in charge in the database, the administrator user can refer to the case accuracy database 255 to grasp the order receipt accuracy of the case.

  The project budget database 256 stores information related to the budget for each project (hereinafter referred to as project budget information), and the project performance database 257 stores information related to the sales performance for each project (hereinafter referred to as project performance information). Remember.

  FIG. 26 shows a configuration example of the case budget information stored in the case budget database 256, and FIG. 27 shows a configuration example of the case result information stored in the case result database 257. As shown in these figures, the project budget information and the project performance information have the same structure, and the project budget information and the project performance information are the scenario NO, customer name, sales, manufacturing cost, gross profit, Includes profit and loss, period, and order accuracy. The order accuracy of the case budget information can be set, for example, by copying the accuracy of the case accuracy database 255 at the time of budgeting. In addition, the order accuracy of the case record information can be set by copying the accuracy of the case budget information when the case is recorded as sales, for example.

  The order accuracy display unit 216 totals the order amounts (hereinafter referred to as the forecast amount) for each accuracy, and displays the total value. FIG. 28 is a diagram showing the flow of the forecast amount display process. FIG. 29 is a diagram showing an example of a screen used for the line-of-sight display processing of FIG.

  When a scenario number is selected from the pull-down list 821 on the screen 820, the order accuracy display unit 216 receives the scenario number selected by the user (S721), and the scenario number (hereinafter, input) from the case budget database 256. The total value of sales corresponding to NO is calculated (S722). The order receipt accuracy display unit 216 calculates the forecast amount for each accuracy by summing up the order receipt amounts corresponding to the input NOs for each accuracy from the case accuracy database 255 (S723). The order accuracy display unit 216 displays the total sales of the case budget information and the forecast amount for each accuracy on the screen 820 (S724). In the display field 822 of the screen 820, the total sales of the project budget information is displayed in the bar graph 823, the estimated amount for each accuracy is displayed in the stacked graph 824, and the budget and the estimated amount are also displayed in the table 825. .

  When any accuracy of the forecast amount 824 by accuracy (for example, accuracy A826 in FIG. 29) is clicked, the order accuracy display unit 216 accepts specification of the clicked accuracy (S725), and the specified accuracy ( Hereinafter, the case accuracy information corresponding to the specified accuracy is read from the case accuracy database 255 (S726), and the read case accuracy information is displayed in a list (S726). A list of displayed case accuracy information is displayed as a screen 830.

  On the screen 830, the accuracy of the case accuracy information can be changed by a pull-down list 831. When the accuracy is changed from the pull-down list 831 and the confirm button 832 is pressed, the order accuracy display unit 216 receives the accuracy selected from the pull-down list 831 and the corresponding customer name 833 (S728: YES). The order accuracy display unit 216 updates the case accuracy database 255 to change the accuracy corresponding to the input NO and the specified customer name 833 to the input accuracy (S729).

  As described above, the order receipt accuracy display unit 216 can display the budget and the forecast amount for each accuracy. Therefore, the user can grasp the overall prospect of orders.

  If there are many cases with low accuracy, the color of the stacked graph 824 may be changed. In this case, for example, a condition in which the order amount of the accuracy C and the accuracy D is 20% or more of the total forecast amount, and a color to be displayed on the stacked graph 824 when the condition is satisfied are stored in the memory. 202, storage order 203, etc., and the order accuracy display unit 216 determines whether or not the stored condition is satisfied, and if it is satisfied, displays the stacked graph 824 in that color. Like that. Thereby, when the prospect of achieving the budget is low, the user can quickly grasp that fact. Thus, for example, the user can quickly take countermeasures such as rethinking the target to which the merchandise is sold.

  The item list display unit 217 displays a list of item budget information or item result information. In the present embodiment, the item list display unit 217 displays a list of items with large sales (large item list) and a list of items with profit / loss in red (red item list). The flow of display processing by the case list display unit 217 is shown in FIG. FIG. 31 is a diagram showing an example of a screen 840 used in the display process of FIG.

The screen 840 includes a pull-down list 841 for specifying a scenario NO, a pull-down list 842 for specifying a budget or an actual result, and a pull-down list 843 for specifying a period. The designation of the budget or the actual result and the input of the period are accepted (S741).
When the budget is specified (S742: YES), the case list display unit 217 reads the case budget information corresponding to the input scenario No. and period from the case budget database 256 (S743), and the read case budget information. A predetermined number is set as a large-scale project list in descending order of sales (S744). Further, the case list display unit 217 sets a predetermined number of items in the read-out item budget information in which the profit / loss is negative in the order of increasing profit / loss in the red as an item list in red (S745).

On the other hand, when the result is designated (S742: NO), the case list display unit 217 reads out the case result information corresponding to the input scenario NO and period from the case result database 257 (S746), and the read case result. Among the information, a predetermined number is set in a large order list in descending order of sales (S747). In addition, the case list display unit 217 sets a predetermined number of items in the order of decreasing profit / loss to the red case list in order of increasing profit / loss in the read case result information in which the profit / loss is negative (S748).
The case list display unit 217 displays a large list of cases (S749), and displays a list of red items (S750). In the screen 840 shown in FIG. 31, a large-scale item list 845 and a red item list 846 are displayed in the display field 844.

  As described above, the item list display unit 217 can display a list of large items or red items among a large number of items. Therefore, the user can easily grasp the risk, loss, etc. when the order cannot be received.

  In general, losses that occur in units of projects and risks that have not occurred are often not counted until the end of the period. However, according to the management information providing apparatus 20 of this embodiment, without waiting for the end of the period, It is possible to easily grasp the outlook for profit and loss. As a result, the manager can make a performance prediction from an early stage, so that it is possible to plan measures more quickly and accurately.

  In addition, since the management information providing apparatus 20 of the present embodiment can display the sales, gross profit, profit / loss, etc. of the case, the user can accurately grasp the situation of each case. Moreover, the transparency of the situation for each case in the organization can be increased, and as a result, the transparency of the entire management can be increased.

  As described above, according to the management information display system of the present embodiment, the user analyzes KPI numbers such as sales, gross profit, profit and loss, etc. using a Web browser, grasps the cash collection schedule, You can manage the performance of each project. Further, in the management information display system, information necessary for management judgment is visually displayed as a graph or a table. Therefore, the user can quickly and accurately grasp information necessary for management judgment. This makes it possible to quickly find problems and plan measures.

  Moreover, in the management information display system of this embodiment, since management information can be browsed easily at an appropriate timing, the user can escape from the month-end culture and perform so-called real-time management.

  Although the present embodiment has been described above, the above embodiment is intended to facilitate understanding of the present invention and is not intended to limit the present invention. The present invention can be changed and improved without departing from the gist thereof, and the present invention includes equivalents thereof.

  For example, although it assumed that it operate | moves as a Web application, you may make it a user operate management information provision apparatus 20 itself. In this case, the management information providing apparatus 20 includes an input device such as a keyboard and a mouse and a display device such as a display. The display device at this time can correspond to the output device of the present invention.

It is a figure showing the whole management information display system composition of this embodiment. It is a figure which shows the hardware constitutions of the management information provision apparatus 20. 3 is a diagram illustrating a software configuration of a management information providing device 20. FIG. It is a figure which shows the structural example of budget information. It is a figure which shows the structural example of track record information. It is a figure which shows the flow of a display process of a KPI numerical value. It is a figure which shows the structural example of tree data. It is a figure which shows the example of the screen displayed in order that the drilldown display part 211 may accept designation | designated of an element. It is a figure which shows the flow of a display process of a KPI numerical value. It is a figure which shows the flow of the totaling display process according to hierarchy. It is a figure which shows the example of a screen which displays KPI in a table format and a bar graph format. It is a figure which shows the example of a screen which displays KPI in a table format and a bar graph format. It is a figure which shows the example of a screen which displays KPI in a table format and a bar graph format. It is a figure which shows the example of a screen at the time of making it total the KPI numerical value about two hierarchy. It is a figure which shows the example of a screen at the time of making it total the KPI numerical value about two hierarchy. It is a figure which shows the structure of merchandise management information. It is a figure which shows the structural example of collection | recovery information. It is a figure which shows the flow of the registration process of collection information by the collection information registration part 213. FIG. It is a figure which shows an example of the screen on which track record information and collection information are displayed. It is a figure which shows an example of the screen on which track record information and collection information are displayed. It is a figure which shows an example of the screen on which track record information and collection information are displayed. It is a figure which shows an example of the screen which displays transition of the working capital days according to a year and month. It is a figure which shows the structure of case probability information. It is a figure which shows the flow of registration processing of case accuracy information. An example of the input screen used for the registration process of case accuracy information is shown. It is a figure which shows the structural example of case budget information. It is a figure which shows the structural example of case performance information. It is a figure which shows the flow of a display process of a forecast amount. It is a figure which shows the example of a screen used for the display process of a forecast amount. It is a figure which shows the flow of a display process of a case list. It is a figure which shows the example of a screen used for the display process of a case list.

Explanation of symbols

10 Client Device 20 Management Information Providing Device 30 Communication Network 201 CPU
202 Memory 203 Storage Device 204 Communication Interface 211 Drill-Down Display Unit 212 Hierarchical Total Display Unit 213 Collection Information Registration Unit 214 Collection Information Display Unit 215 Item Accuracy Information Registration Unit 216 Order Accuracy Display Unit 217 Item List Display Unit 251 Budget Database 252 Results Database 253 Product management database 254 Collection information database 255 Project probability database 256 Project budget database 257 Project results database

Claims (6)

A method for outputting management information of a company,
Computer
Stores management numbers, which are numbers related to the management, in a memory;
In response to an instruction from the user, calculate a total value obtained by totaling the management values stored in the memory,
Outputting the calculated total value to an output device;
Management information output method characterized by The management information output method according to claim 1,
The computer
The management numerical value is stored in the memory in association with a plurality of total items,
Storing the hierarchical relationship of the aggregated items in the memory;
Receiving an input of information specifying the first aggregated item from the user;
Calculating the first aggregate value by aggregating the management values corresponding to the first aggregate item;
A second total item that belongs to a lower layer than the first total item is specified, and the management value corresponding to the first and second total items is totaled to calculate a second total value And
Outputting the first and second aggregated values to the output device;
Management information output method characterized by The management information output method according to claim 2,
The computer
The management numerical value is stored in the memory in association with information indicating time and the plurality of total items,
The management numerical value for each predetermined period corresponding to the second tabulation item is read from the memory,
Calculating the third aggregation value by aggregating the management numerical value for each predetermined period;
Outputting a list of the third tabulated values to the output device;
Management information output method characterized by The management information output method according to claim 1,
The computer
As the management numerical value, at least a stock amount, a sales amount, an accounts receivable amount, and an accounts payable amount of a product in a predetermined period are stored in the memory,
Based on the predetermined period, the inventory amount, and the sales amount, calculate the number of inventory days, which is a predicted value of the number of days until the inventory of the product is issued,
Based on the predetermined period, the amount of accounts receivable, and the amount of sales, calculate the number of accounts receivable, which is an estimate of the number of days until collection of accounts receivable,
Based on the predetermined period, the amount of accounts payable, and the amount of sales, calculate the number of days payable, which is an estimate of the number of days until payment for accounts payable for products,
Based on the inventory days, the accounts receivable days, and the accounts payable days, calculating the number of days of funds turnover, which is the number of days from purchase of goods to cashing,
Outputting the calculated funds turnover days to the output device;
Management information output method characterized by The management information output method according to claim 1,
The computer
Accept the input of the order value and the accuracy indicating the possibility of receiving an order,
Storing the order amount and the accuracy in the memory;
Calculate the aggregate value by aggregating the order amount for each order accuracy,
Outputting the aggregate value for each order accuracy to the output device;
Management information output method characterized by The management information output method according to claim 1,
The computer
For each item specifying information for specifying a received item, at least one of the sales amount and profit / loss of the item is stored in the memory as the management value,
For each case, calculate the aggregate value by aggregating at least one of the sales and profit / loss,
Outputting the case specifying information for specifying the case and the total value to the output device in descending order of the calculated total value;
Management information output method characterized by

Images