System and method for tracking agronomic articles

Abstract

A method for tracking agronomic items with asynchronous behavior, comprising, during a registration phase: a. assigning (S01) an IDX identifier to each inflorescence not previously registered in a plot of agronomic items; b. physically affixing (S02) a marker around or in the immediate vicinity of each inflorescence, said marker bearing the assigned IDX identifier; c. populating (S03) a database so that each of said inflorescence IDX identifiers is associated with at least the following registration data: - a registration date / time D_REPX; - an identifier of said plot PX; - a location data LX within said plot. Abstract: Figure 2

Description

Title of the invention: System and method for tracking agronomic articles Technical field

[0001] The present disclosure relates to the field of agronomy and in particular to non-seasonal plant crops for which neighboring plants may have heterogeneous stages of advancement, such as banana cultivation. Prior art

[0002] In agriculture as in industrial fields, there are numerous computer systems for monitoring production, inventory, transport and more generally for tracing items until their supply to the final consumer, or even until their destruction or recycling. In plant agronomy, existing systems are designed to take into account growing conditions and resolve problems that do not exist in industrial fields or in animal production fields. However, even among the systems dedicated to plant agriculture, the latter are for the most part designed to allow tracking of items in batches, that is to say on a scale, or a grid, of which the smallest unit remains a set or a volume containing a large number of items.It will be agreed that in production (outside of experimental studies) the agronomic monitoring of cereals is carried out by geographical cultivation zone, at best by fields or part of fields and not at the scale of an "ear" for example. Similarly, in fruit production, monitoring is carried out rather at the scale of an orchard containing several trees rather than at the scale of a "bunch" or a fruit. Thus, it is impossible to carry out precise and distinct monitoring between a bunch and its neighbor.

[0003] Furthermore, batch monitoring is generally considered sufficient because it is assumed that agricultural articles growing in close proximity to each other are subject to identical conditions, particularly environmental conditions, during their common development stages. However, this assumption is false for agronomic articles with asynchronous behavior, i.e. plant species whose development is not seasonal. In these cases, two geographically neighboring plants of the same species may have completely different development stages from each other at any given time. In other words, the development stage of the articles within a crop plot is highly heterogeneous. This is particularly the case within banana plantations.

[0004] Thus, existing tracking systems in industry and / or other areas of agriculture do not allow relevant tracking of agronomic articles to be asynchronous behaviors, such as bananas. There is therefore a need for such methods and systems. Summary

[0005] The present disclosure improves the situation.

[0006] A method is proposed for tracking agronomic articles with asynchronous behavior comprising, during a listing phase: a. assign an IDX identifier to each inflorescence not previously listed in a plot of agronomic articles; b. physically affix a marker around or in the immediate vicinity of each of the inflorescences, said marker bearing the assigned IDX identifier; c. feed a database so that each of said inflorescence IDX identifiers is associated with at least the following listing data: - a D_REPX listing date / time; - an identifier of said plot Px; - a location data Lx in said plot.

[0007] According to another aspect, there is provided a system for tracking agronomic articles with asynchronous behaviors comprising a controller capable of accessing a database, and a plurality of devices, each of the devices being connected or capable of being connected to the controller so as to feed the database with data via the controller, each of the devices being further configured to acquire data sets, each data set including at least the following index data associated with each other: - a D_REPX listing date; - an identifier of said plot Px; - a location data Lx in said plot.

[0008] According to another aspect, there is provided a computer program comprising instructions for implementing all or part of a method as defined herein when this program is executed by a processor. According to another aspect, there is provided a non-transitory, computer-readable recording medium on which such a program is recorded.

[0009] The features set out in the following paragraphs may, optionally, be implemented, independently of one another or in combination with one another:

[0010] The method further comprises, during a planning phase: d. determine, for each of the inflorescence identifiers IDX, a date or a range of future dates for pre-calibration D_PLAN_CALX and / or harvest D_PLAN_RECX, as well as a predicted value of at least one development indicator DEVPLAn_cal_x and / or DEVPLAn_rec_x development based on the associated data in the database; and e. feeding the database with said dates D_PLAN_CALX, D_PLAN_RECX and corresponding development indicator values ​​DEVCal_x and / or DEVrec x.

[0011] The method further comprises, during a control phase: f. populate the database so that the IDX identifier of a previously listed inflorescence is associated with at least the following control data: - an effective date / time of D_CALX control; - a measurement or an estimate of at least one development indicator DEV cal_x of at least one fruit from the inflorescence on the effective date of control; - a forecast harvest date D_PLAN_RECX.

[0012] The method further comprises, during a harvesting phase: g. populate the database so that the IDX identifier of a previously listed inflorescence is associated with at least the following harvest data: - an effective date / time of collection D_RECX; - a measurement or estimate of at least one development indicator DEV rec_x of at least one fruit from the inflorescence on the actual harvest date.

[0013] The method further comprises: h. extract a list or map of the inflorescences for which control or harvesting is planned on a preselected or current date based on the data in the database, so that a schedule of a set of control and / or harvesting operations in a plot P or an area P; of plot P on said date is established and then implemented.

[0014] The method further comprises: i. identify the inflorescence by its IDx identifier when weighing said inflorescence and feed the database with the mass obtained.

[0015] The method further comprises: j. extracting at least part of the data from the database based on the geographic position of the inflorescences so that the geographic extent for which the data is extracted can be selected.

[0016] The system further comprises a calculator configured to: d. determine, for each of the inflorescence identifiers IDX, a date or a range of future dates of pre-calibration D_PLAN_CALX and / or harvest D_PLAN_RECX, as well as a predicted value of at least one development indicator DEVPLan_cal_x and / or DEVplan.rec.x based on the associated data in the database; e. populate the database with said D_PLAN_CALX, D_PLAN_RECX dates and corresponding DEVCal_x and / or DEVrec_x development indicator values; and / or h. extract a list or map of the inflorescences for which control or harvesting is planned on a preselected or current date based on the data in the database, so that a schedule of a set of control and / or harvesting operations in a plot P or an area P; of plot P on said date is established and then implemented.

[0017] The devices are further equipped with a human-machine interface and configured to provide, via the human-machine interface, a list or map (MAP) of the previously listed inflorescences for which a check or harvest is planned on a preselected or current date. Brief description of the drawings

[0018] Other characteristics, details and advantages will appear on reading the detailed description below, and on analyzing the attached drawings, in which: Fig.l

[0019] [Fig.l] represents a system according to one embodiment. Fig. 2

[0020] [Fig.2] represents the implementation of a method over time for a plurality of inflorescences with asynchronous development. Fig. 3

[0021] [Fig.3] shows an example of representation of data extracted according to a method according to one embodiment. Fig. 4

[0022] [Fig.4] shows an example of representation of data extracted according to a method according to one embodiment. Fig. 5

[0023] [Fig.5] shows an example of representation of data extracted according to a method according to one embodiment. Description of the embodiments

[0024] Reference is now made to [Fig.l]. [Fig.l] represents a system for tracking agronomic articles with asynchronous behavior. The system comprises a controller 1, a database 2, and at least one device 3. The controller 1 is configured to receive data as input from the at least one device 3, read and write data in the database 2, and transmit data to the at least one device 3. In the example described here, the system further comprises a computing unit 4. To facilitate understanding, a distinction is made on the one hand between the controller 1 which manages the database 2 and provides the interface between the devices 3 and the database 2, and on the other hand between the computing unit 4 which applies algorithms for processing the data contained in the database 2. In practice, the controller 1 and the computing unit 4 may be integrated with each other. The controller 1 and the computing unit 4 may take the form of one or more processors, and / or other computer components configured to operate together.

[0025] The database 2 is stored on at least one memory device, for example a server. The database can also be duplicated on several separate memory devices.

[0026] In the example described here, the controller 1 and the database 2 are distinct and remote. The data are exchanged via a telecommunications network, including for example the internet and / or a mobile telephone network. In variants, the controller 1 and the memory device on which the database 2 is stored may form the same device, such as a computer. The controller 1 may further be used as a device 3 in the sense that it may include a human-machine interface suitable for an operator to enter and / or consult data there.

[0027] In the examples described here, the system comprises a plurality (or “fleet”) of devices 3. Since the devices 3 are intended to be used by operators in the field, the devices are preferably mobile devices. The devices may be devices dedicated to the system or implement other functions such as smartphones or tablets. In the examples described here, the devices 3 are arranged to communicate with the controller 1 via the mobile telephone network, so that the data exchanges can be implemented in near real time as long as the mobile telephone coverage allows it. The devices 3 are each equipped with a memory unit (or local memory) so that, in the event of an interruption in communication with the controller 1, the devices 3 remain operational and the data exchanges are resumed when a connection is reestablished after an interruption.

[0028] Reference is now made to [Fig. 2], representing a method for tracking agronomic articles with asynchronous behavior. The method can for example be implemented by means of a system as described above. In the following, the operations implemented are explained by following the natural chronology of the agronomic articles to facilitate understanding. However, since the articles have an asynchronous development, the operations can be implemented out of order for different articles. For example, the listing of a batch of inflorescences can be done concurrently with the harvesting of another batch of inflorescences.

[0029] During a first phase called “listing”, a data set is created for each new inflorescence. During a first SOI operation, an IDX identifier is assigned to each inflorescence not previously listed in a Px plot of cultivation of the agronomic articles. Each data set is identified by said IDX identifier, so that each inflorescence corresponds to a data set. The data set is then supplemented with information associated with said inflorescence.

[0030] During a second operation S02, an operator physically affixes a marker around or in the immediate vicinity of the inflorescence, said marker bearing the assigned IDX identifier. By “marker” is meant here any physical element allowing an operator to subsequently identify an inflorescence by its IDX identifier. The marker may for example take the form of a label or a ribbon on which the IDX identifier is written. The IDX identifier may be written in the form of a character string readable by a human and / or a visual code readable by an optical reader such as a “barcode” or a “QR code”. In variants, the IDX identifier may be stored in a tag readable by technologies other than optical, such as an RFID chip for example. Preferably, the reader (optical, RFID or other) is integrated into the device 3 worn by the operator.

[0031] In embodiments, for a given inflorescence, the first operation SOI of generating the identifier is implemented, then the second operation S02 of physical marking. For example, the operator reads on the device 3 the new identifier IDX generated and transmitted by the controller 1, then physically transfers the identifier IDX near the inflorescence, for example by manually writing it on a label. Alternatively, the first and second operations SOI, S02 can be interchanged. For example, labels each bearing an identifier IDX can be previously manufactured (or printed). The operator affixes one near a newly identified inflorescence and activates the corresponding identifier, for example by “scanning” the identifier IDX a first time.

[0032] In a third operation S03, the database 2 is supplied with data other than the IDX identifiers. Each data set is therefore completed. Said data is associated with the IDX identifier corresponding to the inflorescence in the database 2. For each data set, the IDX identifier is associated, at least, with the following listing data: - a D_REPX listing date / time; - an identifier of the plot Px in which the inflorescence is located; - a location data Lx in said plot Px.

[0033] The date / time may be the current date or entered manually by the operator via a human-machine interface of the device 3. The accuracy of the date may be adjusted as required (day only or to the nearest second, for example). The plot identifiers Px and location Lx may be entered manually by the operator using the device 3. Alternatively, they may be deduced, for example by the controller 1, from a geographical position recorded via the device 3 and transmitted to the controller 1. The controller 1 can for example compare a geographical position such as “GPS” type coordinates to a map of the previously recorded crop plots. The location Lx can for example take the form of said coordinates themselves while the identifier of the plot Px is deduced from said coordinates. Alternatively, the identifiers Px and the location Lx can form a single piece of data.

[0034] In embodiments, other data may further be associated with each IDX identifier. For example, at least one of the following data may be supplied to the database 2: - a number Nx of flowers of the inflorescence, counted or estimated by an operator and transmitted to the controller 1 via a device 3; - an OP_REPX identifier of an operator carrying out the listing and / or of the device 3 via which the data is sent to the controller 1.

[0035] Once listed, the inflorescences can be subject to a planning phase. The planning phase generally aims to predict the actions to be carried out at the scale of a plot, a group of plots or all of the plots. Since the targeted articles have an asynchronous development, the planning phase therefore involves inflorescences with heterogeneous stages of development. In other words, among the inflorescences taken into account in the planning phase for a plot Px, some inflorescences have only just been listed, that is to say, identified and recorded in the system, while others have reached or passed the harvesting stage and have already been the subject of phases other than listing, which will be described below.

[0036] In the example described here, the planning phase comprises an operation S04 for determining a future date or a range of future dates for control D_PLAN_CALX for each of the inflorescences identified by an identifier IDX. Since the physical action of the control can be optional, the operation for planning the corresponding dates is also optional. The operation S04 is, here, implemented by the calculation unit 4.

[0037] In the example described here, the planning includes the implementation of algorithms from the data stored in the database 2. In a simple example, the control date for each identifier IDX is calculated as the date after a pre-established fixed duration since the listing date D_REPX. A fixed duration of between 8 and 13 weeks can for example be used, in particular for the cultivation of bananas. For example, when the duration between listing and harvest is expected to be 12 weeks, the control date can be that of the expected harvest from which 2 to 5 days are subtracted. In other examples, the algorithm implemented can be refined to present more precise and relevant results, adapted to the nature of the articles, the environmental conditions and / or the available data. In particular, the algorithm implemented can be built to implement, at least in part, agronomic models, known per se or not.

[0038] Among the potentially accessible data that can be taken into account in the algorithm, past (measured and therefore certain) and / or forecast (estimated and therefore uncertain) meteorological data are particularly relevant. Similarly, the intrinsic values ​​of the dates (and not only the durations between two dates) can be retained to take seasonality into account. Geographical conditions can also be retained as calculation parameters, such as the altitude and / or orientation of the terrain when this can have an influence on the meteorological conditions experienced by the agronomic articles, and therefore their development. In one example, the control date D_PLAN_CALX is calculated based on cumulative temperature, light and / or water that the inflorescence is expected to receive.The cumulative quantities can be estimated (predicted in advance), in particular based on the aforementioned data (meteorology and / or environmental and geographical characteristics). In addition, the level of individualization of the calculations for each inflorescence or for a set of inflorescences can be selected according to the desired precision. In other words, the granularity of the calculations can be adapted at will. It can thus be considered that the meteorological and / or environmental data are homogeneous at the scale of the cultivation area as a whole, or they can be specific to each plot (based on the plot identifier Px) or even specific to each inflorescence (based on the location Lx).

[0039] In the example described here, the planning phase comprises an operation S05 for determining a future harvest date or a range of future harvest dates D_PLAN_RECX for each of the inflorescences identified by an identifier IDX. If the harvest itself is generally necessary, planning it in advance is not mandatory. The operation of planning the corresponding dates is therefore optional. Operation S05 is, here, implemented by the calculation unit 4.

[0040] The implementation of the harvest planning operation S05 may be substantially similar to the control planning operation S04 described above. In the example described here, the planning includes the implementation of algorithms from the data stored in the database 2. In one example, the harvest date for each identifier IDX is calculated as the date calculated after a pre-established fixed duration from the listing date D_REPX or from the control date D_CALX when it exists. A fixed duration of between 9 and 14 weeks from the listing date may for example be used, in particular for the cultivation bananas. In other examples, the implemented algorithm can be refined to present more precise and relevant results, adapted to the nature of the articles, the environmental conditions and / or the available data. In particular, the implemented algorithm can be built to implement, at least in part, agronomic models, known per se or not. Among the potentially accessible data that can be taken into account in the algorithm, past (measured and therefore certain) and / or forecast (estimated and therefore uncertain) meteorological data can be selected. Similarly, the intrinsic values ​​of the dates (and not only the relative values ​​of the durations) can be retained to take seasonality into account.Geographical conditions can also be considered as parameters in the calculations, such as altitude and / or terrain orientation when this may have an influence on the weather conditions experienced by agronomic items, and therefore their development. In one example, the harvest date D_PLAN_RECX is calculated based on (cumulative) quantities of temperature, light and / or water to be received by an inflorescence or an area. Said quantities can be estimated (predicted in advance), in particular based on the aforementioned data (meteorology and / or environmental and geographical characteristics). In addition, the level of adjustment of the calculations to each inflorescence can be selected according to the desired precision. In other words, the granularity of the calculations can be adapted.It can thus be considered that the meteorological and / or environmental data are homogeneous at the scale of the cultivation area as a whole, or they can be specific to each plot (depending on the plot identifier Px) or even specific to each inflorescence (depending on the location Lx)•.

[0041] Operations S04, S05 for determining a control and / or harvesting may also include the implementation of algorithms including specific limits or rules. For example, particularly for banana cultivation, a maximum duration between the listing of the inflorescence and the harvesting of the inflorescence (normally transformed into a bunch in the case of bananas) may be pre-established. Thus, the harvest date (or range of dates) is calculated so as to correspond to a cumulative quantity of temperature (or other energy sources) presumed to correspond to that necessary to achieve a target size or level of development. But a maximum development duration may also be set so that, even in the absence of the conditions theoretically allowing the target level of development to be reached, it is hoped to harvest articles, although less developed, which will not yet have degraded.For example, this helps reduce the risk of fruit rotting on the vine in adverse weather conditions.

[0042] The parameterization of the algorithms and their precision are the responsibility of the professional person who will adapt them to the context, in particular to the nature of the items cultivated, the geographical conditions, the specific constraints and the objectives sought.

[0043] Operations S04, S05 for determining a check and / or harvest may also include, in addition to planning dates, planning a development indicator. The terms “development indicator” are used here in their generic meaning to refer to any agronomically relevant indicator in the relevant field of application. For example, we often speak of “size” to designate one or more dimensions of fruits or vegetables. The mass of the edible parts may also serve as a development indicator. The colorimetry of certain parts of plants may also serve as a development indicator for certain plant species. Thus, when the check and / or harvest date is set according to a target size as in the previous example, the development indicator is both an input parameter of the algorithm and also a target output parameter.In examples where time limits before control and / or harvest are established, a development indicator at the deadline (other than the target one) may be determined.

[0044] Once operations S04, S05 for determining dates of the control and / or the harvest have been implemented, an operation S06 for feeding the database 2 is implemented: the dates (or date ranges) D_PLAN_CALX and / or D_PLAN_RECX previously determined are entered in the database 2. It will be noted here that said data may be new or consist of an update of the pre-existing data values ​​in the database 2. For example, the harvest date may be determined from the listing phase, then be updated during a subsequent control operation.

[0045] A control phase can be implemented. The control phase can include operations, implemented by one or more operators in the field, to verify the development of an inflorescence. Such checks usually make it possible to verify that the development is proceeding normally and to detect any anomalies (destruction or disappearance of an inflorescence for example). This control phase can for example be called “pre-calibration” when one of the checks consists of checking the size of a fruit during its development, on the vine and before harvest. Here, the control phase also includes an operation S07 of feeding the database 2 with control data. The identifier IDX of a previously listed inflorescence is associated with control data, for example entered by an operator via a device 3. The data can for example include: - an effective date / time of the D_CALX control; - a measurement or estimation of a CALX control indicator of at least one fruit from the inflorescence on the effective date of the check; - a forecast harvest date D_PLAN_RECX.

[0046] In this example, the effective date of control and the measurement or estimation of the development indicator CALX come from an entry by an operator while the forecast harvest date can result from a determination implemented by the calculation unit 4 from the data then available in the database 2, including those resulting from the control where applicable. This determination can be implemented for the first time or be an update of a previously determined value. In the example of bananas, the development indicator can for example be a pre-calibration, consisting of measuring the size of one or several “fingers” of “hands” of the inflorescence (then become a “bunch”).

[0047] For each inflorescence, several control phases can be implemented before the harvest phase.

[0048] During a harvesting phase, operations substantially similar to those of the control phase may be implemented. For example, the harvesting phase may comprise a feeding operation S08 of the database 2 with harvesting data. The identifier IDX of a previously listed inflorescence is associated with harvesting data entered via a device 3, either used by an operator or integrated into third-party devices such as packaging stations. Such packaging stations receive the articles immediately after the harvest itself. The harvesting data may for example comprise: - an effective date / time of the harvest D_RECX; and - a measurement or estimate of a CALX control indicator of at least one fruit from the inflorescence on the actual date of harvest.

[0049] It is specified here that the harvesting phase means the act of collecting the item itself (separation from the tree for example) but may include at least in part packaging operations when they are carried out concomitantly or shortly after. In the case of bananas for example, the aforementioned operation S08 may be implemented not at each recovery of a bunch from its tree but rather at the end of a harvest day. Operation S08 may for example be carried out in a partially centralized manner for a plurality of inflorescences. The freshly harvested items are grouped in a station provided for this purpose in preparation for their packaging for transport.Thus, the inflorescences, which have become bunches, can for example be weighed one after the other while a reader scans their IDX identifier. The mass, as an indicator of development, can then be transmitted and recorded in the database 2, associated with the corresponding IDX identifier.

[0050] The method may comprise, at any time, an operation S09 of extracting data from the database 2. The extracted data may, for example, take the form of a LIS list, a MAP map or an AGE calendar of the inflorescences for which a check and / or a harvest is planned on a preselected or current date based on the data in the database 2. Such data extraction makes it possible to facilitate the planning of a set of operations to be carried out by operators in a plot P or a zone P; of plot P on a given date. This also facilitates, if necessary, the automation of at least some of the operations. Such extraction makes it possible to geographically guide an operator from one inflorescence to another independently of the operation to be carried out. The operator's path can then be optimized independently of the heterogeneous stage of development of the inflorescences and the corresponding operations to be implemented.The extracted data can be transmitted to the operators, for example via a device 3 equipped with a screen, for example in the form of a route and stages corresponding to operations to be carried out.

[0051] Another data extraction operation S10 can be implemented. Rather than extracting data at the scale of an IDX inflorescence, data can be extracted in aggregated form, for example at the scale of a geographical area, such as a plot P, of inflorescence development stages or combinations of such parameters. The information derived therefrom is generally representative because it is based on all the inflorescences in the area, and not on a sample whose representativeness could be low. In addition, the completeness of the data combined with the asynchronous nature of the articles makes it possible to obtain information relating to all the development stages at each moment, unlike any other monitoring system known elsewhere.If necessary, data can be grouped by inflorescence development stage, for example to identify and isolate an anomaly that would be specific to a particular development stage. Such data extractions can, for example, make it possible to quickly identify (without waiting for a particular season) a growing area in which a disease detrimental to good development would develop. Rapid and precise measures can then be taken to contain the anomaly, limit the spread of a disease (pests, fungi, etc.) and / or eliminate it quickly. Of course, this makes it possible to carry out particularly targeted actions while limiting the quantity of plant protection products used, or even to implement alternative treatment techniques that are effective only when the area to be treated or the number of inflorescences remains low.The advantages in terms of costs, ecology and operators' exposure to phytosanitary products are easily deduced.

[0052] By way of non-limiting example, the applicant was thus able to improve the treatment of black Sigatoka affecting banana plants. Industrial application

[0053] The present technical solutions can be applied to the production of agronomic articles with asynchronous behavior, in particular to the cultivation of bananas.

[0054] The present disclosure is not limited to the examples of methods, systems, programs and physical supports of such programs described above, only by way of example, but it encompasses all the variants that may be envisaged by those skilled in the art within the framework of the protection sought. List of reference signs

[0055] - 1: controller; - 2: database; - 3: device; - 4: calculation unit.

Claims

Claims

1. Method for tracking agronomic articles with asynchronous behaviors comprising, during a listing phase: a. assigning (SOI) an IDX identifier to each inflorescence not previously listed in a plot of cultivation of the agronomic articles; b. physically affixing (S02) a marker around or in the immediate vicinity of each of the inflorescences, said marker carrying the assigned IDX identifier; c. feeding (S03) a database (2) so that each of said inflorescence IDX identifiers is associated with at least the following listing data: - a listing date / time D_REPX; - an identifier of said plot Px; - location data Lx in said plot.

2. Method according to claim 1 further comprising, during a planning phase: d. determining (S04, S05), for each of the inflorescence identifiers IDX, a date or a range of future pre-calibration dates D_PLAN_CALX and / or harvest D_PLAN_RECX, as well as a predicted value of at least one development indicator DEVPLAn_cal_x and / or DEVPLan_rec_x based on the associated data in the database (2); and e. feeding (S06) the database (2) with said dates D_PLAN_CALX, D_PLAN_RECX and corresponding development indicator values ​​DEVCal_x and / or DEVrEC_x.

3. Method according to one of the preceding claims further comprising, during a control phase: f. feeding (S07) the database so that at least the following control data are associated with the identifier IDX of a previously listed inflorescence: - an effective date / time of control D_CALX; - a measurement or an estimation of at least one development indicator DEVCal_x of at least one fruit from the inflorescence on the effective date of control; - a forecast harvest date D_PLAN_RECX.

4. Method according to one of the preceding claims comprising in furthermore, during a harvest phase: g. feed (S08) the database so that the identifier IDX of a previously listed inflorescence is associated with at least the following harvest data: - an effective date / time of harvest D_RECX; - a measurement or an estimate of at least one development indicator DEVrec x of at least one fruit from the inflorescence on the effective date of harvest.

5. Method according to one of the preceding claims further comprising: h. extracting (S09) a list (LIS) or a map (MAP) of the inflorescences for which a control or a harvest is planned on a preselected or current date according to the data of the database (2), so that a planning of a set of control and / or harvest operations in a plot P or an area P; of plot P on said date is established and then implemented.

6. Method according to one of the preceding claims further comprising: i. identifying the inflorescence by its IDx identifier when weighing said inflorescence and feeding the database (2) with the mass obtained.

7. Method according to one of the preceding claims further comprising: j. extracting (S 10) at least part of the data from the database (2) according to the geographical position of the inflorescences so that the geographical extent for which the data is extracted can be selected.

8. System for tracking agronomic articles with asynchronous behaviors comprising a controller (1) capable of accessing a database (2), and a plurality of devices (3), each of the devices (3) being connected or capable of being connected to the controller (1) so as to supply the database (2) with data via the controller (1), each of the devices (3) being further configured to acquire data sets, each data set including at least the following listing data associated with each other: - a listing date D_REPX; - an identifier of said plot Px; - a location data Lx in said plot.

9. System according to the preceding claim further comprising a calculator (4) configured to: d. determine (S04, S05), for each of the inflorescence identifiers IDX, a date or a range of future pre-calibration dates D_PLAN_CALX and / or harvest D_PLAN_RECX, as well as a predicted value of at least one development indicator DEVPLAn_cal_x and / or DEVPLan_rec_x based on the associated data in the database (2); e. feed (S06) the database (2) with said dates D_PLAN_CALX, D_PLAN_RECX and corresponding development indicator values ​​DEVCal_x and / or DEVrec x; and / or h.extract (S09) a list (LIS) or a map (MAP) of the inflorescences for which a control or a harvest is planned on a preselected or current date according to the data of the database (2), so that a planning of a set of control and / or harvest operations in a plot P or an area P; of plot P on said date is established then implemented.

10. System according to one of claims 8 and 9, in which the devices (3) are further equipped with a human-machine interface and configured to provide, via the human-machine interface, a list (LIS) or a map (MAP) of the previously listed inflorescences for which a check or a harvest is planned on a preselected or current date.

11. Computer program comprising instructions for implementing the method according to one of claims 1 to 7 when this program is executed by a processor.

12. Non-transitory recording medium readable by a computer on which is recorded a program for implementing the method according to one of claims 1 to 5 when this program is executed by a processor.

Images