WO2013115929A2

WO2013115929A2 - Systems and methods for machine rollover event alert

Info

Publication number: WO2013115929A2
Application number: PCT/US2012/072261
Authority: WO
Inventors: Paul Matthews
Original assignee: Agco Corporation
Priority date: 2011-12-30
Filing date: 2012-12-31
Publication date: 2013-08-08
Also published as: WO2013115929A3

Abstract

Systems, methods and apparatus are presented for automatic detection and reporting of a machine rollover condition, and directly alerting a predetermined remote contact person for assistance. A machine can be equipped with a RDRM configured to detect a rollover condition by comparing orientation sensor data to predetermined parameters. In the event a rollover condition is detected, a report that includes machine identification and location can be transmitted to a central server. A RAM at the central server can be configured to retrieve predetermined contact information and provide an alert message to a predetermined contact person. An alert message can comprise GPS coordinates which can be used in a mapping application to navigate to the fallen machine. In an example embodiment, GPS coordinates can be translated to localized parameters to facilitate finding a machine in a large isolated field location.

Description

SYSTEMS AND METHODS FOR MACHINE ROLLOVER EVENT ALERT

FIELD OF INVENTION

[001] This invention relates generally to alert systems, and more specifically to systems configured to alert a remote user that an event has occurred.

BACKGROUND OF INVENTION

[002] Because agricultural machines are typically tall, large, and heavy, particularly when towing various types of agricultural implements, they can be difficult to maneuver around turns or obstacles, and difficult to control on inclines. In addition, most machine operating time is spent away from surfaced and maintained roads, in fields of varying terrain that can include terraces, drainage ditches, elevation differences, ponds, and other obstacles that an operator must either avoid or approach with care and deliberation. One of the more critical accidents that can occur while working a field is that a machine can become unstable and roll over. By way of example, an operator may take a turn too quickly or too sharply, or may get too near a drainage ditch, causing a machine to become unbalanced and roll over. Because rollover events can cause serious human injury, efforts have been made to protect operators who experience a machine rollover. For example, government agencies such as the Occupational Safety and Health Administration (OSHA) have developed various safety regulations for agricultural machines, such as strength and energy absorption requirements for machine cab structures. In addition, stationary or deployable roll bars can be installed to provide enhanced protection for operators in the event that a machine does roll over.

[003] Such protective structures may mitigate the harm suffered by an operator to a certain extent; however, serious injury may still occur. In addition, it is very likely that an operator will require some sort of assistance after a rollover event, regardless of the degree of injury. In some situations an operator may not be able to request that assistance himself; for example, an operator may have sustained injuries that prevent him from calling for help, or may not have or be able to access a communication device, such as a mobile phone to call for help. In many cases operators work alone in large fields that can be quite a distance from the nearest town; if an operator is unable to call for help, a rollover event may go undetected by fleet managers or passers by for a prolonged period, leaving the operator alone and without assistance.

[004] Some presently existing systems are designed to assist automobile passengers in the event of an accident. For example, the OnStar™ system can include sensors to detect an impact or airbag deployment. When an impact is detected, a GPS receiver calculates vehicle location and sends a message to a national call center with vehicle location and customer information. In response to receiving the message from the vehicle unit, an operator can call the unit at the vehicle to speak with a passenger about what happened and what type of assistance is needed. The operator is trained to attempt to speak directly with a passenger, however, if there is no passenger response, the operator can proceed to contact emergency services to dispatch help to the vehicle location.

[005] Although the OnStar™ system can provide some assistance to automobile passengers, it is a paid subscription service requiring proprietary equipment that must either be built in during vehicle manufacture, or added on via a replacement rear view mirror kit that, depending on the make, model and year of a vehicle, may or may not be compatible with a consumer's automobile. While generally available in North America, the system and services are generally not available in the remaining countries of the world. Furthermore, because the OnStar™ system requires call center intervention, there are inherent delays in providing assistance. For example: after a collision is detected, vehicle occupants must wait for an available OnStar™ operator to call the automobile unit; occupants must wait for an operator to speak or attempt to speak directly with a passenger; occupants must wait for the OnStar™ operator to determine which service authorities to call (particularly if there is no passenger response) and occupants must wait for the operator to actually contact and relay

information to the proper authorities, who must then dispatch assistance.

Furthermore, if unable to speak directly with a passenger and forced to respond simply on the basis of a detected impact or airbag deployment, an operator may end up contacting an authority who is not the one best suited to help the occupants. Adding further possible complications, operators working out of national call centers, are typically not familiar with the local emergency services at the vehicle location, nor are they familiar with the local environs. In addition, because the system is designed to be activated in response to an impact that has already occurred, it can only be effective in those situations in which the impact does not damage the automobile unit or the antenna used for

communication with the call center.

[006] For agricultural machine operators that work primarily in isolated areas, relying on a third party that is unfamiliar with the local community to coordinate emergency assistance may cause additional delays as emergency personnel will need to locate machines and operators in large fields that can be quite a distance from roads and intersections that appear on street maps. In addition, a third party operator may be unfamiliar with agricultural operations, and if unable to speak directly with an operator may not know the type of assistance that a rollover event requires. Finally, commercial enterprises such as OnStar™ have raised privacy concerns among consumers as they can record and track vehicle locations and activities and sell them to third parties.

OVERVIEW OF INVENTION

[007] Systems and methods are presented to automatically procure assistance for an operator whose machine has rolled over. A Machine Rollover Detection and Alert System (MRDAS) can be configured to automatically detect a rollover condition at a machine and notify a predetermined local contact. In an example embodiment, the MRDAS can include a rollover detection and report module (RDRM) at a machine, and a rollover alert module (RAM) at a central server. The MRDAS can be configured to receive input from one or more orientation sensors to detect a rollover condition at a machine. In an example embodiment, the MRDAS can be configured to receive input from an onboard positioning system to continuously update and store machine location. When a machine orientation exceeds a predetermined angle, the RDRM can use an onboard communication means to provide a rollover report to the RAM. In an example embodiment, the report can provide the machine location and time of the rollover event. By way of example, the RDRM can cooperate with an onboard transmitter configured communicate via a cellular network with a central server at fleet management field office configured to cooperate with the RAM. In an example embodiment, a report can be sent prior to a machine's impact with the ground so that the report can be sent with minimal delay prior to any machine damage that may result from impact with the ground.

[008] In response to reception of a rollover report, an example RAM can automatically provide an alert. For example, an alert can be provided to a web application used to monitor fleet operations so that it shows up on a fleet management web page. In addition, an alert can be provided directly to a predetermined local contact who can respond quickly to assist an operator. In an example embodiment, the RAM can have a list of local contacts, preferably those familiar with the farm industry and having knowledge of the local area and the type of assistance that a rollover event can require. For example, a fleet operator or manager can be listed as a contact, a fleet dealer, a farmer, or a field owner. An emergency assistance service can also be listed, as well as an operator's family point of contact. By way of example, but not limitation, a page or text message can be sent directly to the cell phone, smart phone, personal digital assistant (PDA), or other communication device of one or more contacts.

[009] In an example embodiment, an alert message can include the machine location, which can be provided in latitude and longitude coordinates that can be used by a navigation application at the device to locate the fallen machine. However, an example RAM can include a location translation aspect in which GPS latitude and longitude coordinates are translated into local location parameters, such as a field owner name and a field sector, that can be included in the alert provided to one or more predetermined contacts. Local parameters can reduce the time required to find the accident site.

[0010] The invention can provide a system that can automatically notify a local contact having knowledge of agricultural operations without incurring the delays inherent in a system that requires real-time human intervention by a party that may be hundreds of miles away from the accident scene. In an example embodiment, a system of the invention can use sensors and communication equipment already installed at a machine, obviating the need to purchase proprietary equipment, and enabling the invention to be practiced throughout the world wherever there are adequate communication networks, such as cellular networks. An example system can report a rollover condition prior to machine collision with the ground, reducing response time and avoiding problems that may be caused by damage to the machine. In addition, the system can be practiced within a local community without the privacy concerns that can arise in systems that rely on third party intervention.

BRIEF DESCRIPTION OF THE DRAWINGS

[0011] The above mentioned and other features of this invention will become more apparent and the invention itself will be better understood by reference to the following description of embodiments of the invention taken in conjunction with the accompanying drawings, wherein:

[0012] FIG. 1 shows an example machine rollover detection and alert system (RDAS);

[0013] FIG. 2 shows an example operating environment;

[0014] FIG. 3 shows an example embodiment of an FMS having a RAM;

[0015] FIG. 4 shows a sectored field of an example embodiment;

[0016] FIG. 5 shows an example method;

[0017] FIG. 6 shows an example method; and

[0018] FIG. 7 shows an example method.

[0019] Corresponding reference characters indicate corresponding parts throughout the views of the drawings.

DETAILED DESCRIPTION OF EXAMPLE EMBODIMENTS

[0020] As required, example embodiments of the present invention are disclosed. The various embodiments are meant to be non-limiting examples of various ways of implementing the invention and it will be understood that the invention may be embodied in alternative forms. The present invention will be described more fully hereinafter with reference to the accompanying drawings in which like numerals represent like elements throughout the several figures, and in which example embodiments are shown. The figures are not necessarily to scale and some features may be exaggerated or minimized to show details of particular elements, while related elements may have been eliminated to prevent obscuring novel aspects. The specific structural and functional details disclosed herein should not be interpreted as limiting, but merely as a basis for the claims and as a representative basis for teaching one skilled in the art to variously employ the present invention. For example, functions discussed in the context of being performed by a particular module or device may be performed by a different module or device, or combined, without departing from the scope of the claims.

[0021] FIG. 1 shows an example embodiment in which a machine 10 in a field 1 1 is equipped with a rollover detection and report module (RDRM) 12 configured to provide a rollover report 14 via a communications network 16 to a fleet management system (FMS) 18 having a rollover alert module (RAM) 20. In response to the report 14, the RAM 20 can provide an alert to a predetermined contact 22 who can assist the machine 10 operator (not shown). Preferably, the contact 22 is someone associated with the local community, such as a fleet manager, a fleet dealer, or someone else associated with the machine 10 operator.

[0022] The machine 10 can be in the form of an agricultural vehicle such as, but not limited to, a tractor configured with any of a number of types of

implements, or a combine harvester, configured for field operations. The RDRM 12 can include a transmitter (not shown) for communication over the network 16, or can be configured to coordinate with a transmitter configured to cooperate with a cellular communications antenna already onboard the machine 10. The communications network 16 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 systems, may be utilized. 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.

[0023] The FMS 18 can include one or more devices configured for communication over a communications network. For example, one or more computer servers coupled to a modem for communication capability can be included at the FMS 18. The FMS 18 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 18, as well as any other servers or other devices required to support a system for providing a rollover alert.

[0024] FIG. 2 shows an example operating environment that can include one or more orientation sensors 24 a..n, a positioning system 26, a transmitter unit (TU) 28 and the RDRM 12, which, in an example embodiment, can be

communicatively coupled by a controller area network (CAN) bus 30 as known in the art. In an example embodiment, a CAN system at the machine 10 can further include a controller 29 coupled to the CAN bus 30 that can be configured to coordinate operation and communication among the various nodes. In an example embodiment the controller 29 can be a processor at the machine 10 configured to perform various machine operation and control functions. The orientation sensors 24a... n can comprise gyroscopes, accelerometers, and the like configured to determine motion and/or rotation about an axis. By way of example, but not limitation, the sensors 24a... n can be configured to detect roll, pitch and yaw for the machine 10. In an example embodiment, the TU 28 can comprise a transmitter coupled to an antenna configured for communication over the network 16. The TU 28 can be a legacy transmitter previously installed at the machine 10 and adapted to perform machine 10 communication requirements, or can be a transmitter installed as part of a MRDAS. [0025] The positioning system 26 can be configured to provide a geographical location for the machine 10. In an example embodiment, the positioning system 26 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.

[0026] In an example embodiment, the RDRM 12 can comprise an

orientation submodule (OS) 32, a location monitoring submodule (LMS) 34 and a report submodule (RS) 36. The RDRM 12 can comprise hardware, software, firmware, or some combination thereof, and can include a processor as a portion of any of, or in addition to, the submodules 32-36 to coordinate and/or execute operations and input/output functions of the RDRM 12. By way of example, but not limitation, a submodule can be associated with a dedicated processing device. In a further example embodiment, a submodule can be configured to interact with the processor 29. The OS 32 can be configured to receive data from the orientation sensors 24a... n. In an example embodiment, the OS 32 can be configured to compare orientation data to predetermined parameters to detect a rollover condition. For example, machine specific parameters such as maximum roll, pitch, and yaw angles for the machine 10 to remain stable can be stored at the OS 32 used to detect a rollover condition (or event) at the machine 10. In an example embodiment, the OS 32 can be configured to track orientation by storing a history of orientation angles over a predetermined period of time. By way of example, the OS 32 can trigger the RS 36 to provide a report in response to detection of a rollover condition or event, as defined as an orientation angle that renders a machine unstable and will cause a machine to rollover. In an example embodiment the OS 32 can detect a rollover condition as the machine transitions from a stable orientation angle to an unstable one. Thus a rollover event can be detected prior to a machine colliding with the ground. In an example

embodiment, the RS 36 can detect a rollover condition and trigger the RS 36 prior to a machine's impact with the ground.

[0027] The LMS 34 can be configured to continuously monitor and update machine 10 location while the machine is working. For example, the LMS 34 can receive and store machine 10 latitude and longitude coordinates from the positioning system 26. In an example embodiment, location can be updated at predetermined intervals. In an example embodiment, the LMS 34 can comprise a memory for storing location data, which can be associated with time of day. The LMS 34 can be configured to store a series of location data to track machine 10 movement.

[0028] The RS 36 can be configured to respond to a rollover condition detection by providing a rollover report. In an example embodiment, the RS 36 can extract the most recent location data stored at the LMS 34 and include the data in a message that can be provided to the TU 28 for transmission over the network 16. An example report can further include machine identification, in an example embodiment can be stored at the RS 36. It is contemplated that machine and/or operator identification can also be received at the RS 36 from a separate system or module at the machine 10, such as an operator console or interface at which an operator can log on when starting a machine. In an example embodiment, the time associated with the location data can also be included. By way of example, but not limitation, the RDRM 12 can further include a power supply, such as a battery that can be used to provide backup power should primary power be lost. FIG. 3 shows an example embodiment of the FMS 18. By way of example, the FMS 18 can comprise a central computing device (CCD) 40 coupled to a database 48 and to the RAM 20. The CCD 40 can comprise a processor 42, a memory 44 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 46 for communications capabilities. By way of example, but not limitation, the CCD 40 can be implemented using a personal computer, a network computer, a mainframe, or microcomputer-based

workstation. The database 48 can be configured to store data in various structured arrangements, for example in various accessible records. The database 48 can be embodied as a separate data storage device or as part of the memory 44 resident at the CCD 40. In an exemplary embodiment, records at the database 48 can be indexed and maintained by machine, fleet, operator, field, owner or other index.

[0029] The RAM 20 can include one or more submodules configured to perform various rollover alert functions. Each submodule can be embodied as hardware, software, firmware or some combination thereof. By way of example, but not limitation, a submodule can be associated with a dedicated processing device. In a further example embodiment, a submodule can be configured to interact with the processor 42. By way of example, but not limitation, a submodule can be in the form of an application executed at the processor 42. In an example embodiment, a submodule can be embodied as an application service configured to cooperate with an application executed on-board the machine 10. As shown in FIG. 3, the example RAM 20 can include a contacts submodule 50, a location translation submodule 52, and a notification submodule 54. In an example embodiment, the contacts submodule 50 can be configured to use machine and/or operator identification information in the report 14 to look up contact information previously stored in association with a particular machine and/or an operator. In an example embodiment, contact information can be stored at the database 48. By way of example, for a machine operating as part of a fleet, a fleet manager can be listed as a contact, as well as a fleet dealer. For a machine operated independently of a fleet other contacts can be

designated by an operator and stored. In an example embodiment, a plurality of contacts can be associated with a machine and can be prioritized.

[0030] The location translation submodule 52 can be configured to translate geographical coordinates, such as latitude and longitude coordinates, into local community parameters. For example, location can be expressed as a particular sector of a particular field. In an example embodiment, the FMS 18 includes a field identification capability. For example, the FMS 18 can comprise a field identification capability such as that described in U.S. Patent Application No. 12/648,985 entitled "Auto-Detection of a Field in Fleet Management" filed on December 29, 2009 by Schmidt et al., which is incorporated herein in its entirety by reference. By way of example, but not limitation, an operator's assigned or reported wayline can be used as a basis for field determination. In an example embodiment, fields can be parameterized by geographical coordinates and associated with a particular owner name at the database 48. In a similar manner, a field can be divided into a predetermined number of individually identified sectors that can be defined by geographical parameters.

[0031] As shown in FIG. 4, in an example embodiment the field 1 1 can be identified by field name 60 and divided into a northwest sector 62, a north central sector 64, a northeast sector 66, a southwest sector 68, a south central sector 70, and a southeast sector 72. Each of the sectors can be defined by

geographical coordinates. For example, northwest sector 62 can be configured as a square bounded by (lat A, long A), (lat A, long B), (lat B, long A) and (lat B, long B) where "lat" abbreviates latitude and "long" abbreviates longitude.

Likewise, the other 5 sectors of the field 1 1 can be defined by four pairs of coordinates as shown in FIG. 4. In an example embodiment, field and sector parameters can be stored at the database 48. The location translation

submodule 52 can be configured to receive GPS coordinates provided in the rollover report 14 and compare them to field and sector coordinates stored at the database 48 to identify the field and sector in which the machine 10 is located. It is contemplated that other types of parameters, field identifications and sector identifications can be used dependent on the layout, geographical features or other field attributes.

[0032] The notification submodule 54 can be configured to format an alert message addressed to a predetermined contact that includes a rollover notification and machine location, which can be provided in GPS coordinates, local community coordinates, or by other parameters. In an example

embodiment, the alert message can further include machine and/or operator identification so a contact can learn which machine is disabled. In an example embodiment, an alert can message can be provided to a web application that can provide a fleet management web page that can be viewed by a fleet operator on a display screen associated with a computer, a smart phone, or other internet capable communication device. An example notification submodule 54 can provide a text or voice message to a contact's cell phone, PDA, smart phone or other communication device. In an example embodiment the notification submodule 54 can provide multiple alert messages to a plurality of contacts in a predetermined priority scheme stored at the database 48. By way of example, but not limitation, the notification submodule 54 can format an alert message and provide it to the CCD 40 which can provide it to a communications network, such as, but not limited to, the communications network 16, via the modem 46.

[0033] FIG. 5 depicts a flow diagram of an example method 60 that can be practiced at a machine. At block 62, machine location can be stored. For example, the location submodule 34 of the RDRM 12 at the machine 10 can store current location information provided by the positioning system 26. In an example embodiment, location information can be updated continuously or at predetermined intervals. At block 64, machine orientation can be monitored. For example, the RDRM 12 can receive and monitor orientation information from the sensors 24a..n. In an example embodiment, orientation information can be continuously monitored. At decision block 66 a determination can be made as to whether a rollover condition exists at a machine. For example, the orientation submodule 32 can compare orientation data from the sensors 24a..n to one or more predetermined parameters. In an example embodiment, a predetermined parameter is machine-specific. For example, a predetermined parameter can comprise a maximum roll angle, a maximum pitch angle and/or a maximum yaw angle for a particular machine type. If a machine orientation angle exceeds a predetermined maximum angle, a determination can be made that a rollover condition exists. If no condition exists, the method 60 can continue at block 62. However, if a rollover condition is detected, a rollover report can be provided at block 68. For example, the report submodule 36 can provide a report message that includes machine identification and current location to the TU 28 which can transmit it to the FMS 18 via the network 16.

[0034] FIG. 6 shows an example method 70 that can be practiced at a remote central server, for example at the FMS 18. At block 72, a rollover report can be received. For example, the CCD 40 can receive the rollover report 14 from the machine 10 via the modem 46. At block 74 contact information can be retrieved. For example, the contacts submodule 50 can retrieve predetermined machine-specific contact information from the database 48. At block 76 an alert message can be provided to a predetermined contact. For example, a text message can be sent to a mobile phone of predetermined contact at the number stored at the database 48 in association with the machine 10. The alert message can include notice of a rollover event and include machine 10 location. By way of example, but not limitation, the method 70 can further include translating GPS coordinates into other coordinates, such as local community parameters, to facilitate finding the disabled machine.

[0035] FIG. 7 shows an example method 80 that can be practiced by a system of the invention. Blocks previously discussed in regards to methods 60 and 70 will not be discussed again in reference to method 80. At block 82, a system can store a machine's current location. At block 84 the system can continuously monitor a machine's orientation. At decision block 86 a

determination can be made as to whether a machine is operating normally. If a rollover event is detected at block 86 the system can send a report at block 88, otherwise the method 80 continues at block 82. At block 90 contact information is retrieved so that a priority notification can be sent to a predetermined contact at block 92. At block 94 help can be dispatched to a machine's location. For example, a person who received an alert message can proceed to the machine location or can call for further assistance.

[0036] Thus, the invention can provide systems and methods for detecting a rollover condition or event and alerting a predetermined contact. In an example embodiment, the system can use equipment already installed at a machine, such as transmitter configured for cellular communication, or inertial sensors that are part of an automated guidance system at a machine. However, it is

contemplated that a system can have one or dedicated sensors and a dedicated transmitter. An example system can detect a rollover condition prior to a machine's collision with the ground and immediately send a rollover report, shortening the time that an operator must wait for assistance and increasing the likelihood that a report will be transmitted prior to any damage to a machine. A system can be practiced within a fleet management community, eliminating the need for third party intervention that can impose delays and raise privacy concerns, and ensuring that a party cognizant of agricultural operations is alerted quickly.

[0037] Although the invention has been described with reference to non- limiting example embodiments illustrated in the attached drawings, it is noted that equivalents may be employed and substitutions made herein without departing from the scope of the invention as recited in the appended claims. For example disclosed methods may be practiced in varying order and steps may be added or deleted without departing from the scope of the invention. In addition functions described as performed by a particular apparatus or module may be performed by a separate or different module or apparatus, or combined at a single module or apparatus. System elements disclosed as separate can be combined or reconfigured as will occur to those skilled in the art.

Claims

What is claimed is:

1 . A system, comprising:

a rollover detection and report module (RDRM) configured to detect and report a rollover condition at an agricultural machine; and

a rollover alert module (RAM) configured to alert a predetermined contact in response to said report.

2. The system of claim 1 , further comprising an orientation sensor at said machine.

3. The system of claim 1 , further comprising a transmitting means at said machine.

4. The system of claim 1 , further comprising a positioning means at said machine.

5. The system of claim 1 , wherein said rollover report includes said machine location.

6. The system of claim 1 wherein said predetermined contact is

designated by a user.

7. The system of claim 1 wherein the RDRM comprises:

an orientation submodule configured to detect a rollover condition at a machine;

a location submodule configured to store said machine location; and

a report submodule configured to report a rollover condition.

8. The system of claim 7, wherein said rollover condition is defined by a machine orientation angle that exceeds a predetermined threshold.

9. The system of claim 7, wherein said RDRM is configured to receive input from an orientation sensor at said machine to detect said rollover condition.

10. The system of claim 7, wherein said location submodule is configured to receive input from a geo-positioning means at said machine.

1 1 . The system of claim 7, wherein said RDRM is coupled to a

communication means at said machine, wherein said communication means is configured for cellular communication.

12. The system of claim 7, wherein said report includes said machine location.

13. The system of claim 7, wherein said RDRM is configured to detect said rollover condition prior to an impact caused by a rollover event.

14. The system of claim 7, further comprising a processor for performing processing operations at said rollover alert module.

15. The system of claim 1 wherein the RAM comprises:

a contacts submodule configured to provide predetermined machine-specific contact information; and

a notification submodule configured to provide a rollover alert to at least one predetermined contact associated with said contact information.

16. The system of claim 15 further comprising a location translation module configured to provide machine location in other than latitude and longitude coordinates.

17. The system of claim 15, wherein said contacts submodule is configured to retrieve said predetermined machine-specific contact information from a database.

18. A method, comprising:

storing a machine's current location;

monitoring said machine's orientation; and

detecting whether a rollover condition exists at said machine, wherein said detecting a rollover condition comprises comparing said machine's orientation angle to a predetermined parameter..

19. The method of claim 18, further comprising providing a rollover report in response to detecting a rollover condition.

20. The method of claim 18 further comprising:

retrieving predetermined machine-specific contact information; and providing an alert message to a contact associated with said predetermined machine-specific contact information.