JP7233148B2 - PLANNING PROGRAM, PLANNING DEVICE AND PLANNING METHOD - Google Patents

Description

TECHNICAL FIELD The present invention relates to a plan creation program and the like for creating a management plan.

Conventionally, a system has been proposed that assists a company in creating a management plan (Patent Document 1).

Japanese Patent Application Laid-Open No. 2004-334620

However, in order to create a management plan using the conventional system, the income statement (P/L), balance sheet (B/S), cash flow statement (C/F), etc. for the past few years performance data input is required, which is cumbersome. In addition, when the planned value of each item listed in the management plan is determined based on past performance data, it is difficult for inexperienced and inexperienced personnel to make the determination. The present invention has been made in view of such circumstances. The purpose is to provide a plan creation program that enables even an inexperienced and inexperienced person in charge to determine planned values based on past performance data .

A plan creation program according to the present invention acquires performance data of a plurality of items related to management, acquires a period for creating a management plan, and outputs a question to be answered by selecting the expected fluctuation of the item. and acquiring selection information of the expected variation for the question , acquiring calculation logic that is associated with the acquired selection information and containing a coefficient that converts the expected variation, and based on the acquired calculation logic, the actual result It is characterized in that the computer is caused to perform a process of calculating a planned value of the item from the data and creating a management plan for the period based on the calculated planned value .

According to the present invention, even an inexperienced and inexperienced person in charge can determine planned values based on past performance data .

It is explanatory drawing which shows the structural example of a plan management system. It is a block diagram which shows the hardware structural example of a management server. 3 is a block diagram showing a hardware configuration example of a user terminal; FIG. 3 is a block diagram showing a hardware configuration example of an administrator terminal; FIG. It is explanatory drawing which shows the example of user DB. It is explanatory drawing which shows the example of accounting DB. It is explanatory drawing which shows the example of accounting DB. It is explanatory drawing which shows the example of reservation DB. FIG. 4 is an explanatory diagram showing an example of a POS-DB; It is explanatory drawing which shows the example of attendance DB. It is explanatory drawing which shows the example of order receiving/ordering DB. FIG. 4 is an explanatory diagram showing an example of a logic DB; It is explanatory drawing which shows the example of forecast/actual DB. FIG. 4 is an explanatory diagram showing an example of a report DB; FIG. It is explanatory drawing which shows the example of alert DB. It is a flow chart which shows an example of a procedure of plan creation processing. 9 is a flow chart showing an example of a procedure of automatic creation processing; FIG. 10 is an explanatory diagram showing an example of automatic creation; 10 is a flow chart showing an example of the procedure of question creation processing; 10 is a flow chart showing an example of the procedure of question creation processing; It is explanatory drawing which shows the example of question preparation. 7 is a flow chart showing an example of a procedure of direct editing processing; 9 is a flow chart showing an example of a procedure of graph editing processing; FIG. 11 is a flowchart showing an example of a procedure of simulation editing processing; FIG. FIG. 9 is an explanatory diagram showing an example of a creation method selection screen; FIG. 9 is an explanatory diagram showing an example of an automatic creation setting screen; FIG. 10 is an explanatory diagram showing an example of a question-and-answer screen; It is explanatory drawing which shows the example of a plan display screen. FIG. 11 is an explanatory diagram showing an example of an editing method selection screen; FIG. 11 is an explanatory diagram showing an example of a direct edit screen; FIG. 9 is an explanatory diagram showing an example of a graph edit screen; FIG. 9 is an explanatory diagram showing an example of a simulation edit screen; 6 is a flow chart showing an example of a procedure of planned operation processing; 9 is a flowchart illustrating an example of a procedure for budget/actual management processing; 10 is a flow chart showing an example of the procedure of report setting processing; 10 is a flowchart illustrating an example procedure of alert setting processing; 6 is a flowchart illustrating an example of batch processing procedures; FIG. 10 is a flowchart showing an example of a procedure of a forecast creation process; FIG. 7 is a flow chart showing an example of the procedure of report creation processing; FIG. 11 is an explanatory diagram showing an example of the auto report creation logic; 10 is a flowchart illustrating an example procedure of alert creation processing; 7 is a flowchart illustrating an example of a procedure for prediction/recreation processing; FIG. 4 is an explanatory diagram showing an example of prediction logic; FIG. 11 is an explanatory diagram showing an example of an operation menu screen; FIG. 11 is an explanatory diagram showing an example of a budget/actual management menu screen; FIG. 11 is an explanatory diagram showing an example of a budget/actual management setting screen; FIG. 11 is an explanatory diagram showing an example of a forecast/actual situation display screen; FIG. 10 is an explanatory diagram showing an example of a report selection screen; FIG. 11 is an explanatory diagram showing an example of a template report setting screen; FIG. 11 is an explanatory diagram showing an example of a report setting screen; FIG. 11 is an explanatory diagram showing an example of an auto report. FIG. 9 is an explanatory diagram showing an example of an alert setting screen; FIG. 11 is an explanatory diagram showing an example of a prediction/recreation menu screen; FIG. 11 is an explanatory diagram showing an example of a recreating method selection screen; FIG. 10 is an explanatory diagram showing an example of an advice DB; It is explanatory drawing which shows the example of advertisement DB. It is a flow chart which shows another procedure example of budget creation processing and alert creation processing. FIG. 11 is an explanatory diagram showing an example of a cooperation setting screen; FIG. 4 is an explanatory diagram showing a multi-CSV upload function;

Embodiments will be described below with reference to the drawings.

FIG. 1 is an explanatory diagram showing a configuration example of a plan management system. The plan management system 100 includes a management server (plan creation device) 1 , a user terminal 2 and an administrator terminal 3 . The plan management system 100 is connected with other systems 4, which are various data sources. A management server 1, a user terminal 2, an administrator terminal 3, and another system 4 are connected by a network N so as to be able to communicate with each other. Other systems 4 include a reservation system, a POS (Point of sale system) system, an attendance system, an accounting system, a payroll system, and an ordering system. Reservation system for medical institutions, seat reservations for restaurants, facility reservations for rental conference rooms, tour reservations for travel, ticket reservations for transportation, lesson reservations for language learning, treatment reservations for esthetic salons and nail salons, etc. including a system for making reservations for The POS system includes not only a general system that tallies the sales results of product sales on an individual item basis, but also a system that tallies the sales results of services in the service industry on a service menu basis. The attendance system is a system that manages the attendance of employees, including regular employees, contract employees, and part-timers. Accounting systems include management accounting systems, financial accounting systems, and the like. A payroll system is a system that calculates salaries to be paid to employees and stores payroll history. The ordering system is a system for receiving and placing orders for products and services. Although two user terminals 2 and two administrator terminals 3 are shown in FIG. 1, each may be one or three or more. A single user terminal 2 and administrator terminal 3 may be used. The other system 4 may further include a purchase inventory management system, an employee goal/evaluation management system, an employee motivation management system, a review site management system, a coupon site management system, a customer questionnaire management system, and the like. good.

FIG. 2 is a block diagram showing a hardware configuration example of a management server. The management server 1 collects various data related to the management of each user from the other system 4, and performs processing such as creating a management plan based on the collected data. The management server 1 is composed of a server computer and the like. The management server 1 includes a CPU (Central Processing Unit) 11 , a ROM (Read Only Memory) 12 , a RAM (Random Access Memory) 13 , a large capacity storage section 14 and a communication section 15 . Each configuration is connected by a bus B.

The CPU 11 controls each part of the hardware according to a control program (planning program) 1P stored in the ROM 12 . The RAM 13 is, for example, SRAM (Static RAM), DRAM (Dynamic RAM), or flash memory. The RAM 13 temporarily stores data generated when the CPU 11 executes the program.

The large-capacity storage unit 14 is, for example, a hard disk or an SSD (Solid State Drive). The large-capacity storage unit 14 stores various databases (DB: DataBase). The large-capacity storage unit 14 stores a user DB 141, an accounting DB 142, a reservation DB 143, a POS-DB 144, an attendance DB 145, an order receiving/ordering DB 146, a logic DB 147, a forecast DB 148, a report DB 149, and an alert DB 14A. Also, the control program 1P may be stored in the large-capacity storage unit 14 . All or part of the databases from the user DB 141 to the alert DB 14A may be stored outside the management server 1 . For example, it may be stored in a database server or cloud storage.

The communication unit 15 communicates with the user terminal 2 , the administrator terminal 3 and the other system 4 via the network N. FIG. Alternatively, the CPU 11 may use the communication unit 15 and the management server 1 may be composed of a plurality of physical server computers. Also, the functions of the management server 1 may be provided by a cloud service.

The reader 16 reads portable storage media 1a including CD (Compact Disc)-ROM and DVD (Digital Versatile Disc)-ROM. The CPU 11 may read the control program 1P from the portable storage medium 1a via the reading section 16 and store it in the large-capacity storage section 14 . Alternatively, the CPU 11 may download the control program 1P from another computer via the network N or the like and store it in the large-capacity storage unit 14 . Furthermore, the CPU 11 may read the control program 1P from the semiconductor memory 1b.

FIG. 3 is a block diagram showing a hardware configuration example of a user terminal. A user terminal 2 is a terminal used by a user of the plan management system 100 . The user terminal 2 is composed of a notebook computer, a panel computer, a tablet computer, or the like. The user terminal 2 includes a CPU 21 , ROM 22 , RAM 23 , communication section 24 , input section 25 , display section 26 and mass storage section 27 . Each configuration is connected by a bus B.

The CPU 21 controls each part of the hardware according to a control program (plan editing program) 2P stored in the ROM 22 . RAM 23 is, for example, SRAM, DRAM or flash memory. The RAM 23 temporarily stores data generated when the CPU 21 executes the program.

The communication unit 24 communicates with the management server 1 and other systems 4 via the network N. FIG. Alternatively, the CPU 21 may use the communication section 24 to download the control program 2P from another computer via the network N or the like and store it in the large-capacity storage section 27 .

The display unit 26 includes a liquid crystal display panel and the like. The display unit 26 displays the plan output by the management server 1 and the like. The input unit 25 is a keyboard or mouse. Also, the input unit 25 may be a touch panel display integrated with the display unit 26 . Note that the user terminal 2 may display on an external display device.

The mass storage unit 27 is, for example, a hard disk or SSD. The large-capacity storage unit 27 stores various data.

FIG. 4 is a block diagram showing a hardware configuration example of an administrator terminal. A manager terminal 3 is a terminal used by a manager of the plan management system 100 . The administrator terminal 3 is composed of a notebook computer, a panel computer, a tablet computer, or the like. The administrator terminal 3 includes a CPU 31 , a ROM 32 , a RAM 33 , a communication section 34 , an input section 35 , a display section 36 and a mass storage section 37 . Each configuration is connected by a bus B. Since each configuration of the administrator terminal 3 is the same as each configuration of the user terminal 2 having the same name, description thereof will be omitted.

Next, the database used by the plan management system 100 will be described. FIG. 5 is an explanatory diagram showing an example of the user DB. The user DB 141 stores information on users who use the plan management system 100 . The user DB 141 includes a user ID column, a form column, a name/name column, a phone number column, an e-mail address column, a password column, a chat column, an account column, and a cooperation setting column. The user ID column stores user IDs that uniquely identify users. A user ID is issued at the time of user registration. The name/name column stores the name of the user. If the user is a company, the company name is stored in the name/name column. If the user is a sole proprietor, the personal name is stored in the name/name column. The phone number column stores the user's phone number. The mail address column stores the user's e-mail address. The password column stores the user's login password. The encrypted password is stored in the password column. In FIG. 5, it is indicated by "*" for convenience. The chat column stores the identification of the chat service for which the user wishes to receive alerts, such as the name of the chat service. The account column stores the user's account with the chat service. The cooperation setting column stores the setting of cooperation with the other system 4 . The linkage setting columns include an accounting column, a POS column, an attendance column, and a reservation column. The accounting column, the POS column, the attendance column, and the reservation column each store identification information, such as names, of the accounting system, POS system, attendance system, and reservation system.

6 and 7 are explanatory diagrams showing examples of the accounting DB. The accounting DB 142 mainly stores user's accounting data collected from the accounting system. As shown in FIG. 6, the accounting DB 142 stores annual data/past 1421 and annual data/current period 1422 . Yearly data/past 1421 stores past data in units of years. For example, the annual data/past 1421 includes P/L plan 14211, P/L actual result 14212, B/S plan 14213, B/S actual result 14214, C/F plan 14215, C/F actual result 14216, sales plan 14217, and sales performance 14218. P/L Plan 14211 contains several years of P/L plan data for past years. P/L Performance 14212 includes several years of P/L performance data for past years. B/S Plan 14213 contains several years of B/S plan data for past years. B/S Performance 14214 includes several years of performance data for past years. C/F Plan 14215 contains several years of C/F plan data for past years. The C/F Actual 14216 includes several years of C/F actual data for past years. Sales plan 14217 contains several years of sales plan data for past years. Actual Sales 14218 includes several years of actual sales data for past years. The annual data/current term 1422 includes P/L plan 14221, B/S plan 14222, C/F plan 14223, and sales plan 14224, for example. The P/L plan 14221 is P/L plan data for the current term. The B/S plan 14222 is B/S plan data for the current period. The C/F plan 14223 is C/F plan data for the current period. The sales plan 14224 is sales plan data for the current term. Sales in the sales plan include sales of each product or each service, sales for each product group or service group in which a plurality of products or services are combined, sales for each customer, and the like. A year may be a calendar year beginning in January and ending in December, or may be a fiscal year beginning in April and ending in March of the following year. Also, the start month and end month may be set according to the user's accounting period. The past data may be stored as P/L, B/S, and C/F, and the past plan and performance data related to sales may be stored not only in yearly units but also in monthly units.

In addition, as shown in FIG. 7, the accounting DB 142 stores monthly data/plan 1423 and monthly data/result 1424 . Monthly data/plan 1423 and monthly data/result 1424 are data for the current term. The monthly data/plan 1423 includes, for example, a P/L plan 14231, a B/S plan 14232, a C/F plan 14233, and a sales plan 14234. The P/L plan 14231 includes monthly P/L plan data for the current term. The B/S plan 14232 includes monthly B/S plan data for the current term. The C/F plan 14233 includes monthly C/F plan data for the current term. The sales plan 14234 includes monthly sales plan data for the current term. Monthly data/results 1424 include P/L results 14241 , B/S plans 14242 , C/F plans 14243 and sales plans 14244 . The P/L performance record 14241 stores the P/L performance data for the current period on a monthly basis. The B/S plan 14242 stores B/S performance data for the current period on a monthly basis. The C/F plan 14243 stores actual C/F data for the current period on a monthly basis. The sales plan 14244 stores actual sales data for the current period on a monthly basis. For example, if the current period is 2018 and the current period is June, the monthly data/results 1424 includes complete data for April and May 2018. contains useful data.

FIG. 8 is an explanatory diagram showing an example of a reservation DB. The reservation DB 143 includes initial registration data 1431 and real-time data 1432 . Initial registration data 1431 is static data. The initial registration data 1431 is determined for each type of industry. The restaurant initial registration data 1431 includes, for example, a user ID, a store ID, seat information, the number of frames, the number of reservation plans, and the like. The seat information includes the number of tables, the number of seats, and the like. A frame is a time frame that includes a start and end time. The number of frames is the number of frames per day. The number of reservation plans is the number of plans including service contents and fees that can be selected by the customer at the time of reservation. The initial registration data 1431 of the massage salon includes, for example, a user ID, a store ID, the number of treatments, the number of sessions, and the number of treatment plans. The number of treatments is the number of treatment tables, and indicates the maximum number of customers who can receive treatments at the same time. The number of frames is the same as in the restaurant. The number of treatment plans is the number of plans including treatment content, treatment time, and treatment fee. The real-time data 1432 is obtained by collecting the reservation status of each store at any time. Real-time data 1432 includes, for example, user IDs, store IDs, data update dates and times, number of reservations, cancellation rates, and the like. The cancellation rate is the number of reservation cancellations on the business day divided by the number of reservations.

FIG. 9 is an explanatory diagram showing an example of POS-DB. The POS-DB 144 stores data collected from the POS system from time to time. The POS-DB 144 includes sales ranking 1441, cost ranking 1442, unit price per customer 1443, repeat rate 1444, number of coupons 1445, consumption materials 1446, and the like. Repeat rate 1444 includes daily, weekly, and monthly repeat rates. The period for which the repeat rate is to be obtained is appropriately determined according to the type of industry. The number of coupons 1445 includes the type and number of issued coupons, the type and number of used coupons, and the like. Consumed Materials 1446 contains the names and quantities of materials consumed.

FIG. 10 is an explanatory diagram showing an example of the attendance DB. The attendance DB 145 stores attendance data collected as needed from the attendance system. The attendance data includes real-time data 1451 and monthly data 1452 . The real-time data 1451 includes attendance data for each employee. The real-time data 1451 includes, for example, attendance classification, name, attendance/exit date/time, cumulative working hours per month, number of working days per month, number of consecutive working days on the current day, and the like. Monthly data 1452 includes monthly attendance data. The monthly data 1452 may include data for each store in addition to data obtained by aggregating the real-time data 1451 for each month. The monthly data 1452 for each store includes, for example, store name, monthly data, total number of employees, number of full-time employees, number of part-timers, number of new hires, and number of retirees.

FIG. 11 is an explanatory diagram showing an example of an order receiving/ordering DB. The order receiving/ordering DB 146 stores the order receiving/ordering data collected as needed from the order receiving/ordering system. The order data 1461 includes monthly data, customer code, order product name, order unit price, and order quantity. The order data 1461 of a customer who has received an order for a plurality of products may include, in one record, the name of the ordered product, the unit price of the ordered product, and the quantity of ordered products. The order data 1462 includes monthly data, supplier code, order product name, order unit price, and order quantity. The order data 1462 of a supplier who has ordered a plurality of products may include, in one record, the name of the ordered product, the unit price of the order, and the quantity of orders received. The data to be stored in the reservation DB 143, POS-DB 144, attendance DB 145, and order receiving/ordering DB 146 may be not only data generated in the current period but also data in the past period. In addition, current term data aggregated daily, weekly, monthly, or yearly, or past term data may be stored. In addition, planning data for the current period and previous periods may be stored.

FIG. 12 is an explanatory diagram showing an example of the logic DB. Logic DB147 memorize|stores the logic at the time of plan creation and prediction. FIG. 12A shows an example of auto-creation logic 1471 . The automatic creation logic 1471 shown in FIG. 12A is logic for making a P/L plan for the current term from past P/L data. FIG. 12B shows an example of query logic 1472 . For example, if the user answers "slightly increase" to the expected fluctuation of selling, general and administrative expenses, the planned value for this term is calculated as 5% higher than the previous term (previous term x 1.05). FIG. 12C shows an example of prediction logic 1473 . The prediction logic 1473 shown in FIG. 12C is logic that uses actual sales from January to March to predict annual sales from January to December and monthly sales from April to December. .

FIG. 13 is an explanatory diagram showing an example of a forecast/actual DB. The forecast/actual DB 148 stores numerical values to be subject to forecast/actual management. The forecast/actual DB 148 includes a user ID column, a store ID column, an item column, a January column, a February column, a March column, . . . and a December column. The user ID column stores user IDs. The store ID column stores store IDs. The item column stores managed objects. For example, sales, cost of sales, and SG&A expenses. The January column, February column, March column, .

FIG. 14 is an explanatory diagram showing an example of the report DB. The report DB 149 stores settings for budget/actual management reports. The report DB 149 includes a user ID column, a unit column, a subject column, a year plan column, a cumulative value column, a format column and an image column. The user ID column stores user IDs. The units column stores the units in which numerical values are displayed. Units include stores, regions, divisions, and the entire company. The item column stores the items subject to budget/actual management. The yearly plan column stores whether to display annual plan values in the report. The cumulative value column stores whether or not to display the cumulative value up to the current month in the report. For example, when displaying cumulative sales in a report for April, the total sales from January to April are displayed. The format column stores the name of the format used when creating the report. Memorize the format in advance. The Image column stores the most recent reports as images or PDFs.

FIG. 15 is an explanatory diagram showing an example of the alert DB. The alert DB 14A stores alert conditions set by the user. The alert DB 14A includes a user ID column, a number column, an evaluation index column, a reference value column, a unit column, an alert method column, and an address column. The user ID column sets the alert conditions and stores the user ID of the user who receives the alert. The number column stores the sequential number of the alert condition. The sequence number is unique for each user. The evaluation index column stores indexes (subjects) to be evaluated. The evaluation index is, for example, sales volume, gross profit, and unit price per customer. The reference value column stores a reference value for determining whether or not to issue an alert. The unit column stores the unit of reference value. The unit is, for example, %, million yen, or ten million yen. The alert method column stores the alert method. The alert method is e-mail, SMS (Short Message Service), for example. The address column stores the address to which the alert is sent. When the alert method is email, the To column stores email addresses.

The plan management system 100 can be used when creating and operating a management plan. First, the processing performed by the plan management system 100 when a user creates a plan using the plan management system 100 will be described.

FIG. 16 is a flow chart showing an example of the procedure of planning processing. The CPU 11 transmits the creation method selection screen to the user terminal 2 . The user selects a creation method on the creation method selection screen. The creation method selected by the user is transmitted to the management server 1 . The CPU 11 of the management server 1 receives the plan creation method from the user terminal 2 (step S1). The CPU 11 determines whether or not the acquired creation method is automatic creation (step S2). When the CPU 11 determines that the acquired creation method is automatic creation (YES in step S2), automatic creation is performed (step S3). When the CPU 11 determines that the acquired creation method is not automatic creation (NO in step S2), it creates a question (step S4). The CPU 11 transmits the plan created in step S2 or S3 to the user terminal 2 (step S5). The user terminal 2 acquires the plan received from the management server 1 and displays it. The user refers to the displayed plan, determines whether to accept the plan as it is or edit it, and transmits the result from the user terminal 2 to the management server 1 . The CPU 11 of the management server 1 receives the judgment result from the user terminal 2 (step S6). The CPU 11 determines whether or not the determination result received from the user terminal 2 is editing (step S7). When the CPU 11 determines that the result of determination is not editing (NO in step S7), the process proceeds to step S13. When the CPU 11 determines that the result of determination is editing (YES in step S7), it determines whether or not the editing method is direct input (step S8). When the CPU 11 determines that the editing method is direct input (YES in step S8), direct editing is performed (step S9). When the CPU 11 determines that the editing method is not direct input (NO in step S8), it determines whether it is graph editing (step S10). When the CPU 11 determines that the editing method is graph editing (YES in step S10), graph editing is performed (step S11). When the CPU 11 determines that the editing method is not graph editing (NO in step S10), simulation editing is performed (step S12). The CPU 11 stores the created plan or the edited plan (step S13). Databases that store plans vary in content. For example, if the created plan is P/L, it is stored in the accounting DB 142 . Note that when creating a plan for a plurality of periods, the series of processes shown in FIG. 16 are repeatedly executed.

FIG. 17 is a flow chart showing an example of the procedure of automatic creation processing. The automatic creation process is a process of estimating fluctuations from the previous term and creating a plan for the current term based on actual data. The CPU 11 of the management server 1 transmits a setting screen to the user terminal 2 (step S21). The CPU 21 of the user terminal 2 displays the setting screen on the display section 26 (step S22). The user terminal 2 uses the input unit 25 to set a method for acquiring performance data and instruct transmission. The CPU 21 transmits the acquisition method of performance data to the management server 1 (step S23). The CPU 11 of the management server 1 determines whether the acquisition method is file upload (step S24). When the CPU 11 determines that the acquisition method is file upload (YES in step S24), it transmits a file setting screen (step S25). The CPU 21 of the user terminal 2 displays the file setting screen on the display section 26 (step S26). The user uses the input unit 25 to set a file to be uploaded and instruct transmission. The CPU 21 transmits the file to the management server 1 (step S27). The CPU 11 of the management server 1 acquires performance data (step S31). When the CPU 11 determines that the acquisition method is not file upload (NO in step S24), it transmits the cooperation setting screen to the user terminal 2 (step S28). The CPU 21 of the user terminal 2 displays the cooperation setting screen on the display section 26 (step S29). The user uses the input unit 25 to set data linkage with the other system 4 . The CPU 21 transmits the cooperation settings to the management server 1 (step S30). The CPU 11 of the management server 1 acquires performance data from the other system 4 according to the cooperation setting (step S31). The CPU 11 notifies the user terminal 2 of the acquisition completion of the performance data (step S32). The user sets automatic creation and instructs transmission. The CPU 21 transmits the settings to the management server 1 (step S33). The CPU 11 of the management server 1 acquires the setting (step S34). The CPU 11 creates a plan according to the acquired settings and the automatic creation logic stored in the logic DB 147 (step S35). The CPU 11 returns the process to the caller. In addition, step S25, step S26, step S27, and step S31 may be repeatedly executed, and the files may be uploaded from the user terminal 2 to the management server 1 in multiple batches.

FIG. 18 is an explanatory diagram showing an example of automatic creation. The processing described with reference to FIG. 18 corresponds to step S35 in FIG. 17 and is an example of processing performed by the CPU 11 of the management server 1. FIG. FIG. 18 is an example of creating P/L data. This is an example of creating a plan for the current term (2018) using P/L performance data for the past two terms (2016 and 2017) according to the automatic creation logic 1471 shown in FIG. 12A. Although the variable cost ratio is not included in the P/L, it is necessary for planning. The upper table of FIG. 18 is an example of the increase/decrease rates of P/L items and variable cost ratios calculated from data for the past two terms. This is the preparation process for applying the automatic creation logic. The lower table of FIG. 18 shows an example of creating a plan for the current term (2018) by the automatic creation logic. The sales amount is the sales amount for 2017 plus the increase/decrease rate for the past two terms. That is, the rate of change from 2016 to 2017 and the rate of change from 2017 to 2018 are assumed to be the same. Cost of sales is calculated by multiplying sales by the variable cost ratio. Here, the variable cost ratio in 2018 is assumed to be the same as in 2017. As with sales, it may change at the same rate of change as the past two periods. Gross profit is calculated by subtracting the cost of sales from sales. We assume that selling, general and administrative expenses will fluctuate to 2017 values at the same rate of change as the last two periods. Gross profit is calculated by subtracting selling, general and administrative expenses from gross profit.

Although the P/L plan was used as an example, B/S, C/F, sales plans, etc. can be similarly planned for the current term based on the performance data of the past two terms. Furthermore, not only the annual plan but also the monthly plan can be planned by the same logic.

19 and 20 are flow charts showing an example of the procedure of question creation processing. The question creation process is a process of estimating the change from the previous term based on the answers to the questions to the user and creating a plan for the current term. Steps S41 to S52 in FIG. 19 are the same as steps S21 to S32 in FIG. 17 , so description thereof will be omitted. After step S52, the user makes settings for creating a question and instructs transmission. The CPU 21 transmits the settings to the management server 1 (step S53). The CPU 11 of the management server 1 acquires the settings (step S54). Based on the acquired settings, the CPU 11 acquires a question for the user from the logic DB 147 (step S55). The CPU 11 transmits a question screen including the acquired question to the user terminal 2 (step S56). The CPU 21 of the user terminal 2 displays the question screen on the display section 26 (step S57). The user inputs an answer to the question using the input unit 25 and instructs transmission. The CPU 21 transmits the reply to the management server 1 (step S58). The CPU 11 of the management server 1 acquires the reply (step S59). The CPU 11 determines whether or not there are any remaining questions (step S60). When the CPU 11 determines that there are remaining questions (YES in step S60), the process returns to step S56. When the CPU 11 determines that there are no remaining questions (NO in step S60), it creates a plan based on the answers (step S61). The CPU 11 returns the process to the caller.

FIG. 21 is an explanatory diagram showing an example of question preparation. The processing described with reference to FIG. 21 corresponds to step S61 in FIG. 20 and is an example of processing performed by the CPU 11 of the management server 1. FIG. FIG. 21 is an example of P/L data creation. FIG. 12B is an example of creating a plan for the current term (2018) from the data of the previous term (2017) according to the query logic 1472 . Again, the variable cost ratio is not included in the P/L, but it is necessary for planning. The upper table in FIG. 21 is an example of obtaining planned figures for the current term based on the user's answers to questions for some subjects of P/L. The user is asked, "How much will selling, general and administrative expenses increase?" According to question logic 1472, "slightly increased" is replaced with a 5% increase. Based on the figures for the previous term, the planned figures for the current term are obtained. Furthermore, the question "How much will the target operating profit increase?" is asked to the user, and "20%" is obtained as the answer. Based on this answer, the planned value of the operating gross profit for the current term is calculated assuming that the operating profit for the current term will increase by 20%. Furthermore, regarding the change ratio ratio, the user is asked "How much will it decrease?" According to query logic 1472, "slightly decreased" is replaced with a 2% decrease. Based on the figures for the previous term, the planned figures for the current term are obtained. In the lower part of FIG. 21, sales, cost of sales, and gross profit are obtained from selling, general and administrative expenses, operating income, and variable cost ratio obtained from the answers. Sales for the current term can be obtained from the current term's selling, general and administrative expenses, operating income, and variable cost ratio obtained in the upper row. Cost of sales is obtained from sales and the variable cost ratio. Gross profit is obtained from sales and cost of sales.

Although the P/L plan was taken as an example, B/S, C/F, sales plans, etc. are similarly set with questions and optional answers about some items, and plan values are set according to the answers from users. demand. Then, based on the obtained planned values, it is possible to obtain planned values for the remaining items. Also, not only the annual plan but also the monthly plan can be planned by the same question logic. When creating plans for multiple terms, first create a plan for the current term. After that, plans are created for the next term, next term, and so on.

FIG. 22 is a flow chart showing a procedure example of direct editing processing. The direct editing process is a process of editing a plan automatically created or question created by directly editing the numerical values included in the plan. The CPU 11 of the management server 1 transmits an edit screen to the user terminal 2 (step S71). The CPU 21 of the user terminal 2 displays the editing screen on the display section 26 (step S72). The user changes the planned values displayed on the edit screen using the input unit 25 as necessary. The planned value can be changed by directly inputting a numerical value or by inputting a formula. For example, when the planned value is 110, inputting =110*0.85 enables the planned value to be changed to 85% of the original value. The CPU 21 determines whether or not the planned value has been changed (step S73). When the CPU 21 determines that the planned values have been changed (YES in step S73), the screen is displayed again (step S74). At this time, other planned values linked with the changed planned value are also updated. When the CPU 21 determines that the planned value has not been changed (NO in step S73), the process proceeds to step S75. The CPU 21 determines whether or not to decide the plan (step S75). The CPU 21 determines whether or not the user has input an instruction to end the editing and decide the plan. When the CPU 21 determines not to determine the plan (NO in step S75), the process returns to step S73. When the CPU 21 determines to determine the plan (YES in step S75), it transmits the edited result to the management server 1 (step S76). The CPU 11 of the management server 1 acquires the editing result (step S77). The CPU 11 returns the process to the caller. The editing result to be sent from the user terminal 2 to the management server 1 may be a correspondence between the subject and the changed plan value only for the subject whose plan value has been changed, or all of the items including those whose plan value has not been changed. You may send the planned value of

FIG. 23 is a flow chart showing an example of the procedure of graph editing processing. The graph editing process is a process of displaying a plurality of numerical values included in the plan in a graph and editing the displayed graph to edit the created plan. The CPU 11 of the management server 1 transmits an edit screen to the user terminal 2 (step S81). The CPU 21 of the user terminal 2 displays the editing screen on the display section 26 (step S82). The user uses the input unit 25, particularly a pointing device such as a mouse or a trackpad, to operate the graph displayed on the editing screen and change the graph as necessary. The CPU 21 determines whether or not the graph has been changed (step S83). When the CPU 21 determines that the graph has not been changed (NO in step S83), the process proceeds to step S88. When the CPU 21 determines that the graph has been changed (YES in step S83), the CPU 21 acquires the graph to be changed and the content of the change (step S84). The CPU 21 converts the changed contents of the graph into numerical values (step S85). The CPU 21 changes the corresponding planned value based on the numerical value obtained by conversion (step S86). The CPU 21 displays the screen again (step S87). The CPU 21 determines whether or not to decide the plan (step S88). It is determined whether or not the user has input an instruction to finish editing and decide the plan. When the CPU 21 determines not to determine the plan (NO in step S88), the process returns to step S83. When the CPU 21 determines to determine the plan (YES in step S88), it transmits the edited result to the management server 1 (step S89). The CPU 11 of the management server 1 acquires the editing result (step S90). The CPU 11 returns the process to the caller. Editing results transmitted from the user terminal 2 to the management server 1 are the same as in direct editing.

FIG. 24 is a flow chart showing a procedure example of simulation editing processing. The simulation editing process is a process of editing a created plan assuming that a predetermined numerical value included in the plan has changed. The CPU 11 of the management server 1 transmits a setting screen to the user terminal 2 (step S101). The CPU 21 of the user terminal 2 displays the setting screen on the display section 26 (step S102). The user uses the input unit 25 to set simulation conditions. For example, increase sales by 10% from the current planned value, or decrease the variable cost ratio by 1 point from the planned value. The CPU 21 determines whether or not to determine the conditions (step S103). It is determined whether or not the user has input an instruction to end the setting and determine the conditions. If the CPU 21 determines not to determine the conditions (NO in step S103), it repeats step S103. When the CPU 21 determines to determine the conditions (YES in step S103), it transmits the setting contents of the simulation conditions to the management server 1 (step S104). The CPU 11 of the management server 1 acquires the setting content (step S105). The CPU 11 recalculates the planned values according to the set simulation conditions (step S106). The CPU 11 returns the process to the caller.

Next, screens displayed on the user terminal 2 in the above process will be described. FIG. 25 is an explanatory diagram showing an example of the creation method selection screen. The creation method selection screen d01 is a screen for selecting a method for creating a plan. The preparation method selection screen d01 includes an automatic preparation button d011 and a question preparation button d012. When the automatic creation button d011 is selected, the management server 1 creates a plan by automatic creation. When the question creation button d012 is selected, the management server 1 creates a plan by question creation.

FIG. 26 is an explanatory diagram showing an example of an automatic creation setting screen. The automatic creation setting screen d02 is a screen for performing necessary settings when automatically creating a plan. The automatic creation setting screen d02 includes an acquisition method setting d021, a period setting d022, a unit setting d023, and a creation button d024. In the acquisition method setting d021, a method for acquiring performance data is set. The acquisition method setting d021 includes an upload link d0211 and an API (Application Programming Interface) linkage link d0212. When the upload link d0211 is selected, a screen for setting a CSV (Comma-Separated Values) file to be uploaded is displayed, and the CSV file is uploaded using this screen. When the cooperation link d0212 is selected, a screen for setting API cooperation is displayed, and settings are made for obtaining performance data from the other system 4 through API cooperation. The period number setting d022 sets the number of periods for creating a plan. In the unit setting d023, the unit for creating the plan is set. A plan is created when the creation button d024 is selected. The creation button d024 is inactive and cannot be selected until a method for acquiring performance data is set by the acquisition method setting d021.

FIG. 27 is an explanatory diagram showing an example of a question answer screen. The question answer screen d03 is a screen for inputting an answer to a question presented when creating a question. The question answer screen d03 includes a first answer setting d031, a second answer setting d032, a third answer setting d033 and a next button d034. The first answer setting d031 is a pull-down menu for setting the answer to the first question. The second answer setting d032 includes a numerical input box d0321 and a unit setting menu d0322. Enter the numerical value for the answer in the numerical input box d0321. The unit setting menu d0322 sets units for numerical values. The third answer setting d033 is a pull-down menu for setting the answer to the third question. The next button d034 is a button for confirming the answer and proceeding to the next screen. One question, two questions, or four or more questions may be displayed on the question answer screen d03. What to display as an answer setting is determined according to the content of the question. The contents are stored in the logic DB 147 .

FIG. 28 is an explanatory diagram showing an example of a plan display screen. The plan display screen d04 is a screen for displaying the created management plan. The plan display screen d04 includes a plan value table d041, a decision button d042 and an edit button d043. The created planned values are displayed in the planned value table d041. The decision button d042 is a button for deciding the created plan as it is. The edit button d043 is a button for editing the created plan.

FIG. 29 is an explanatory diagram showing an example of an editing method selection screen. The editing method selection screen d05 is a screen for selecting an editing method when editing a plan automatically created or question created. The edit method selection screen d05 includes a direct edit button d051, a graph edit button d052, and a simulation edit button d053. When the user selects the direct edit button d051, the management server 1 executes direct edit processing. When the user selects the graph edit button d052, the management server 1 executes graph edit processing. When the user selects the simulation edit button d053, the management server 1 executes simulation edit processing.

FIG. 30 is an explanatory diagram showing an example of a direct edit screen. The direct editing screen d06 is a screen for directly editing the created plan. It includes a plan value table d061 and a determination button d062. The created plan values are displayed in the plan value table d061. Planned values can be changed by selecting cells in the same way as with spreadsheet software. The decision button d062 is a button for finalizing the change result and determining the plan.

FIG. 31 is an explanatory diagram showing an example of the graph editing screen. The graph edit screen d07 is a screen for editing the created plan using a graph. The graph editing screen d07 includes a planned value table d071, a planned graph d072 and a decision button d073. The created planned values are displayed in the planned value table d071. A plan graph d072 is a graphical representation of the plan value table d071. It is not necessary to graphically display all items displayed in the planned value table d071. FIG. 31 graphically displays sales, SG&A expenses (selling and general administrative expenses), and operating profit. The planned value can be changed by dragging and dropping a point on the graph with a pointing device. Changes made by the graph are reflected in the planned values in the planned value table d071. The decision button d073 is a button for finalizing the change result and determining the plan.

FIG. 32 is an explanatory diagram showing an example of a simulation editing screen. The simulation edit screen d08 is a screen for setting when the created plan is edited by simulation. The simulation edit screen d08 includes a planned value table d081, setting areas d082 to d084, and an OK button d085. The created planned values are displayed in the planned value table d081. Setting areas d082 to d084 are areas for setting simulation conditions. Sales can be set in the setting area d082. SG&A expenses can be set in the setting area d083. A variable cost ratio can be set in the setting area d084. The decision button d085 is a button for confirming the setting and starting recalculation of the planned values according to the simulation conditions.

As described above, the plan management system 100 has the following effects when creating a business plan. Since the plan is created using actual data, it is possible to create a highly accurate and realistic plan. In addition, since the plan can be created by automatic creation or question creation, even a user who is not very familiar with management can create a plan. Furthermore, since the created plan can be edited, the plan created by the plan management system 100 can be changed to a plan more in line with the user's intention. By providing a graph editing function as an editing function, the plan can be changed intuitively. By providing a simulation editing function as an editing function, it is possible to fine-tune the plan, for example, to increase sales by 5%.

Next, in the plan management system, functions that can be used by the user at the time of plan operation will be described. FIG. 33 is a flow chart showing an example of the procedure of planned operation processing. Planned operation processing is processing for providing functions related to planned operation. The CPU 11 of the management server 1 transmits a menu screen to the user terminal 2 (step S201). The user selects a function to be executed from the menu screen. User terminal 2 transmits the selected function to management server 1 . The CPU 11 acquires the selected function (step S202). The CPU 11 determines whether or not the selected function is budget/actual management (step S203). When the CPU 11 determines that the selected function is budget/actual management (YES in step S203), the CPU 11 performs budget/actual management processing (step S204). When the CPU 11 determines that the selected function is not budget/actual management (NO in step S203), it determines whether the selected function is report setting (step S205). When the CPU 11 determines that the selected function is the report setting (YES in step S205), it performs report setting processing (step S206). When the CPU 11 determines that the selected function is not the report setting (NO in step S205), it determines whether the selected function is the alert setting (step S207). When the CPU 11 determines that the selected function is the alert setting (YES in step S207), it performs alert setting processing (step S208). When the CPU 11 determines that the selected function is not the alert setting (NO in step S207), it performs prediction/recreation processing (step S209). The CPU 11 terminates the planned operation processing.

FIG. 34 is a flow chart showing an example of the procedure of budget/actual management processing. The budget/actual management processing is processing for setting the budget/actual management target and displaying the status of the management target. The CPU 11 of the management server 1 transmits the menu screen to the user terminal 2 (step S221). The CPU 21 of the user terminal 2 displays the menu screen on the display section 26 (step S222). The user uses the input unit 25 to make a menu selection. The CPU 21 transmits the menu (selection menu) selected by the user to the management server 1 (step S223). The CPU 11 acquires the selection menu (step S224). The CPU 11 determines whether or not the selection menu is set (step S225). When the CPU 11 determines that the selection menu is setting (YES in step S225), it transmits the setting screen to the user terminal 2 (step S226). The CPU 21 of the user terminal 2 displays the setting screen on the display section 26 (step S227). The user makes settings using the input unit 25 . The CPU 21 transmits the setting information to the management server 1 (step S228). The CPU 11 of the management server 1 acquires the setting information (step S229). The CPU 11 stores the setting information (step S230). The setting information is stored in the forecast/actual DB 148, for example. When the CPU 11 determines that the selection menu is not set (NO in step S225), it acquires forecast/actual data (step S231). The CPU 11 transmits a forecast/actual screen including the obtained forecast/actual data to the user terminal 2 (step 232). The CPU 11 returns the process to the caller.

FIG. 35 is a flow chart showing an example of the procedure of report setting processing. The report setting process is a process of setting the report to be created regarding the plan. The CPU 11 of the management server 1 transmits the menu screen to the user terminal 2 (step S241). The CPU 21 of the user terminal 2 displays the menu screen on the display section 26 (step S242). The user uses the input unit 25 to make a menu selection. The CPU 21 transmits the menu (selection menu) selected by the user to the management server 1 (step S243). The CPU 11 acquires the selection menu (step S244). The CPU 11 determines whether or not the selected menu is Random Creation (step S245). When the CPU 11 determines that the selected menu is not created automatically (NO in step S245), it transmits the setting screen to the user terminal 2 (step S246). The CPU 21 of the user terminal 2 displays the setting screen on the display section 26 (step S247). The user uses the input unit 25 to set the report to be created and instruct transmission to the management server 1 . The CPU 21 transmits setting information to the management server 1, such as selection of subjects to be included in the standard report, for setting the report (step S248). The CPU 11 of the management server 1 acquires the setting information (step S249). The CPU 11 stores the acquired setting information (step S250). When the CPU 11 determines that the selected menu is the omakase creation (YES in step S245), it stores information indicating omakase creation (omakase information) (step S251). The CPU 11 transmits the report setting screen to the user terminal 2 (step S252). The CPU 21 of the user terminal 2 displays the report setting screen on the display section 26 (step S253). The user uses the input unit 25 to make report settings. Report settings include report frequency, method (e-mail, SNS, pop-up), address, and the like. The CPU 21 transmits the report setting information to the management server 1 (step S254). The CPU 11 of the management server 1 acquires report setting information (step S255). The CPU 11 stores the report setting information (step S256). The CPU 11 returns the process to the caller. Setting information, automatic information, and report setting information are stored in the report DB 149, for example.

FIG. 36 is a flow chart showing an example of a procedure for alert setting processing. The alert setting process is a process for setting alerts. An alert is to warn a user when a numerical value related to a plan satisfies a predetermined condition set in advance. The CPU 11 of the management server 1 transmits the setting screen to the user terminal 2 (step S261). The CPU 21 of the user terminal 2 displays the setting screen on the display section 26 (step S262). The user uses the input unit 25 to set the alert. For example, the alert setting is to send an alert when the difference between the planned sales amount and the actual sales amount is 10% or more of the planned sales amount. The CPU 21 transmits the alert settings to the management server 1 (step S263). The CPU 11 of the management server 1 acquires the alert setting (step S264). The CPU 11 stores the alert settings in the alert DB 14A (step S265). The CPU 11 returns the process to the caller.

FIG. 37 is a flow chart showing an example of batch processing procedure. Batch processing is processing for correcting data related to forecasts and actual results. The CPU 11 of the management server 1 performs budget creation processing (step S271). The CPU 11 performs report creation processing (step S272). The CPU 11 performs alert creation processing (step 273). Batch processing is performed daily, for example.

FIG. 38 is a flow chart showing an example of the procedure for the process of creating a forecast. The forecast/actual preparation process collects forecast/actual data related to numerical values to be managed, calculates differences in the forecast/actual, and the like. The CPU 11 of the management server 1 acquires the forecast/actual setting from the forecast/actual DB 148 (step S281). The CPU 11 selects one unprocessed expected/actual setting (step S282). The CPU 11 determines whether or not it is time to execute (step S283). For example, when the budget/actual setting is set to manage the budget/actual on a monthly basis and the budget/actual for the last month has not been created, it is the execution timing. Also, if the execution time is after the closing time of the closing date, it is the execution timing. Otherwise, it is not execution timing. When the CPU 11 determines that it is not the execution timing (NO in step S283), the processing proceeds to step S287. When the CPU 11 determines that it is the execution timing (YES in step S283), it acquires the plan data and the performance data (step S284). If the target of budget/actual management is sales, the CPU 11 acquires plan data and performance data from the accounting DB 142 . The CPU 11 creates forecast data (step S285). For example, forecast/actual data is a set of planned data, actual data, and difference data between the two. The CPU 11 stores the expected/actual data in the expected/actual DB 148 (step S286). The CPU 11 determines whether or not there is an unprocessed forecast/actual setting (step S287). When the CPU 11 determines that there is an unprocessed expected/actual setting (YES in step S287), the process returns to step S282 to process the unprocessed expected/actual setting. When the CPU 11 determines that there is no unprocessed forecast/actual setting (NO in step S287), it terminates the forecast/actual creation process and returns the process to the caller.

FIG. 39 is a flow chart showing a procedure example of report creation processing. The report creation process is a process of creating and transmitting a report according to report settings. The CPU 11 of the management server 1 acquires report settings from the report DB 149 (step S291). The CPU 11 selects one unprocessed report setting (step S292). The CPU 11 determines whether or not it is time to report (step S293). For example, in the report setting, when it is set to create a report on a monthly basis, and if the report for the last month has not been created, it is the report timing. Also, if the execution time is after the closing time of the closing date, it is report timing. Otherwise, it is not time to report. When the CPU 11 determines that it is not the report timing (NO in step S293), the process proceeds to step S297. When the CPU 11 determines that it is time to report (YES in step S293), it determines whether or not the creation method is automatic creation (step S294). When the CPU 11 determines that the preparation method is not the automatic preparation (NO in step S294), it prepares a fixed form report according to the report settings (step S295). When the CPU 11 determines that the preparation method is the automatic preparation (YES in step S294), the report is prepared automatically (step S298). CPU 11 transmits the report (step S296). The CPU 11 transmits the report by a method according to the report settings of the user to be processed stored in the report DB 149 . The CPU 11 determines whether or not there is an unprocessed report setting (step S297). If the CPU 11 determines that there is an unprocessed report setting (YES in step S297), the process returns to step S292 to process the unprocessed report setting. If the CPU 11 determines that there is no unprocessed report setting (NO in step S297), it terminates the report creation process and returns the process to the caller.

In creating a standard report, the CPU 11 prepares plan data and performance data for target items each time a period elapses according to a target item selected from a plurality of items (subjects) and a period (for example, one month). get. The CPU 11 outputs a report on the target item. At that time, the CPU 11 uses the forecast/actual data created in the forecast/actual creation process.

In automatic creation, the CPU 11 calculates the degree of divergence (for example, difference value) from the actual data for each item (item) of the plan data. The CPU 11 determines a priority order for each item based on the calculated degree of divergence for each item. The CPU 11 generates a report in which each item is laid out based on the determined priority.

FIG. 40 is an explanatory diagram showing an example of the optional report creation logic. The example shown in FIG. 40 is an example of creating a report based on past performance data instead of forecast/actual data. FIG. 40 shows an example of analyzing the factors that increased the operating profit. The subject to be analyzed may be specified in advance by the user, or may be determined by the CPU 11 of the management server 1 . In the example of FIG. 40, items such as sales, cost of sales, variable cost ratio, gross profit, selling, general and administrative expenses (selling, general and administrative expenses), and operating profit have increased. The CPU 11 obtains the difference between the actual values in 2016 and 2017 for each subject. Further, the CPU 11 calculates an increase/decrease rate. The CPU 11 compares the rate of increase/decrease of each subject, and selects the subject with the largest absolute value as the subject of analysis. In the example of FIG. 40, the operating profit has the largest absolute value of the increase/decrease rate, so the CPU 11 makes the operating profit the analysis target. Next, the CPU 11 ranks the items related to the operating income in order of the absolute value of the increase/decrease rate. Here, gross profit on sales ranks first, sales amount ranks second, variable cost ratio ranks third, cost of sales ranks fourth, and selling, general and administrative expenses ranks fifth. This ranking is the order of the factors that affected the increase in operating profit. The CPU 11 lays out the display of each subject, for example, a graph, in the report to be output so that the user can see them in order of rank. As a result, the user can intuitively grasp the order of the factors that have influenced the increase in operating profit.

Actual data is used as an example here, but the same process can be performed for forecast/actual data. For example, if the operating profit for a certain month greatly exceeds the planned value, the difference between the planned value and the actual value is calculated for each item of P/L, and converted into the increase/decrease rate with respect to the planned value. Then, the order of priority can be obtained according to the magnitude of the increase/decrease rate.

FIG. 41 is a flow chart showing an example of the procedure of alert creation processing. The alert creation process is a process of creating and transmitting an alert in accordance with the alert settings when the target of planned/actual management satisfies alert conditions. The CPU 11 of the management server 1 acquires alert settings from the alert DB 14A (step S311). The CPU 11 selects one unprocessed alert setting (step S312). The CPU 11 determines whether or not it is time for an alert (step S313). For example, when an alert for sales is set and forecast data can be collected on a daily basis, every day is the timing of the alert. When forecast/actual data can only be collected on a monthly basis, the alert timing is only one day in a month. When the CPU 11 determines that it is not the alert timing (NO in step S313), the process proceeds to step S318. When the CPU 11 determines that it is time for an alert (YES in step S313), it acquires an evaluation index (step S314). An evaluation index is an index used to determine whether to send an alert. For example, actual sales figures. The CPU 11 determines whether or not the alert conditions are satisfied (step S315). When the CPU 11 determines that the alert condition is not satisfied (NO in step S315), the process proceeds to step S318. When the CPU 11 determines that the alert condition is satisfied (YES in step S315), it creates an alert (step S316). The CPU 11 transmits the created alert (step S317). The CPU 11 sends alerts in a user-specified manner included in the alert settings. The CPU 11 determines whether or not there is an unprocessed alert setting (step S318). If the CPU 11 determines that there is an unprocessed alert setting (YES in step S318), the process returns to step S312 to process the unprocessed alert setting. When the CPU 11 determines that there is no unprocessed alert setting (NO in step S318), it terminates the alert creation process and returns the process to the caller.

FIG. 42 is a flow chart showing an example of a procedure for prediction/recreation processing. The prediction/recreation process is a process of predicting changes in numerical values included in the plan, recreating the plan, and the like. The CPU 11 of the management server 1 transmits the menu screen to the user terminal 2 (step S331). The CPU 21 of the user terminal 2 displays the menu screen on the display section 26 (step S332). The user selects a menu to be executed using the input unit 25 . The CPU 21 transmits the menu (selection menu) selected by the user to the management server 1 (step S333). The CPU 11 of the management server 1 acquires the selection menu (step S334). The CPU 11 determines whether or not the selection menu is to recreate (step S335). When the CPU 11 determines that the selection menu is to recreate (YES in step S335), it transmits a method selection screen to the user terminal 2 (step S336). The CPU 21 of the user terminal 2 displays the method selection screen on the display section 26 (step S337). The user uses the input unit 25 to select a re-creation method. The CPU 21 transmits the re-creation method to the management server 1 (step S338). The CPU 11 of the management server 1 acquires the re-creation method (step S339). The CPU 11 recreates the plan according to the acquired method (step S340). The CPU 11 stores the recreated plan in the accounting DB 142 or the like (step S341). The CPU 11 moves to step S5 in FIG. The user can edit the plan recreated by the management server 1 in the same way as when the plan was created. When the CPU 11 determines that the selection menu is not to be recreated (NO in step S335), prediction is performed (step S343). For example, based on the actual monthly sales in the first quarter, the monthly sales in the second and subsequent quarters are predicted. The CPU 11 transmits the prediction result to the user terminal 2 . The CPU 11 ends the prediction/recreation process and returns the process to the caller.

FIG. 43 is an explanatory diagram showing an example of prediction logic. FIG. 43 shows an example of predicting sales from April 2018 onward based on actual sales from January to March 2018. The unit of sales is, for example, 10,000 yen. The upper part of FIG. 43 shows a method of obtaining a seasonal variation index for each month from sales for each month in the three years before prediction (2015 to 2017). The seasonal variation index is the ratio of each month's sales to annual sales expressed as a percentage. In the lower part of FIG. 43, annual sales are predicted from the monthly sales from January to March and from the seasonal fluctuation index from January to March. With January sales of 1,300 and a January seasonality index of 9.3%, the projected sales are 13,919. Annual sales are 13,283 from sales in February, and 14,311 from sales in March. Furthermore, the average value of the predicted annual sales is used as the final predicted value of the annual sales. Here, the average value of 13,838 of the values of 13,919, 13,283, and 14,311 is the final predicted annual sales. Based on this value and the seasonal variation index for each month from April onwards, the predicted value of sales for each month is obtained. The middle part of FIG. 43 shows the final prediction result. Cost of sales, SG&A expenses, ordinary income, etc. can also be predicted using the same method used for sales. Furthermore, by predicting the B/S, it is possible to predict the tax amount and cash balance at the end of the term. From these forecast figures, it is possible to decide whether to make capital investments toward the end of the term or to refrain from making investments that were originally planned.

Next, screens displayed on the user terminal 2 in the above process will be described. FIG. 44 is an explanatory diagram showing an example of the operation menu screen. The operation menu screen d09 is a screen for selecting a function to be executed among the functions related to planning and operation. The operation menu screen d09 includes a budget/actual management button d091, a report setting button d092, an alert setting button d093, and a prediction/recreation button d094. The budget/actual management button d091 is a button for executing budget/actual management processing. The report setting button d092 is a button for executing report setting processing. The alert setting button d093 is a button for executing alert setting processing. The prediction/recreation button d094 is a button for executing prediction/recreation processing.

FIG. 45 is an explanatory diagram showing an example of the budget/actual management menu screen. The budget/actual management menu screen d10 is a screen for selecting a function to be executed among functions related to budget/actual. The budget/actual management menu screen d10 includes a setting button d101 and a reference button d102. The setting button d101 is a button for setting targets for budget/actual management. The reference button d102 is a button for referring to the forecast/actual situation.

FIG. 46 is an explanatory diagram showing an example of a budget/actual management setting screen. The budget/actual management setting screen d11 is a screen for setting the budget/actual management target. The budget/actual management setting screen d11 includes a first setting area d111, a second setting area d112, an add button d113, and an enter button d114. The first setting area d111 includes an index selection menu d1111 and a timing menu d1112. The second setting area d112 includes an index selection menu d1121 and a timing menu d1122. The index selection menu d1111 and the index selection menu d1121 are menus for selecting an index to be subject to budget/actual management. The timing menu d1112 and the timing menu d1122 are menus for setting the unit of management. The add button d113 is used when three or more targets for budget/actual management are set. When the add button d113 is operated, a setting area is additionally displayed. The decision button d114 is a button for deciding the setting contents.

FIG. 47 is an explanatory diagram showing an example of the forecast/actual situation display screen. The forecast/actual status display screen d12 is a screen for displaying the forecast/actual status. The forecast/actual status display screen d12 includes a selection menu d121, management contents d122, an forecast/actual table d123, and a close button d124. The selection menu d121 is a menu for selecting management targets to be displayed. The management content d122 displays the content of budget and actual management. The forecast/actual table d123 shows the forecast/actual situation in a table. The close button d124 closes the forecast/actual status display screen d12. If the units are the same for multiple managed objects, they may be displayed collectively. For example, if sales are managed on a monthly basis and operating profits are also managed on a monthly basis, they may be displayed in one forecast table d123 instead of being displayed individually.

FIG. 48 is an explanatory diagram showing an example of the report selection screen. The report selection screen d13 is a screen for selecting a report to be created. The report selection screen d13 includes a standard report creation button d131, an auto report button d132, and a close button d133. The standard report creation button d131 is a button for making settings for creating a standard report. The auto report button d132 is a button for auto creating a report. The close button d133 is a button for closing the report selection screen.

FIG. 49 is an explanatory diagram showing an example of a standard report setting screen. The standard report setting screen d14 is a screen for setting the contents of the standard report. The standard report setting screen d14 includes an item setting table d141 and an OK button d142. The item setting table d141 has a display similar to that of spreadsheet software. The user uses the input unit 25 to set subjects, etc., to be displayed in the report, in the item setting table d141. The content to be entered is selected and entered from the pull-down menu. or typed by the user. In this case, pattern matching is performed on the input character string, and input of character strings other than those registered in advance is prohibited. The decision button d142 is a button for deciding the setting contents. In the example shown in FIG. 49, for sales and SG&A expenses, monthly planned values, actual values, and difference values between the planned and actual values are displayed. , the cumulative plan value, cumulative actual value, and cumulative difference value up to the current month are set to be displayed in a table.

FIG. 50 is an explanatory diagram showing an example of a report setting screen. The report setting screen d15 is a screen for setting the destination of the report. The report setting screen d15 includes a first setting area d151, a second setting area d152, an add button d153 and an enter button d154. A first setting area d151 and a second setting area d152 are areas for setting a report destination. The first setting area d151 includes a frequency menu d1511, a method menu d1512 and an address box d1513. The frequency menu d1511 sets the frequency of reporting. Method menu d1512 sets the reporting method. Enter the address of the report in the address box d1513. If the reporting method is e-mail, enter the mail address. If the reporting method is message service, enter the ID. The second setting area d152 includes frequency menus d1521 and d1522, method menu d1523 and address box d1524. Frequency menus d1521 and d1522 are for inputting the frequency of reporting. Here, a case is shown in which two parameters are input as frequencies such as 5:00 pm every day. The method menu d1523 and address box d1524 are similar to the method menu d1512 and address box d1513, respectively. The add button d153 is used when three or more report destinations are set. When the add button d153 is operated, a setting area is additionally displayed. The decision button d154 is a button for deciding the setting contents.

FIG. 51 is an explanatory diagram showing an example of the auto report. As shown in FIG. 51, graphs of management-related indices are displayed in order of priority. If each graph shown in FIG. 51 is displayed on a screen, one graph is displayed on one screen. In paper documents, one graph is printed on one page. As a result, the user can appropriately grasp the indexes that have influenced management.

FIG. 52 is an explanatory diagram showing an example of an alert setting screen. The alert setting screen d16 is a screen for setting alert conditions. The alert setting screen d16 includes an index menu d161, a threshold box d162, a unit menu d163, a method menu d164, an address box d165, an add button d166 and an enter button d167. An index to be monitored is set in the index menu d161. In the threshold box d162, enter a threshold that is used as a reference when determining whether or not to generate an alert. A threshold unit is selected in the unit menu d163. The method menu d164 stores the alert notification method. Enter the alert notification destination in the address box d165. The add button d166 is a button used when adding an alert condition. The decision button d167 is a button for deciding alert settings.

FIG. 53 is an explanatory diagram showing an example of the prediction/recreation menu screen. The prediction/recreation menu screen d17 is a screen for selecting execution of either prediction or recreation. The prediction/recreation menu screen d17 includes a recreate button d171, a prediction button d172, and a close button d173. The recreate button d171 is a button for recreating the plan. The prediction button d172 is a button for predicting sales and the like. The close button d173 is a button for closing the prediction/recreation menu screen d17.

FIG. 54 is an explanatory diagram showing an example of a regeneration method selection screen. The re-creation method selection screen d18 is a screen for selecting a method for re-creating the plan. The regeneration method selection screen d18 includes an automatic creation button d181, a direct input creation button d182, a graph edit creation button d183, a simulation button creation d184, and a close button d185. The automatic creation button d181 is a button for recreating by automatic creation. The direct input creation button d182 is a button for recreating by direct input. The graph editing creation button d183 is a button for recreating the graph by manipulating the graph. Simulation button creation d184 is a button for recreating by simulation. In either method, re-creation is performed by processing similar to plan editing in plan creation. The close button d185 is a button for closing the regeneration method selection screen d18.

As described above, the plan management system 100 has the following effects when operating the management plan. Since it is possible to create a report of forecast/actual management, it is possible to quickly take a countermeasure when there is a large discrepancy between forecast and actual. If there is no effective workaround, it will be possible to recreate the plan. It is also possible to receive an alert when there is a large divergence between forecast and actual. In particular, setting alerts for indicators that have a large impact on the business situation, and setting the alert creation cycle to be shorter than the report creation cycle, makes it possible to respond more quickly. In addition, since it is possible to predict the situation at the end of the term in the middle of the term, it is also possible to take additional measures in anticipation of the situation at the end of the term.

The forecast/actual status display screen d12 may display an advice message according to the forecast/actual status or an advertisement corresponding to the content of the advice. Similarly, alert messages may include advisory messages and advertisements.

FIG. 55 is an explanatory diagram showing an example of an advice DB. The advice DB 14B is stored, for example, in the large-capacity storage unit 14 of the management server 1. FIG. The advice DB 14B stores advice to be displayed on the forecast/actual situation display screen d12 and advice to be added to alerts. The advice DB 14B includes an advice ID column, an evaluation index column, a condition column and an advice column. The advice ID column stores advice IDs that can uniquely identify advice. The evaluation index column stores indexes (subject names) corresponding to advice. The condition column stores conditions for adding advice. The advice column stores advice to display or send.

FIG. 56 is an explanatory diagram showing an example of an advertisement DB. The advertisement DB 14C is stored in the mass storage unit 14 of the management server 1, for example. Advertisement DB 14C stores advertisements to be displayed or transmitted together with advice. Advertisement DB 14C includes an advertisement ID column, an advice ID column, a text column and a link column. The advertisement ID column stores advertisement IDs that can uniquely identify advertisements. The advice ID column stores corresponding advice IDs. A text column stores the text of the advertisement. A link column stores hyperlinks that you embed in the text. A hyperlink is a URL (Uniform Resource Locator) of a home page that describes the advertised product or service in detail.

FIG. 57 is a flow chart showing another procedure example of the forecast creation process and the alert creation process. FIG. 57A shows another procedure example of the budget creation process. FIG. 57B shows another procedure example of alert creation processing. Figures 57A and 57B show a portion of the flow chart. As shown in FIG. 57A, in the forecast/actual preparation process, processes are added to the procedures in FIG. 38, and some of the processes are changed. In the forecast/actual creation process, the CPU 11 of the management server 1 selects advice (step S288) after executing forecast/actual data creation (step S285). Specifically, the CPU 11 compares the created forecast/actual data with the evaluation index column and the situation column of the advice DB 14B, and the forecast/actual data includes an evaluation index that matches the conditions defined in the evaluation index column and the situation column. Determine if the When the CPU 11 determines that there is an evaluation index that matches the conditions, it selects corresponding advice. The CPU 11 selects an advertisement corresponding to the selected advice (step S289). Specifically, the CPU 11 searches the advertisement DB 14C using the advice ID of the selected advice as a search key. If multiple advertisements hit the search, select at random, for example. The CPU 11 stores the selected advice and advertisement together with the created projected/actual data (step S286). The CPU 11 executes steps from step S287.

As shown in FIG. 57B, in the alert creation process, processes are added to the procedures in FIG. 41, and some of the processes are changed. In the alert creation process, the CPU 11 of the management server 1 selects advice (step S319) after executing alert creation (step S316). Specifically, the CPU 11 determines whether the conditions for creating an alert satisfy the conditions defined in the evaluation index column and the status column of the advice DB 14B. When the CPU 11 determines that the conditions are met, it selects advice corresponding to the conditions. The CPU 11 selects an advertisement corresponding to the selected advice (step S320). Step S320 is similar to step S89 described above. The selected advice and advertisements are sent along with the generated alert (step S317). The CPU 11 executes steps after step S318.

In the case of the Random Report, the advice can be selected based on the subject to be analyzed and the subject that influenced the subject to be analyzed. Advertisements are then selected based on the selected advice.

FIG. 58 is an explanatory diagram showing an example of a cooperation setting screen. The linkage setting screen d19 is a screen for setting data linkage with the other system 4 . The cooperation setting screen d119 includes an accounting selection menu d191, a POS selection menu d192, an attendance selection menu d193, a reservation selection menu d194, a word-of-mouth site entry field d195, and a cooperation button d196. The accounting selection menu d191 is a pull-down menu for selecting an accounting system to be linked. The POS selection menu d192 is a pull-down menu for selecting a POS system to be linked. The attendance selection menu d193 is a pull-down menu for selecting the attendance system to be linked. The reservation selection menu d194 is a pull-down menu for selecting a reservation system to be linked. The word-of-mouth site input field d195 is for inputting the URL of the word-of-mouth site to be linked. When the cooperation button d196 is clicked with the mouse, the cooperation setting is stored.

According to the cooperation setting screen d19, the management server 1 acquires user data held by various cloud services at any time by API cooperation. The acquired data is stored in the database of the large-capacity storage unit 14 . Various cloud services include a reservation management service, a POS (Point Of Sale) service, an attendance management service, an accounting service, a salary processing service, and an order management service. The cloud service desirably transmits the contents to the management server 1 each time the user data is updated. If that is difficult, the management server 1 polls the cloud service.

FIG. 59 is an explanatory diagram showing the multi-CSV upload function. The CSV here is a collection of a plurality of subjects (indexes) in one file. Each line is one subject. FIG. 59A is an example of converting CSV in which the values are arranged in the same order in each row, but the number of rows of subjects is different. In both the CSV format 561 of company X and the CSV format 562 of the company, each line is "subject, amount, date and time, remarks". However, the second line of Company X is "sales discount", while the second line of our company is "cost of sales". “Cost of sales” is the fourth line for Company X. Similarly, "labor cost" is on the 9th line for Company X and on the 3rd line for our company. In such a case, the conversion logic 563 is prepared as data for conversion and stored in the large-capacity storage unit 14 . As with the conversion logic 563, by preparing the conversion logic 563 in which the 4th line of company X corresponds to the 2nd line of the company and the 9th line of company X corresponds to the 3rd line of the company, It is possible to convert the CSV file of the company into the company's CSV file. If the company's own CSV format and conversion logic 563 are registered in the management server 1, for example, plan data exported from the company's sales system and performance data exported from X company's POS system can be uploaded to the management server 1. It is possible to manage sales forecasts and actual sales.

FIG. 59B is an example of converting CSV in which the number of rows in which items appear is the same, but the order of values in each row is different. Both the CSV format 564 of Company Y and the CSV format 565 of the company have the same order of rows, such as "Sales" in the first row and "Cost of sales" in the second row. However, each line of Company Y has a sequence of "Sales, Date, Time, Amount, Remarks", while each line of its own company has a sequence of "Sales, Amount, Date, Remarks". In such a case, the conversion logic 566 is prepared as data for conversion and stored in the large-capacity storage unit 14 . As in the conversion logic 566, by preparing the conversion logic 566 in which the second (B column) value in each row of company Y corresponds to the third (C column) value in each row of our own company, Y It is possible to convert the company's CSV file into the company's own CSV file. If the company's CSV format and conversion logic 566 are registered in the management server 1, for example, plan data exported from the company's procurement system and performance data exported from Y's purchasing system can be uploaded to the management server 1. It is possible to manage the cost of sales forecast and actual.

Further, the following additional remarks are disclosed with respect to the above embodiment.

(Appendix 1)
Acquire performance data of multiple items related to management,
Get a period to create a business plan,
create a management plan for the period based on the performance data;
Output the created management plan,
Acquiring performance data corresponding to the management plan after a predetermined period has elapsed after the start of the period in which the management plan was created,
A plan creation and operation program that causes a computer to output a report based on the management plan data and the performance data.

(Appendix 2)
The plan creation operation program according to appendix 1, wherein the management plan includes graph data that can be displayed as a graph.

(Appendix 3)
The plan creation operation program according to appendix 1 or appendix 2, wherein the report includes graph data that can be displayed graphically.

The technical features (components) described in each embodiment can be combined with each other, and new technical features can be formed by combining them.
The embodiments disclosed this time are illustrative in all respects and should not be considered restrictive. The scope of the present invention is indicated by the scope of the claims rather than the above-described meaning, and is intended to include all modifications within the scope and meaning equivalent to the scope of the claims.

100 plan management system 1 management server 11 CPU
12 ROMs
13 RAM
14 Large capacity storage unit 141 User DB
142 Accounting DB
143 Reservation DB
145 Attendance DB
146 Order DB
147 Logic DB
148 Forecast DB
149 Report DB
14A Alert DB
15 communication unit 16 reading unit 1P control program 1a portable storage medium 1b semiconductor memory 2 user terminal 21 CPU
22 ROMs
23 RAM
24 communication unit 25 input unit 26 display unit 27 mass storage unit 2P control program 3 administrator terminal 4 other system

Claims (7)

Get performance data for multiple items , including sales, profits, or cash balances ,
Get a period to create a business plan,
outputting a question to select and answer the probability of change for said item from a past period corresponding to said period ;
obtaining selection information of the likelihood of variation for the question;
Acquiring calculation logic that is associated with the acquired selection information and includes a coefficient that converts the probability of variation;
Based on the acquired calculation logic, calculate the planned value of the item from the actual data,
A plan creation program for causing a computer to perform a process of creating a management plan for the period based on the calculated plan values. Acquiring the performance data for each unit period with the period as a unit,
2. The plan creation program according to claim 1, wherein the business plan is created based on the performance data for a plurality of continuous unit periods. 3. The plan creation program according to claim 2 , wherein it is specified whether or not to create the management plan based on the performance data of the plurality of unit periods. 4. The plan creation program according to any one of claims 1 to 3, wherein the planned values of sales, profit, or cash balance calculated based on the calculation logic are editable. the performance data is obtained from another computer different from the computer;
The plan creation program according to any one of claims 1 to 4, wherein the obtained performance data is converted into a common data format. a first acquisition unit that acquires performance data of a plurality of items including sales, profit, or cash balance ;
a second acquisition unit that acquires a period for creating a plan;
a first output unit for outputting a question for selecting and answering the expected change of the item from the past period corresponding to the period ;
a third acquisition unit that acquires selection information of the variation prospect for the question;
a fourth acquisition unit that acquires calculation logic associated with the acquired selection information and that includes a coefficient obtained by converting the expected fluctuation;
A plan creation device, comprising: a creation unit that calculates planned values of the items from the actual data based on the obtained calculation logic, and creates a management plan for the period based on the calculated planned values. the computer
Get performance data for multiple items , including sales, profits, or cash balances ,
Get the period to create the plan,
outputting a question to select and answer the probability of change for said item from a past period corresponding to said period ;
obtaining selection information of the likelihood of variation for the question;
Acquiring calculation logic that is associated with the acquired selection information and includes a coefficient that converts the probability of variation;
A method of creating a plan, comprising: calculating a planned value of the item from the actual data based on the acquired calculation logic; and creating a management plan for the period based on the calculated planned value.

Images