WO2013096716A1 - Optimisation de réglages de boucle fermée à l'aide de mesure de recettes - Google Patents

Optimisation de réglages de boucle fermée à l'aide de mesure de recettes Download PDF

Info

Publication number
WO2013096716A1
WO2013096716A1 PCT/US2012/071124 US2012071124W WO2013096716A1 WO 2013096716 A1 WO2013096716 A1 WO 2013096716A1 US 2012071124 W US2012071124 W US 2012071124W WO 2013096716 A1 WO2013096716 A1 WO 2013096716A1
Authority
WO
WIPO (PCT)
Prior art keywords
machine
revenue
fleet
metric
settings
Prior art date
Application number
PCT/US2012/071124
Other languages
English (en)
Inventor
Christopher O'neil
Original Assignee
Agco Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Agco Corporation filed Critical Agco Corporation
Publication of WO2013096716A1 publication Critical patent/WO2013096716A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/04—Forecasting or optimisation specially adapted for administrative or management purposes, e.g. linear programming or "cutting stock problem"
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
    • G06Q50/02—Agriculture; Fishing; Forestry; Mining

Definitions

  • This invention pertains generally to methods and systems for supporting agricultural operations, and more particularly to adjusting machine settings.
  • precision farming techniques can reduce product, operator and equipment costs.
  • automated guidance systems relying on geo-positioning satellites for accurate location data, and on user input for designated tasks, can reduce operator error and fatigue, further mitigating costs.
  • machine settings can be adjusted to improve the revenue ratio either by increasing the yield or decreasing operational costs.
  • all machines in a fleet are initialized with the same settings prior to heading out to the fields for a work assignment.
  • the expectation that all machines will perform equally well with identical settings is rather unrealistic.
  • a system can include a telemetry unit (TU) configured to receive and transmit machine data, and a fleet revenue assessment system (FRAS) configured to receive said machine data and determine a real-time revenue metric.
  • a FRAS is part of a fleet management system at a remote location from the TU.
  • the TU can be configured for communication with the fleet management system over a communications network, such as a cellular network.
  • the FRAS can be configured to receive data from a plurality of machines, and determine a revenue metric for each.
  • the plurality of revenue metrics can be aggregated to provide a fleet average revenue metric.
  • An example system can be configured to map one or more machine revenue metrics to provide a dynamic revenue/loss view of a field.
  • a system can be configured to assess a revenue metric to determine whether an opportunity exists to increase machine or fleet revenue through adjustments to machine settings.
  • a system can be configured to automatically adjust machine settings to improve the revenue metric.
  • An example FRAS system can comprise a machine revenue metric module (MRMM) configured to determine a revenue metric for one or more individual machines; a fleet revenue metric module (FRMM) configured to determine a fleet revenue metric based on machine revenue metrics; a revenue metric mapping module (RMMM) configured to map one or more revenue metrics; and a revenue metric assessment module (RMAM) configured to assess machine or fleet revenue metrics, and a machine settings adjustment module (MSAM) configured to determine and implement machine settings adjustments.
  • a system of the invention can include a machine settings optimization module (MSOM) at the machine configured to cooperate with an MSAM to implement adjustments.
  • a method of the invention can include: determining a machine revenue metric, determining a fleet revenue metric, mapping a revenue metric, assessing a revenue metric, and automatically adjusting machine settings based on a revenue metric.
  • FIG. 1 A depicts an example system for fleet revenue ratio
  • FIG. 1 B depicts an example system of the invention.
  • FIG. 2 depicts an example system of the invention.
  • FIG. 3 depicts an example fleet revenue assessment system (FRAS)
  • FIG. 4A depicts an example machine record.
  • FIG. 4B depicts an example fleet record.
  • FIG. 5A depicts an example revenue metric mapping.
  • FIG. 5B depicts an example revenue metric mapping.
  • FIG. 6 depicts a flow diagram of an example method of the invention.
  • FIG. 7 depicts an example method of the invention.
  • an example system 100 can include one or more agricultural machines, represented here by machines 102, 104, 106, equipped with a telemetry data unit (TU) 1 10.
  • the TU 1 10 can be configured to provide machine data, such as machine identification, location, and state information, over a communications network 120 to a fleet management system (FMS) 130 equipped with a Fleet Revenue Assessment System (FRAS) 140.
  • FMS fleet management system
  • FRAS Fleet Revenue Assessment System
  • the FRAS 140 can be configured to determine a real-time revenue metric for each of the machines 102, 104, and 106 as well as a fleet average revenue for the plurality of machines.
  • the example system 100 is configured to optimize machines settings through closed loop adjustment based on a revenue metric determined by the FRAS 140.
  • FIG. 1 B shows a block diagram 150 that can represent the system 100 for closed loop optimization of machine settings.
  • Harvester settings at block 152 can be provided to a revenue metric determination block 154.
  • Harvester settings can include the settings for such machine parameters as speed, engine revolutions, implement height and clearance distances, and the like. They can comprise actual current settings at a machine, or the standard settings typically applied to machine of a particular type.
  • the revenue metric determination block 154 can also receive current yield and loss monitors from the plurality of machines in a fleet, represented by block 156 to determine a revenue metric such as a machine revenue ratio for each machine in a fleet, and a fleet average revenue ratio.
  • Block 158 represents the machine settings optimization process by which optimum settings for achieving an improved revenue metric are determined.
  • Block 160 represents implementing the changes to machine settings, which can be performed through cooperation of the FMS 130 and the particular machine 102, 104, 106.
  • the agricultural machines 102, 104, 106 can be in the form of an agricultural vehicle, by way of example, but not limitation, a combine harvester configured to cut, thresh and winnow crop product.
  • the machines 102, 104, 106 can be equipped with any of a variety of implements, such as a standard header, wheat header, corn header, etc., and can include a flight elevator for transporting grain up the feederhouse into the combine, and a crop bin for collection of winnowed product.
  • the machines 102, 104, 106, and any attached implement may be provided with a variety of sensors, actuators, hydraulics and other tools to monitor and control various machine and implement states.
  • the TU 1 10 can be embodied as a unit configured to receive input from various machine sensors and tools, and transmit the machine data.
  • the TU 1 10 can comprise a data recorder configured to receive and record apparatus data from a plurality of sources, coupled to a data transmitter configured to transmit apparatus data received at the data recorder to the FMS 130.
  • the TU 1 10 can be configured to provide apparatus/machine data to the FMS130 by any suitable means, by way of example, but not limitation, by communication over the communication network 120, which can include one or more networks, for example a local area network (LAN) and a wide area network (WAN).
  • a wireless communications system, or a combination of wire line and wireless may be utilized to communicate apparatus data.
  • Wireless can be defined as radio transmission via the airwaves. However, other transmission techniques including, but not limited to, infrared line of sight, cellular, microwave, satellite, packet radio, and spread spectrum radio can also be employed.
  • the FMS 130 can include one or more devices configured for communication over a communications network.
  • one or more computer servers coupled to a modem for communication capability can be included at the FMS 130.
  • the FMS 130 can include one or more dedicated servers, such as an application server configured to process data associated with a particular software application, a verification server configured to determine whether a user is authorized to communicate with the FMS 130, as well as any other servers or other devices required to support a system for determining machine and fleet revenue metrics for a plurality of machines.
  • the FMS 130 can include the FRAS 140 for determining a revenue metric for each of the machines 102, 104, 106, using machine data transmitted by the TU 1 10.
  • the FRAS 140 can include one or more components or modules that can comprise hardware, software, firmware or some combination thereof.
  • a module can be embodied as an application executed at a computing device or server at the FMS 130.
  • the FRAS 140 can be configured to determine an average revenue metric for the fleet, and further be configured to compare individual machine metrics to each other or to a fleet metric to determine whether adjustments to machine settings should be made to improve machine and overall fleet performance.
  • the FRAS 140 can be configured to implement settings adjustments.
  • FIG. 2 shows an example operating environment 200 that can be associated with the system 100 and includes a TU 210, one or more sensors 212 a...n, a positioning system 214, a processor 216, and an electronic control unit (ECU) 218.
  • a data acquisition module (DAM) 222 can be included for
  • the TU 210 can be configured to receive data from a plurality of sensors 212a..n, as well as other input associated with the agricultural machine 102.
  • a sensor 212a can be positioned at a crop bin and configured to provide information regarding the weight or volume of harvested crop collected.
  • a sensor 212b can be positioned at a supply container, and configured to provide data representing the volume of consumable product remaining.
  • a sensor 212c can provide input associated with the state of a power take-off (PTO) on the agricultural machine 102.
  • PTO power take-off
  • the type and location of sensors can vary in accordance with the type of agricultural machine, tool and/or implement.
  • the sensors 212a-n can comprise mechanical or electrical sensors as well as electronic assemblies or modules. Further non-limiting examples include sensors that measure the height of an implement, machine speed, ignition state, and the like.
  • the TU 210 can receive status data from various subsystems or modules at the machine 102.
  • the TU 210 can receive data from an electronic control unit (ECU) 218 configured to control various aspects of an apparatus or an implement.
  • ECU electronice control unit
  • the ECU 218 can be embodied as an autosteer system such as the Auto-GuideTM system manufactured by AGCO® of Duluth, GA.
  • the TU 210 can be configured to receive information from the ECU 218 regarding current machine and implement state. For example, vehicle speed, rpm and direction can be provided by the Auto-Guide system, as well as information regarding the type of implement attached and its current setting position, such as raised or lowered, engaged or unengaged.
  • the TU 210 can be configured to receive data directly from various sensors or systems.
  • the components of the example operating environment 200 can be configured to form nodes for a controller area network (CAN) bus that provides serial communication capability between nodes, or, alternatively, can be communicatively coupled by other means.
  • input from various sensors/systems can be received at the processor 216, configured to control and coordinate operation of and interaction among various machine apparatus and components, and provided to the TU 210 in a compatible format.
  • CAN controller area network
  • the TU 210 can comprise a data receiver 202, a data recorder 204 and a data transmitter 206.
  • the data recorder 204 can be configured to record data received at the TU 210.
  • the data transmitter 206 can be configured to transmit data recorded at the data recorder 202. In an example embodiment, the data transmitter 206 can be configured to transmit to the FMS 130 over the
  • TU 210 data acquisition and transmission can be controlled by the DAM 222, which can comprise hardware, software, firmware or some combination thereof.
  • the DAM 222 can be in the form of an application executed at the processor unit 216.
  • the DAM 212 can be embodied as a dedicated device such as, but not limited to, a microprocessor configured to control the TU 210 operation.
  • the positioning system 214 can be configured to provide a geographical location for the machine 102.
  • the positioning system 214 can include a global positioning system (GPS) or global navigation satellite system (GNSS) receiver configured to receive satellite signals and determine a geographical location therefrom, as known in the art.
  • Input from the positioning system 214 can be used to provide location data, as well as velocity data.
  • GPS global positioning system
  • GNSS global navigation satellite system
  • the MSOM 220 can be configured to cooperate with the FRAS 140 to automatically adjust settings at a machine.
  • the MSOM 220 can be configured to adjust settings based on a prompt received from the FRAS 140.
  • the MSOM 220 can comprise a look-up table or an algorithm to determine the machine parameters to be adjusted, such as rpm, speed, etc and the adjustments to be made.
  • the FRAS 140 can be configured to determine the machine adjustments and provide them to a machine, for example over the network 120. Adjustment
  • Constant Flow is an embodiment of MSOM.
  • Constant Flow software module will alter the engine RPM, Machine Speed, Rotor speed, concave settings, sieve etc to maintain a constant flow of material. Thus if a section of land is momentarily filled with less dense crop the machine speeds up and the slows down when the field becomes more dense with crop.
  • This invention is stating that when multiple machines are in an area, they can communicate the field effects so that the Constant Flow feature can predict when it will make its adjustments before actually entering the portion of the field.
  • the CF must wait for several meters before its sensors are able to detect that the land has dropped /increase in crop density, so the communication between machine reduces this inefficiency of adjustment.
  • the first machine does experience the delay in making the adjustment, but the remaining machines can be updated in advance of arriving at that section of the field.
  • the FMS 130 can be embodied as an FMS 330 depicted in FIG. 3.
  • the FMS 330 can comprise a central computing device (CCD) 332, a database 338 coupled to the CCD 332, and a fleet operations subsystem (FRAS) 340 coupled to the CCD 332 and the database 338.
  • the CCD 332 can comprise a processor 334, a memory 336 that can comprise read-only memory (ROM) for computing capabilities and random access memory (RAM), a removable disc (not shown), and/or other devices with data storage capabilities, and a communications modem (not shown) for communications capabilities.
  • ROM read-only memory
  • RAM random access memory
  • communications modem not shown
  • the CCD 332 can be implemented using a personal computer, a network computer, a mainframe, or microcomputer-based workstation.
  • the database 338 can be configured to store data in various structured arrangements, for example in various accessible records.
  • the database 338 can be embodied as a separate data storage device or as part of the memory 336 resident at the CCD 332.
  • records can be indexed and maintained by machine, fleet, and/or operator.
  • the FRAS 340 can include one or more modules configured to perform various revenue assessment related functions.
  • Each module can be embodied as hardware, software, firmware or some combination thereof.
  • a module can be associated with a dedicated processing device.
  • a module can be configured to interact with the processor 334.
  • a module can be in the form of an application executed at the processor 334.
  • a module can be embodied as an application service configured to cooperate with an application executed onboard the machines 102, 104, 106.
  • the exannple FRAS 340 can include a machine revenue metric module (MRMM) 342, a fleet revenue metric module (FRMM) 344, a revenue metric mapping module (RMMM) 346, and a revenue metric assessment module (RMAM) 348.
  • the MRMM 342 can be configured to determine a metric or measure/quantifier of machine income or revenue.
  • the MRMM 342 can be configured to determine total revenue, net profit or loss, or some other measure or quantifier of yield or revenue to provide a revenue metric.
  • the MRMM 342 is configured to determine a revenue ratio, defined as revenue divided by costs associated with its production.
  • the MRMM 342 can be configured to receive machine data associated with a particular machine and determine in real-time the potential revenue produced by the machine.
  • the MRMM 342 can receive machine data pertaining to the type and weight of machine yield, i.e. the harvested crop collected in a crop bin at the machine.
  • crop type can be input by an operator through a user interface at the machine 102, and subsequently identified in TU 210 transmissions to the FMS 330.
  • implement data such as header type can be provided by the ECU 218 to the TU 210, which can in turn transmit it to the FMS 330, where it can be used to determine crop type.
  • a standard header can be associated with cereal grains, a wheat header associated with wheat, a corn header, associated with corn, a flex platform associated with soybeans, etc.
  • the MRMM 342 can be configured to determine a real-time crop unit price, for example, the MRMM 342 can be configured to obtain current commodity pricing from the internet via a modem (not shown)at the CCD 332.
  • the MMRM 342 can use the real-time unit price and the machine yield to determine the revenue generated by the machine.
  • the MRMM 342 can be configured to determine a cost associated with generating its projected revenue. Several factors can be considered in the cost determination; by way of example, but not limitation, operator hourly wage, number of operator work hours, fuel consumption, and fuel unit cost. In an example embodiment, the number of operator work hours can be determined from a machine start time and current time.
  • the positioning system 214 can include a date/time stamp in its location calculations which can begin at engine start-up.
  • the TU 210 can transmit date and time data with machine location data to the FMS 330.
  • the MRMM 342 can use the initial time stamp of the day and the most recent time stamp to determine the number of hours worked. Operator wage can be provided by a fleet manager and stored at the FMS 330, for example at the database 338. Fuel consumption can be
  • the TU 210 can receive initial fuel tank data from a sensor at the machine fuel tank, or from the ECU 218, when an operator starts up the machine.
  • the initial fuel level can be transmitted by the TU 210 to the FMS 330 where it can be stored, for example at the database 338 in a format retrievable by the MRMM 342.
  • subsequent fuel levels can be detected and provided to the TU 210 for transmission to the FMS 330.
  • machine fuel consumption can be determined.
  • Fuel cost can be determined in a variety of ways.
  • a fleet manager can provide actual fuel cost information via user input to the CCD 332, an average fuel cost per gallon can be provided by user input to the CCD 332, or the MRMM 342 can be configured to retrieve spot market price of fuel from an internet source.
  • the MRMM 342 can be configured to use fuel unit price and fuel consumption to determine fuel cost. If desired, other costs, such as prorated insurance costs, maintenance costs, and the like can be provided to the FMS 330 by a user and stored, for example at the database 338.
  • the MRMM 342 can be configured to retrieve the costs and include them in the machine cost determination.
  • a machine revenue ratio can be determined by dividing projected revenue by cost.
  • the MRMM 342 can be configured to determine a machine revenue ratio; however, it is contemplated that other performance measures or quantifiers can be determined.
  • the MRMM 342 can be configured to determine machine profit or loss by subtracting machine costs from revenue produced by the machine.
  • the MRMM 342 can be configured to determine revenue, costs, and revenue ratios for a plurality of machines in a fleet. Each machine can provide its current location to the FMS 330 via TU 210 transmission of location data that can be provided by the positioning system 214. Current machine location can be stored at the database 338 in a machine record that can also include the machine revenue ratio determined at the MRMM 346.
  • FIG. 4A shows an example 400 of machine record that can be maintained at the database 338.
  • machine identity can be provided in the header of TU 210 messages to the FMS 330 so that machine data contained therein can be associated with the proper machine.
  • Time can be expressed in column 402.
  • time is represented by to (an initial time), t1 , t2, etc. however, it is understood that actual times can be recorded so that time differences between initial and current times can be determined.
  • Machine location coordinates can be expressed in terms of latitude and longitude in column 404, coordinates typically provided by GPS systems.
  • the example 400 can further include a column 406 in which the field in which the machine is located can be identified. Fields can be defined by predetermined parameters, such as longitude and latitude
  • the FMS 330 can be configured to use machine location coordinates and field parameter coordinates to identify the field in which the machine is currently located.
  • the yield for a particular machine as a function of time can be recorded in column 408. For example, yield can be recorded in units of weight that can be used as a basis for calculating current revenue.
  • the cost associated with producing the revenue can be recorded in column 410.
  • Column 412 can include the revenue metric determined for each machine.
  • the FRMM 344 can be configured to determine an average revenue metric for a fleet based on a plurality of individual machine revenue metrics.
  • the FRMM 344 can be configured to determine an average fleet revenue ratio.
  • a fleet can be spread out over a geographical area having a variety of fields, crops, and field conditions, while at other times, a fleet may be assigned to a more limited and homogenous area.
  • the FRMM 344 can be configured to use one or more predetermined criteria for selecting the machines to be included in the determination of the average revenue metric.
  • predetermined criteria can include: 1 ) selecting only those machines harvesting the same crop; 2) selecting only those machines working in the same field; 3) selecting only those machines within a predetermined radius of a predetermined location; 4) selecting only those machines producing at least a minimum yield; 5) selecting only those machines having yield/revenue within a certain percentage of a median yield/revenue, etc.
  • the FRMM 344 can determine an average metric by any of a variety of methods. In an example embodiment, an average value is determined by averaging the individual revenue ratios of the selected machines.
  • the FRMM 344 can be configured to maintain a fleet revenue record, for example at the database 338.
  • FIG. 4B shows a non-limiting example 420 of a fleet revenue record. The record can be compiled at a particular time, indicated in column 422.
  • Column 424 identifies the individual machines in the fleet.
  • the location coordinates of each machine can be indicated in column 426, and the field that each is working in column 428.
  • Machine location and field can be obtained from the machine record 400.
  • the machine revenue metric for each machine for example, the machine revenue ratio, can be provided in column 430.
  • the average fleet revenue metric for example, the average fleet revenue ratio, can be listed in column 432.
  • the RMMM 346 can be configured to map a revenue metric, or a comparison of revenue metrics, as a function of time and location to determine the nominal revenue potential at a field.
  • FIG. 5A shows a mapping 500 of machine revenue ratio for machines A-F in Field 1 at time t1 .
  • the machines A-F can be mapped based on the locations and MRMs provided in columns 426, 430 respectively of the fleet record 420.
  • a statistical mapping can be used to identify those machines having lower than average revenue production. Referring to FIG. 5A, machine F has the lowest revenue ratio of the six fleet machines.
  • the RMMM 346 can be configured to compare each individual machine revenue metric with the fleet metric, and map the comparison, (which can be referred to as a comparison metric) allowing a machine to be compared to other machines and a fleet average in real time.
  • FIG. 5B shows a mapping 520 of comparison metrics, here comparison or machine revenue ratio with fleet revenue ratio, for machines A-F in Field 1 at time t1 .
  • comparison metrics here comparison or machine revenue ratio with fleet revenue ratio
  • the comparison between machine and fleet metrics can be expressed as a percentage that is plotted by location to indicate profitable and non-profitable areas of the field, and identify underperforming machines.
  • predetermined criteria which can be the same or different from the predetermined criteria used at the FRMM 344, can be used to select the machine revenue ratios to be compared to the fleet average ratio.
  • a statistical mapping of the comparison of revenue ratios of all machines in the same field with the fleet average can be provided.
  • the comparison between machine revenue ratio and fleet average revenue ratio for each machine can be stored at the database 338 as part of the machine record, as depicted in column 434 of the record 420 shown in FIG. 4B. It can also be stored in column 414 of the machine record 400. As shown in FIG.
  • the machine F has a machine comparison metric lower than the other fleet machines.
  • the 0.89 value indicates that the current revenue ratio of machine F is only 89% of the fleet average, indicating that it is underperforming in comparison with the other machines.
  • the RMMM 346 can be configured to map revenue metrics other than revenue ratio as well. For example, the RMMM 346 can provide a statistical mapping of individual machine yields or revenues by location, or average fleet revenue by location and/or time.
  • the RMAM 348 can be configured to assess a revenue metric. Values for machine, fleet, and comparison metrics can be considered along with predetermined evaluation criteria in this assessment.
  • the RMAM 348 can be configured to retrieve information from machine and fleet records at the database 338 to perform this evaluation.
  • Predetermined criteria can include minimum expected values for a particular revenue metric, maximum time periods for lower than expected values, minimum expected fleet metrics for a field, etc.
  • the RMAM 348 can be configured to provide determination as to whether an opportunity exists to increase revenue by altering machine operation, either by adjusting machine settings or altering machine instructions or tasks. For example, if machine revenue ratio is less than 90% of the fleet average for longer than 10 minutes, the RMAM 348 can determine that machine settings for the particular machine need to be adjusted.
  • the MSAM 350 can be configured to determine how machine settings are to be adjusted.
  • the MSAM 350 can include a look-up table of optimized adjusted values for particular parameters, such as speed, rpm, header parameters and the like.
  • the MSAM 350 can comprise an algorithm to adjust settings based on current machine settings/states.
  • an algorithm can include changing a setting to a first value if current machine speed and rpm satisfy a first set of conditions, and changing a setting to a second value of current machine speed and rpm satisfy a second set of conditions.
  • Changes can be implemented via control signals transmitted to the TU 210 over the network 120, which can then be provided to the appropriate control node via the CAN bus 235 to adjust machine and implement settings such as machine speed, machine rpm, implement height, conveyor speed, header drum speed, clearance distances, etc.
  • the FMS 330 can be configured to cooperate with the MSOM 220 at a machine.
  • the FMS 330 can be configured to provide a signal via the network 120 to a machine identified as a candidate for settings adjustments.
  • the signal can include the adjustments to be made, or can provide notice to the MSOM 220 to determine and adjust settings.
  • Via the CAN bus 235, the signal can be provided to the appropriate modules, by way of example, but not limitation, the PROC 216 and MSOM 220 to implement adjustments.
  • the FRAS 340 can be configured to provide a report pertaining to revenue metric to a user.
  • a mapping can be presented to a fleet manager as a visual display, by way of example, but not limitation, at a display device coupled to the CCD 332 at the FMS 330, or as a download to a personal computing or communication device.
  • the FRAS 340 can be configured to cooperate with one or more applications to provide a visual display of the mapping as a function of time and location, either at a display device coupled to the FMS 300 or at a remote display device.
  • revenue or machine/fleet revenue metric comparisons can be superimposed on an image of the field being worked.
  • a report can also be in the form of text provided to a fleet manager or an operator.
  • an audio report can be provided by way of telephone.
  • a report can comprise a notice that a machine or fleet revenue is below an expected value, or an advisory message to check machine equipment and settings for possible adjustments.
  • a report can include an alert to a fleet manager that the fleet revenue metric of a field is below desired levels, giving a fleet manager the opportunity to change fleet
  • a report can include notice of automatic settings adjustments for the machine.
  • FIG. 6 shows a flow diagram of an example method 600 that can be practiced as part of a fleet revenue metric determination process.
  • the method can begin in response to the satisfaction of a triggering condition, such as, but not limited to, key ON, engine ignition, or operator input, at which a machine can begin telemetry communication with the FMS 330, for example via the network 120.
  • a triggering condition such as, but not limited to, key ON, engine ignition, or operator input
  • machine data can be provided to the FMS 330.
  • the DAM 222 can trigger activation of the various sensors 212a..n to provide input to the TU 210.
  • sensors 212a..n can be configured to provide input to the TU 210 independent of the DAM 222.
  • a communications bus communicatively couples the TU 210 and the sensors 212a...n, the positioning system 214, the ECU 218 and the processor 216.
  • a controller area network (CAN) bus can provide connectivity between the TU 210 and the sensors
  • the sensors 212a..n can be coupled to the TU 210 via wireless transmission, direct coupling or other communicative means.
  • An example method can include receiving machine data at the processor 216, at which it can be formatted for compatibility with the TU 210 and/or the FMS 330 and then provided to the TU 210.
  • the TU 210 can be configured to receive sensor input continuously, or at designated intervals, for example at intervals controlled by the DAM 222.
  • Machine data can include real-time machine yield data.
  • the crop bin sensor 212a can provide data characterizing the weight of harvested crop product at the crop bin.
  • Machine data can also include current machine location.
  • the positioning system 214 can determine machine location from satellite signals as known in the art, and provide location coordinates to the TU 210 via the CAN bus 235, along with a date/time stamp.
  • Machine data can be recorded at the TU 210 as data points that include machine identification data, data from a plurality sensors and various
  • the DAM 222 comprising hardware, software, firmware or some combination thereof, can control the acquisition and transmission of apparatus data by the TU 210.
  • the DAM 222 can be in the form of software executed at the processor 216.
  • a cooperative initialization and authorization process can be performed prior to transmitting machine data.
  • the initialization communications can comprise service request, machine identification and/or operator identification, verification, configuration, or authorization messages, and/or other messages consistent with FMS 330 partitioning and communication protocols.
  • Machine data can be transmitted by the TU 210 to the FMS 330 via the network 120.
  • the communications network 120 comprises a cellular network, and the machine data comprises current yield information, such as, but not limited to, crop type and weight.
  • machine adjustments can be received.
  • the machine 102 can receive adjustments determined by the FRAS 140, which can be implemented by the processor 216 and/or the MSOM 220.
  • the machine 102 can receive a signal
  • the machine 102 can receive machine and fleet revenue metrics, perform an assessment to determine whether adjustments should be made, and should the determination be in the affirmative, determine and implement the actual adjustments. For example of the fuel consumption of the fleet of machines in a particular section of the field is exceeded by one machine, then a setting can be sent to the machine operator to reduce RPM. The example of Constant Flow would be applicable here. I once heard a fleet manager complain that when his machines are transporting from one field to another that one or two of the machines will be delayed because the operator is taking a break. The FRAS could detect this and send a notice to the operator that their transportation time expectation is below the norm for the fleet.
  • FIG. 7 shows an example method 700 that can be practiced in a fleet revenue determination process.
  • machine data can be received at the FMS 130.
  • machine crop yield data such as 50 kg of wheat
  • a machine revenue metric can be determined, for example, a machine revenue ratio can be determined.
  • the MRMM 342 can obtain market spot pricing for the crop, for example from the internet through a modem (not shown) at the CCD 332 .
  • the MRMM 342 can determine the revenue expected from the current machine yield.
  • the MRMM 342 can further determine the cost of producing the expected machine revenue.
  • operator cost can determined by multiplying hourly wage and hours worked. As stated previously above, operator wage rate can be stored at the database 338. Hours worked can be determined from the difference between initial transmission time stamp and most recent time stamp. Fuel cost can be determined by multiplying price per gallon of fuel and the number of gallons of fuel consumed, which can be derived from initial and current fuel tank sensor data. If desired, additional costs, such as insurance costs, and the like can be stored at the database 338 for retrieval by the MMRM 342. The MRMM 342 can determine a machine revenue ratio by dividing expected revenue by the determined costs.
  • a fleet revenue metric can be determined.
  • the FRMM 344 can determine an average fleet revenue ratio.
  • individual machine revenue ratios can be selected and averaged to provide an average fleet revenue ratio.
  • machine revenue ratios and other relevant information such as machine location, can be retrieved from machine records stored at the database 338 for use in this determination.
  • a mapping of a revenue metric can be performed at the RMMM 346.
  • individual machine revenue ratio can be mapped by time and machine location, as shown in mapping 500 (FIG. 5A).
  • a comparison of machine revenue ratio and fleet revenue ratio can be mapped by time and location.
  • Each machine ratio can be divided by the fleet average revenue ratio to provide a machine revenue comparison metric.
  • the machine revenue comparison metric can be mapped by location to provide a view of fleet revenue production for a field, as shown by the mapping 520 (FIG. 5B).
  • the machine revenue comparison metric can be stored in column 434 of the fleet record 420. Data from the fleet record 420 and machine record can be used in the mapping process.
  • a fleet revenue metric can be mapped by field location, for instance machine metrics for machines in a first portion of a field can be aggregated to provide a fleet metric for that portion of the field, while machines in a different section of the field can be aggregated to provide a fleet metric for the different section.
  • the fleet metrics for the different sections can be mapped to show fleet metrics over the field.
  • a revenue metric can be assessed.
  • the RMAM 348 can use predetermined adjustment criteria or conditions, machine revenue metrics and fleet revenue metrics for this
  • comparison metrics listed in columns listed in columns 412, 414 of the machine record 400, or listed in columns 430, 434 respectively can be user predetermined criteria can include predetermined thresholds, predetermined time periods for which thresholds are exceeded or failed, and the like.
  • An assessment can include a determination as to whether an opportunity exists to improve a revenue metric by altering machine or fleet operation. For example, if the machine revenue comparison metric is 10% below the average for 10 minutes or longer, a determination can be made to adjust machine settings.
  • adjustments to machine settings can be performed to improve a revenue metric.
  • the MSAM 350 can determine adjusted values for one or more machine parameters and provide them to the machine 102 via the network 120.
  • a report can be provided based on a revenue metric.
  • the mapping 520 can be provided to a fleet manager.
  • a message that one or more machines has a poor revenue metric can be provided, or a notice that one or more adjustments have been made to a machine's settings.
  • a revenue metric can be any measure or quantifier of revenue, including, but not limited to total revenue, profit, loss, total yield, average revenue, average yield, or revenue ratio.
  • Individual machine metrics can be determined, as well as a fleet metric.
  • a system can determine a machine metric for each of a plurality of machines in a fleet.
  • a fleet metric can be determined by the aggregation of a plurality of machine metrics.
  • a plurality of machine metrics can be averaged to provide a fleet metric, and the individual machine metrics can be compared to the fleet metric.
  • a system of the invention can be configured to map a revenue metric or a comparison between a machine and a fleet revenue metric to provide a dynamic revenue/loss view of the field.
  • the revenue metric map can be used to more robustly recognize opportunities to improve the revenue metric and eliminate poor field condition artifacts.
  • a revenue metric map can display machine revenue metrics, such as machine revenue ratios, fleet revenue metrics, such as a fleet average revenue ratio, or a comparison between machine metrics and a fleet metric, such as a comparison of machine revenue ratio with a fleet revenue ratio.
  • the mapping can help identify those machines whose subpar performance is likely caused by poor field conditions, as well as machines whose unsatisfactory performance is likely to be the result of non-optimal machine operation.
  • a system of the invention can automatically change a machine's parameters, such as speed, rpm, header settings, etc.
  • a machine's parameters such as speed, rpm, header settings, etc.
  • a look-up table or an algorithm can be used to determine what types of adjustments should be made to optimize performance.
  • a central fleet management system can cooperate with a machine over a communications network to implement the adjustments.
  • a system can provide a report based on one or more revenue metrics. For example, a dynamic revenue view of a field can be provided to a fleet manager in real time. In an example embodiment, if an individual machine revenue ratio falls too far below the fleet average, but it is working under similar field conditions, an alert to that effect can be sent to an operator or fleet manager.
  • a dynamic revenue metric mapping or view of a field can also be used to determine when harvesting a field or portion of a field is no longer profitable. For example, if an average fleet revenue metric indicates a loss, or an
  • a decision can be made by an operator or fleet manager to spend less time on the field, abandon a portion of it, or begin a new task.

Landscapes

  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Strategic Management (AREA)
  • Human Resources & Organizations (AREA)
  • Economics (AREA)
  • Theoretical Computer Science (AREA)
  • General Business, Economics & Management (AREA)
  • Entrepreneurship & Innovation (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • Tourism & Hospitality (AREA)
  • Marketing (AREA)
  • Development Economics (AREA)
  • Quality & Reliability (AREA)
  • Operations Research (AREA)
  • Game Theory and Decision Science (AREA)
  • Life Sciences & Earth Sciences (AREA)
  • Marine Sciences & Fisheries (AREA)
  • Primary Health Care (AREA)
  • Mining & Mineral Resources (AREA)
  • General Health & Medical Sciences (AREA)
  • Health & Medical Sciences (AREA)
  • Animal Husbandry (AREA)
  • Agronomy & Crop Science (AREA)
  • Educational Administration (AREA)
  • Traffic Control Systems (AREA)
  • Control Of Transmission Device (AREA)

Abstract

L'invention concerne des systèmes et des procédés d'optimisation de réglages de machine à boucle fermée en temps réel. Le système peut être configuré pour fournir une vue des recettes/pertes en temps réel d'un domaine pour identifier des machines non performantes dont les performances de recettes peuvent être améliorées en ajustant les réglages pour différents paramètres de machine, tels que la vitesse, les tours-moteur, les réglages de mise en œuvre et autres. Des données de rendement de machine peuvent être fournies à un système d'évaluation de recettes de flotte (FRAS) à distance qui peut être configuré pour déterminer une mesure de recettes de machine, telle qu'un rapport de recettes, pour une pluralité de machines dans une flotte. Des mesures de recettes de machine peuvent être agrégées pour fournir une mesure de recettes de flotte à laquelle des mesures de recettes de machine peuvent être comparées pour identifier des machines non performantes. En éliminant des artéfacts de domaine médiocre, une détermination peut être obtenue quant au point de savoir si les recettes peuvent ou non être augmentées par des ajustements de réglage. Un algorithme ou une table de consultation peut être utilisée pour optimiser les réglages et déterminer les ajustements appropriés.
PCT/US2012/071124 2011-12-21 2012-12-21 Optimisation de réglages de boucle fermée à l'aide de mesure de recettes WO2013096716A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201161578299P 2011-12-21 2011-12-21
US61/578,299 2011-12-21

Publications (1)

Publication Number Publication Date
WO2013096716A1 true WO2013096716A1 (fr) 2013-06-27

Family

ID=45788776

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2012/071124 WO2013096716A1 (fr) 2011-12-21 2012-12-21 Optimisation de réglages de boucle fermée à l'aide de mesure de recettes

Country Status (2)

Country Link
GB (1) GB201200425D0 (fr)
WO (1) WO2013096716A1 (fr)

Cited By (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9892376B2 (en) 2014-01-14 2018-02-13 Deere & Company Operator performance report generation
EP3488686A1 (fr) * 2017-11-22 2019-05-29 Deere & Company Procédé de fonctionnement d'une machine forestière et processeur d'opération mettant en uvre ce procédé
US10311527B2 (en) 2014-01-14 2019-06-04 Deere & Company Agronomic variation and team performance analysis
US10310455B2 (en) 2017-06-19 2019-06-04 Deere & Company Combine harvester control and communication system
US10380704B2 (en) 2014-01-14 2019-08-13 Deere & Company Operator performance recommendation generation
US20190266815A1 (en) * 2018-02-28 2019-08-29 Waymo Llc Fleet management for vehicles using operation modes
US10437243B2 (en) 2017-06-19 2019-10-08 Deere & Company Combine harvester control interface for operator and/or remote user
US10453018B2 (en) 2014-01-14 2019-10-22 Deere & Company Agricultural information sensing and retrieval
US10694668B2 (en) 2017-06-19 2020-06-30 Deere & Company Locally controlling settings on a combine harvester based on a remote settings adjustment
US10782672B2 (en) 2018-05-15 2020-09-22 Deere & Company Machine control system using performance score based setting adjustment
US10963825B2 (en) 2013-09-23 2021-03-30 Farmobile, Llc Farming data collection and exchange system
DE102020105244A1 (de) 2020-02-27 2021-09-02 Wacker Neuson Produktion GmbH & Co. KG System und Verfahren zum Individualisieren und Steuern eines Baugeräts
US11589507B2 (en) 2017-06-19 2023-02-28 Deere & Company Combine harvester control interface for operator and/or remote user
US11789413B2 (en) 2017-06-19 2023-10-17 Deere & Company Self-learning control system for a mobile machine

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040073468A1 (en) * 2002-10-10 2004-04-15 Caterpillar Inc. System and method of managing a fleet of machines
US20110130905A1 (en) * 2009-12-01 2011-06-02 Ise Corporation Remote Vehicle Monitoring and Diagnostic System and Method
US20110288738A1 (en) * 2010-04-19 2011-11-24 Icr Turbine Engine Corporation Multi-fuel vehicle strategy

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040073468A1 (en) * 2002-10-10 2004-04-15 Caterpillar Inc. System and method of managing a fleet of machines
US20110130905A1 (en) * 2009-12-01 2011-06-02 Ise Corporation Remote Vehicle Monitoring and Diagnostic System and Method
US20110288738A1 (en) * 2010-04-19 2011-11-24 Icr Turbine Engine Corporation Multi-fuel vehicle strategy

Cited By (26)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11164116B2 (en) 2013-09-23 2021-11-02 Farmobile, Llc Farming data collection and exchange system
US11941554B2 (en) 2013-09-23 2024-03-26 AGI Suretrack LLC Farming data collection and exchange system
US10963825B2 (en) 2013-09-23 2021-03-30 Farmobile, Llc Farming data collection and exchange system
US11107017B2 (en) 2013-09-23 2021-08-31 Farmobile, Llc Farming data collection and exchange system
US11507899B2 (en) 2013-09-23 2022-11-22 Farmobile, Llc Farming data collection and exchange system
US11410094B2 (en) 2013-09-23 2022-08-09 Farmobile, Llc Farming data collection and exchange system
US11361261B2 (en) 2013-09-23 2022-06-14 Farmobile, Llc Farming data collection and exchange system
US11361260B2 (en) 2013-09-23 2022-06-14 Farmobile, Llc Farming data collection and exchange system
US11151485B2 (en) 2013-09-23 2021-10-19 Farmobile, Llc Farming data collection and exchange system
US11126937B2 (en) 2013-09-23 2021-09-21 Farmobile, Llc Farming data collection and exchange system
US10311527B2 (en) 2014-01-14 2019-06-04 Deere & Company Agronomic variation and team performance analysis
US10453018B2 (en) 2014-01-14 2019-10-22 Deere & Company Agricultural information sensing and retrieval
US10380704B2 (en) 2014-01-14 2019-08-13 Deere & Company Operator performance recommendation generation
US9892376B2 (en) 2014-01-14 2018-02-13 Deere & Company Operator performance report generation
US10310455B2 (en) 2017-06-19 2019-06-04 Deere & Company Combine harvester control and communication system
US10694668B2 (en) 2017-06-19 2020-06-30 Deere & Company Locally controlling settings on a combine harvester based on a remote settings adjustment
US10437243B2 (en) 2017-06-19 2019-10-08 Deere & Company Combine harvester control interface for operator and/or remote user
US11589507B2 (en) 2017-06-19 2023-02-28 Deere & Company Combine harvester control interface for operator and/or remote user
US11789413B2 (en) 2017-06-19 2023-10-17 Deere & Company Self-learning control system for a mobile machine
EP3488686A1 (fr) * 2017-11-22 2019-05-29 Deere & Company Procédé de fonctionnement d'une machine forestière et processeur d'opération mettant en uvre ce procédé
CN111788592A (zh) * 2018-02-28 2020-10-16 伟摩有限责任公司 使用操作模式的车辆的车队管理
WO2019168827A1 (fr) * 2018-02-28 2019-09-06 Waymo Llc Gestion de flotte pour véhicules utilisant des modes de fonctionnement
US20190266815A1 (en) * 2018-02-28 2019-08-29 Waymo Llc Fleet management for vehicles using operation modes
US11062537B2 (en) 2018-02-28 2021-07-13 Waymo Llc Fleet management for vehicles using operation modes
US10782672B2 (en) 2018-05-15 2020-09-22 Deere & Company Machine control system using performance score based setting adjustment
DE102020105244A1 (de) 2020-02-27 2021-09-02 Wacker Neuson Produktion GmbH & Co. KG System und Verfahren zum Individualisieren und Steuern eines Baugeräts

Also Published As

Publication number Publication date
GB201200425D0 (en) 2012-02-22

Similar Documents

Publication Publication Date Title
WO2013096716A1 (fr) Optimisation de réglages de boucle fermée à l'aide de mesure de recettes
WO2013096721A2 (fr) Détermination en temps réel d'une mesure de recettes de flotte
US9269200B2 (en) Real-time evaluation of machine performance for fleet management
US20200221635A1 (en) Field condition determination
EP3570228B1 (fr) Système de commande de machines à l'aide d'un score de performance basé sur le réglage de paramètres
US9668420B2 (en) Crop sensing display
US10251341B2 (en) Farm work machine, farm work management method, farm work management program, and recording medium recording the farm work management program
EP2944179B1 (fr) Détermination du rendement agricole à l'aide de capteurs multiples
US10311527B2 (en) Agronomic variation and team performance analysis
US20140230396A1 (en) Crop sensing
KR102113297B1 (ko) 대지 작업 차량, 대지 작업 차량 관리 시스템, 대지 작업 정보 표시 방법
CN106163261B (zh) 农业机具和农业机具操作者监控装置、系统及方法
US20140249893A1 (en) Agricultural performance information systems and related methods
US20120143642A1 (en) Fleet Management Revenue Assurance
JP2014067309A (ja) 作業機及び作業機の管理システム
US11423305B2 (en) Network-based work machine software optimization
WO2012092599A1 (fr) Évaluation en temps réel des performances d'une machine pour la gestion d'une flotte
US11470775B2 (en) Control of settings on a combine harvester with bias removal
JP5806997B2 (ja) 農作業情報管理装置及び農作業情報管理システム
CN110122045A (zh) 割草机的刀片更换提示方法、装置、存储介质和系统
Isaac et al. Combine harvester econometric model with forward speed optimization
CN102646293A (zh) 新型监控农用机械设备的方法
US20040122894A1 (en) Electronic data exchange system for users acting as both servers and receivers of information
JP6289536B2 (ja) 作業機
Plunkett Choosing Fit for Purpose Open Source AgTech Innovations on a Large Broadacre Mixed Farming Enterprise in Western Australia

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 12859561

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 12859561

Country of ref document: EP

Kind code of ref document: A1