JP2017117200A - Information processor, control method and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an information processor, a control method and a program capable of carrying out need prediction for merchandise, etc., with good accuracy.SOLUTION: A demand prediction is set for after an established period by setting a merchandise to be object of demand prediction by using a merchandise information setting screen and using a sales plan value for the period for which the sales plan is established for that merchandise. A result of carrying out a demand prediction from the past demand performance is displayed to a sales plan input screen 400. A user reviews a demand prediction value based on a sales plan value the user grasps or input from an outside system for the established period and inputs the sales plan value to an input column 401 when there is a need to correct the demand prediction value. A demand prediction value is calculated by carrying out a demand prediction again for after the established period by using the sales plan value.SELECTED DRAWING: Figure 12

Description

  The present invention relates to a technique for predicting demand for goods and the like.

As for the demand forecast calculated from the past demand record, the accuracy of the demand forecast is higher as it is closest, and the accuracy of the forecast is lower as it is earlier.

  The present invention relates to an information processing apparatus and information capable of making an appropriate prediction for a previous prediction in which the prediction accuracy is lowered by utilizing a latest sales (sales) plan for a demand prediction calculated from a past demand record. It relates to the processing method.

  Usually, when making a demand prediction for a product or the like, a prediction for this month (this week) or later is made based on a past demand record up to the previous month (previous week) (see, for example, Patent Document 1).

JP 2007-293623 A

  However, the accuracy of demand prediction is higher in the most recent month (week), and the accuracy of prediction is lower the earlier.

  This is because if the previous market environment is different from the current situation, the previous demand trend cannot be properly grasped from the past demand record.

  On the other hand, there is a case where a sales (sales) plan is made using the demand prediction, and this plan is made by human purchase work based on the demand prediction.

  Further, in the sales (sales) plan, in a monthly / weekly operation, for example, the plan for the next month is generally determined by, for example, the 20th of every month, so that a certain period is determined.

  The plan for the fixed period is used as input information for production plans and order plans for subsequent operations, and the sales (sales) plan after the fixed period is used for load adjustment of the production line, material procurement plan, personnel plan, budget management, etc. In many cases.

  Therefore, generally, a sales plan for a fixed period has a high accuracy of demand forecast as a base, and the information on the latest market trends and the like is taken into consideration by humans, so the planning accuracy is also high.

  However, the sales plan after the fixed period has a low accuracy of the basic demand forecast, and further, it is impossible to accurately grasp the previous factors that affect the demand, so the planning accuracy is low and it may affect the subsequent related operations. Have sex

  As described above, when the future market environment is different from the current situation, it is difficult to properly grasp the future demand trend from the past demand results, and thus there is a possibility that it cannot be predicted appropriately.

  In addition, for new products that have no past demand record, for example, there are cases where the sales plan for the next several months is planned using a separate system before the release, but the future forecast results are necessary for future material procurement, etc. It may become.

  The present invention has been made in view of such problems, and an object of the present invention is to provide an information processing apparatus, a control method, and a program capable of accurately predicting demand for goods and the like.

  The invention for solving the above-mentioned problems is an information processing apparatus that performs demand prediction for products,

  A forecasting means for forecasting demand using actual demand; a receiving means for accepting an input of a sales plan value for an arbitrary period; and the forecasting means for the sales plan in an arbitrary period for which the input is accepted by the accepting means Demand prediction after the arbitrary period is performed using the value as the demand record.

  According to the present invention, it is possible to accurately predict demand for products and the like by performing demand prediction for products and the like by using a determined sales plan.

It is a block diagram which shows the function structure of a demand prediction calculation apparatus. It is a block diagram which shows schematic structure of the hardware of the information processing apparatus applicable to a demand prediction calculation apparatus. It is a flowchart which shows a demand prediction process. It is a block diagram which shows the structure of merchandise information DB. It is a block diagram which shows the structure of demand performance DB103. It is a block diagram which shows the structure of prediction model information DB. It is a block diagram which shows the structure of prediction result DB. It is a block diagram which shows the structure of prediction re-execution result DB. It is a block diagram which shows the structure of sales plan DB. It is a block diagram which shows the structure of a merchandise information setting screen. It is a flowchart which shows the detail of a prediction execution process. It is a block diagram which shows the structure of a sales plan input screen. It is a flowchart which shows the detail of prediction re-execution determination processing. It is explanatory drawing for demonstrating an example of a cumulative sales plan error (rate). It is explanatory drawing for demonstrating an example of a cumulative demand prediction error (rate). It is explanatory drawing for demonstrating the example where the precision of the sales plan in a fixed period is favorable, but the demand forecast using a sales plan value becomes invalid. It is a flowchart which shows the detail of a prediction re-execution process. It is explanatory drawing for demonstrating that the demand forecast after the fixed period was performed using the sales plan value. It is a block diagram which shows the structure of a sales plan input screen.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings.

  FIG. 1 is a configuration diagram illustrating an example of a functional configuration of a demand prediction calculation device 100 that is an example of an information processing device (computer).

  As shown in FIG. 1, the demand prediction calculation device 100 according to the present embodiment includes a storage unit 101 for storing data required for processing executed by the demand prediction calculation device 100, and a product information setting unit. 108, a prediction execution unit 109, a sales plan input unit 110, a prediction re-execution determination unit 111, a prediction re-execution unit 112, and a prediction result confirmation unit 113.

  The storage unit 101 includes a product information DB 102, a demand result DB 103, a prediction model information DB 104, a prediction result DB 105, a prediction re-execution result DB 106, and a sales plan DB 107.

  The merchandise information DB 102 stores merchandise information related to merchandise. For example, as shown in FIG. 4, a merchandise code, a merchandise name, a fixed period, a cycle, whether a sales plan is used, a prediction re-execution determination flag, an error evaluation period The database includes items such as a prediction error cumulative period and a sales plan error threshold.

  The product information is registered in the product information DB 102 by setting the product information in the product information setting unit 108. The setting of product information will be described later.

  The demand result DB 103 stores the past demand result values for each product and each day, and includes items such as a product code, a date when the product is in demand, and a demand result, for example, as shown in FIG. Database.

  The prediction model information DB 104 stores various predictable prediction models (for example, moving average, exponential smoothing, etc.). For example, as shown in FIG. 6, prediction models and predictions indicating parameters used in the prediction models are stored. This is a database having items such as model parameter 1, prediction model parameter 2,.

  The prediction result DB 105 stores the result of the product demand prediction. For example, as shown in FIG. 7, the product code, the prediction calculation start date, the demand prediction value 1, the demand prediction value 2, the demand prediction value. 3 is a database having items such as.

  As the results of these predictions, the results of demand prediction executed in the prediction execution unit 109 are stored. Details of the demand prediction executed by the prediction execution unit 109 will be described later.

  The forecast calculation start date means the cycle start date on which the forecast execution unit 109 performs the demand forecast calculation.

  The cycle means a unit for calculating the demand forecast. For example, when a forecast value in units of months (weeks) is required, the cycle start date is the first day of the month (week).

  As an example, if the prediction calculation execution date is October 4, 2015 and the prediction unit is the month, the prediction calculation start date is October 1, 2015.

  Moreover, the demand forecast value stores the calculated value for the forecast calculation period for each cycle from the forecast calculation start date.

  As an example, if the forecast start date is October 1, 2015 and the cycle is a month, the demand forecast value 1 is the demand forecast value in October, the demand forecast value 2 is November, and the demand forecast value 3 is December. Stores the demand forecast value.

  The prediction re-execution result DB 106 stores the result of recalculating the demand prediction using the sales plan value in the confirmed sales plan. For example, as shown in FIG. 8, the product code, the fixed period, the prediction The database includes items such as a calculation start date, a demand forecast value 1, a demand forecast value 2, a demand forecast value 3,.

  As a result of recalculating the demand forecast using these sales plan values, the result of the demand forecast executed in the forecast re-execution unit 112 is stored. Details of the recalculation of the demand forecast executed by the forecast re-execution unit 112 will be described later.

  The forecast calculation start date means the cycle start date on the day when the forecast re-execution unit 112 performs the demand forecast re-calculation.

  The demand forecast value stores a calculation value for each cycle ahead of the fixed period for the forecast calculation period.

  As an example, if the forecast start date is October 1, 2015 and the forecast value is monthly, and the fixed period is 1 (month), the demand forecast value 1 is not stored, and the demand forecast value 2 is November. The demand forecast value 3 stores the demand forecast value for December.

  The sales plan DB 107 stores information related to the sales plan of the product. For example, as shown in FIG. 9, the product code, the sales plan start date, the sales plan value 1, the sales plan value 2, the sales plan value 3 This is a database with items such as.

  As information related to these sales plans, information input by the sales plan input unit 110 and information taken from an external system are stored. The sales plan input unit 110 will be described later.

  The sales plan start date means a cycle start date on the date when the sales plan is confirmed by taking the sales plan from the sales plan input unit 110 or an external system.

  For example, when a monthly sales plan value is required, the cycle start date is the first day of the month (week).

  As an example, if the final date of the sales plan is October 5, 2015 and the sales plan unit is the month, the starting date of the sales plan is October 1, 2015.

  The sales plan value stores the sales plan value for a fixed period for each cycle.

  As an example, if the sales plan start date is October 1, 2015, the fixed period is 2 (months), and the cycle is a month, the sales plan value 1 is the sales plan value for October, the sales plan value 2 is Stores the November sales plan value.

  FIG. 2 is a diagram illustrating an example of a hardware configuration of the demand prediction calculation device 100.

  In FIG. 2, reference numeral 201 denotes a CPU that comprehensively controls each device and controller connected to the system bus 204.

  Further, the ROM 202 or the external memory 211 is necessary to realize a BIOS (Basic Input / Output System) or an operating system program (hereinafter referred to as an OS), which is a control program of the CPU 201, or a function executed by each server or each PC. Various programs to be described later are stored.

  A RAM 203 functions as a main memory, work area, and the like for the CPU 201. The CPU 201 implements various operations by loading a program or the like necessary for execution of processing from the ROM 202 or the external memory 211 into the RAM 203 and executing the loaded program.

  An input controller 205 controls input from a keyboard (KB) 209 or a pointing device such as a mouse (not shown). A video controller 206 controls display on a display device such as a CRT display (CRT) 210. In FIG. 2, although described as CRT 210, the display device is not limited to the CRT, but may be another display device such as a liquid crystal display. These are used by the administrator as needed.

  A memory controller 207 is connected via an adapter to a hard disk (HD), flexible disk (FD), or PCMCIA card slot for storing a boot program, various applications, font data, user files, editing files, various data, and the like. The access to the external memory 211 such as a compact flash (registered trademark) memory is controlled.

  A communication I / F controller 208 is connected to and communicates with an external device via a network (for example, the LAN 600 shown in FIG. 1), and executes communication control processing on the network. For example, communication using TCP / IP is possible.

  Note that the CPU 201 enables display on the CRT 210 by executing outline font rasterization processing on a display information area in the RAM 203, for example. In addition, the CPU 201 enables a user instruction with a mouse cursor (not shown) on the CRT 210.

  Various programs to be described later for realizing the present invention are recorded in the external memory 211 and executed by the CPU 201 by being loaded into the RAM 203 as necessary.

  Furthermore, definition files and various information tables used when executing the program are also stored in the external memory 211, and a detailed description thereof will be described later.

  FIG. 3 is a flowchart illustrating an example of a demand prediction process executed by the demand prediction calculation apparatus 100.

  In this demand prediction process, the computer recorded in the external memory 211 or the like is connected to each function unit (product information setting unit 108, prediction execution unit 109, sales plan input unit 110, and prediction re-execution determination unit shown in FIG. 111, the prediction re-execution unit 112, and the prediction result confirmation unit 113) are performed by the CPU 201 according to control of a program for causing the computer to function.

  In step S101, the merchandise information setting unit 108 sets merchandise information necessary for demand forecast of merchandise.

  At this time, the product information setting unit 108 displays a product information setting screen 300 as shown in FIG. 10 on the CRT 210 to prompt the user to input.

  Then, the product information setting unit 108 receives information input via the product information setting screen 300.

  Note that the user sets, for the setting of each item on the product information setting screen 300, product information for which demand prediction is to be performed, in the product information setting area 301.

  In the product information setting area 301, a product code, a product name, a fixed period, a cycle, whether or not a sales plan is used, a prediction re-execution determination flag, an error evaluation period, a prediction error cumulative period, a sales plan error threshold, and the like are set.

  This fixed period means an arbitrary period in which the sales plan is used, and the forecast re-execution unit 112 uses the sales plan for the fixed period from the current month (current week) when the demand forecast is recalculated. Is recalculated.

  A cycle means a unit for calculating a demand forecast. For example, when the cycle is a month, the predicted value is calculated on a monthly basis, and when the cycle is a week, the predicted value is calculated on a weekly basis.

  The cycle depends on whether the sales plan is monthly or weekly, but the cycle is not necessarily monthly or weekly.

  If the sales plan is a daily unit, the cycle can be a day, and a planning unit for the sales plan may be set.

  Whether or not the sales plan is used means whether or not to perform the prediction calculation using the sales plan value determined in the sales plan. When the sales plan is not used, only the forecast calculation from the actual demand is performed.

  The prediction re-execution determination flag is valid only when the sales plan is used or not, and indicates whether or not to determine the effectiveness of the prediction calculation using the sales plan value.

  When the prediction re-execution determination flag is N, the prediction re-execution is performed using the sales plan, and when the determination flag is Y, the prediction re-execution using the sales plan is determined based on the validity.

  The error evaluation period, the prediction error cumulative period, and the sales plan error threshold are valid only when the prediction re-execution determination flag is Y, and are parameters necessary for error calculation described later. The error evaluation period, the prediction error cumulative period, and the sales plan error threshold will be described later.

  When it is desired to add product information to the product information setting area 301, when an add button 302 is pressed, one blank record is added to the product information setting area 301, and product information is set in this record.

  To delete the product information displayed in the product information setting area 301, when the delete button 303 is pressed while the product information to be deleted is selected, the product information is deleted and hidden from the product information setting area 301. .

  When the product information displayed in the product information setting area 301 is stored, when the save button 304 is pressed, the product information displayed in the product information setting area 301 is stored in the product information DB 102 and the product information setting screen 300 is displayed. In the case of closing, the close button 305 is pressed.

  Returning to the description of FIG. 3 again, in step S302, the forecast execution unit 109 acquires the demand record of the forecast target product in the demand record DB 103 for the product registered in the product information DB 102, and calculates the forecast quantity. calculate.

  In step S102, the product registered in the product information DB 102 is a processing target.

  FIG. 11 is a flowchart for explaining details of the prediction execution processing in step S102.

  In step S201, the cycle of the predicted product is acquired from the product information DB 102, the actual demand up to the previous month (previous week) of the predicted product is acquired from the demand actual DB 103, and the actual demand is totaled according to the cycle.

  In step S202, the demand forecast quantity after the current month (the current week) of the forecasted product is calculated from the demand record totaled in step S201 and the mathematical forecast model registered in the forecast model information DB 104. The demand forecast quantity calculated at this time is registered in the forecast result DB 105.

  In step S203, the process ends when the demand prediction calculation of all the products is completed, and when there is an uncalculated product, the process returns to step S201.

  Returning to the description of FIG. 3 again, in step S103, the demand forecast value of the product calculated in step S102 from the prediction result DB 105 is displayed on the sales plan input screen 400 to prompt the input of the sales plan.

  FIG. 12 shows an example of the configuration of the sales plan input screen 400. In addition to displaying the calculated demand forecast value on the sales plan input screen 400, the past demand record acquired from the demand record DB 103 is also displayed so that the validity of the demand forecast value can be verified.

  In addition, regarding the sales plan input field 401, it is possible to avoid omissions in the sales plan by displaying the demand forecast value as a default display.

  The sales plan DB 107 is not limited to registration in this step as long as it is information equivalent to the sales plan, and any method may be used.

  When the information input in the input field 401 is stored, when the save button 402 is pressed, the input information is registered in the sales plan DB 107. When the sales plan input screen 400 is closed, the close button 403 is pressed.

  For example, when there is unlisted information from a business partner or when a sales plan is created by another system, it becomes a target of subsequent processing by registering in advance in the sales plan DB 107.

  Returning to the description of FIG. 3 again, in step S104, the prediction re-execution determination unit 111 is in the demand result and prediction result DB 105 of the prediction target product in the demand result DB 103 for the product registered in the product information DB 102. Demand forecast value, demand forecast value in forecast re-execution result DB 106, and sales plan value registered in sales plan DB 107 are acquired, and forecast re-execution using the sales plan from the error between demand forecast value and sales plan value It is determined whether or not to perform.

  That is, the judgment whether the market trend inferred from the sales plan in the fixed period should be taken into consideration is judged from the past actual situation.

  FIG. 13 is a flowchart for explaining details of the prediction re-execution determination process in step S104.

  In step S301, it is determined whether or not the sales plan use of the product information of the predicted product is present, the prediction re-execution determination flag is Y, and the determination period is greater than zero. That is, it is determined whether prediction using the sales plan value is possible.

  If the above condition is satisfied, the process proceeds to step S302. If the condition is not satisfied, the process proceeds to step S307. Note that the presence / absence of the sales plan for the predicted product, the prediction re-execution determination flag, and the fixed period are registered in the product information DB 102.

  In step S302, the actual demand demand for the forecasted product for a certain period in the past is obtained from the demand performance DB 103, the past sales plan value for the forecasted product is obtained from the sales plan DB 107, and the cumulative sales plan error for the fixed period is calculated.

There are various error calculation methods, but the error calculation method is not particularly defined as long as it represents the difference between the sales plan value and the actual demand. As an example, the calculation is performed using a calculation formula such as [Formula 1] as follows.
[Formula 1]

  FIG. 14 shows an example of the cumulative sales plan error (rate). Note that a certain past period is registered in the product information DB 102 as an error evaluation period.

  In step S303, if the sales plan error calculated in step S302 is less than or equal to the threshold value, it is determined that the accuracy of the sales plan is good, and the process proceeds to step S303. If the sales plan error is greater than the threshold value, the sales plan value is regarded as the actual demand. The prediction re-execution process that has been performed is determined to be impossible, and the process proceeds to step S307. The threshold is registered in the product information DB 102 as a sales plan error threshold.

  In step S304, the demand actual value of the forecasted product for a certain period in the past is obtained from the demand result DB 103, and the past demand forecast value of the forecast product is obtained from the forecast result DB 105, and the respective cumulative demand forecast errors of the fixed period destination are calculated. .

  There are various error calculation methods as in step S302, but the error calculation method is not particularly defined as long as it represents the difference between the demand forecast value and the demand record.

  As an example, with respect to the parameters used in [Equation 1], there is a method of replacing the sales plan value at the time k point at the time point i with the actual demand value at the time point k at the time point i.

  FIG. 15 shows an example of the accumulated demand forecast error (rate). The past certain period is registered in the product information DB 102 as an error evaluation period, and the cumulative period is registered as a prediction error cumulative period.

  In FIG. 15, the demand forecast value (k = 2) as of January of the forecast start date means the demand forecast value for February calculated in January (January (k = 1) is a fixed period), Similarly, the demand forecast value (k = 3) as of January of the forecast start date means the demand forecast value of March calculated in January (January (k = 1) is a fixed period).

  In step S305, the demand prediction errors calculated in step S304 are compared.

  When the demand forecast error based on the demand forecast performed using the past sales plan value calculated in step S302 is smaller than the demand forecast error performed using the past demand result calculated in step S304, the sales plan value is set. It is determined that the used demand prediction is valid, and the process proceeds to S306.

  On the other hand, if the demand forecast error based on the demand forecast performed using the past sales plan value calculated in step S302 is greater than or equal to the demand forecast error performed using the past demand record calculated in step S304, the sales plan It is determined that the demand prediction using the value is invalid, and the process proceeds to step S307.

  Sales plan accuracy during the fixed period is good, but as an example where the demand forecast using the sales plan value is invalid, the sales plan in the past fixed period shows only a temporary demand trend and is not continuous Cases.

  For example, as shown in the upper part of FIG. 16, a sales plan value is set at the time of August, taking into account the increase in the demand level from August onwards, and the demand forecast after the fixed periods in August and September is also set. Suppose that it matches the market trend.

  And as shown in the lower part of FIG. 16, when it comes to the time of October, there is a case where it falls to the original demand level after October.

  In step S306, the prediction re-execution flag is stored as Y for the product for which the demand prediction using the sales plan value is determined to be valid in step S305. Note that the prediction re-execution flag is an internally held flag having an initial value N, and is cleared when the processing of the subsequent step S305 is completed.

  In step S307, if the prediction re-execution determination for all target products is completed, the process ends. If undecided products remain, the process returns to step S301.

  Returning to FIG. 3 again, in step S105, the forecast re-execution unit 112 registers the demand record of the forecast target product in the demand record DB 103 and the sales plan DB 107 in the demand record DB 103 for the merchandise registered in the merchandise information DB 102. To obtain the sales plan to be recalculated.

  When recalculating the demand forecast quantity as in step S102, the mathematical forecast model registered in the forecast model information DB 104 is used. The demand forecast quantity calculated at this time is registered in the forecast re-execution result DB 106.

  FIG. 17 is a flowchart for explaining details of the prediction re-execution process in step S105.

  In step S401, it is determined whether or not the sales plan for the predicted product is used, the prediction re-execution flag stored in step S306 is Y or the prediction re-execution determination flag is N, and the product confirmation period is greater than 0. . That is, it is determined whether or not to perform demand prediction using the sales plan value.

  If it is determined that the above determination condition is satisfied, the process proceeds to step S402. If it is determined that the condition is not satisfied, the process proceeds to step S404. In addition, the confirmation period of the predicted product is registered in the product information DB 102.

  In step S402, the cycle of the predicted product is acquired from the product information DB 102. Further, the demand actual result of the predicted product is acquired from the demand actual result DB 103, and the sales plan value for the fixed period of the predicted product is acquired from the sales plan DB 107. That is, the aggregated sales plan values are regarded as future demand results and are used as input information for demand forecast calculation.

  FIG. 18 is a processing example of step S402 after the actual demand and sales plan values are aggregated when the fixed period is 2 and the cycle is a month.

  As shown in the upper part of FIG. 18, when the current month is July, if the sales plan values are confirmed as 150 for July and 200 for August, this sales plan is shown in the lower part of FIG. The demand forecast value (July, August) is used as the demand actual value (July, August), and the demand forecast after the fixed period (July, August) is performed using the demand actual result until August.

  In step S403, the demand forecast quantity after the fixed period of the said prediction goods is calculated from the demand performance and sales plan value which were totaled in step S402, and the mathematical prediction model registered into prediction model information DB104. The demand forecast quantity calculated at this time is registered in the forecast re-execution result DB 106.

  In step S404, when the prediction calculation for all the products is completed, the process ends, and the prediction re-execution flag stored in step S306 is cleared. If uncalculated products remain, the process returns to step S401.

  Returning to the description of FIG. 3 again, in step S106, the prediction result confirmation unit 113 calculates the demand prediction value of the product calculated in step S102 from the prediction result DB 105 and the demand prediction of the product calculated in step S105 from the prediction re-execution result DB 106. The value is displayed on the sales plan input screen 400, the validity of the demand forecast value is confirmed, and the sales plan value is corrected as necessary.

  FIG. 19 shows an example of the sales plan input screen 400 displayed in step S305 when the current month is November 2015, the fixed period is 2, and the cycle is month.

  The sales plan values for November and December 2015 are purchased by humans and the latest demand trends are taken into account.

  The demand forecast value after January 2016 displays the result of taking into account the latest demand trend using the actual demand up to October 2015 and the sales plan values for November 2015 and December 2015.

  In addition, as for the demand forecast value after January, 2016, when the accuracy of the demand forecast using the past sales plan value is better than the accuracy of the demand forecast using the past demand record, Calculation is made using the sales plan values for November and December 2015.

  On the other hand, if the demand forecast value after January 2016 is not better than the accuracy of the demand forecast using the past sales plan value, the accuracy of the demand forecast using the past demand record , Using a past demand record before November 2016.

  As described above, according to the present invention, it is possible to accurately predict demand for products and the like by performing demand prediction for products and the like by using a determined sales plan.

  Further, the present invention can take an embodiment as, for example, a system, method, program, or storage medium.

  As described above, a recording medium that records a program that implements the functions of the above-described embodiments is supplied to a system or apparatus, and a computer (or CPU or MPU) of the system or apparatus stores the program stored in the recording medium. It goes without saying that the object of the present invention can also be achieved by performing reading.

  In this case, the program itself read from the recording medium realizes the novel function of the present invention, and the recording medium storing the program constitutes the present invention. As a recording medium for supplying the program, for example, a flexible disk, hard disk, optical disk, magneto-optical disk, CD-ROM, CD-R, DVD-ROM, magnetic tape, nonvolatile memory card, ROM, EEPROM, silicon A disk or the like can be used.

  Further, by executing the program read by the computer, not only the functions of the above-described embodiments are realized, but also an OS or the like operating on the computer based on an instruction of the program is a part of the actual processing or It goes without saying that the case where the functions of the above-described embodiments are realized by performing all of the above processing is also included.

  Furthermore, after the program read from the recording medium is written to the memory provided in the function expansion board inserted into the computer or the function expansion unit connected to the computer, the function expansion board is based on the instructions of the program code. It goes without saying that the case where the CPU or the like provided in the function expansion unit performs part or all of the actual processing and the functions of the above-described embodiments are realized by the processing.

  Needless to say, the present invention can be applied to a case where the present invention is achieved by supplying a program to a system or apparatus.

  In this case, by reading a recording medium storing a program for achieving the present invention into the system or apparatus, the system or apparatus can enjoy the effects of the present invention.

  Furthermore, by downloading and reading a program for achieving the present invention from a server, database, etc. on a network using a communication program, the system or apparatus can enjoy the effects of the present invention. In addition, all the structures which combined each embodiment mentioned above and its modification are also included in this invention.

100 demand prediction calculation device 201 CPU
202 RAM
203 ROM
204 System bus 205 Input controller 206 Video controller 207 Memory controller 208 Communication I / F (interface) controller 209 Keyboard (KB)
210 Display device (CRT)
211 External memory

Claims (4)

An information processing apparatus for forecasting demand for products, etc.
A forecasting means for forecasting demand using actual demand,
An accepting means for accepting an input of a sales plan value for an arbitrary period;
The information processing apparatus according to claim 1, wherein the prediction unit performs demand prediction after the arbitrary period using the sales plan value as the demand record in an arbitrary period in which an input is received by the reception unit. First storage means for storing a prediction value obtained by performing demand prediction using the actual demand by the prediction means;
Second storage means for storing a predicted value for which a demand prediction has been performed with the sales plan value as the demand result;
The predicted value obtained by performing demand prediction using the demand record stored in the first storage unit, the prediction error obtained from the demand record, and the sales plan value stored in the second storage unit are used as the demand record. Determination means for determining which forecast method is used for forecasting from the forecast value for which demand forecast is performed and the forecast error obtained from the demand record;
With
The information processing apparatus according to claim 1, wherein the prediction unit performs a demand prediction after the arbitrary period using the prediction method according to the determination of the determination unit. A method for controlling an information processing apparatus that performs demand prediction for products,
The information processing apparatus includes:
A forecasting step for forecasting demand using actual demand,
A reception step for accepting input of sales plan values for an arbitrary period;
In the information processing apparatus, the prediction step performs a demand prediction after the arbitrary period using the sales plan value as the demand result in the arbitrary period in which the input is received in the receiving step. Control method. It is a program that can be read and executed by an information processing device that performs demand prediction of products, etc.
The information processing apparatus;
A forecasting means for forecasting demand using actual demand,
An accepting means for accepting an input of a sales plan value for an arbitrary period;
The said prediction means functions as performing the demand prediction after the said arbitrary period by making the said sales plan value into the said demand performance in the arbitrary periods which received the input by the said reception means.

Images