Shipping planning system

Abstract

To provide a shipping plan formulation system capable of automatically formulating a shipping plan of crops.SOLUTION: A shipping plan formulation system 1 includes: a growth prediction device 3 for acquiring a daily growth amount of a crop predicted by using a growth prediction model 14 for predicting the growth amount of the crop from weather information (a solar radiation amount and temperature) of a field after a planting date of the crop planted in the field; and a shipping plan formulation device 2 for presenting a day when the growth amount satisfies a shipping standard (a day when a spherical weight We becomes a minimum value Wmin of the shipping standard or more) as a harvestable day (a ship date).SELECTED DRAWING: Figure 6

Description

[Technical Field]

[0001] The present invention relates to a shipping plan formulation system. [Background technology]

[0002] When producing crops such as outdoor vegetables, crops are planted in multiple fields at different times so that the daily harvest volume during the harvest season matches the shipping contract volume established with the shipping destination. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] International Publication No. 2017 / 164097 Summary of the Invention [Problem to be solved by the invention]

[0004] However, because crop growth is affected by weather conditions, actual harvest yields fluctuate daily, and there are cases where the harvest falls short of the shipping contract amount, or the harvest is so large that a surplus occurs, or harvesting cannot be completed due to a labor shortage. To prevent this, it is desirable to predict the daily harvest yield in advance, share a shipping plan that determines when and how much to ship with the shipping destination, and adjust supply and demand as appropriate. However, formulating such a shipping plan taking into account daily changing weather conditions is an extremely difficult task, even for an experienced worker.

[0005] An object of the present invention is to provide a shipping plan formulation system that can automatically formulate a shipping plan for crops. [Means for solving the problem]

[0006] The shipping plan development system of the present invention comprises: a planned shipping quantity acquisition unit that acquires planned shipping quantities for a crop planted in a field for each of a plurality of shipping dates; a growth quantity acquisition unit that acquires predicted daily growth quantities of the crop using a prediction model that predicts the growth quantity of the crop from meteorological information for the field after the planting date of the crop; a predicted harvest quantity calculation unit that calculates predicted harvest quantities of the crop for each of the plurality of shipping dates based on the acquired growth quantities; and a presentation unit that, when the predicted harvest quantity for a first shipping date among the plurality of shipping dates exceeds the planned shipping quantity, presents a second shipping date among the plurality of shipping dates that is different from the first shipping date as a harvest date for harvesting the portion of the predicted harvest quantity that exceeds the planned shipping quantity; The system is provided with: [Effects of the Invention]

[0007] The shipment plan formulation system of the present invention can automatically formulate a crop shipment plan. [Brief explanation of the drawings]

[0008] [Figure 1] FIG. 1 is a system configuration diagram of a shipment planning system according to the first embodiment. [Figure 2] FIG. 2 is a functional configuration diagram of the shipment plan development device according to the first embodiment. [Figure 3] FIG. 3 is a functional configuration diagram of the growth prediction device according to the first embodiment. [Figure 4] FIG. 4 is a flowchart of a growth prediction method executed by the growth prediction device according to the first embodiment. [Figure 5] FIG. 5 is a schematic diagram of the growth amount prediction process according to the first embodiment. [Figure 6] FIG. 6 is a sequence diagram showing the operation of the shipment planning system according to the first embodiment. [Figure 7] FIG. 7 is a schematic diagram of a growth amount table according to the first embodiment. [Figure 8] FIG. 8 is a hardware configuration diagram of the shipment plan development device according to the first embodiment. [Figure 9] FIG. 9 is a sequence diagram showing the operation of the shipment planning system according to the second embodiment. [Figure 10] FIG. 10 is a schematic diagram of a growth amount table according to the second embodiment. [Figure 11] FIG. 11 is a schematic diagram of a presentation example of a presentation unit according to the second embodiment. [Figure 12] FIG. 12 is a sequence diagram showing the operation of the shipment planning system according to the third embodiment. [Figure 13] FIG. 13 is a flowchart showing the process executed by the presentation unit of the shipment plan development device according to the third embodiment in step S148 of FIG. [Figure 14]14(a) to 14(e) are diagrams for explaining the processing of FIG. [Figure 15] FIG. 15 is a functional configuration diagram of a shipment plan development device according to the fourth embodiment. [Figure 16] FIG. 16 is a schematic diagram of a growth amount table according to the fourth embodiment. [Figure 17] FIG. 17 is a schematic diagram of a harvestable period table according to the fourth embodiment. [Figure 18] FIG. 18 is a schematic diagram of a presentation example of a presentation unit according to the fourth embodiment. [Figure 19] FIG. 19 is a flowchart showing a shipment plan formulation method executed by a presentation unit according to the fourth embodiment. [Figure 20] FIG. 20 is a schematic diagram of the day difference information according to this embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0009] First Embodiment FIG. 1 is a system configuration diagram of a shipment planning system according to the first embodiment.

[0010] The shipping plan formulation system 1 according to the first embodiment is a system that formulates shipping plans for crops planted in a farm field, and includes a shipping plan formulation device 2, a growth prediction device 3, a user terminal 4, and a weather data providing device 5. These devices are connected to each other via a network 6 such as the Internet.

[0011] The shipment plan formulation device 2 is a computer such as a physical server or a virtual server for formulating a shipment plan for crops.

[0012] The growth prediction device 3 is a computer such as a physical server or a virtual server that predicts the amount of crop growth required for the shipping plan formulation device 2 to formulate a shipping plan. As an example, the growth prediction device 3 is a computer for predicting the amount of growth managed by the National Agriculture and Food Research Organization, a National Research and Development Agency.

[0013] The user terminal 4 is a portable terminal such as a smartphone or tablet terminal that allows an operator to input parameters required by the growth prediction device 3. A PC (Personal Computer) may be used as the user terminal 4 to improve the efficiency of input work. However, when working in a field, it is preferable to use a smartphone or tablet terminal as the user terminal 4, as portability is important. The user terminal 4 also acquires the shipping plans formulated by the shipping plan formulation device 2 and presents them to the user.

[0014] The weather data providing device 5 is a computer such as a physical server or a virtual server that provides the growth prediction device 3 with weather data required for the growth prediction device 3 to predict the amount of crop growth. As an example, the weather data providing device 5 is a server managed by the Japan Meteorological Agency that provides AMeDAS data, but is not limited to this. For example, the weather data providing device 5 may be a server that stores and provides AMeDAS weather data at a location closest to the field where the crops are cultivated. Note that a weather observation point may be set up near the field to acquire weather data, and the growth prediction device 3 may acquire the average values ​​acquired there over a single or multiple years as weather data.

[0015] While there are no particular limitations on the crops for which a shipping plan is formulated, in this embodiment, a shipping plan for outdoor vegetables is formulated. Examples of such outdoor vegetables include cabbage, lettuce, broccoli, onion, leek, and Chinese cabbage. Unlike greenhouse crops such as tomatoes, which can produce multiple fruits in several batches from a single plant, these outdoor vegetables can only be harvested once from a single plant. Therefore, unlike greenhouse crops such as tomatoes, which can fine-tune the shipping volume by harvesting each fruit from a single plant at different times, outdoor vegetables require a more detailed shipping plan. The following explanation uses cabbage as an example of an outdoor vegetable.

[0016] The shipment plan development system 1 will be described in more detail. First, an operator inputs initial conditions using the user terminal 4. The initial conditions include at least the type of crop, the leaf area of ​​the crop when planted, the location of the field where the crop is to be planted, the date of planting, and the required shipping specifications of the crop, such as grade, size, or weight. Note that the operator may select the type of crop from a list of types registered in advance, rather than directly inputting it into the user terminal 4. In this case, it is sufficient to list the types of crop registered in a parameter table 30 stored as information necessary for growth prediction in the memory unit 22 of the shipment plan development device 2, which will be described later.

[0017] The user terminal 4 is configured to be connectable to the network 6 by means of an internal communication function.

[0018] After inputting the initial conditions, when the worker instructs the shipment plan development device 2 to execute processing from the user terminal 4, the shipment plan development device 2 starts calculating a shipment plan (scheduled shipping date) that matches the initial conditions. When the shipment plan development device 2 finishes calculating the shipment plan, the result is displayed on the user terminal 4, and the shipment plan development process ends.

[0019] (Shipping plan formulation device 2) Next, a description will be given of the shipment plan development device 2 according to this embodiment. Fig. 2 is a functional configuration diagram of the shipment plan development device 2. As shown in Fig. 2, the shipment plan development device 2 includes a communication unit 21, a storage unit 22, and a control unit 23.

[0020] The communication unit 21 is an interface for connecting the shipment plan development device 2 to the network 6 (see FIG. 1). The storage unit 22 stores a growth amount table 15 and a parameter table 30, which will be described later.

[0021] On the other hand, the control unit 23 is a processing unit that controls each unit of the shipping plan formulation device 2. As an example, the control unit 23 includes a parameter acquisition unit 25, a condition setting unit 26, a growth amount acquisition unit 27, a determination unit 28, and a presentation unit 29.

[0022] Among these, the parameter acquisition unit 25 is a processing unit that acquires from the user terminal 4 various parameters required for the shipping plan formulation device 2 to formulate a shipping plan. The various parameters are initial conditions input to the user terminal 4. Specifically, the parameters include field location information indicating the location of the field where the crop is to be cultivated, the type of crop, the leaf area of ​​the crop at the time of cultivation, the planned shipping date of the crop, and the shipping specification value. For example, if the type of crop to be cultivated is cabbage, the shipping specification value is generally determined by the weight of the cabbage, i.e., the head weight, and cabbages are classified into small, medium, large, etc., based on the head weight. When shipping is planned as an L-size cabbage, if the shipping specification for the L-size cabbage is between 2000g and 2300g, the minimum shipping specification value is 2000g, and the maximum shipping specification value is 2300g. Note that "head weight" is an example of growth amount and is the fresh weight (g) of a cabbage head.

[0023] The condition setting unit 26 is a processing unit that sets the day (target day) on which the growth prediction device 3 calculates the amount of growth of the crop.

[0024] The growth amount acquisition unit 27 is a processing unit that acquires the growth amount of the target day predicted by the growth prediction device 3.

[0025] The determination unit 28 is a processing unit that determines whether or not the growth amount acquired by the growth amount acquisition unit 27 matches the determination condition.

[0026] The presentation unit 29 is a processing unit that presents to the user terminal 4 the date that the determination unit 28 determines to match the determination condition as the scheduled shipping date.

[0027] (Growth prediction device 3) Next, a description will be given of the growth prediction device 3. Fig. 3 is a functional configuration diagram of the growth prediction device 3. As shown in Fig. 3, the growth prediction device 3 includes a communication unit 11, a storage unit 12, and a control unit 13.

[0028] The communication unit 11 is an interface for connecting the growth prediction device 3 to the network 6. The storage unit 12 stores a growth prediction model 14 for predicting the amount of crop growth.

[0029] On the other hand, the control unit 13 is a processing unit that controls each unit of the growth prediction device 3. As an example, the control unit 13 includes an acquisition unit 16, a prediction unit 17, and a notification unit 18.

[0030] The acquisition unit 16 acquires the date of planting of the crop, the leaf area (m 2 / plant), and planting density (plant / m 2 The acquisition unit 16 also acquires daily weather conditions after the planting date that affect the growth amount. Examples of such weather conditions include daily solar radiation (MJ / m 2 ) and temperature (℃) (average daily temperature), but are not limited to these.

[0031] The prediction unit 17 is a processing unit that predicts the daily growth amount of the crop after planting, based on the leaf area and weather conditions at the time of planting acquired by the acquisition unit 16. When making the prediction, the prediction unit 17 makes the prediction using an algorithm and parameters corresponding to the type of crop acquired by the acquisition unit 16 from the growth prediction model 14 stored in the memory unit 12.

[0032] The notification unit 18 notifies the shipment plan development device 2 of the results predicted by the prediction unit 17 via the network 6.

[0033] (Processing by growth prediction device 3) Next, a description will be given of a growth prediction method executed by the growth prediction device 3. FIG.

[0034] First, the acquisition unit 16 acquires the location of the field, the type of crop, and the leaf area (m 2 The acquiring unit 16 acquires information such as planting density (plants / m), planting date, etc. (Step S1). As will be described later, this information is information input to the user terminal 4. 2 ) information is also obtained.

[0035] In this example, several average crops are selected in the field, and the average leaf area per plant (m 2 The acquisition unit 16 acquires the leaf area (m / plant). Based on the image of the crop taken by a drone from above the field, the user terminal 4 acquires the leaf area (m 2 Furthermore, the leaf area (m 2 The user terminal 4 may measure the number of shares (shares) and notify the shipment plan development device 2 of the result.

[0036] Next, the acquisition unit 16 acquires the value of n, which indicates the number of days after the planting date, from the shipping plan development device 2 (step S2). The initial value of n is 1, and n increases by 1 each time it is acquired.

[0037] Next, the acquisition unit 16 acquires the weather conditions of the field for the day (nth day) after the planting date (step S3). If the nth day is in the past, the acquisition unit 16 acquires the past weather conditions from the weather data providing device 5, and if the nth day is in the future, the acquisition unit 16 acquires the future weather conditions from the weather data providing device 5. The past weather conditions are, for example, meteorological information observed by the AMeDAS observation station nearest to each field, such as solar radiation (MJ / m 2 ) and temperature (℃). Future weather conditions are also calculated using solar radiation (MJ / m ), which can be obtained from the Japan Meteorological Agency database. 2 ) and temperature (℃), etc., and are assumed to be forecast values ​​or normal values.

[0038] Next, the prediction unit 17 performs a prediction process to predict the amount of growth of the crop on the nth day using the growth prediction model 14 (step S4). The prediction process will be described in detail later.

[0039] Next, the notification unit 18 notifies the shipment plan formulation device 2 of the predicted growth amount on the nth day (step S5).

[0040] Next, the acquisition unit 16 determines whether a new n has been acquired (step S6). If the determination is affirmative, the process returns to step S3, and the processes from step S3 onward are repeatedly executed. On the other hand, if the determination in step S6 is negative, the entire process in FIG. 4 ends.

[0041] In step S3 of Fig. 4, weather conditions for a predetermined number of days after the planting date may be acquired all at once. In this case, if the determination in step S6 is positive, the process may return to step S4 instead of step S3.

[0042] (Detailed explanation of step S4) FIG. 5 is a schematic diagram of the growth amount prediction process in step S4. FIG. 5 is a schematic diagram of the growth amount prediction process taking as an example the case where cabbage is input as the type of crop. In response to the selection of cabbage as the type, the prediction unit 17 acquires the algorithm and parameters required for prediction from the growth prediction model 14 in the storage unit 12. As parameters for predicting the growth of cabbage, the growth prediction model 14 includes the solar radiation use efficiency (g / MJ) for cabbage, the leaf head dry matter distribution rate (%), the outer leaf dry matter rate (%), the leaf head dry matter rate (%), and the leaf area / fresh weight ratio (m 2 / g) are stored in advance.

[0043] As will be described later, the solar radiation use efficiency, outer leaf dry matter rate, and leaf head dry matter rate may depend on the daily mean temperature, and the relationships between these may be stored in the growth prediction model 14.

[0044] The prediction unit 17 executes the work of steps S21 to S28 according to the acquired algorithm. Executing steps S21 to S28 once is one day's worth of growth prediction work. The prediction unit 17 executes the prediction process assuming that planting was performed on the day specified by the shipping plan formulation device 2.

[0045] First, in step S21, the leaf area per plant of the crop assumed at the time of input planting is used for the prediction for the day after the planting date, and if it is after the day after the planting date, the leaf area calculated as the predicted value for the previous day and the daily accumulated solar radiation (MJ / m 2 ) and calculate the daily integrated amount of light received (MJ / plant). For example, 2 / share) and daily accumulated solar radiation (MJ / m 2 ) to obtain the daily accumulated amount of received light (MJ / share). The prediction unit 17 may obtain the daily accumulated amount of received light from the weather data providing device 5, or may obtain the daily accumulated amount of received light stored in advance in the storage unit 12.

[0046] Next, the process proceeds to step S22, where the prediction unit 17 calculates the daily dry matter production (g / plant) for that day from the calculated daily accumulated amount of received light (MJ / plant). In calculating this daily dry matter production, the prediction unit 17 uses the solar radiation use efficiency (g / MJ), which represents the amount of photosynthetic product produced per unit of physical energy of solar radiation received by the crop. For example, the prediction unit 17 obtains the daily dry matter production (g / plant) from the product of the daily accumulated amount of received light (MJ / plant) and the solar radiation use efficiency (g / MJ). Note that the solar radiation use efficiency (g / MJ) may be given a different value depending on the daily mean temperature.

[0047] Next, proceeding to step S23, the prediction unit 17 calculates the dry matter weight (g / plant) of the plant on that day by adding (not shown) the daily dry matter production (g / plant) calculated in step S22 to the dry matter weight (g / plant) up to the previous day.

[0048] Next, the process proceeds to step S24, where the prediction unit 17 calculates the head dry matter weight (g / plant) and the outer leaf dry matter weight (g / plant) using the plant dry matter weight (g / plant) and the head dry matter distribution rate (%), which indicates the proportion of the head dry matter weight (g / plant) to the plant dry matter weight (g / plant). Note that cabbage has a characteristic in which the head dry matter weight (g / plant) does not increase unless the outer leaf dry matter weight (g / plant) increases to a certain extent. In other words, the head dry matter distribution rate (%) depends on the outer leaf dry matter weight (g / plant), and when the outer leaf dry matter weight (g / plant) is smaller than a predetermined weight, the head dry matter distribution rate (%) used to calculate the head dry matter weight (g / plant) may be set to "0."

[0049] Next, proceeding to step S25, the prediction unit 17 calculates the outer leaf fresh weight (g / plant) based on the outer leaf dry matter weight (g / plant) calculated in step S24 and the outer leaf dry matter rate (%) indicating the ratio of the dry matter weight (g / plant) to the fresh weight (g / plant) of the outer leaves. For example, the outer leaf fresh weight (g / plant) is calculated from the product of the outer leaf dry matter weight (g / plant) and the outer leaf dry matter rate (%) indicating the ratio of the dry matter weight (g / plant) to the fresh weight (g / plant). Note that the outer leaf dry matter rate (%) may be given a different value depending on the daily average temperature.

[0050] Next, the process proceeds to step S26, where the prediction unit 17 calculates the leaf head fresh weight (g / plant) based on the leaf head dry matter weight (g / plant) calculated in step S24 and the leaf head dry matter rate (%), which indicates the ratio of the dry matter weight (g / plant) to the fresh weight of the leaf head (g / plant). For example, the prediction unit 17 obtains the leaf head fresh weight (g / plant) from the product of the leaf head dry matter weight (g / plant) and the leaf head dry matter rate (%), which indicates the ratio of the dry matter weight (g / plant) to the fresh weight of the leaf head (g / plant). Note that the leaf head dry matter rate (%) may be given a different value depending on the daily average temperature. This leaf head fresh weight (g / plant) becomes the "head weight" in the growth amount table 15.

[0051] Next, the process proceeds to step S28, and the prediction unit 17 calculates the leaf area / fresh weight ratio (m 2 / g) and the fresh weight of outer leaves (g / plant) to obtain the leaf area (m 2 This completes the prediction for one day. Every time the value of n is input from the shipping plan formulation device 2, the growth prediction device 3 executes the above process to predict the growth amount for the nth day from the planting date.

[0052] (Operation of shipping plan formulation system 1) FIG. 6 is a sequence diagram showing the operation of the shipment planning system 1 according to the first embodiment.

[0053] First, when the processing of the shipping plan development system 1 is started, the user terminal 4 accepts input of the field location information (L), the type of crop (F), the leaf area at the time of planting (S), the date of planting (D), and the minimum value of the head weight (Wmin) as the shipping standard or shipping standard value, and inputs these values ​​into the parameters L, F, S, D, and Wmin (steps S31 to S35). When the shipping standard is specified on the user terminal 4, the user terminal 4 can refer to the parameter table 30 of the shipping plan development device 2 and obtain the minimum value of the head weight of the input shipping standard.

[0054] Next, the user terminal 4 notifies these parameters L, F, S, D, and Wmin to the shipment planning device 2 (step S36), and the parameter acquisition unit 25 of the shipment planning device 2 acquires these parameters.

[0055] Next, the condition setting unit 26 of the shipping plan formulation device 2 assigns 1 to the parameter n that specifies the target date for predicting the growth amount (step S37). When n=1, the target date means one day after the planting date (number of cultivation days=1 day).

[0056] Next, the shipping plan formulation device 2 notifies the growth prediction device 3 of the parameters L, F, S, D, and n (step S38).

[0057] Next, the acquisition unit 16 of the growth prediction device 3 acquires weather data for the target day (nth day) for the location closest to the field from AMeDAS, which is the weather data providing device 5, based on the location information of the field indicated by the parameter L (step S39).

[0058] Next, the growth prediction device 3 calculates the head weight We at D+n when planted at D based on the parameters F, S, D, and n (step S40). The head weight We is calculated using the data for one day from steps S21 to S28 described above.

[0059] Next, the growth prediction device 3 notifies the shipping plan formulation device 2 of the calculated head weight We (step S41), and the growth amount acquisition unit 27 of the shipping plan formulation device 2 acquires the head weight We. The growth amount acquisition unit 27 stores information about the head weight We in a growth amount table 15 as shown in FIG. 7. Here, as shown in FIG. 7, the growth amount table 15 is a table in which "dates" and "head weights," which indicate the growth amount on those dates, are arranged in chronological order in association with the "number of cultivation days" (n) counted from the planting date. In the case of FIG. 7, for example, the growth amount table 15 records that the head weight was predicted to be 1,880 g on October 21, the 67th day of cultivation.

[0060] Next, the determining unit 28 of the shipment plan development device 2 determines whether the ball weight We is equal to or greater than the minimum value Wmin of the shipment standard (step S42).

[0061] If this determination is negative, the condition setting unit 26 increments n by 1 (step S43), and then starts over from step S38.

[0062] On the other hand, if the determination in step S42 is positive, the process proceeds to step S44. In the example of Fig. 7, if the minimum value Wmin of the shipping standard is 2000g, the determination in step S42 is positive on October 23rd when n=69.

[0063] In step S44, the determination unit 28 of the shipping plan formulation device 2 determines that the nth day counted from the planting date D is the harvestable date and presents this to the user terminal 4. The user terminal 4 then presents this harvestable date to the user as the scheduled shipping date (step S45). This completes the processing.

[0064] (Hardware configuration) Next, a hardware configuration of the shipment plan development device 2 according to the first embodiment will be described.

[0065] Fig. 8 is a hardware configuration diagram of the shipment plan development device 2. As shown in Fig. 8, the shipment plan development device 2 has a storage device 2a, a memory 2b, a processor 2c, a communication interface 2d, and a medium reading device 2g. These components are connected to each other by a bus 2h.

[0066] Of these, the storage device 2a is a non-volatile storage such as an HDD (Hard Disk Drive) or an SSD (Solid State Drive), and stores the shipment plan development program 100 according to this embodiment.

[0067] The shipment planning program 100 may be recorded on a computer-readable recording medium 2k, and the processor 2c may read the shipment planning program 100 via a medium reader 2g.

[0068] Such recording media 2k include physically portable recording media such as CD-ROMs (Compact Disc Read Only Memory), DVDs (Digital Versatile Discs), and USB (Universal Serial Bus) memories. Furthermore, semiconductor memories such as flash memories and hard disk drives may also be used as the recording media 2k. These recording media 2k are not temporary media such as carrier waves that do not have a physical form.

[0069] Furthermore, the shipment planning program 100 may be stored in a device connected to a public line, the Internet, a LAN, etc. In this case, the processor 2c may read and execute the shipment planning program 100.

[0070] On the other hand, the memory 2b is hardware that temporarily stores data, such as a DRAM (Dynamic Random Access Memory), and the shipment planning program 100 is developed on it.

[0071] The processor 2c is hardware such as a CPU (Central Processing Unit) or a GPU (Graphical Processing Unit) that controls each part of the shipment plan development device 2. The processor 2c also executes the shipment plan development program 100 in cooperation with the memory 2b.

[0072] In this way, the memory 2b and the processor 2c cooperate to execute the shipment planning program 100, thereby realizing the functions of the control unit 23 in FIG.

[0073] Furthermore, the communication interface 2d is hardware such as a network interface card (NIC) for connecting the shipment plan development device 2 to the network 6 (see FIG. 1). The communication interface realizes a communication unit 21 (see FIG. 2).

[0074] The medium reader 2g is hardware such as a CD drive, a DVD drive, or a USB interface for reading the recording medium 2k.

[0075] As explained in detail above, according to the first embodiment, the shipping plan formulation system 1 includes a growth prediction device 3 that acquires predicted daily crop growth amounts using a growth prediction model 14 that predicts crop growth amounts from meteorological information (solar radiation and temperature) in the field from the planting date of the crop planted in the field, and a shipping plan formulation device 2 that presents the day on which the growth amount meets the shipping standard (the day on which the head weight We is equal to or greater than the minimum value Wmin of the shipping standard) as the harvestable date (scheduled shipping date). As a result, in the first embodiment, it is possible to provide workers with the predicted day on which they can harvest crops with head weight We that meet the shipping standard.

[0076] In the first embodiment, the operator inputs the planting date in step S35 of FIG. 6 and the leaf area on the planting date in step S34. However, the present invention is not limited to this. For example, the operator may input the survey date on which the leaf area was surveyed instead of the planting date. Furthermore, the operator may input the leaf area on the survey date instead of the leaf area at the time of planting. In this case, the growth prediction device 3 can predict the growth amount on the nth day from the survey date using the leaf area on the survey date as the initial value. Therefore, when a new leaf area is surveyed, the operator can predict the future growth amount more accurately by inputting the survey date and the leaf area. Furthermore, since past weather information can be used up to the survey date and average values ​​or forecast values ​​can be used from the survey date onwards, the growth amount can be predicted more accurately than when average values ​​or forecast values ​​are used as all weather information.

[0077] Second Embodiment FIG. 9 is a sequence diagram showing the operation of the shipment planning system 1 according to the second embodiment.

[0078] In the first embodiment described above, the day on which the bulb weight is predicted to reach the minimum value (minimum weight) of the shipping standard value is presented as the harvest date, but in this second embodiment, the period when the bulb weight is between the minimum value (minimum weight) and the maximum value (maximum weight) of the shipping standard is presented as the harvest period.

[0079] 9, in the second embodiment, first, the user terminal 4 accepts input of the field location information (L), the type of crop planted (F), the leaf area at the time of planting (S), the date of planting (D), and the minimum (Wmin) and maximum (Wmax) bulb weight as shipping standard values, and inputs these into the parameters L, F, S, D, Wmin, and Wmax (steps S131 to S136). Note that, as in the first embodiment, the shipping standard may be input instead of the shipping standard value.

[0080] Next, the user terminal 4 notifies these parameters L, F, S, D, Wmin, and Wmax to the shipment planning device 2 (step S137), and the parameter acquisition unit 25 of the shipment planning device 2 acquires these parameters.

[0081] Next, the condition setting unit 26 of the shipment plan formulation device 2 assigns 1 to the parameter n that identifies the target date for predicting the growth amount (step S138).

[0082] Next, the shipment plan formulation device 2 notifies the growth prediction device 3 of the parameters L, F, S, D, and n (step S139).

[0083] Next, the acquisition unit 16 of the growth prediction device 3 acquires weather data for the target day (nth day) for the location closest to the field from AMeDAS, which is the weather data providing device 5, based on the location information of the field indicated by the parameter L (step S140).

[0084] Next, the growth prediction device 3 calculates the head weight We at D+n when planted at D based on the parameters F, S, D, and n (step S141). The head weight We is calculated using the data for one day from steps S21 to S28 described above.

[0085] Next, the growth prediction device 3 notifies the calculated head weight We to the shipping plan formulation device 2 (step S142), and the growth amount acquisition unit 27 of the shipping plan formulation device 2 acquires the head weight We. The growth amount acquisition unit 27 stores information about the head weight We in a growth amount table 15 as shown in FIG.

[0086] Next, the determination unit 28 of the shipping plan development device 2 determines whether the ball weight We is greater than the maximum value Wmin of the shipping specifications (step S143). If this determination is negative, the process proceeds to step S144, where the condition setting unit 26 increments n by 1, and then starts over from step S139.

[0087] On the other hand, if the determination in step S143 is positive, the process proceeds to step S145. In the example of Fig. 10, if the maximum value Wmax of the shipping specifications is 2300g, the determination in step S143 is positive on October 27th when n=73.

[0088] In step S145, the presentation unit 29 of the shipping plan formulation device 2 extracts the period where Wmin≦We≦Wmax as the harvestable period. In the example of FIG. 10, if Wmin=2000g and Wmax=2300g, October 23rd to October 26th is extracted as the harvestable period. Then, the presentation unit 29 presents the harvestable period to the user terminal 4 as the scheduled shipping period (step S146). Then, the user terminal 4 presents the scheduled shipping period to the user (step S147). For example, the user terminal 4 can present a table showing the scheduled shipping period as shown in FIG. 11 to the worker. This completes the processing.

[0089] As described above, according to the second embodiment, the shipping plan formulation system 1 includes a growth prediction device 3 that acquires predicted daily crop growth amounts using a growth prediction model 14 that predicts crop growth amounts from meteorological information (solar radiation and temperature) in the field from the planting date of the crop planted in the field, and a shipping plan formulation device 2 that presents the days when the growth amounts meet the shipping standards (the period when the head weight We is equal to or greater than the minimum value Wmin and equal to or less than the maximum value Wmax of the shipping standards) as the harvestable period. As a result, in the second embodiment, it is possible to provide workers with a predicted period during which they can harvest crops with head weight We that meet the shipping standards.

[0090] In the second embodiment, as in the first embodiment, the operator may input the inspection date in step S135 and the leaf area on the inspection date in step S134. When the operator inspects the leaf area for the first time, the operator can input the inspection date and the leaf area to more accurately predict the future growth amount.

[0091] Third Embodiment Next, a shipping plan formulation system 1 according to the third embodiment will be described in detail. In the second embodiment, the harvestable period is presented to the worker as the scheduled shipping period. However, while the harvest amount is determined by the amount of crop planted at the time of planting, there is an upper limit to the contracted shipping amount, and there may also be a limit to the amount that can be shipped per day due to the number of workers involved in harvesting, adjustment, and packing, as well as the capacity of the work machinery. In such cases, it is necessary to distribute the harvesting and shipping work and carry out the harvesting and shipping over several days. In the third embodiment, the amount of crop that can be harvested and shipped per day is taken into consideration, and the amount that can be shipped on each harvestable day is presented to the worker.

[0092] In the third embodiment, an example will be described in which when and how much of a crop planted on one planting day will be harvested and shipped is presented. Fig. 12 is a sequence diagram showing the operation of the shipping plan formulation system 1 according to the third embodiment.

[0093] In the third embodiment, steps S131 to S145 are the same as those in the second embodiment. In step S145, it is assumed that the harvestable period as shown in Fig. 14(a) is extracted.

[0094] After step S145, the process proceeds to step S148. In step S148, the presentation unit 29 executes a process of formulating a shipping plan based on the harvestable period. Specifically, in step S148, the presentation unit 29 executes a process in accordance with the flowchart in Fig. 13. The process in Fig. 13 will be described in detail below.

[0095] In the process of FIG. 13, first, in step S202, the presentation unit 29 accepts input of a priority order k for each harvestable date. The worker inputs, for example, the priority order as shown in FIG. 14(b) from the user terminal 4. Note that the smaller the value of the priority order k, the higher the priority order. Note that the presentation unit 29 may automatically set the priority order using a predetermined method (for example, a method of setting a higher priority order for an earlier date).

[0096] Next, in step S204, the presentation unit 29 accepts input of a planned shipment quantity per day. The worker inputs, for example, a planned shipment quantity such as the area H indicated by the thick frame in FIG. 14(c) from the user terminal 4. The planned shipment quantity means the number of cabbage heads.

[0097] Next, in step S206, the presentation unit 29 accepts input of the planting volume for the planting day. The worker inputs the planting volume for the planting day from the user terminal 4, for example, as shown in area I framed in a thick line in FIG. 14(c). The planting volume is the number of cabbage seedlings. Since the planting volume may decrease during cultivation due to pests and diseases, the decrease may be investigated and the value obtained by subtracting it from the planting volume may be input.

[0098] Next, in step S208, the presentation unit 29 assigns 1 to a parameter k indicating the priority.

[0099] Next, in step S210, the presentation unit 29 assigns the shipping volume based on the planted volume to the harvestable date of priority k. For example, as shown in area J indicated by a bold line frame in Figure 14(d), assuming that all of the cabbage planted on the planting date will be shipped on October 23rd, the total planted volume is set to the shipping volume for October 23rd. Note that it is assumed here that one cabbage head can be shipped from each of the planted seedlings.

[0100] Next, in step S212, the presentation unit 29 determines whether the shipping volume on the kth harvestable day is equal to or less than the planned shipping volume. If the determination in step S212 is positive, no further processing is required, and the processing in Figure 13 ends. On the other hand, if the planned shipping volume (2000) is less than the shipping volume (3000), as in Figure 14(d), the determination in step S212 is negative.

[0101] If the determination in step S212 is negative and the process proceeds to step S214, the presentation unit 29 determines whether there is a k+1-th harvest date. If this determination is positive, the process proceeds to step S216, where the presentation unit 29 substitutes the excess amount for the k-th harvest date for the shipping amount for the k+1-th harvest date. In the case of FIG. 14(e), the presentation unit 29 substitutes the surplus amount (1000) for October 23rd into the shipping amount for the next priority day (October 24th) (see the bold-lined area L). Thereafter, in step S220, the presentation unit 29 increments k by 1 (k←k+1) and returns to step S212. For example, in the case of FIG. 14(e), the shipping amount for October 24th is less than or equal to the planned shipping amount, so the determination in step S212 is positive. As a result, all of the processing in FIG. 13 is completed.

[0102] On the other hand, if the determination in step S214 is negative, that is, if there is a surplus but there is no next-priority harvest date, the presentation unit 29 proceeds to step S218. When proceeding to step S218, the presentation unit 29 determines that a surplus will occur. After that, all the processing in FIG. 13 ends.

[0103] Returning to FIG. 12, after step S148 is performed in the shipping plan formulation device 2, the formulated shipping plan (for example, FIG. 14(e)) and whether or not a surplus has occurred are presented to the user terminal 4 (step S149). The user terminal 4 then presents the shipping plan and whether or not a surplus has occurred to the user (step S150). This completes the processing. In the third embodiment, information such as that shown in FIG. 14(e) is displayed on the user terminal 4, allowing the user to confirm how much to harvest and ship each day.

[0104] As described above, according to the third embodiment, the presentation unit 29 automatically shifts the date for harvesting the portion of the "shipping volume" in a certain field that exceeds the "planned shipping volume" to a second shipping date that is different from the first shipping date. This makes it possible for even an expert to easily formulate a difficult crop shipping plan.

[0105] Furthermore, since it is possible to avoid a situation in which the shipping volume on the first shipping day exceeds the planned shipping volume, there is no need to secure personnel to harvest a large amount of crops, and furthermore, the planned shipping volume contracted with the contracting party can be shipped every day.

[0106] Fourth Embodiment Next, a shipping plan formulation system 1 according to a fourth embodiment will be described in detail. In the above third embodiment, an example was described in which when and how much of a crop planted on one planting day should be harvested and shipped was presented. However, shipping generally occurs continuously over a certain period of time, and to make this possible, there are multiple planting days. In this fourth embodiment, when there are multiple planting days, a shipping plan is formulated that indicates how crops planted on multiple planting days should be harvested and shipped in order to ship the crops in accordance with the shipping plan over a certain period of time.

[0107] Fig. 15 is a functional configuration diagram of a shipment plan development device 2 according to the fourth embodiment. As shown in Fig. 15, the shipment plan development device 2 according to the fourth embodiment stores a growth amount table 15, a harvestable period table 24, and a parameter table 30 in a storage unit 22. The parameter table 30 is the same as that in the first embodiment.

[0108] (Growth Table 15)

[0109] Fig. 16 is a schematic diagram of the growth amount table 15. As shown in Fig. 16, the growth amount table 15 is a table in which the "number of cultivation days" counted from the planting date and the "head weight" are associated with each other and arranged in chronological order for each field.

[0110] In this embodiment, the shipping plan development system 1 executes the processes of steps S131 to S145 in FIG. 9 for each field, thereby obtaining the growth amount table 15 in FIG.

[0111] (Harvestable Period Table 24) 17 is a schematic diagram of the harvest period table 24. The harvest period table 24 is information indicating a period during which a crop meets shipping standards during cultivation, and the presentation unit 29 creates a harvest period for each field, similar to that in the second embodiment, based on the growth amount table 15.

[0112] For example, consider the case where the shipping standard for cabbage (large size) is a head weight of 2000 g or more and 2300 kg or less, as described above. In this case, the presentation unit 29 identifies a period in the growth amount table 15 during which the head weight is 2000 g or more and 2300 kg or less. The presentation unit 29 then associates dates within the identified period with the head weights on those dates and stores them in the harvest period table 24. In the example of FIG. 17, the harvest period for "Field 1" is from November 22nd to November 26th.

[0113] (Presentation part 29) The presentation unit 29 uses the harvestable period table 24 (FIG. 17) created from the growth amount table 15 of FIG. 16 to create a shipping schedule table 32 as shown in FIG. 18, which associates fields with shipping dates, and presents the table to the user terminal 4. The dates for each field stored in the harvestable period table 24 correspond to the harvestable period described in the second embodiment.

[0114] When creating the shipping schedule table 32, the presentation unit 29 acquires planned shipping quantities for each of a plurality of shipping dates for the crop. For example, if the crop is cabbage, the planned shipping quantity is the number of cabbage heads scheduled to be shipped on the shipping date. As an example, the presentation unit 29 acquires information that associates the shipping date with the number of heads, such as 1,000 heads on November 27th, 2,000 heads on November 26th, and so on.

[0115] The source from which the planned shipment amount is obtained is not particularly limited. For example, an operator inputs the planned shipment amount for each shipping date into the user terminal 4, and the user terminal 4 notifies the shipping plan formulation device 2 of this information, and the presentation unit 29 then obtains the planned shipment amount. The planned shipment amount is an amount determined by a contract between the producer of the crop and the buyer who purchases the crop, and is fixed in principle at the time the contract is concluded. However, if the sales of the crops sold by the buyer are good or bad, the planned shipment amount may be changed midway. In that case, the presentation unit 29 obtains the changed planned shipment amount again.

[0116] Furthermore, when creating the shipping schedule table 32, the presentation unit 29 acquires the planting volume of the crop for each field from the user terminal 4. If the crop is cabbage, the presentation unit 29 acquires the number of plants (heads) for each field as the planting volume from the user terminal 4. Note that the planting volume may decrease during cultivation due to pests and diseases, etc., so the amount of decrease may be investigated and subtracted from the planting volume to obtain a value.

[0117] (Shipping Schedule Table 32) FIG. 18 is a schematic diagram of the shipping schedule table 32 that the presentation unit 29 presents to the user terminal 4. As shown in FIG.

[0118] The shipping schedule table 32 is a table showing a shipping plan for crops. In the shipping schedule table 32, as shown in item 32a, "field name," "area (a)," and "number of plants" are associated with each other. Of these, "area (a)" is the area of ​​each field.

[0119] On the other hand, "number of plants" is a mutual correspondence between "planting," "harvesting," and "surplus." "Planting" indicates the number of plants of a crop planted in the corresponding field. "Harvesting" indicates the total number of plants that will ultimately be harvested from that field. "Surplus" indicates the number of plants that will remain surplus and not be harvested in that field.

[0120] The “crop type”, “field name”, and “area (a)” are acquired by the parameter acquisition unit 25 from the user terminal 4.

[0121] Furthermore, item 32b of the shipping schedule table 32 associates "Plan (bulb)," "Forecast (bulb)," and "Shortage (bulb)." Note that, since one bulb of cabbage is harvested from one head, the number of heads is the same as the number of heads.

[0122] Of these, "Plan (bulb)" is the number of bulbs for each shipping date as determined in the shipping plan, and is the shipping plan amount acquired by the presentation unit 29. "Forecast (bulb)" indicates the number of bulbs planned to be harvested from all fields on the corresponding shipping date. "Shortage (bulb)" is the difference between "Plan (bulb)" and "Forecast (bulb)", and indicates the number of bulbs expected to be in short supply on the corresponding shipping date.

[0123] The hatched areas 32c in the shipping schedule table 32 correspond to the harvestable period of each farm field. The presenting unit 29 identifies the harvestable period from the harvestable period table 24.

[0124] The numerical value in each cell in the area 32c indicates the predicted yield for each field and shipping date presented by the presentation unit 29.

[0125] For example, let's consider "Field 1." The harvestable period for "Field 1" is from November 22nd to November 26th. Since the planting for "Field 1" is "8000," if the daily predicted harvest volume is not adjusted, 8000 bulbs can be harvested on November 22nd. However, this exceeds the "Plan (bulbs)" for November 22nd, which is "2600."

[0126] Therefore, the presentation unit 29 shifts the date for harvesting the predicted yield that exceeds "2600" to any day within the harvestable period other than November 22nd. Because the harvestable period for "Field 1" is November 22nd to November 26th, the presentation unit 29 sets the predicted yields for November 22nd, November 23rd, November 24th, November 25th, and November 26th, which are within the harvestable period for "Field 1," to "2600," "2600," "2000," "800," and "0," respectively. As a result, the portion of "8000," which is the "planting" for "Field 1," that exceeds "2600," which is the "plan (bulbs)," for November 22nd, becomes the predicted yield for "Field 1" for a day after November 22nd.

[0127] In this way, the presentation unit 29 presents the shipping date for which a value other than "0" is entered in the area 32c as the harvest date for harvesting the portion that exceeds the planned shipping amount.

[0128] Furthermore, by not storing the predicted harvest amount for days outside the harvest period, the presentation unit 29 does not present days outside the harvest period as harvest dates. This allows the presentation unit 29 to present as harvest dates the days on which the crops meet shipping standards, enabling the harvest of crops that meet the shipping standards stipulated in the contract with the business partner.

[0129] Furthermore, by taking the same measures for "Field 2," the presentation unit 29 makes the predicted harvest volume for all fields combined equal to the "Plan (bulbs)" of 1500 on November 25th, when the harvest volume for "Field 1" alone falls short of the "Plan (bulbs)." This makes it possible to make the predicted harvest volume for all fields combined on November 25th equal to the "Plan (bulbs)," and to fulfill the contract with the business partner.

[0130] 18 shows the state after the presentation unit 29 has finished adjusting the predicted yields for all fields for all shipping dates. Before adjustment, the predicted yield calculated by the presentation unit 29 is stored in the cell for the first day of the harvestable period for each field in area 32c, and "0" is stored in the other cells.

[0131] Furthermore, if there is a shipping date where "Forecast (bulbs)" < "Plan (bulbs)", the presentation unit 29 displays a warning by displaying the symbol "▲" and the quantity of the shortage next to "Shortage (bulbs)" on that shipping date. Also, if there is a field where "Harvest" > "Cultivation", the presentation unit 29 displays the number of plants next to "Surplus" in that field to notify the occurrence.

[0132] This allows workers to know in advance whether the "forecast (bulbs)" will be lower than the "plan (bulbs)" on that shipping date or whether there will be a surplus harvest.

[0133] The method for calculating the predicted yield of each cell in the region 32c is not particularly limited. In this embodiment, the presentation unit 29 presents the predicted yield according to the following procedure.

[0134] First, set the parameters as follows:

[0135] ·S ij …Predicted yield on the jth shipping date for the i-th field P j ..."Plan (ball)" for the jth shipping date Q i ..."Cropping" of the i-th field L j ..."Shortage (bulbs)" on the jth shipping date ·R i ...the "surplus" of the i-th field In addition, the predicted harvest yield S ij The initial value of is the predicted yield calculated by the presentation unit 29 as described above. j and Crop Q i are the planned shipping quantities and the cultivated quantities for each field acquired by the presentation unit 29.

[0136] Next, the presenting unit 29 determines whether the inequality in formula (1) holds.

number

[0137] When the inequality in formula (1) is satisfied, the planned shipping quantity on the jth shipping date is satisfied by the predicted harvest quantities of all fields except the i-th field. Therefore, the presentation unit 29 outputs the predicted harvest quantity S ij Enter 0 in (S ij ←0).

[0138] On the other hand, if the inequality in formula (1) does not hold, the presenting unit 29 determines whether the inequality in the following formula (2) holds.

[0139]

number

[0140] If the inequality in formula (2) is satisfied, the presentation unit 29 outputs the predicted yield S on the jth shipping date of the i-th field. ij is updated as shown in the following equation (3).

[0141]

number

[0142] On the other hand, if the inequality in formula (1) does not hold, the presentation unit 29 outputs the predicted yield S ij is updated as shown in the following equation (4).

[0143]

number

[0144] After the update is completed, the presentation unit 29 calculates the shortage (balls) L for all shipping dates j. j is calculated according to the following formula (5).

[0145]

number

[0146]

number

[0147] (Shipping plan formulation method) Next, a shipment planning method according to the fourth embodiment will be described below. Fig. 19 is a flowchart of the shipment planning method according to the fourth embodiment.

[0148] 19 starts, it is assumed that the growth amount table 15 has already been created in the shipping plan formulation device 2, and that the harvestable period table 24 has also been created based on the growth amount table 15.

[0149] When the process of FIG. 19 starts, the presentation unit 29 acquires the planned shipping amounts for each of a plurality of shipping dates from the user terminal 4 (step S330).

[0150] Next, the presentation unit 29 acquires the crop yield for each field from the user terminal 4 (step S332).

[0151] Next, the presentation unit 29 creates and updates the shipping schedule table 32 based on the harvestable period table 24 (step S334). At this time, the presentation unit 29 presents to the user terminal 4 day difference information indicating the difference in number of days between the planned harvest date at the beginning of cultivation and the current predicted harvest date.

[0152] Fig. 20 is a schematic diagram of the day difference information 40 presented on the user terminal 4. As shown in Fig. 20, the day difference information 40 is information that indicates, for each field, the day difference 40c between the planned harvest date 40a at the beginning of cultivation and the current predicted harvest date 40b.

[0153] The planned harvest date 40a is the planting date on which the growth prediction device 3 determines that the harvest period will be reached. On the other hand, the predicted harvest date 40b is the date on which the growth prediction device 3 predicts the growth amount using the latest weather information and determines that the harvest period will be reached based on the prediction result.

[0154] By presenting such day difference information 40 to the worker, the worker can understand how much the harvest date has deviated from the average year.

[0155] When step S334 is performed for the first time, the predicted harvest yield obtained by the presentation unit 29 is stored in the cell for the first day of the harvestable period for each field in area 32c of the shipping schedule table 32, and "0" is stored in all other cells.

[0156] Next, the presentation unit 29 determines whether there is a shipping date where "Forecast (global)" > "Plan (global)" among the multiple shipping dates in the shipping schedule table 32 (step S336).

[0157] If it is determined that there is a shipping date where "Forecast (ball)" > "Plan (ball)" (YES), the process proceeds to step S338.

[0158] In step S338, the presentation unit 29 shifts all or part of the harvest volume of the "forecast (bulb)" that exceeds the "planned (bulb)" in a certain field corresponding to a shipping date (first shipping date) where "forecast (bulb)" > "planned (bulb)" to a second shipping date that is different from the first shipping date and that is within the harvestable period. The shift can be made before or after the first shipping date, but in this embodiment, the shift is made to a date later than the first shipping date. This increases the period during which the crops are present in the field, allowing the crops to mature more quickly than if the shift was made earlier than the first shipping date.

[0159] As an example, the presentation unit 29 calculates the predicted yield S according to the above-mentioned formulas (1) to (6). ij By updating the "predicted (bulbs)", the harvest date for the portion of the "forecasted (bulbs)" that exceeds the "planned (bulbs)" is shifted to a later date. Then, the process returns to step S334.

[0160] On the other hand, if it is determined in step S336 that there is no shipping date where "Forecast (global)" > "Plan (global)" (NO), the process proceeds to step S340.

[0161] In step S340, it is determined whether there is a shipping date in the shipping schedule table 32 where "forecast (global)" is smaller than "plan (global)".

[0162] If there is a shipping date where "Forecast (bulb)" < "Plan (bulb)" (YES), then "Forecast (bulb)" will be less than "Plan (bulb)" on that shipping date. In this case, the process proceeds to step S342, where the presentation unit 29 presents a warning to the user terminal 4, and the process ends. As an example, the presentation unit 29 displays the warning by displaying the symbol "▲" and the quantity of the shortage, as shown in FIG. 18.

[0163] On the other hand, if the determinations at steps S336 and S340 are negative, then "Forecast (bulbs)" = "Plan (bulbs)" for all shipping dates. In this case, there is no shortage of "Forecast (bulbs)" compared to "Plan (bulbs)," so there is no need to shift the harvest date. Therefore, in this case, the shipping schedule table 32 created and updated at step S336 is presented to the user terminal 4 (step S344), and the process ends.

[0164] As a result of the processing, a "surplus" may occur in the number of harvested stalks, as shown in item 32a of the shipping schedule table 32 in Figure 18. In this case, the planted stalks will not be shipped and will be wasted, so the shipping plan quantity may be increased and the processing may be restarted from step S330.

[0165] This completes the basic processing of the shipment plan formulation method according to the fourth embodiment.

[0166] According to the fourth embodiment described above, in step S338, the presentation unit 29 automatically shifts the date for harvesting the portion of the "predicted (bulbs)" that exceeds the "planned (bulbs)" in a certain field to a second shipping date that is different from the first shipping date. This makes it possible to easily formulate a shipping plan for a crop that is difficult even for an expert.

[0167] Furthermore, the shipping schedule table 32 used in the determination in step S336 is created by the presentation unit 29 in step S334 based on the acquired harvest period table 24. Because the harvest period table 24 is created from meteorological information from the planting date onwards, the meteorological information can be reflected in the shipping schedule table 32, and the expected harvest date in the shipping schedule table 32 can be predicted with high accuracy.

[0168] Furthermore, if there is a shipping date where the "forecast (bulb)" is smaller than the "plan (bulb)", the notification unit 29 issues a warning in step S340 (S342). This allows the worker to notify the contractor in advance that the shipping volume on the shipping date will be lower than the "plan (bulb)" specified in the contract.

[0169] In addition, since it is possible to detect in advance that the predicted harvest volume on the first shipping date will be greater than the "plan (bulbs)," by securing personnel to harvest a large amount of crops and new sales outlets, the planted crops can be shipped without waste.

[0170] The above-described embodiment is a preferred example of the present invention, but the present invention is not limited to this and can be modified in various ways without departing from the spirit of the present invention.

[0171] For example, in the above-described embodiment, the shipping plan formulation device 2 and the growth prediction device 3 are separate pieces of hardware as shown in FIG. 1, but the growth prediction device 3 may be made unnecessary by giving the shipping plan formulation device 2 the functions of the growth prediction device 3. [Explanation of symbols]

[0172] 1...Shipping plan formulation system, 2...Shipping plan formulation device, 3...Growth prediction device, 4...User terminal, 5...Weather data providing device, 6...Network, 11...Communication unit, 12...Memory unit, 13...Control unit, 14...Growth prediction model, 15...Growth amount table, 16...Acquisition unit, 17...Prediction unit, 18...Notification unit, 21...Communication unit, 22...Memory unit, 23...Control unit, 24...Harvestable period table, 25...Parameter acquisition unit, 26...Condition setting unit, 27...Growth amount acquisition unit, 28...Determination unit, 29...Presentation unit, 32...Shipping schedule table, 40...Day difference information

Claims

1. a planned shipment quantity acquisition unit that acquires planned shipment quantities for each of a plurality of shipping dates of crops planted in a field; a growth amount acquisition unit that acquires a daily growth amount of the crop predicted using a prediction model that predicts the growth amount of the crop from meteorological information of the field on or after the planting date of the crop; a predicted yield calculation unit that calculates a predicted yield of the crop for each of the plurality of shipping dates based on the acquired growth amount; a presentation unit that, when the predicted harvest volume on a first shipping date among the plurality of shipping dates exceeds the planned shipping volume, presents a second shipping date among the plurality of shipping dates that is different from the first shipping date as a harvest date for harvesting the portion of the predicted harvest volume that exceeds the planned shipping volume; A shipping planning system that includes:

2. a shipping standard acquisition unit that acquires shipping standards for the crop; a harvestable period specifying unit that specifies a harvestable period in which the crop satisfies the shipping standard when the crop is planted in the field, 2. The shipment plan formulation system according to claim 1, wherein the presentation unit presents any day within the harvestable period as the harvest date.

3. 3. The shipment plan formulation system according to claim 1, wherein the notification unit issues a warning when the predicted harvest amount is less than the shipment plan amount.

4. the predicted yield calculation unit calculates the predicted yield for each of the plurality of farm fields, A shipping plan formulation system as described in any one of claims 1 to 3, characterized in that the presentation unit presents the second shipping date as the harvest date for one of the multiple fields when the predicted harvest volume for the multiple fields combined on the first shipping date exceeds the shipping plan volume.

5. The shipment plan formulation system according to claim 4 , wherein the presentation unit presents the predicted harvest yield for each of the plurality of farm fields on the first shipping date.

Images