WO2012092592A1 - Détection automatique d'état de machine pour une gestion de parc - Google Patents

Détection automatique d'état de machine pour une gestion de parc Download PDF

Info

Publication number
WO2012092592A1
WO2012092592A1 PCT/US2011/068182 US2011068182W WO2012092592A1 WO 2012092592 A1 WO2012092592 A1 WO 2012092592A1 US 2011068182 W US2011068182 W US 2011068182W WO 2012092592 A1 WO2012092592 A1 WO 2012092592A1
Authority
WO
WIPO (PCT)
Prior art keywords
machine
status
data
state
performance
Prior art date
Application number
PCT/US2011/068182
Other languages
English (en)
Inventor
Lee Schmidt
Lorenz Riegger
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
Priority claimed from US13/341,475 external-priority patent/US9269200B2/en
Publication of WO2012092592A1 publication Critical patent/WO2012092592A1/fr

Links

Classifications

    • G—PHYSICS
    • G08—SIGNALLING
    • G08G—TRAFFIC CONTROL SYSTEMS
    • G08G1/00—Traffic control systems for road vehicles
    • G08G1/20—Monitoring the location of vehicles belonging to a group, e.g. fleet of vehicles, countable or determined number of vehicles
    • 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
    • G07—CHECKING-DEVICES
    • G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C5/00—Registering or indicating the working of vehicles
    • G07C5/008—Registering or indicating the working of vehicles communicating information to a remotely located station
    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C5/00—Registering or indicating the working of vehicles
    • G07C5/08—Registering or indicating performance data other than driving, working, idle, or waiting time, with or without registering driving, working, idle or waiting time
    • G07C5/0841—Registering performance data
    • G07C5/085—Registering performance data using electronic data carriers

Definitions

  • This invention pertains generally to methods and systems for supporting agricultural operations, and more particularly to automatic detection systems.
  • an automatic machine status detection system can include an apparatus data unit (ADU) configured to receive apparatus data associated with an agricultural machine, and a fleet operations subsystem (FOS) communicatively coupled to the ADU and configured to determine a status of the machine using apparatus data received from the ADU.
  • apparatus data can be in the form of input from a sensor positioned on the machine, or on an implement, such as, but not limited to, a tractor, a power take-off (PTO) or a baler or other implement, or input from a system or module at the vehicle, such as a guidance system, or electronic control unit (ECU).
  • the FOS is part of a fleet management system (FMS) configured to communicate with the ADU over a communications network such as a wireless, radio or cellular network.
  • FMS fleet management system
  • an FMS can include one or more servers or communication-enabled computing devices and a data storage device.
  • a FOS can be configured to determine machine status for a plurality of agricultural machines in a vehicle fleet.
  • an FOS can include a status determination module (SDM) configured to determine machine status based on apparatus data.
  • SDM status determination module
  • a machine status can be determined to be "Stopped/Idle”, “Working”, “Transport/Travel”, “Head-Turning” or “Off/Parked”.
  • An SDM can be in the form of software, hardware, firmware or some combination thereof.
  • an SDM can be in the form of an application executed at an FMS server.
  • an SDM can be located and operate onboard an agricultural machine and be communicatively coupled to the ADU. Machine status can then be provided to an FMS over a communications network for fleet management purposes.
  • An example method of the invention can include detecting on/off state of a machine engine, detecting whether a machine is in motion, detecting the rate and magnitude of changes in machine heading, detecting the presence of an implement, detecting the state of an implement and detecting the state of a power take-off (PTO).
  • PTO power take-off
  • An example method for automatically detecting machine status can include receiving apparatus data, and determining machine status using the apparatus data.
  • machine status can be characterized as "Off, "Stopped/Idle", “Working”, “Headland-Turning” or "Traveling”.
  • a method of the invention can include compiling a record of machine status over a period of time. Monitoring the status of a machine can enable improved management of human and material resources, as well as facilitate quicker and more accurate billing and administrative services.
  • An example FOS can include a report generating module configured to generate a report of machine status.
  • a report can be in the form of a visual display.
  • a graphic with an appearance or attribute coded to convey a status can be used to report machine status.
  • FIG. 1 depicts an example system for automatic detection of machine status.
  • FIG. 2 depicts an example operating environment for a system for automatic detection of machine status.
  • FIG. 3 depicts an example fleet management system (FMS).
  • FMS fleet management system
  • FIG. 4 depicts a flow diagram of an example method of the invention. [0013] FIG,
  • an automatic machine status detection system (AMSDS) 100 can include one or more agricultural machines 105 equipped with an apparatus data unit (ADU) 110.
  • the ADU 110 can be configured to provide apparatus data, such as location and apparatus state data, over a communications network 120 to a fleet management system (FMS) 130 equipped with a Fleet Operations System (FOS) 140.
  • FMS fleet management system
  • FOS Fleet Operations System
  • the FOS 140 can be configured to determine a current status for the machine 105.
  • the FOS 140 can further be configured to use a history of machine status to evaluate machine and/or operator performance.
  • the FOS 140 can be configured to generate a report of machine status and performance for fleet management purposes.
  • the agricultural machine 105 can be in the form of an agricultural vehicle, by way of example, but not limitation, a combine harvester, tractor, sprayer, or windrower.
  • the machine 105 can be equipped with a variety of different implements, such as a cultivator, a header, a boom, etc.
  • the machine 105 can be configured to perform various agricultural related tasks, such as, but not limited to, harvesting crop, cultivating, applying crop products, irrigating, and the like, using the various implements.
  • the machine 105 and any attached implement may be provided with a variety of sensors, actuators, and other tools to monitor the various states of apparatus and implements at the machine.
  • the ADU 110 can be embodied as a unit configured to receive input from various apparatus sensors and tools, and further configured to transmit the apparatus data.
  • the ADU 110 can be embodied as a telemetry unit.
  • the ADU 110 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.
  • the ADU 110 can be configured to provide apparatus data to the FMS130 by any suitable means, by way of example, but not limitation, by communication over the FMS130.
  • communication network 120 which can include one or more networks, for example a local area network (LAN) and a wide area network (WAN).
  • LAN local area network
  • WAN wide area network
  • 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 an AMSDS.
  • the FMS 130 can include the FOS 140 for determining a status for the machine 105 using apparatus data transmitted by the ADU 110.
  • the FOS 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 FOS 140 can further be configured to determine the performance of the machine 105 over time, so that a poorly performing machine can be detected, providing a fleet manager or machine operator the opportunity to make adjustments to improve machine and overall fleet performance.
  • FIG. 2 shows an example operating environment 200 that can include an ADU 210, one or more sensors 212 a...n, a positioning system 214, a processing device 216, and an electronic control unit (ECU) 218.
  • a data acquisition module (DAM) 222 can further be included for coordinating and/or controlling ADU 210 operation.
  • the ADU 210 can be in the form of a telemetry unit.
  • the ADU 210 can be configured to receive data from a plurality of sensors 212a..n, as well as other input associated with the agricultural machine 105.
  • 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 210b can be positioned at a supply container, and configured to provide data representing the volume of consumable product remaining.
  • a sensor 210c can provide input associated with the state of a power take-off (PTO) on the agricultural machine 105.
  • 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 ADU 210 can receive status data from various subsystems or modules at the machine 105.
  • the ADU 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 ADU 210 can be configured to receive information from the ECU 218 regarding the work state of an apparatus. For example, vehicle speed and direction can be provided by the Auto-Guide system, as well as information regarding the type of implement attached and its current position, such as raised or lowered, or engaged or unengaged.
  • the ADU 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
  • CAN controller area network
  • 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 ADU 210 in a compatible format.
  • the ADU 210 can comprise a data recorder 202 and a data transmitter 204.
  • the data recorder 202 can be configured to record data received at the ADU 210.
  • the data transmitter 204 can be configured to transmit data recorded at the data recorder 202.
  • the data transmitter 204 can be configured to transmit to the FMS 130 over the communication network 120.
  • ADU 210 data acquisition and transmission such as commencement and termination of data recording, the type of data recorded, and the intervals at which apparatus data is received and transmitted to the FMS 130, 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
  • the DAM 222 can be embodied as a dedicated device such as, but not limited to, a microprocessor configured to control the ADU 210 operation.
  • the positioning system 214 can be configured to provide a geographical location for the machine 105.
  • 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.
  • the ECU 218 can provide machine and/or implement speed and direction data.
  • 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 (FOS) 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 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 and/or operator.
  • the FOS 340 can include one or more modules configured to perform various fleet operations functions. Each module can be embodied as hardware, software, firmware or some combination thereof. By way of example, but not limitation, a module can be associated with a dedicated processing device. In a further example embodiment, a module can be configured to interact with the processor 334. By way of example, but not limitation, a module can be in the form of an application executed at the processor 334. In an example embodiment, a module can be embodied as an application service configured to cooperate with an application executed onboard the machine 105, such as a data acquisition application. In yet a further example embodiment, one or more FOS 340 modules can reside at the machine itself and be configured to interact with an onboard computer or processor, such as the processor 216.
  • the example FOS 340 can include a status determination module (SDM) 342.
  • SDM status determination module
  • the SDM 342 can be configured to receive apparatus data and use it to determine a machine status for the machine 105.
  • machine status can be stored at the database 338 so that a record of machine status over time can be compiled.
  • the FOS 340 can be configured to provide a report of machine status.
  • a report generating module (RGM) 346 comprising hardware, software, firmware or some combination thereof, can be configured to provide a report of machine status.
  • the RGM 346 can be configured to cooperate with one or more applications to provide a visual display of machine status as a function of time and/or location, either at a display device coupled to the FMS 300 or at a remote display device.
  • images indicating machine status can be imposed on an image depicting a geographical map to provide a visual display of machine status as a function of time and location on a display device, such as, but not limited to, a computer monitor or cell phone screen.
  • FIG. 4 shows a flow diagram of an example method 400 for automatic detection of machine status.
  • apparatus data can be received.
  • the SDM 342 can receive apparatus data via ADU 110 transmission to the FMS 330 over the network 120.
  • the apparatus data can include machine identification data, and can also include operator identification data.
  • Machine location data from the positioning system 214 can be included in the apparatus data as well as apparatus data from the sensors 212a-n, and the ECU 218.
  • a time and date stamp can be included in each ADU 210 transmission.
  • apparatus data can be stored at the FMS 330, for example at the database 338.
  • FIG. 5 shows a flow diagram of an example method 500 that can be practiced at the machine 105 as part of a process for determining machine status.
  • the apparatus state for one or more apparatus at a machine can be detected.
  • FIG. 6 shows an example method 600 that can be practiced in the detection of apparatus state data.
  • machine engine state can be detected.
  • an engine sensor, or the ECU 218, can detect whether an engine is operating, i.e. whether it is in an ON or OFF state and provide that state data to the ADU 210.
  • machine motion can be detected. For example, speed can be detected at the ECU 218 or at the positioning system 214 and provided to the ADU 210.
  • machine heading can be detected and provided to the ADU 210.
  • machine heading can be detected by the positioning system 214, or provided by the ECU 218.
  • the PTO state can be detected.
  • a sensor 212c can be configured to detect whether a PTO is operating, and provide data representing PTO state to the ADU 210.
  • the presence of an implement can be detected.
  • one or more sensors 212a..n, for example a sensor 210d can be configured to couple with an implement and provide data indicating the presence of an implement.
  • implement state can be detected.
  • a sensor 210e, or the ECU 218, can be configured to detect whether an implement is in an active/engaged state or in an inactive/transport state and provide data representing the implement state to the ADU 210.
  • apparatus data can be provided to an FOS.
  • the data transmitter 204 of the ADU 210 can transmit apparatus data to the FOS 340 of the FMS 330 over the communications network 120.
  • a DAM comprising hardware, software, firmware or some combination thereof, such as the DAM 222 at the machine 105, can control the acquisition and transmission of apparatus data by the ADU 210.
  • the DAM 222 can be in the form of software executed at the processor 216.
  • FIG. 7 shows an example method 700 that can be practiced in acquisition and transmission of apparatus data for the automatic determination of machine status.
  • 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.
  • a triggering condition such as, but not limited to, key ON, engine ignition, or operator input.
  • an initialization process can be performed. Execution of this process can depend on system configuration.
  • an initialization process can begin with a transmission from the ADU 210 to the FMS 330.
  • the transmission can be a request that a data acquisition application be downloaded to the machine 105. This initial request can be followed by authorization and/ or billing
  • a DAM previously resident on the machine 105 can control initialization communications transmitted by the ADU 210.
  • 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.
  • apparatus data can be received at the ADU 210.
  • a DAM can trigger activation of the various sensors 212a..n to provide input to the ADU 210.
  • sensors 212a..n can be configured to provide input to the ADU 210 independent of a DAM.
  • a communications bus communicatively couples the ADU 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 ADU 210 and the sensors 212a..n.
  • the sensors 212a..n can be coupled to the ADU 210 via wireless transmission, direct coupling or other communicative means.
  • An example method can include receiving apparatus data at the processor 216, at which it can be formatted for compatibility with the ADU 210 and/or the FMS 330 and then provided to the ADU 210.
  • the ADU 210 can be configured to receive sensor input continuously, or at designated intervals, for example at intervals controlled by the DAM 222.
  • apparatus data can be recorded at the ADU 210, for example at the data recorder 206.
  • Apparatus data can be recorded as data points that include machine identification data, data from a plurality of sensors and various components in the ADU 210 operating environment, and date and time information. Operator identification can also be included.
  • apparatus data can be transmitted to the FMS 130.
  • the data transmitter 207 can transmit the apparatus data stored at the data recorder 206 to the FMS 330 via the communications network 120 to provide the apparatus data to the SDM 342.
  • the communications network 120 comprises a cellular network.
  • the process can terminate.
  • the data acquisition and transmission process can end in response to a termination trigger, such as a key OFF state, an engine shutoff, and the like.
  • a termination trigger such as a key OFF state, an engine shutoff, and the like.
  • the SDM 342 at the FOS 340 can be configured to designate a machine status as "Off, "Stopped/Idle”, “Working”, "Headland-Turning” or "Travel/Transport". A further designation of "Travel/Turning" can be included.
  • FIG. 8 shows a flow chart of an example method 800 that can be practiced to determine machine status at a particular time based on data received in a time-stamped ADU transmission.
  • a determination can be made as to whether a machine engine is operating. For example, apparatus data regarding engine state can be examined.
  • a determination can be made as to whether the machine is in motion. For example, apparatus data indicating speed can be used by the SDM 342 to determine whether a machine is moving or stationary.
  • a determination can be made as to whether an implement is present at the vehicle. Data provided by one or more sensors 212a..n deployed on an implement, for example the sensor 212d, can be used to make this determination. It is conceivable that a machine, such as a tractor can be equipped with an implement, but the implement is not currently in use.
  • the method 800 includes a check of both implement state and PTO state, which may be redundant in some configurations.
  • a determination can be made as to whether the direction of machine motion is undergoing a rapid and/or substantial change.
  • Machine heading data can be used to make this determination.
  • the SDM 342 can examine heading data received over time to determine whether the machine is moving in a generally constant direction, or is changing direction at a rate above a predetermined threshold, so as to determine whether a machine is performing a head-turn.
  • Agricultural machines generally traverse a field heading in a first direction, then perform a headland-turn, essentially a 180° turn, to proceed back across the field in an opposite direction.
  • a predetermined threshold for change in heading, and/or rate of change in heading can be established.
  • a change in heading greater than the predetermined threshold can indicate that a headland-turn was performed.
  • a headland-turn can be determined from input from the ECU 218 or other system or module at the machine. It is noted that a method of the invention can contain more or fewer process blocks than shown in the example method 800, and that the process blocks can be performed in various sequences.
  • FIG. 9 shows a diagram 900 of example logic that can be implemented by the SDM 342.
  • the example diagram 900 shows various combinations of apparatus states and machine parameters, and example resultant machine status designations.
  • Columns 902-912 identify various apparatus states or machine parameters that can be determined at the SDM 342 using received apparatus data, generally corresponding to steps 802-814 in the example method 800.
  • Rows 901-917 provide various combinations of the various state determinations.
  • Column 914 provides possible resultant machine status designations based on the various apparatus state combinations.
  • a variety of determination schemes can be employed. For example, a scheme can be devised that takes into consideration machine type, as different agricultural vehicles can be equipped with different equipment.
  • Machine status can be designated as OFF/PARKED, regardless of values in the remaining columns.
  • detection of engine shut-off can lead to the determination that the machine is in an OFF/PARKED status. That status can be considered to continue until an engine start is detected, even if ADU transmissions cease during the parked period.
  • machine status can be designated as IDLE.
  • a machine engine is ON and the machine is in motion headed in a generally constant direction with an implement present and engaged (active), and a PTO is turned ON, machine status can be designated as WORKING.
  • machine status can be designated as HEAD-TURNING.
  • rows 907, 917 when a machine is in motion in a generally constant direction, but an implement is either absent or not engaged, and a PTO is not engaged, machine status can be designated as TRAVELLING. Other example combinations are shown in remaining rows.
  • machine status can be recorded, for example, machine status can be stored at the database 338.
  • a record of machine status over time can be compiled and stored at the database 338.
  • a machine status record can be indexed by machine identification and provide a sequential record that includes date, time, location, and machine status. Operator identification can further be included.
  • a record can be indexed by machine and/or operator identification.
  • a report of machine status can be generated.
  • the RGM 346 can provide a machine status report in real-time or at a later time.
  • a machine status report can be expressed in a variety of formats, including but not limited to text, graphics, or images. For example, images representing machine status at a particular time and/or location can be superimposed over a map of the field being worked by a particular machine and displayed on a display device such as a computer monitor, cell phone display screen, or other display device communicatively coupled to the FOS 340 and accessible to a fleet manager, machine operator or other interested party.
  • a machine status report can be provided by short message service (SMS) to a cellular phone device or internet capable device, by text in an e-mail application, by a text file downloaded to a computer, etc.
  • SMS short message service
  • FIG. 10 shows a screenshot 1000 of an example display in which machine status can be reported.
  • the display can be shown on a computer monitor, cellular device screen, machine display screen, or other display apparatus associated with a device communicatively coupled to the FOS 340 or FMS 330.
  • the display is provided to a display screen of a device employed by a fleet manager.
  • the FMS 330 can include a display device coupled to the CCD 332 and configured to display the screenshot 1000 to a fleet manager at the FMS 330 location.
  • a fleet manager can be positioned at a site remote from the FMS 330, in which case a display device can be coupled to a communication device communicatively coupled to the FMS 330, for example by the communications network 120.
  • the screenshot 1000 shows a satellite view map 1010 of a plurality of fields 1011A-H that can be separated by natural or man-made boundaries, or roads, such as roads 1 and 2.
  • One or more machine status indicators 1012 can be superimposed on the field map to indicate machine status and location.
  • a legend 1014 can be included to explain the way in which various statuses are portrayed by the machine status indicator 1012.
  • the status indicator 1012 is in the form of a graphic having a generally geometric shape, a generally square shape in the current example, in which various statuses can be differentiated by infill patterns.
  • an OFF status can be represented by the absence of a fill pattern
  • a STOPPED/IDLE status can be represented by a dotted infill
  • a WORKING status can be represented by diagonal line infill
  • a TURNING (HEADLAND-TURNING) status can be represented by cross hatched diagonal infill
  • a TRAVEL status can be represented by a horizontal line infill.
  • Other infill patterns or ways to distinguish statuses will occur to those skilled in the art.
  • the different statuses can be differentiated by indicators having different colors. For example, a geometric shape, such as a square, can be filled with a color rather than a black/white pattern.
  • an OFF status can be represented by a gray infill
  • a STOPPED status can be represented by a square having a red infill
  • a WORK status can be represented by an indicator having a dark green infill
  • a TURNING status can be represented by a light green infill
  • a TRAVEL status can be represented with a yellow infill.
  • the colors and/or patterns employed have sufficient contrast with each other as well as the underlying map image to provide an easily ascertainable indication of machine status.
  • a display can further include a machine identifier portion providing information pertaining to machine and/or operator identification and characteristics for the machine for which the status is provided.
  • machine status indicators 1012 can be positioned on the map 1010 to correspond with the location of a machine at the time the machine was in the indicated status or operational mode. Accordingly, as seen in FIG. 10 a machine can typically be in a HEADTURNING status at the end of a traversed row. Furthermore, as shown in FIG. 10, a first machine status indicator 1012 can overlap one or more other status indicators 1012. This can result from an actual overlapping of common ground by a machine, or simply from the size of the indicator 1012 relative to the distance between location points at which the status is determined. From FIG. 10 it can be seen that a machine status report can be in the form of images or graphics superimposed on an underlying image, such as a satellite map.
  • An RGM can cooperate with one or more separate applications, such as a computer-based or internet-based mapping application, to provide a report of machine status.
  • a machine status report can be embodied as a list of times, locations and corresponding machine status. Alternative forms of reports that convey machine status will be apparent to those skilled in the art.
  • machine performance can be determined over a predetermined time period.
  • FIG. 11 shows an example method 1100 that can be practiced to determine machine performance.
  • the method can begin in response to satisfaction of a triggering condition, for example, upon reception of apparatus data from a machine, or in response to user input, or upon compilation of a performance record spanning 24 hours, etc.
  • a determination can be made as to the amount of time a particular machine spent in a particular status.
  • a performance determination module (PDM) 344 can be configured to use data in a status record stored at the database 338 to determine the amount of time a machine spent in each status mode over a predetermined time period.
  • PDM performance determination module
  • the predetermined time interval is stored at the PDM 344 or the memory 336.
  • the predetermined time period can be the most recent 24-hour period for which apparatus data is available.
  • an interval can be selected by a user via a user interface that allows the FMS 330 to receive input from a user, such as a fleet manager.
  • a percentage of time spent in each status mode over the time interval can be determined.
  • the PDM 344 can be configured to make this determination by using the amount of time spent in each status and the amount of time included in the time interval.
  • the PDM 344 can be configured to generate a performance record that can be stored at the database 338.
  • a performance record can include the time period for which it is determined, the number of hours spent in each status, and the percentage of time spent in each status over the time interval.
  • the PDM 344 can be configured to determine machine performance for a plurality of machines.
  • the PDM 344 can generate a performance record for each machine that can be stored at the database 338.
  • a performance report based on one or more performance determinations or performance records can be generated.
  • a performance report can present each status or operational mode that a machine exhibited over the predetermined interval, and the percentage of time spent in each status mode.
  • a performance report can report performance determinations for a plurality of machines to apprise a user, such as a fleet manager, of the performance of multiple machines in a fleet.
  • a performance report can enable a fleet manager to compare the performance of a first machine to the performance of one or more other machines. Detection of a machine with a disappointing or unsatisfactory performance provides a fleet manager or machine operator an opportunity to make adjustments to the machine and/ or operator activity to improve performance, increase revenue and decrease costs.
  • a report generating module (RGM) 346 can generate a performance report based on the performance determination by the SDM 344 or the performance record stored at the database 338.
  • a performance report can be provided in any form, including but not limited to, a visual display, a text file, a short-message-service message, an electronic mail message, or other form.
  • the RGM 346 can generate a performance report that can be provided to a fleet manager over the network 120 and observed on a computer monitor, lap-top screen, smart phone screen or other display device as a visual display.
  • FIG. 12 shows a screenshot 1200 of an example fleet management display containing a performance report 1202.
  • the performance report 1202 includes a performance indicator 1204 that graphically represents the performance of an agricultural machine.
  • the performance indicator 1204 conveys the percentage of time that a machine spent in a particular status during a predetermined time interval.
  • the performance indicator 1204 is embodied as a bar having differentiated portions representing the various status modes of the identified agricultural machine over a 24-hour period.
  • the legend 1206 provides an explanation of the various patterns used to distinguish one status state from another.
  • the agricultural machine identified as " Manitou MLA" spent about 30% of its time in a transport status, 65% of its time in a working status, and about 5% of its time in a stopped/idle status.
  • the patterns used in the performance indicator 1204 can correspond with the patterns used with the status indicator 1014 in FIG. 10.
  • various colors can be used to differentiate portions of the performance indicator 1204 in accordance with the colors used to indicate status in the status indicator 1014.
  • the performance report 1202 can be configured to provide performance indicators 1204 for a plurality of agricultural machines. Accordingly, a fleet manager can quickly assess the performance of a plurality of machines. In addition, the performance of one machine can be compared to that of other machines in a fleet to detect a sub-par performing machine. For example, referring to the performance report 1202, of the three machines listed, the MF 6480 spent the largest percentage of its time in a Travel/Transport mode, about 70%, a quarter of its time stopped, and was working the least of the machines, only about 5% of the time over the past 24 hour period.
  • the present invention allows a fleet manager to quickly detect and identify a machine and/ or operator whose performance differs from that of other machines in a fleet. In response, a fleet manager can notify the machine's operator and alert him of the situation.
  • An operator has an incentive to produce revenue. Because revenue is generated during the time a machine spends working, transport, idle and parked times can reduce the amount of revenue produced over a period. If an operator learns that he is operating at a lower revenue point than other machines in the fleet, he can consider making changes to his machine or to his operating methods.
  • a fleet manager can consider whether adjustments need to be made to the machine itself and/or to administration and allocation of fleet resources.
  • the FMS 330 can be configured to alert an operator whose machine is underperforming. For example, the FMS 330 can communicate an alarm to the machine 105 over the network 120.
  • the FOS 340 can be configured to evaluate a machine's performance based on one or more performance standards.
  • FIG. 13 shows an example method 1300 for evaluating a machine's performance.
  • a machine's performance can be compared to at least one predetermined performance standard or performance parameter.
  • a performance parameter can be variably defined.
  • a performance parameter can comprise a predetermined threshold, such as a percentage threshold, or number of hours threshold, for a particular status.
  • a performance parameter can comprise a working status threshold of 30%, meaning that a machine is expected to be working at least 30% of the time over the measured time interval.
  • a performance parameter can comprise a maximum of 12 hours for a travel/transport status, meaning that no more than 12 hours out of 24 should be spent traveling over the observed time period.
  • One or more performance parameters can be established by setting thresholds for various machine states.
  • a performance parameter can comprise a fleet status or performance average, and each machine can be compared to the fleet average.
  • the PDM 344 can determine the amount of time that each machine spent in a travel/transport mode by and generate a fleet average for transport time. The PDM 344 can then compare the amount of time an individual machine spent in a transport mode to the fleet average time.
  • a separate module such as a performance evaluation module at an FOS can be configured to perform the comparison or evaluation.
  • a performance parameter can be based on the performance of a particular machine in the fleet. As one example, a particular machine, or machine of a particular operator can be selected. In a further example, the machine with the most time spent in a working status, the machine with the least time spent parked or idle, etc., can be designated as the standard for comparison.
  • the PDM 344 can be configured to select a machine from the fleet whose performance can be used as a performance standard from which to generate one or more performance parameters to which the performance of other machines can be compared.
  • performance parameters can be stored at the PDM 344, or alternatively at the memory 336. The PDM 344 can be configured to compare a machine's performance to one or more performance parameters.
  • a performance score based on the comparison between a machine's performance and a performance parameter can be generated.
  • one or more performance scores can be associated with a machine for a particular time interval.
  • a performance score can be expressed as one or more numerical quantities.
  • a performance score can reflect the number of performance parameters satisfied, or conversely, the number of performance parameters that were not satisfied.
  • a performance score can be in the form of one or more qualitative, rather than quantitative, evaluations.
  • a performance score can reflect the margin by which one or more performance parameters was not satisfied.
  • a variety of schemes can be used to generate a performance score based the comparison of machine performance with one or more performance parameters.
  • a performance score for a particular machine over a particular time period can be stored at the database 338, for example in association with a machine performance record.
  • a performance evaluation report can be generated.
  • the RGM 346 can generate a report of a machine's performance evaluation, by way of example, but not limitation, by reporting its performance score.
  • a performance evaluation report can comprise a performance marker, a graphic in a visual display.
  • the screenshot 1200 further includes an evaluation report portion 1206 that can provide a list of machines associated with a performance marker 1208.
  • the performance marker 1208 can indicate that a machine's performance is adequate, or is below par.
  • a performance marker 1208 can flag those machines that require additional observation, or whose operator should be contacted.
  • the performance marker is based on the performance score determined by the PDM 344.
  • the performance marker 1208 can be in the form of a warning symbol, such as a yellow triangle, associated with a machine operating up to a predetermined threshold, for example 15%, below a performance parameter, like that shown associated with the MF 8470 machine. Should a machine operate at more than 15% below the performance parameter, the performance marker 1208 can appear as an alert or alarm symbol, such as the red triangle associated with the MF 6480 machine, whose time spent working was only 5 %, well below a performance parameter set at 30% for time spent working.
  • a plurality of performance parameters can be established, and that the performance marker 1208 can be in response to a machine's performance falling below one or more of the performance parameters.
  • the performance marker 1208 can appear in a variety of shapes and patterns to convey a variety of evaluations.
  • five performance parameters can be established, and the performance marker 1208 can be in the form of a warning symbol if a machine falls below 1 or 2 parameters, and in the form of an alarm symbol if 3 or more parameters are not satisfied.
  • a plurality of parameters can be prioritized and a failure to satisfy a high priority parameter can result in the performance marker 1208 appearing as an alarm symbol, while a failure to satisfy a lower priority parameter can result in the performance marker appearing in the form of a warning symbol.
  • a performance marker 1208 can be in the form of a warning symbol when at least 2 performance parameters are not satisfied, and in the form of an alarm symbol when at least 4 parameters are not satisfied.
  • a variety of schemes for devising performance markers 1208 can be practiced.
  • a machine whose performance is satisfactory, or whose performance exceeds that of the remaining machines in a fleet need not be associated with a performance marker, such as the Manitou MLA.
  • a performance marker 1208 can be provided that conveys satisfactory performance, such as a green triangle.
  • an alarm performance marker can prompt a fleet manager to contact the operator of the machine in regard to the machine's performance.
  • the FMS 330 can be configured to automatically contact a machine associated with an alarm performance marker indicating a poor performance score.
  • the evaluation report 1206 can also provide a current posture indicator 1210.
  • the current posture indicator 1210 can indicate machine status, such as Idle/Stopped, Working, Transport/Travel, or Head-Turning, as well as additional states such as a Parked/Off condition, or a condition in which no machine communications have been received for a period of 2 hours or longer.
  • a posture indicator can indicate that a current condition is unknown.
  • the posture indicator 1210 can be in the form of a geometrical shape, such as a square, with a fill pattern or fill color associated with a particular status.
  • the evaluation report 1206 enables a fleet manager to learn at a glance the current status of a machine, and whether any machines are performing below expectations as indicated by the performance marker 1208.
  • a warning or alarm symbol can prompt a manager to check the performance indicator 1204 to gauge the performance of a machine to see what type of problem, if any, may be occurring.
  • a system for automatic detection of machine status can use apparatus data to determine and track machine status for an agricultural machine and/or operator.
  • Sensor input received at an ADU can be provided as apparatus data to an FOS at which machine status can be determined.
  • Records of machine status for particular machines and/or operators can be compiled and maintained. These records can be used for efficient resource management, discovery of opportunities to increase revenue or decrease operational costs, operator notification, and other administrative purposes.

Landscapes

  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Strategic Management (AREA)
  • Economics (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Human Resources & Organizations (AREA)
  • Educational Administration (AREA)
  • Marketing (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • Game Theory and Decision Science (AREA)
  • General Business, Economics & Management (AREA)
  • Development Economics (AREA)
  • Theoretical Computer Science (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Traffic Control Systems (AREA)

Abstract

L'invention concerne un système de détection automatique d'état de machine qui utilise des données d'appareil provenant d'un ou plusieurs capteurs d'éléments de machine afin de déterminer un état pour une machine agricole. Une unité de données automatique embarquée dans une machine peut recevoir des données d'appareil et les communiquer à un système de gestion centralisé. Dans un mode de réalisation donné à titre d'exemple, un module de détermination d'état peut recevoir les données d'appareil, les utiliser pour effectuer une ou plusieurs déterminations d'état et, à partir des résultats de ces déterminations, déterminer un état d'activité pour une machine. Un état de machine, un état de déplacement, un état de direction, un état de mise en œuvre et un état de prise de force (PTO) peuvent être utilisés pour déterminer qu'une machine a un état identifié comme « désactivé », « inactif », « en progression », « en cours de rotation » ou « en fonctionnement » afin d'améliorer l'efficacité des opérations et de faciliter la facturation et les services administratifs.
PCT/US2011/068182 2010-12-30 2011-12-30 Détection automatique d'état de machine pour une gestion de parc WO2012092592A1 (fr)

Applications Claiming Priority (12)

Application Number Priority Date Filing Date Title
US201061428692P 2010-12-30 2010-12-30
US201061428693P 2010-12-30 2010-12-30
US201061428695P 2010-12-30 2010-12-30
US61/428,693 2010-12-30
US61/428,692 2010-12-30
US61/428,695 2010-12-30
US13/341,475 US9269200B2 (en) 2010-12-30 2011-12-30 Real-time evaluation of machine performance for fleet management
US13/341,450 US20120253743A1 (en) 2010-12-30 2011-12-30 Real-Time Determination of Machine Performance for Fleet Management
US13/341,450 2011-12-30
US13/341,475 2011-12-30
US13/341,500 US20120253709A1 (en) 2010-12-30 2011-12-30 Automatic Detection of Machine Status for Fleet Management
US13/341,500 2011-12-30

Publications (1)

Publication Number Publication Date
WO2012092592A1 true WO2012092592A1 (fr) 2012-07-05

Family

ID=45607810

Family Applications (3)

Application Number Title Priority Date Filing Date
PCT/US2011/068182 WO2012092592A1 (fr) 2010-12-30 2011-12-30 Détection automatique d'état de machine pour une gestion de parc
PCT/US2011/068174 WO2012092588A1 (fr) 2010-12-30 2011-12-30 Détermination en temps réel de performances de machines pour gestion de parc
PCT/US2011/068194 WO2012092599A1 (fr) 2010-12-30 2011-12-30 Évaluation en temps réel des performances d'une machine pour la gestion d'une flotte

Family Applications After (2)

Application Number Title Priority Date Filing Date
PCT/US2011/068174 WO2012092588A1 (fr) 2010-12-30 2011-12-30 Détermination en temps réel de performances de machines pour gestion de parc
PCT/US2011/068194 WO2012092599A1 (fr) 2010-12-30 2011-12-30 Évaluation en temps réel des performances d'une machine pour la gestion d'une flotte

Country Status (1)

Country Link
WO (3) WO2012092592A1 (fr)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2942401A1 (fr) 2014-05-09 2015-11-11 Lifecodexx AG Détection d'ADN qui provient d'un type cellulaire spécifique
EP2942400A1 (fr) 2014-05-09 2015-11-11 Lifecodexx AG Détection multiplexe d'ADN qui provient d'un type cellulaire spécifique
EP3521454A1 (fr) 2014-05-09 2019-08-07 LifeCodexx AG Détection d'adn provenant d'un type cellulaire spécifique et procédés associés
US10963825B2 (en) 2013-09-23 2021-03-30 Farmobile, Llc Farming data collection and exchange system
US11753684B2 (en) 2015-11-10 2023-09-12 Eurofins Lifecodexx Gmbh Detection of fetal chromosomal aneuploidies using DNA regions that are differentially methylated between the fetus and the pregnant female

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE102010019063A1 (de) * 2010-05-03 2011-11-03 Heidelberger Druckmaschinen Ag System zur Verbesserung von Produktionsprozessen
US10997534B2 (en) * 2015-11-20 2021-05-04 Caterpillar Inc. System and method for connecting an operator with worksite operations
EP3229200A1 (fr) * 2016-04-05 2017-10-11 CLAAS E-Systems KGaA mbH & Co KG Système d'administration de données de travail et de données opérationnelles d'au moins une machine agricole

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020059075A1 (en) * 2000-05-01 2002-05-16 Schick Louis A. Method and system for managing a land-based vehicle
US6505106B1 (en) * 1999-05-06 2003-01-07 International Business Machines Corporation Analysis and profiling of vehicle fleet data
DE20023681U1 (de) * 2000-11-08 2005-09-01 Mobiworx Telematik Gmbh Vorrichtung zum Erfassen und Verarbeiten von Zustandsdaten, die an Bord eines Fahrzeuges aufgenommen sind
US20060250281A1 (en) * 2002-07-31 2006-11-09 Mahoney Brian J Method for remote monitoring equipment for an agricultural machine
US20080255722A1 (en) * 2006-05-22 2008-10-16 Mcclellan Scott System and Method for Evaluating Driver Behavior

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20010018628A1 (en) * 1997-03-27 2001-08-30 Mentor Heavy Vehicle Systems, Lcc System for monitoring vehicle efficiency and vehicle and driver perfomance
US20020116107A1 (en) * 2001-02-07 2002-08-22 Deere & Company Method of monitoring equipment of an agricultural machine

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6505106B1 (en) * 1999-05-06 2003-01-07 International Business Machines Corporation Analysis and profiling of vehicle fleet data
US20020059075A1 (en) * 2000-05-01 2002-05-16 Schick Louis A. Method and system for managing a land-based vehicle
DE20023681U1 (de) * 2000-11-08 2005-09-01 Mobiworx Telematik Gmbh Vorrichtung zum Erfassen und Verarbeiten von Zustandsdaten, die an Bord eines Fahrzeuges aufgenommen sind
US20060250281A1 (en) * 2002-07-31 2006-11-09 Mahoney Brian J Method for remote monitoring equipment for an agricultural machine
US20080255722A1 (en) * 2006-05-22 2008-10-16 Mcclellan Scott System and Method for Evaluating Driver Behavior

Cited By (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
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
US11126937B2 (en) 2013-09-23 2021-09-21 Farmobile, Llc Farming data collection and exchange system
US11151485B2 (en) 2013-09-23 2021-10-19 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
US11507899B2 (en) 2013-09-23 2022-11-22 Farmobile, 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
US11410094B2 (en) 2013-09-23 2022-08-09 Farmobile, Llc Farming data collection and exchange system
US11164116B2 (en) 2013-09-23 2021-11-02 Farmobile, Llc Farming data collection and exchange system
EP3521454A1 (fr) 2014-05-09 2019-08-07 LifeCodexx AG Détection d'adn provenant d'un type cellulaire spécifique et procédés associés
US11965207B2 (en) 2014-05-09 2024-04-23 Eurofins Lifecodexx Gmbh Detection of DNA that originates from a specific cell-type and related methods
EP2942401A1 (fr) 2014-05-09 2015-11-11 Lifecodexx AG Détection d'ADN qui provient d'un type cellulaire spécifique
US9822413B2 (en) 2014-05-09 2017-11-21 Lifecodexx Ag Multiplex detection of DNA that originates from a specific cell-type
EP2942400A1 (fr) 2014-05-09 2015-11-11 Lifecodexx AG Détection multiplexe d'ADN qui provient d'un type cellulaire spécifique
US11773443B2 (en) 2014-05-09 2023-10-03 Eurofins Lifecodexx Gmbh Multiplex detection of DNA that originates from a specific cell-type
US10017818B2 (en) 2014-05-09 2018-07-10 Lifecodexx Ag Multiplex detection of DNA that originates from a specific cell-type
US9822412B2 (en) 2014-05-09 2017-11-21 Lifecodexx Ag Detection of DNA that originates from a specific cell-type
US11753684B2 (en) 2015-11-10 2023-09-12 Eurofins Lifecodexx Gmbh Detection of fetal chromosomal aneuploidies using DNA regions that are differentially methylated between the fetus and the pregnant female

Also Published As

Publication number Publication date
WO2012092588A1 (fr) 2012-07-05
WO2012092599A1 (fr) 2012-07-05

Similar Documents

Publication Publication Date Title
US9269200B2 (en) Real-time evaluation of machine performance for fleet management
WO2012092592A1 (fr) Détection automatique d'état de machine pour une gestion de parc
US10251341B2 (en) Farm work machine, farm work management method, farm work management program, and recording medium recording the farm work management program
US9870654B2 (en) Ground work vehicle, ground work vehicle management system, and ground work information display method
EP3125670B1 (fr) Procédés de surveillance d'opérateur de machine agricole
US5870689A (en) Scouting system for an agricultural field
Amiama et al. Design and field test of an automatic data acquisition system in a self-propelled forage harvester
WO2013096721A2 (fr) Détermination en temps réel d'une mesure de recettes de flotte
WO2013096716A1 (fr) Optimisation de réglages de boucle fermée à l'aide de mesure de recettes
EP2530630A1 (fr) Procédé de surveillance de position
EP3751501B1 (fr) Système de soutien à l'agriculture
JP6320498B2 (ja) 農作業機と農作業管理プログラム
JP7144145B2 (ja) 農業支援システム
Harkin et al. Field-to-Field Coordinate-Based Segmentation Algorithm on Agricultural Harvest Implements
JP6289536B2 (ja) 作業機

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: 11818964

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: 11818964

Country of ref document: EP

Kind code of ref document: A1