Patent Document

RELATED APPLICATIONS 
       [0001]    The present application is a continuation of U.S. patent application Ser. No. 12/234,441, filed Sep. 19, 2008, which is a continuation of U.S. patent application Ser. No. 10/974,392, filed Oct. 26, 2004, entitled, “Reactive Replenishable Device Management,” now U.S. Pat. No. 7,444,192, both commonly assigned herewith. 
         [0002]    The present application is also related to co-pending U.S. patent application Ser. No. 10/974,335 filed Oct. 26, 2004 in the name of inventors Blake Dickinson, Lisa Lei Horluchi, and Nathaniel Jordan Ramer, entitled “Dynamic Replenisher Management”, commonly assigned herewith. 
     
    
     BACKGROUND OF THE INVENTION 
       [0003]    1. Field of the Invention 
         [0004]    The present invention relates to the field of computer science. More particularly, the present invention relates to reactive replenishable device management. 
         [0005]    2. Description of the Related Art 
         [0006]    Systems for monitoring numerous replenishable device parameters are known in the art. Such systems typically collect battery pack information, recharger information, or both, and make the information available for viewing by an operator. While such systems typically provide visibility with respect to parameters of a particular charger or replenishable device, acting upon these parameters is typically left to operator. Furthermore, operators responsible for multiple devices must scrutinize similar information for several devices in order to determine optimal replenishable device asset allocation. Thus the burden on the operator increases as the number of replenishable device assets increases. 
         [0007]    Accordingly, a need exists in the art for a solution that provides relatively integrated replenishable device management. A further need exists for such a solution that is relatively automated. Yet a further need exists for such a solution that provides relatively efficient replenishable device asset resource allocation. 
     
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         [0008]    The accompanying drawings, which are incorporated into and constitute a part of this specification, illustrate one or more embodiments of the present invention and, together with the detailed description, serve to explain the principles and implementations of the invention. In the drawings: 
           [0009]      FIG. 1  is a block diagram of a computer system suitable for implementing aspects of the present invention. 
           [0010]      FIG. 2  is a block diagram that illustrates a system for reactive control of one or more devices based at least in part on device measurement data obtained from the one or more devices in accordance with one embodiment of the present invention. 
           [0011]      FIG. 3  is a block diagram that illustrates a system for reactive control of one or more networked devices based at least in part on device measurement data obtained from the one or more devices in accordance with one embodiment of the present invention. 
           [0012]      FIG. 3A  is a block diagram that illustrates an apparatus for reactive control of one or more devices based at least in part on device measurement data obtained from the one or more devices in accordance with one embodiment of the present invention. 
           [0013]      FIG. 4  is a high level data flow diagram that illustrates dynamic control of one or more devices based at least in part on device measurement data collected from the one or more devices in accordance with one embodiment of the present invention. 
           [0014]      FIG. 4A  is a flow diagram that illustrates a method for reactive control of one or more devices based at least in part on device measurement data obtained from the one or more devices in accordance with one embodiment of the present invention. 
           [0015]      FIG. 4B  is a flow diagram that illustrates a method for optimized management of a fleet of replenishable devices and devices associated with the replenishable devices, in accordance with one embodiment of the present invention. 
           [0016]      FIG. 5  is a high level block diagram that illustrates a system for automatic control of one or more devices based at least in part on device measurement data obtained from the one or more devices in accordance with one embodiment of the present invention. 
           [0017]      FIG. 6  is a high level control flow diagram that illustrates automatic control of one or more devices based at least in part on device measurement data obtained from the one or more devices in accordance with one embodiment of the present invention. 
           [0018]      FIG. 7  is a data flow diagram that illustrates automatic control of one or more chargers based at least in part on device measurement data obtained from one or more batteries in accordance with one embodiment of the present invention. 
           [0019]      FIG. 8  is a data flow diagram that illustrates automatic control of one or more vehicles based at least in part on device measurement data obtained from the one or more vehicles and from one or more batteries associated with the one or more vehicles in accordance with one embodiment of the present invention. 
           [0020]      FIG. 9  is a high level block diagram that illustrates a system for issuing one or more management recommendations based at least in part on device measurement data obtained from one or more devices in accordance with one embodiment of the present invention. 
           [0021]      FIG. 10  is a high level control flow diagram that illustrates issuing one or more management recommendations based at least in part on device measurement data obtained from one or more devices in accordance with one embodiment of the present invention. 
           [0022]      FIG. 11  is a low level data flow diagram that illustrates issuing one or more management recommendations based at least in part on device measurement data obtained from one or more vehicles and from one or more batteries associated with the one or more vehicles in accordance with one embodiment of the present invention. 
           [0023]      FIG. 12  is a high level block diagram that illustrates a system for issuing one or more user alerts based at least in part on device measurement data obtained from one or more devices in accordance with one embodiment of the present invention. 
           [0024]      FIG. 13  is a high level control flow diagram that illustrates issuing one or more user alerts based at least in part on device measurement data obtained from one or more devices in accordance with one embodiment of the present invention. 
           [0025]      FIG. 14  is a low level data flow diagram that illustrates issuing one or more user alerts based at least in part on device measurement data obtained from one or more vehicles and from one or more batteries associated with the one or more vehicles in accordance with one embodiment of the present invention. 
           [0026]      FIG. 15  is a block diagram that illustrates dynamic control of one or more chargers based at least in part on device measurement data collected from the one or more chargers and one or more vehicles associated with the one or more chargers in accordance with one embodiment of the present invention. 
           [0027]      FIG. 16  is a block diagram that illustrates dynamic control of one or more chargers and one or more vehicles associated with the one or more chargers based at least in part on device measurement data collected from the one or more chargers and the one or more vehicles in accordance with one embodiment of the present invention. 
           [0028]      FIG. 17  is a block diagram that illustrates dynamic control of one or more chargers based at least in part on device measurement data collected from the one or more chargers an in accordance with one embodiment of the present invention. 
           [0029]      FIG. 18  is a flow diagram that illustrates a method for battery fault management in accordance with one embodiment of the present invention. 
       
    
    
     DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS 
       [0030]    Embodiments of the present invention are described herein in the context of reactive replenishable device management. Those of ordinary skill in the art will realize that the following detailed description of the present invention is illustrative only and is not intended to be in any way limiting. Other embodiments of the present invention will readily suggest themselves to such skilled persons having the benefit of this disclosure. Reference will now be made in detail to implementations of the present invention as illustrated in the accompanying drawings. The same reference indicators will be used throughout the drawings and the following detailed description to refer to the same or like parts. 
         [0031]    In the interest of clarity, not all of the routine features of the implementations described herein are shown and described. It will, of course, be appreciated that in the development of any such actual implementation, numerous implementation-specific decisions must be made in order to achieve the developer&#39;s specific goals, such as compliance with application- and business-related constraints, and that these specific goals will vary from one implementation to another and from one developer to another. Moreover, it will be appreciated that such a development effort might be complex and time-consuming, but would nevertheless be a routine undertaking of engineering for those of ordinary skill in the art having the benefit of this disclosure. 
         [0032]    In accordance with one embodiment of the present invention, the components, process steps, and/or data structures may be implemented using various types of operating systems (OS), computing platforms, firmware, computer programs, computer languages, and/or general-purpose machines. The method can be run as a programmed process running on processing circuitry. 
         [0033]    The processing circuitry can take the form of numerous combinations of processors and operating systems, or a stand-alone device. The process can be implemented as instructions executed by such hardware, hardware alone, or any combination thereof. The software may be stored on a program storage device readable by a machine. In addition, those of ordinary skill in the art will recognize that devices of a less general purpose nature, such as hardwired devices, field programmable logic devices (FPLDs), including field programmable gate arrays (FPGAs) and complex programmable logic devices (CPLDs), application specific integrated circuits (ASICs), or the like, may also be used without departing from the scope and spirit of the inventive concepts disclosed herein. 
         [0034]    In accordance with one embodiment of the present invention, the method may be implemented on a data processing computer such as a personal computer, workstation computer, mainframe computer, or high performance server running an OS such as Solaris® available from Sun Microsystems, Inc. of Santa Clara, Calif., Microsoft® Windows® XP and Windows® 2000, available from Microsoft Corporation of Redmond, Wash., or various versions of the Unix operating system such as Linux available from a number of vendors. The method may also be implemented on a multiple-processor system, or in a computing environment including various peripherals such as input devices, output devices, displays, pointing devices, memories, storage devices, media interfaces for transferring data to and from the processor(s), and the like. In addition, such a computer system or computing environment may be networked locally, or over the Internet. 
         [0035]    In the context of the present invention, the term “network” comprises local area networks, wide area networks, the Internet, cable television systems, telephone systems, wireless telecommunications systems, fiber optic networks, ATM networks, frame relay networks, satellite communications systems, and the like. Such networks are well known in the art and consequently are not further described here. 
         [0036]    In the context of the present invention, the term “identifier” describes one or more numbers, characters, symbols, or the like. More generally, an “identifier” describes any entity that can be represented by one or more bits. 
         [0037]    In the context of the present invention, the term “identification data” describes one or more time-invariant attributes of a device. By way of example, identification data comprises an identifier of the device, the size of the device, the capacity of the device, the manufacturer of the device, the maintenance schedule of the device, the warranty schedule of the device, and the like. 
         [0038]    In the context of the present invention, the term “historical data” describes one or more time-variant attributes of a device. Exemplary historical data are shown in Table 1, below. 
         [0000]    
       
         
               
             
               
               
             
           
               
                 TABLE 1 
               
               
                   
               
               
                 Historical Data 
               
               
                   
               
             
             
               
                   
               
             
          
           
               
                   
                 Date Battery Monitor Identification (BMID) Was Initialized 
               
               
                   
                 Days in Operation 
               
               
                   
                 Total Charge Abs 
               
               
                   
                 Total Charge kilowatt-hours 
               
               
                   
                 Total Discharge Ahs 
               
               
                   
                 Total Discharge kilowatt-hours 
               
               
                   
                 Total Fast Charge Time 
               
               
                   
                 # of Fast Charge Events 
               
               
                   
                 Total Full Charge Time 
               
               
                   
                 Number of Complete Full Charge Events 
               
               
                   
                 Total Equalization Charge Time 
               
               
                   
                 Number of Complete Equalization Charge Events 
               
               
                   
                 Total External Charge Time 
               
               
                   
                 Total Run Time 
               
               
                   
                 Total Key On Time 
               
               
                   
                 Total Key Off Time 
               
               
                   
                 Maximum Battery Temperature T 1   
               
               
                   
                 Number of Times the Battery Exceeds Temperature T 1   
               
               
                   
                 Minimum Battery Temperature T 2   
               
               
                   
                 Number of Times the Battery Temperature falls below T 2   
               
               
                   
                 Average Battery Temperature 
               
               
                   
                 Minimum Battery Voltage V 1   
               
               
                   
                 Number of Times the Battery Voltage Falls Below V 1   
               
               
                   
                 Maximum Battery Voltage V 2   
               
               
                   
                 Number of Times the Battery State-Of-Charge Falls Below 20% 
               
               
                   
                 Number of Low Water Events 
               
               
                   
                 Last Equalization Start Date 
               
               
                   
                 Last Equalization Start Time 
               
               
                   
                 Last Equalization End Date 
               
               
                   
                 Last Equalization End Time 
               
               
                   
                 Last Equalization Ahs 
               
               
                   
                 Last Equalization kilowatt-hours 
               
               
                   
                 Last Equalization Term Code 
               
               
                   
                 Last Equalization Start Temperature 
               
               
                   
                 Last Equalization Start Voltage 
               
               
                   
                 Last Equalization Start Current 
               
               
                   
                 Last Equalization End Temperature 
               
               
                   
                 Last Equalization End State-Of-Charge 
               
               
                   
                 Last Equalization End Voltage 
               
               
                   
                 Last Equalization End Current 
               
               
                   
                 Maximum Days Between Equalizations 
               
               
                   
                 Maximum Ahs Between Equalizations 
               
               
                   
                 Days Since Last Complete Equalization 
               
               
                   
                 Ahs Since Last Complete Equalization 
               
               
                   
                   
               
             
          
         
       
     
         [0039]    In the context of the present invention, the term “real-time data” describes a single sample of one or more time-variant attributes of a device. Real-time data comprises real-time descriptive data and real-time performance data. Exemplary real-time data are shown in Table 2, below. The real-time data in Table 2 is illustrative and is not intended to be an exhaustive list. Those of ordinary skill in the art will recognize that other real-time data may be used. 
         [0000]    
       
         
               
             
               
               
             
           
               
                 TABLE 2 
               
               
                   
               
               
                 Real-Time Data 
               
               
                   
               
             
             
               
                   
               
             
          
           
               
                   
                 Charge Ahs 
               
               
                   
                 Discharge Ahs 
               
               
                   
                 Charge Kilowatt-hours 
               
               
                   
                 Discharge Kilowatt-hours 
               
               
                   
                 Fast Charge Time 
               
               
                   
                 Full Charge Time 
               
               
                   
                 Equalization Charge Time 
               
               
                   
                 Key On Time 
               
               
                   
                 Key Off Time 
               
               
                   
                 Run Time 
               
               
                   
                 Full Charge Complete 
               
               
                   
                 Equalization Complete 
               
               
                   
                 Minimum Battery State-Of-Charge 
               
               
                   
                 Maximum Battery State-Of-Charge 
               
               
                   
                 Average Battery State-Of-Charge 
               
               
                   
                 Minimum Battery Temperature T 2   
               
               
                   
                 Maximum Battery Temperature T 1   
               
               
                   
                 Average Battery Temperature 
               
               
                   
                 Minimum Battery Voltage V 1   
               
               
                   
                 Maximum Battery Discharge Current 
               
               
                   
                 Low Water Event 
               
               
                   
                 Fault Code(s) 
               
               
                   
                   
               
             
          
         
       
     
         [0040]      FIG. 1  depicts a block diagram of a computer system  100  suitable for implementing aspects of the present invention. As shown in  FIG. 1 , computer system  100  includes a bus  102  which interconnects major subsystems such as a central processor  104 , a system memory  106  (typically RAM), an input/output (I/O controller  108 , an external device such as a display screen  110  via display adapter  112 , serial ports  114  and  116 , a keyboard  118 , a fixed disk drive  120 , a floppy disk drive  122  operative to receive a floppy disk  124 , and a CD-ROM player  126  operative to receive a CD-ROM  128 . Many other devices can be connected, such as a pointing device  130  (e.g., a mouse) connected via serial port  114  and a modem  132  connected via serial port  116 . Modem  132  may provide a direct connection to a remote server via a telephone link or to the Internet via a POP (point of presence). Alternatively, a network interface adapter  134  may be used to interface to a local or wide area network using any network interface system known to those skilled in the art (e.g., Ethernet, xDSL, AppleTalk™). 
         [0041]    Many other devices or subsystems (not shown) may be connected in a similar manner. Also, it is not necessary for all of the devices shown in  FIG. 1  to be present to practice the present invention, as discussed below. Furthermore, the devices and subsystems may be interconnected in different ways from that shown in  FIG. 1 . The operation of a computer system such as that shown in  FIG. 1  is readily known in the art and is not discussed in detail in this application, so as not to overcomplicate the present discussion. Code to implement the present invention may be operably disposed in system memory  106  or stored on storage media such as fixed disk  120 , floppy disk  124 , or CD-ROM  128 . 
         [0042]      FIGS. 2 ,  3 , and  3 A illustrate systems for reactive control of one or more devices based at least in part on device measurement data obtained from the one or more devices in accordance with embodiments of the present invention.  FIG. 2  illustrates the one or more devices operatively coupled via a dedicated communication means to a remote device manager adapted to control the one or more devices.  FIG. 3  illustrates the one or more devices and the remote device manager operatively coupled via a network.  FIG. 3A  illustrates the device manager as part of the one or more devices. 
         [0043]    Turning now to  FIG. 2 , a block diagram that illustrates a system for reactive control of one or more devices based at least in part on device measurement data obtained from the one or more devices in accordance with one embodiment of the present invention is presented. As shown in  FIG. 2 , one or more devices  206  comprise a local device controller  240  adapted to control the one or more devices  206  based at least in part on one or more commands from manual control means  238 , or automatic controller  228 . Battery  200  and vehicle  204  are exemplary devices represented by one or more devices  206 . Remote device manager  202  may receive input via manual input means  252 . The type of input received via manual input means  252  may vary depending at least in part on the particular device or devices being managed. Exemplary manual inputs are listed below in Table 3. The manual input data in Table 3 is illustrative and is not intended to be an exhaustive list. Those of ordinary skill in the art will recognize that other manual input data may be used. Manual input means  252  comprises an input device, such as alphanumeric keyboard  118 , numeric keyboard  118 , joystick  116 , roller  114 , directional navigation pad  126 , or display screen  110  of  FIG. 1 . Those of ordinary skill in the art will recognize that other input devices may be used. 
         [0000]    
       
         
               
             
               
               
             
           
               
                 TABLE 3 
               
               
                   
               
               
                 Manual Inputs 
               
               
                   
               
             
             
               
                   
               
             
          
           
               
                   
                 Utility Schedule 
               
               
                   
                 Vehicle Pricing 
               
               
                   
                 Replenishable Device Pricing 
               
               
                   
                 Vehicle Purchase Profile 
               
               
                   
                 Replenishable Device Purchase Profile 
               
               
                   
                 Maintenance Schedule 
               
               
                   
                 Dealer/Distributor Contact Information 
               
               
                   
                 Plant Operation Schedule 
               
               
                   
                 Driver Associated with a Particular Vehicle 
               
               
                   
                 Vehicle Type of a Particular Vehicle 
               
               
                   
                 Vehicle Location 
               
               
                   
                 Charger Associated with a Particular Vehicle 
               
               
                   
                 Vehicle Periodic Maintenance Log/Status 
               
               
                   
                 Local Daylight Savings Time 
               
               
                   
                 Rechargeable Device Manufacture Date 
               
               
                   
                 Vehicle Manufacture Date 
               
               
                   
                 Driver Complaints for a Particular Vehicle 
               
               
                   
                 Operator Schedule 
               
               
                   
                 Utility Power Purchase Agreement(s) 
               
               
                   
                   
               
             
          
         
       
     
         [0044]    According to one embodiment, the one or more devices  206  comprise one or more replenishers and one or more replenishable devices. The one or more replenishers may comprise one or more refuelers and the one or more replenishable devices may comprise one or more refuelable devices. By way of example, the one or more refuelable devices may comprise a fuel cell. According to another embodiment, the one or more devices may comprise one or more replenishers and one or more rechargeable devices. According to one embodiment, the one or more replenishers may comprise one or more chargers and the one or more replenishable devices may comprise one or more batteries. According to another embodiment, the one or more chargers may comprise battery chargers and the one or more batteries may comprise one or more replaceable battery packs. According to another embodiment, the one or more devices  206  may further comprise an electric vehicle powered by the one or more replaceable battery packs. According to another embodiment, the one or more devices  206  may further comprise a vehicle powered by one or more replaceable or refuelable fuel cells. The vehicle may be any vehicle that is powered at least in part by a replenishable device. By way of example, the vehicle may comprise an electrically- or fuel cell-powered fork lift, automobile, truck, motorcycle, moped, scooter, airplane, locomotive, submersible vessel, boat, spacecraft, automated guided vehicle (AGV), and automated unguided vehicle (AUGV). 
         [0045]    According to embodiments of the present invention, the replaceable battery packs are based on one or more of the following battery technologies: lead acid, nickel cadmium, nickel metal hydride, nickel zinc, nickel iron, silver zinc, nickel hydrogen, lithium ion, lithium polymer, lithium/iron sulfide, zinc air, zinc bromine, sodium sulfur, regenerative fuel cell, and ultracapacitor. The battery technologies listed are for the purpose of illustration and are not intended to be limiting in any way. Those of ordinary skill in the art will recognize that replaceable battery packs based on other battery technologies may be used. 
         [0046]    According to another embodiment of the present invention, the one or more devices  206  comprises a vehicle powered by the one or more replenishable devices, and the one or more devices  206  further comprises one or more devices that reside in, on, or are otherwise associated with the vehicle. By way of example, the one or more devices may comprise one or more movement sensors, access control devices, shock meters, force meters, and the like. 
         [0047]    According to another embodiment of the present invention, the one or more devices  206  comprises automation equipment. 
         [0048]    According to another embodiment of the present invention, the one or more devices  206  comprises energy management systems, such as distributed generation equipment and the like. 
         [0049]    Still referring to  FIG. 2 , remote device manager  202  comprises an aggregator  210 , an analyzer  218 , a determiner  222 , an automatic controller, an advisor  226 , and an alerter  224 . Aggregator  210  is adapted to receive device measurement data  208  from the one or more devices  206 . The received device measurement data  208  comprises one or more of identification data  212 , historical data  214 , and real-time data  216 . Analyzer  218  is adapted to update one or more usage profiles  220  based at least in part on one or more of the identification data  212 , the historical data  214 , and the real-time data  216 . 
         [0050]    The one or more usage profiles  220  comprise information regarding the use of the one or more devices  206 . The one or more usage profiles  220  may be stored in a memory (not shown in  FIG. 2 ) associated with the remote device manager  202 . 
         [0051]    Determiner  222  is adapted to invoke one or more of automatic controller  228 , advisor  226 , and alerter  224  based at least in part on the one or more usage profiles  220 . Automatic controller  228  is adapted to automatically control attributes or operations of the one or more devices based at least in part on the device measurement data  208  obtained from the one or more devices  206  by issuing one or more commands  236  to the one or more devices  206 . Automatic controller  228  is described in more detail below with respect to  FIGS. 5-8 . Advisor  226  is adapted to issue one or more management recommendations to a user  234 , based at least in part on the device measurement data  208  obtained from the one or more devices. Advisor  226  is described in more detail below with respect to  FIGS. 9-11 . Alerter  224  is adapted to issue one or more user alerts to the user  234 , based at least in part on the device measurement data  208  obtained from the one or more devices  206  (either directly from real-time data  216  as shown by reference numeral  250 , or from usage profile  220 ). Alerter  224  is described in more detail below with respect to  FIGS. 12-14 . Manual control means  238  may be used by user  234  to control the one or more devices  206  based at least in part on one or more management recommendations received from advisor  226 , or one or more user alerts received from alerter  224 . Manual control means  238  comprises an input device, such as alphanumeric keyboard  118 , numeric keyboard  118 , joystick  116 , roller  114 , directional navigation pad  126 , or display screen  110  of  FIG. 1 . Those of ordinary skill in the art will recognize that other input devices may be used. 
         [0052]    In operation, device measurement data  208  is transferred from device  206  to remote device manager  202 . According to one embodiment of the present invention, the transfer is initiated by the one or more devices  206 . According to another embodiment of the present invention, the transfer is initiated by the remote device manager  202 . Aggregator  210  of remote device manager  202  receives the device measurement data  208 . Analyzer  218  updates one or more usage profiles  220  based at least in part on one or more of the identification data  212 , the historical data  214 , and the real-time data  216 . Determiner  222  invokes zero or more of automatic controller  228 , advisor  226 , and alerter  224  based at least in part on the one or more usage profiles  220 . Automatic controller  228  automatically controls attributes or operations of the one or more devices  206  based at least in part on the device measurement data  208  obtained from the one or more devices  206  by issuing one or more commands  236  to the one or more devices  206 . Advisor  226  issues one or more management recommendations to a user  234 , based at least in part on the device measurement data  208  obtained from the one or more devices. Alerter  224  issues one or more user alerts to the user  234 , based at least in part on the device measurement data  208  obtained from the one or more devices  206 . 
         [0053]    According to one embodiment of the present invention, remote device manager  202  comprises one or more of automatic controller  228 , adviser  226 , and alerter  224 . 
         [0054]    Turning now to  FIG. 3 , a block diagram that illustrates a system for reactive control of one or more networked devices based at least in part on device measurement data obtained from the one or more devices in accordance with one embodiment of the present invention is presented.  FIG. 3  is similar to  FIG. 2 , except that the one or more devices illustrated in  FIG. 3  are operatively coupled to a remote device manager via a network. As shown in  FIG. 3 , one or more devices  306  comprise a local device controller  340  adapted to control the one or more devices  306  based at least in part on one or more commands from manual control means  338 , or automatic controller  328 . Battery  300  and vehicle  304  are exemplary devices represented by one or more device  306 . The one or more devices  306  are operatively coupled to a remote device manager  302  via a network  344 . At least part of network  344  may reside inside or outside of a physical facility where one or more of the one or more devices  306  and the remote device manager  302  are located. Remote device manager  302  may receive input via manual input means  352 . The type of input received via manual input means  352  may vary depending at least in part on the particular device or devices being managed. Exemplary manual inputs are listed above in Table 3. The manual input data in Table 3 is illustrative and is not intended to be an exhaustive list. Those of ordinary skill in the art will recognize that other manual input data may be used. Manual input means  352  comprises an input device, such as alphanumeric keyboard  118 , numeric keyboard  118 , joystick  116 , roller  114 , directional navigation pad  126 , or display screen  110  of  FIG. 1 . Those of ordinary skill in the art will recognize that other input devices maybe used. 
         [0055]    According to one embodiment of the present invention, the one or more devices  306  comprise one or more replenishers and one or more replenishable devices. According to one embodiment of the present invention, the one or more replenishers comprise one or more refuelers and the one or more replenishable devices comprises one or more refuelable devices. By way of example, the one or more refuelable devices may comprise a fuel cell. According to another embodiment of the present invention, the one or more devices comprises one or more replenishers and one or more rechargeable devices. According to one embodiment of the present invention, the one or more replenishers comprises one or more chargers and the one or more replenishable devices comprises one or more batteries. According to another embodiment of the present invention, the one or more chargers comprise battery chargers and the one or more batteries comprise one or more replaceable battery packs. According to another embodiment of the present invention, the one or more devices  306  further comprises an electric vehicle powered by the one or more replaceable battery packs. According to another embodiment of the present invention, the one or more devices  306  further comprises a vehicle powered by one or more replaceable or refuelable fuel cells. The vehicle may be any vehicle that is powered at least in part by a replenishable device. By way of example, the vehicle may comprise an electrically- or fuel cell-powered fork lift, automobile, truck, motorcycle, moped, scooter, airplane, locomotive, submersible vessel, boat, spacecraft, automated guided vehicle (AGV), and automated unguided vehicle (AUGV). 
         [0056]    According to another embodiment of the present invention, the one or more devices  306  comprises a vehicle powered by the one or more replenishable devices, and the one or more devices  306  further comprises one or more devices that reside in, on, or are otherwise associated with the vehicle. By way of example, the one or more devices may comprise one or more movement sensors, access control devices, shock meters, force meters, and the like. 
         [0057]    According to another embodiment of the present invention, the one or more devices  306  comprises automation equipment. 
         [0058]    According to another embodiment of the present invention, the one or more devices  306  comprises energy management systems, such as distributed generation equipment and the like. 
         [0059]    According to embodiments of the present invention, the replaceable battery packs are based on one or more of the following battery technologies: lead acid, nickel cadmium, nickel metal hydride, nickel zinc, nickel iron, silver zinc, nickel hydrogen, lithium ion, lithium polymer, lithium/iron sulfide, zinc air, zinc bromine, sodium sulfur, regenerative fuel cell, and ultracapacitor. The battery technologies listed are for the purpose of illustration and are not intended to be limiting in any way. Those of ordinary skill in the art will recognize that replaceable battery packs based on other battery technologies may be used. 
         [0060]    Still referring to  FIG. 3 , remote device manager  302  comprises an aggregator  310 , an analyzer  318 , a determiner  322 , an automatic controller, an advisor  326 , and an alerter  324 . Aggregator  310  is adapted to receive device measurement data  308  from the one or more devices  306  (either directly from real-time data  316  as shown by reference numeral  350 , or from usage profile  320 ). The received device measurement data  308  comprises one or more of identification data  312 , historical data  314 , and real-time data  316 . Analyzer  318  is adapted to updates one or more usage profiles  320  based at least in part on one or more of the identification data  312 , the historical data  314 , and the real-time data  316 . 
         [0061]    The one or more usage profiles  320  comprise information regarding the use of the one or more devices  306 . The one or more usage profiles  320  may be stored in a memory (not shown in  FIG. 3 ) associated with the remote device manager  302 . 
         [0062]    Determiner  322  is adapted to invoke one or more of automatic controller  328 , advisor  326 , and alerter  324  based at least in part on the one or more usage profiles  320 . Automatic controller  328  is adapted to automatically control attributes or operations of the one or more devices based at least in part on the device measurement data  308  obtained from the one or more devices  306  by issuing one or more commands  336  to the one or more devices  306 . Automatic controller  328  is described in more detail below with respect to  FIGS. 5-8 . Advisor  326  is adapted to issue one or more management recommendations to a user  334 , based at least in part on the device measurement data  308  obtained from the one or more devices. Advisor  326  is described in more detail below with respect to  FIGS. 9-11 . Alerter  324  is adapted to issue one or more user alerts to the user  334 , based at least in part on the device measurement data  308  obtained from the one or more devices  306 . Alerter  324  is described in more detail below with respect to  FIGS. 12-14 . Manual control means  338  may be used by user  334  to control the one or more devices  306  based at least in part on one or more management recommendations received from advisor  326 , or one or more user alerts received from alerter  324 . Manual control means  338  comprises an input device, such as alphanumeric keyboard  118 , numeric keyboard  118 , joystick  116 , roller  114 , directional navigation pad  126 , or display screen  110  of  FIG. 1 . Those of ordinary skill in the art will recognize that other input devices may be used. 
         [0063]    In operation, device measurement data  308  is transferred from device  306  to remote device manager  302 . According to one embodiment of the present invention, the transfer is initiated by the one or more devices  306 . According to another embodiment of the present invention, the transfer is initiated by the remote device manager  302 . Aggregator  310  of remote device manager  302  receives the device measurement data  308 . Analyzer  318  updates one or more usage profiles  320  based at least in part on one or more of the identification data  312 , the historical data  314 , and the real-time data  316 . Determiner  322  invokes zero or more of automatic controller  328 , advisor  326 , and alerter  324  based at least in part on the one or more usage profiles  320 . Automatic controller  328  automatically controls operations or attributes of the one or more devices  306  based at least in part on the device measurement data  308  obtained from the one or more devices  306  by issuing one or more commands  336  to the one or more devices  306 . Advisor  326  issues one or more management recommendations to a user  334 , based at least in part on the device measurement data  308  obtained from the one or more devices. Alerter  324  issues one or more user alerts to the user  334 , based at least in part on the device measurement data  308  obtained from the one or more devices  306 . 
         [0064]    According to one embodiment of the present invention, remote device manager  302  comprises one or more of automatic controller  328 , adviser  326 , and alerter  324 . 
         [0065]    Turning now to  FIG. 3A , a block diagram that illustrates an apparatus for reactive control of one or more devices based at least in part on device measurement data obtained from the one or more devices in accordance with one embodiment of the present invention. Unlike  FIGS. 2 and 3 ,  FIG. 3A  shows one or more devices  3 A 06  that comprise a device manager  3 A 02 . Device manager  3 A 02  is configured to operate as discussed previously with respect to reference numeral  202  of  FIG. 2  and reference numeral  302  of  FIG. 3 , except that the communication of measurement data  3 A 08  to the device manager  3 A 02  and the communication of commands from the device manager  3 A 02  to the local device controller  3 A 40  occurs within the one or more devices  3 A 06 . 
         [0066]    Turning now to  FIG. 4 , a high level data flow diagram that illustrates dynamic control of one or more devices based at least in part on device measurement data collected from the one or more devices in accordance with one embodiment of the present invention is presented. As shown in  FIG. 4 , device measurement data comprising one or more of identification data  412 , historical performance and descriptive data  414 , and real-time performance and descriptive data  416  are obtained from one or more devices, such as a charger,  452 , a battery  400 , and a vehicle  404 . The device measurement data is analyzed to update one or more usage profiles  420 . According to one embodiment of the present invention, an automatic controller  428  uses the one or more usage profiles  420  to automatically control attributes or operations of the one or more devices ( 400 ,  404 , and  452 ). According to another embodiment of the present invention, an advisor  426  uses the one or more usage profiles  420  to issue one or more management recommendations to a user. According to another embodiment of the present invention, an alerter  426  uses the one or more usage profiles to issue one or more user alerts to a user. Having the benefit of a management recommendation from advisor  426 , or an alert from alerter  426 , the user may control the one or more devices ( 400 ,  404 , and  452 ) via manual control means  438 . 
         [0067]    Turning now to  FIG. 4A , a flow diagram that illustrates a method for reactive control of one or more devices based at least in part on device measurement data obtained from the one or more devices in accordance with one embodiment of the present invention is presented.  FIG. 4A  corresponds with  FIGS. 2 and 3 . The processes illustrated in  FIG. 4A  may be implemented in hardware, software, firmware, or a combination thereof. At  4 A 00 , device measurement data from one or more devices is received. The device measurement data comprises one or more of identification data, historical data, and real-time data. At  4 A 05 , one or more usage profiles associated with the device are modified based at least in part on the device measurement data. At  4 A 15 , a determination is made regarding whether automatic control of the one or more devices is enabled. If automatic control is enabled, the automatic control is performed at  4 A 20 . At  4 A 25 , a determination is made regarding whether management recommendations with respect to the one or more devices are enabled. If management recommendations are enabled, the management recommendation processing is performed at  4 A 30 . At  4 A 35 , a determination is made regarding whether user alerts with respect to the one or more devices is enabled. If user alerts is enabled, the user alert processing is performed at  4 A 40 . 
         [0068]    Turning now to  FIG. 4B , a flow diagram that illustrates a method for optimized management of a fleet of replenishable devices and devices associated with the replenishable devices, in accordance with one embodiment of the present invention is presented. The processes illustrated in  FIG. 4B  may be implemented in hardware, software, firmware, or a combination thereof. At  4 B 00 , device usage information for a fleet of replenishable devices and vehicles associated with the replenishable devices is accumulated. Step  4 B 00  may be performed using the process illustrated in  FIG. 4A , above. At  4 B 04 , the accumulated device usage information is stored in a global memory. At  4 B 10 , the device usage information accumulated at  4 B 00  and stored at  4 B 05  is used to manage fleet assets. By way of example, if the accumulated device usage information indicates a first vehicle is over utilized and a second vehicle capable of performing substantially the same functions as the first vehicle is underutilized, the first vehicle may be switched with the second vehicle. As a further example, if the accumulated device usage information indicates the fleet as a whole is over utilized, additional devices may be added to the fleet. Likewise, if the accumulated device usage information indicates the fleet as a whole is underutilized, one or more devices may be removed from the fleet. 
         [0069]      FIGS. 5-14  illustrate more detail for an automatic controller, an advisor, and an alerter in accordance with embodiments of the present invention.  FIGS. 5-8  illustrate an automatic controller,  FIGS. 9-11  illustrate an advisor, and  FIGS. 12-14  illustrate an alerter. 
         [0070]    Turning now to  FIG. 5 , a high level block diagram that illustrates a system for automatic control of one or more devices based at least in part on device measurement data obtained from the one or more devices in accordance with one embodiment of the present invention is presented. As shown in  FIG. 5 , device  506  comprises a local device controller  540  adapted to control the one or more devices  506  based at least in part on one or more commands from automatic controller  528 . According to one embodiment of the present invention, device  506  and remote device controller  502  are operatively coupled via a dedicated communication means. According to another embodiment of the present invention, device  506  and remote device manager  502  are operatively coupled via a network (not shown in  FIG. 5 ). Remote device manager  502  comprises an analyzer  518  and an automatic controller  528 . Analyzer  518  is adapted to update one or more usage profiles  520  based at least in part on one or more of the identification data, the historical data, and the real-time data that comprises the device measurement data  508 . 
         [0071]    The one or more usage profiles  520  comprise information regarding the use of the one or more devices  506 . The one or more usage profiles  520  may be stored in a memory associated with the remote device manager  502 . 
         [0072]    Automatic controller  528  is adapted to automatically control attributes or operations of the one or more devices  506  based at least in part on the device measurement data  508  obtained from the one or more devices  506  by issuing one or more commands  536  to the one or more devices  506 . 
         [0073]    In operation, device measurement data  508  is transferred from device  506  to remote device manager  502 . According to one embodiment of the present invention, the transfer is initiated by the one or more devices  506 . According to another embodiment of the present invention, the transfer is initiated by the remote device manager  502 . Analyzer  518  updates one or more usage profiles  520  based at least in part on one or more of the identification data, the historical data, and the real-time data that comprises the device measurement data  508 . Automatic controller  528  automatically controls attributes or operations of the one or more devices  506  based at least in part on the device measurement data  508  obtained from the one or more devices  506  by issuing one or more commands  536  to the one or more devices  506 . 
         [0074]    Turning now to  FIG. 6 , a high level control flow diagram that illustrates automatic control of one or more devices based at least in part on device measurement data obtained from the one or more devices in accordance with one embodiment of the present invention is presented.  FIG. 6  corresponds with  FIG. 5  and provides more detail for reference numeral  4 A 20  of  FIG. 4A . The processes illustrated in  FIG. 6  may be implemented in hardware, software, firmware, or a combination thereof. At  600 , a usage profile corresponding to a device is analyzed. At  605 , a determination is made regarding whether the device usage is sub-optimal. If the device usage is sub-optimal, at  610  a command is issued to automatically perform one or more maintenance operations, or to adjust one or more device parameters. Alternatively, the remote device manager stores the command and the one or more devices are adapted to query the remote device manager for the command. 
         [0075]    According to one embodiment of the present invention, process  610  comprises adjusting one or more charge rates. According to another embodiment of the present invention, process  610  comprises adjusting a battery monitor identification (BMID) device to optimize charging rates. According to another embodiment of the present invention, process  610  comprises watering a battery. According to another embodiment of the present invention, process  610  comprises unscheduled battery equalization. 
         [0076]    According to another embodiment of the present invention, process  610  comprises adjusting one or more vehicle performance levels. By way of example, process  610  may comprise adjusting one or more of the vehicle traction acceleration, the vehicle speed, and if the vehicle is a fork lift, the vehicle lift rate and the vehicle lift lockout. 
         [0077]    Turning now to  FIG. 7 , a data flow diagram that illustrates automatic control of one or more chargers based at least in part on device measurement data obtained from one or more batteries in accordance with one embodiment of the present invention is presented. As shown in column  702 , the types of data used for automatic control of chargers comprise identification data  704 , real-time descriptive data  706 , real-time performance data  708 , and historical data  710 . As shown in column  704 , exemplary descriptive data  706  comprises battery water level  712 , battery temperature  714 , and battery state-of-charge  716 . Additionally, exemplary real-time performance data comprises battery faults  718 , battery capacity  720 , battery usage  722 , and battery charge rate  724 . Exemplary battery fault information is presented in Table 4, below. The battery fault information listed in Table 4 is illustrative and is not intended to be an exhaustive list. Those of ordinary skill in the art will recognize that other battery fault information may be used. Column  706  illustrates information derivable from the sample data in column  704 . A low water level condition  726  is indicated if the battery water level  712  falls below a predetermined water level. A low state-of-charge condition  728  is indicated if the battery state-of-charge falls below a predetermined state-of-charge level. A sub-optimized charging regimen  730  or a sub-par battery performance  732  may also be indicated based at least in part on device measurement data obtained from the battery  702 . 
         [0000]    
       
         
               
             
               
               
             
           
               
                 TABLE 4 
               
               
                   
               
               
                 Fault Event Information 
               
               
                   
               
             
             
               
                   
               
             
          
           
               
                   
                 Charger Identifier 
               
               
                   
                 Charge Port 
               
               
                   
                 Fault Start Date 
               
               
                   
                 Fault Start Time 
               
               
                   
                 Fault End Date 
               
               
                   
                 Fault End Time 
               
               
                   
                 Fault Code 
               
               
                   
                 Fault Information 
               
               
                   
                   
               
             
          
         
       
     
         [0078]    Charge Event Data is a type of real-time data. Exemplary real-time data is listed in Table 5, below. The charge event data listed in Table 5 is illustrative and is not intended to be an exhaustive list. Those of ordinary skill in the art will recognize that other charge event data may be used. 
         [0000]    
       
         
               
             
               
               
             
           
               
                 TABLE 5 
               
               
                   
               
               
                 Charge Event Data 
               
               
                   
               
             
             
               
                   
               
             
          
           
               
                   
                 Charger Identifier 
               
               
                   
                 Charge Port 
               
               
                   
                 Charge Start Date 
               
               
                   
                 Charge Start Time 
               
               
                   
                 Charge End Date 
               
               
                   
                 Charge End Time 
               
               
                   
                 Charge Time 
               
               
                   
                 Charge Ahs 
               
               
                   
                 Charge KWhs 
               
               
                   
                 Charge Start Temperature 
               
               
                   
                 Charge End Temperature 
               
               
                   
                 Charge Start State-Of-Charge 
               
               
                   
                 Charge End State-Of-Charge 
               
               
                   
                 Charge Start Voltage 
               
               
                   
                 Charge End Voltage 
               
               
                   
                 Charge Start Current 
               
               
                   
                 Charge End Current 
               
               
                   
                 Charge Type 
               
               
                   
                 Charge Start Code 
               
               
                   
                 Charge Term Code 
               
               
                   
                   
               
             
          
         
       
     
         [0079]    Exemplary battery charge parameters are listed in Table 6, below. The battery charge parameters listed in Table 6 is illustrative and is not intended to be an exhaustive list. Those of ordinary skill in the art will recognize that other battery charge parameters may be used. 
         [0000]    
       
         
               
             
               
               
             
           
               
                 TABLE 6 
               
               
                   
               
               
                 Battery Charge Parameters 
               
               
                   
               
             
             
               
                   
               
             
          
           
               
                   
                 Battery Identifier 
               
               
                   
                 Truck Identifier 
               
               
                   
                 Battery Type 
               
               
                   
                 Number of Cells 
               
               
                   
                 Battery Capacity 
               
               
                   
                 Start Current Limit 
               
               
                   
                 FC State-Of-Charge Limit 
               
               
                   
                 Maximum Ahs between 
               
               
                   
                 Maximum Days Between Equalizations 
               
               
                   
                 Equalization day of week 
               
               
                   
                 Internal Resistance 
               
               
                   
                 Target Voltage Limit 
               
               
                   
                 Temperature Fold back Coefficient 
               
               
                   
                   
               
             
          
         
       
     
         [0080]    Column  708  illustrates exemplary automatic control measures that may be initiated based at least in part on the indicators in column  706 . In more detail, a low water level indication triggers a command to a watering system  742  that effectuates automatic watering of the battery  702 . A low battery state-of-charge triggers a reduction of temperature fold back in small steps per week  736 . A sub-optimized charging regimen  730  triggers an adjustment of the charge rates. Sub-par battery performance  732  triggers initiation of unscheduled battery equalization 
         [0081]    Turning now to  FIG. 8 , a data flow diagram that illustrates automatic control of one or more vehicles based at least in part on device measurement data obtained from the one or more vehicles and from one or more batteries associated with the one or more vehicles in accordance with one embodiment of the present invention is presented. As shown in column  802 , the types of data used for automatic control of the one or more vehicles comprises vehicle identification data  804 , vehicle real-time descriptive data  806 , vehicle real-time performance data  808 , vehicle and battery historical data  810 , and battery real-time descriptive data, identification data, and real-time performance data  812 . As shown in column  804 , exemplary vehicle real-time descriptive data  806  comprises energy usage  814  and charge compliance  816 . Additionally, exemplary vehicle real-time performance data comprises faults  818 . Exemplary battery real-time performance data comprises the battery state of charge  820 . Column  806  illustrates information derivable from the sample data in column  804 . Energy usage data  814 , charge compliance data  816 , and fault data  818  may be used to determine whether the vehicle energy usage is sub-optimal  822 . An indication  824  is also made if the battery state of charge  820  is less than a predetermined amount. As shown in column  808 , exemplary automatic vehicle control actions comprise adjusting the vehicle traction acceleration  826 , adjusting the vehicle speed  828 , or adjusting the vehicle lift rates  830  (if the vehicle comprises a fork lift) when the vehicle energy usage is sub-optimal. Exemplary vehicle control actions also comprise performing a lift lockout  832  when the battery state of charge is less than a predetermined amount  824 . 
         [0082]    Column  808  illustrates exemplary automatic control measures that may be initiated based at least in part on the indicators in column  806 . In more detail, a low water level indication triggers a command to a watering system  842  that effectuates automatic watering of the battery  802 . A low battery state-of-charge triggers a reduction of temperature fold back in small steps per week  836 . A sub-optimized charging regimen  830  triggers an adjustment of the charge rates. Sub-par battery performance  832  triggers initiation of unscheduled battery equalization. 
         [0083]    Turning now to  FIG. 9 , a high level block diagram that illustrates a system for issuing one or more management recommendations based at least in part on device measurement data obtained from one or more devices in accordance with one embodiment of the present invention is presented. As shown in  FIG. 9 , one or more devices  906  comprises a local device controller  940  adapted to control the one or more devices  906  based at least in part on one or more commands from manual control means  938 . According to one embodiment of the present invention, one or more devices  906  and remote device controller  902  are operatively coupled via a dedicated communication means. According to another embodiment of the present invention, the one or more devices  906  and remote device manager  902  are operatively coupled via a network (not shown in  FIG. 9 ). 
         [0084]    Still referring to  FIG. 9 , remote device manager  902  comprises an analyzer  918  and an adviser  928 . Analyzer  918  is adapted to update one or more usage profiles  920  based at least in part on one or more of the identification data, the historical data, and the real-time data that comprises the device measurement data  908 . 
         [0085]    The one or more usage profiles  920  comprise information regarding the use of the one or more devices  906 . The one or more usage profiles  920  may be stored in a memory associated with the remote device manager  902 . 
         [0086]    Adviser  928  is adapted to issue one or more management recommendations to a user  942 , based at least in part on the device measurement data  908  obtained from the one or more devices  906 . 
         [0087]    In operation, device measurement data  908  is transferred from the one or more devices  906  to remote device manager  902 . According to one embodiment of the present invention, the transfer is initiated by the one or more devices  906 . According to another embodiment of the present invention, the transfer is initiated by the remote device manager  902 . Analyzer  918  updates one or more usage profiles  920  based at least in part on one or more of the identification data, the historical data, and the real-time data that comprises the device measurement data  908 . Advisor  928  issues one or more management recommendations  936  to a user  942 , based at least in part on the device measurement data  908  obtained from the one or more devices  906 . 
         [0088]    Turning now to  FIG. 10 , a high level control flow diagram that illustrates issuing one or more management recommendations based at least in part on device measurement data obtained from one or more devices in accordance with one embodiment of the present invention is presented.  FIG. 10  corresponds with  FIG. 9  and provides more detail for reference numeral  4 A 30  of  FIG. 4A . The processes illustrated in  FIG. 10  may be implemented in hardware, software, firmware, or a combination thereof. At  1000 , a usage profile corresponding to a device is analyzed to provide recommendations with respect to management of the particular device, as well as other assets. The usage profile comprises performance data of the device gathered over a period of time. At  1005 , a determination is made regarding whether the device usage is sub-optimal. If the device usage is sub-optimal, at  1010  a management recommendation is issued. 
         [0089]    According to one embodiment, a management recommendation comprises an asset rotation recommendation. The asset rotation recommendation may be based at least in part on the capabilities of a device and the workload of the device with respect to capabilities and workloads of other devices. 
         [0090]    According to another embodiment, a management recommendation comprises an asset reduction recommendation. According to another embodiment, a management recommendation comprises an asset addition recommendation. The asset reduction recommendation and the asset addition recommendation may be based at least in part on the capabilities of fleet devices and the workload of the fleet devices. 
         [0091]    A management recommendation may be delivered to the user  942  many ways. According to one embodiment of the present invention, a management recommendation is delivered to user  942  via a phone call. By way of example, the phone number of a phone associated with user  942  is dialed and when the phone is answered, an audio message regarding the management recommendation is played for user  942  to hear. According to one embodiment of the present invention, a management recommendation is delivered to user  942  via a pager. By way of example, a text message regarding the management recommendation is sent to the pager number of a pager associated with user  942 . According to one embodiment of the present invention, a management recommendation is delivered to user  942  via an email message. By way of example, a text message comprising a management recommendation, or a Universal Resource Locator (URL) that references a management recommendation, is delivered in an email message to an email address associated with user  942 . According to one embodiment of the present invention, a management recommendation is delivered to user  942  via a message on a display screen. By way of example, a management recommendation is rendered on a display screen associated with user  942 . According to one embodiment of the present invention, a management recommendation is delivered to user  942  via an alarm. By way of example, an audio message regarding the management recommendation may be played over a public address system of a facility associated with the user  942 . As another example, an audio message or an audio-video message regarding the management recommendation may be played on a computing device adapted to render audio messages and associated with the user  942 . The audio or audio-video message may comprise one or more of a verbal message and a nonverbal message (e.g. one or more “beeps” or other sounds associated with a particular management recommendation). According to another embodiment of the present invention, a management recommendation comprises two or more of the types of management recommendations mentioned above. 
         [0092]    Turning now to  FIG. 11 , a low level data flow diagram that illustrates issuing one or more management recommendations based at least in part on device measurement data obtained from one or more vehicles and from one or more batteries associated with the one or more vehicles in accordance with one embodiment of the present invention is presented. As shown in column  1102 , the types of data used for issuing one or more management recommendations comprises vehicle and battery identification data  1104 , vehicle and battery real-time descriptive data  1112 , vehicle and battery real-time performance data  1114 , and vehicle and battery historical data  1116 . Column  1106  illustrates information derivable from the sample data in column  1102 . The data  1118  may be used to determine whether there is sub-optimal usage of vehicle assets, battery assets, or both, whether one or more operators are underutilized, and whether a schedule is inefficient  1120 . As shown in column  1108 , exemplary management recommendations comprise one or more of recommendations for increasing the number of operators, reducing the number of operators, rearranging the shift schedule, using a different utility schedule, training operators, using 3PL, using peak-season rentals, reevaluating maintenance schedules, reducing the rental fleet, using a capital purchase instead of leasing, leasing instead of using a capital purchase, use different type of vehicle when a vehicle needs to be replaced, using a different type of battery when a battery needs to be replaced, increasing the fleet size, decreasing the fleet size, and rotating batteries or vehicles according to actual usage  1122 . The management recommendation  1108  is presented to a user  1130  who is free to make a management decision  1128  based at least in part on the management recommendation  1108 . 
         [0093]    The management recommendations listed at  1122  are illustrative and are not intended to be an exhaustive list. Those of ordinary skill in the art will recognize that other management recommendations may be used. 
         [0094]    Turning now to  FIG. 12 , a high level block diagram that illustrates a system for issuing one or more user alerts based at least in part on device measurement data obtained from one or more devices in accordance with one embodiment of the present invention is presented. As shown in  FIG. 12 , device  1206  comprises a local device controller  1240  adapted to control the one or more devices  1206  based at least in part on one or more commands from manual control means  1238 . According to one embodiment of the present invention, device  1206  and remote device controller  1202  are operatively coupled via a dedicated communication means. According to another embodiment of the present invention, device  1206  and remote device manager  1202  are operatively coupled via a network (not shown in  FIG. 12 ). 
         [0095]    Still referring to  FIG. 12 , remote device manager  1202  comprises an analyzer  1218  and an alerter  1228 . Analyzer  1218  is adapted to update one or more usage profiles  1220  based at least in part on one or more of the identification data, the historical data, and the real-time data that comprises the device measurement data  1208 . 
         [0096]    The one or more usage profiles  1220  comprise information regarding the use of the one or more devices  1206 . The one or more usage profiles  1220  may be stored in a memory associated with the remote device manager  1202 . 
         [0097]    Analyzer  1218  comprises one or more of a historical data analyzer  1222 , a schedule milestone recognizer  1224 , and an exception recognizer  1226 . Historical data analyzer  1222  is adapted to analyze historical data, schedule milestone recognizer is adapted to analyze schedule milestones, and exception recognizer  1226  is adapted to recognize exceptions. Alerter  1224  is adapted to issue one or more user alerts to the user  1242 , based at least in part on the device measurement data  1208  obtained from the one or more devices  1206 . Manual control means  1238  may be used by user  1242  to control the one or more devices  1206  based at least in part on one or more user alerts received from alerter  224 . Manual control means  1238  comprises an input device, such as alphanumeric keyboard  118 , numeric keyboard  118 , joystick  116 , roller  114 , directional navigation pad  126 , or display screen  110  of  FIG. 1 . 
         [0098]    In operation, device measurement data  1208  is transferred from device  1206  to remote device manager  1202 . According to one embodiment of the present invention, the transfer is initiated by the one or more devices  1206 . According to another embodiment of the present invention, the transfer is initiated by the remote device manager  1202 . Analyzer  1218  updates one or more usage profiles  1220  based at least in part on one or more of the identification data, the historical data, and the real-time data that comprise the device measurement data  1208 . Historical data analyzer  1222  of analyzer  1218  analyzes historical data. Schedule milestone recognizer  1224  of analyzer  1218  analyzes schedule milestones. Exception recognizer  1226  of analyzer  1218  analyzes exceptions. Alerter  1228  issues one or more user alerts to the user  1242 , based at least in part on the one or more usage profiles  1220 . 
         [0099]    Turning now to  FIG. 13 , a high level control flow diagram that illustrates issuing one or more user alerts based at least in part on device measurement data obtained from one or more devices in accordance with one embodiment of the present invention is presented.  FIG. 13  corresponds with  FIG. 12  and provides more detail for reference numeral  4 A 40  of  FIG. 4A . The processes illustrated in  FIG. 3  may be implemented in hardware, software, firmware, or a combination thereof. At  1300 , a usage profile corresponding to a device is analyzed. At  1305 , one or more historical usage or performance profiles associated with the one or more devices are analyzed. At  1310 , one or more maintenance schedule milestones associate with the one or more devices are analyzed. At  1315 , a determination is made regarding whether the fault codes indicate a fault. At  1320 , a determination is made regarding whether the one or more profiles indicate a fault. At  1325 , a determination is made regarding whether the maintenance schedule indicates a fault. If a fault is indicated at  1315 ,  1320 , or  1325 , a user alert corresponding to the particular fault is issued at  1330 . 
         [0100]    While the operations shown in  FIG. 13  are illustrated in a specific order, other sequences of the operations are conceivable. For example, the order of processes  1300 ,  1305 , and  1310  with respect to each other is not important. Additionally, the order of determinations  1315 ,  1320 , and  1325  with respect to each other is not important. 
         [0101]    According to one embodiment of the present invention, a user alert comprises a compliance alert. By way of example, if a user responsible for a particular vehicle charges the vehicle less frequently than suggested, a user alert informs the user of the non-compliance. 
         [0102]    According to another embodiment of the present invention, a user alert comprises a warranty period ending alert. By way of example, if the warranty for a particular device will end within a predetermined amount of time, a user alert informs the user of this fact. 
         [0103]    According to another embodiment of the present invention, a user alert comprises a non-warranty replacement alert. 
         [0104]    According to another embodiment of the present invention, a user alert comprises a maintenance alert. By way of example, if the maintenance schedule of a device indicates maintenance should be performed and it has not yet been performed, a user alert informs the user of this fact. 
         [0105]    According to another embodiment of the present invention, a user alert comprises a charger service alert. By way of example, if a charger requires unscheduled service, a user alert informs the user of this fact. 
         [0106]    According to another embodiment of the present invention, a user alert comprises a vehicle service alert. By way of example, if a vehicle requires unscheduled service, a user alert informs the user of this fact. 
         [0107]    According to another embodiment of the present invention, a user alert comprises a battery service alert. By way of example, if a battery requires unscheduled service, a user alert informs the user of this fact. 
         [0108]    A user alert may be delivered to the user  1242  many ways. According to one embodiment of the present invention, a user alert is delivered to user  1242  via a phone call. By way of example, the phone number of a phone associated with user  1242  is dialed and when the phone is answered, an audio message regarding the user alert is played for user  1242  to hear. According to one embodiment of the present invention, a user alert is delivered to user  1242  via a pager. By way of example, a text message regarding the user alert is sent to the pager number of a pager associated with user  1242 . According to one embodiment of the present invention, a user alert is delivered to user  1242  via an email message. By way of example, a text message comprising a user alert, or a Universal Resource Locator (URL) that references a user alert, is delivered in an email message to an email address associated with user  1242 . According to one embodiment of the present invention, a user alert is delivered to user  1242  via a message on a display screen. By way of example, a user alert is rendered on a display screen associated with user  1242 . According to one embodiment of the present invention, a user alert is delivered to user  1242  via an alarm. By way of example, an audio message regarding the user alert may be played over a public address system of a facility associated with the user  1242 . As another example, an audio message or an audio-video message regarding the user alert may be played on a computing device adapted to render audio messages and associated with the user  1242 . The audio or audio-video message may comprise one or more of a verbal message and a nonverbal message (e.g. one or more “beeps” or other sounds associated with a particular user alert). According to another embodiment of the present invention, a user alert comprises two or more of the types of user alerts mentioned above. 
         [0109]    Turning now to  FIG. 14 , a low level data flow diagram that illustrates issuing one or more user alerts based at least in part on device measurement data obtained from one or more vehicles and from one or more batteries associated with the one or more vehicles in accordance with one embodiment of the present invention is presented. As shown in column  1402 , the types of data used for issuing one or more user alerts comprises vehicle and battery identification data  1410 , vehicle real-time descriptive data  1412 , vehicle and battery real-time performance data  1414 , and vehicle and battery historical data  1416 . As shown in column  1404 , exemplary identification data  1410  comprises a vehicle maintenance schedule  1418 . Exemplary vehicle real-time descriptive data  1412  comprises battery capacity  1420 . Exemplary vehicle and battery real-time performance data comprise faults. Column  1406  illustrates information derivable from the sample data in column  1404 . The data  1404  may be used to determine whether the time for scheduled maintenance is near, whether a warranty period has ended  1424 , whether operator compliance procedures are being followed  1426 , whether a battery is displaying low capacity  1428 , and whether a battery, vehicle, or charger requires maintenance  1430 . As shown in column  1408 , exemplary user alerts comprise indicating a warranty period is ending  1432 , indicating maintenance is required  1434 , indicating an operator is operating a vehicle in a noncompliant manner  1440 , indicating a battery requires either (1) full or cell replacement, or (2) service  1442 , and indicating another charger, vehicle, or battery service alert. The user alert  1404  is presented to a user  1448  who is free to make a management decision  1446  based at least in part on the user alert  1404 . 
         [0110]      FIGS. 15-17  illustrate dynamic control of one or more devices based at least in part on device measurement data collected from the one or more devices in accordance with embodiments of the present invention. 
         [0111]    Turning now to  FIG. 15 , a block diagram that illustrates dynamic control of one or more chargers based at least in part on device measurement data collected from the one or more chargers and one or more vehicles associated with the one or more chargers in accordance with one embodiment of the present invention is presented. As shown in  FIG. 15 , multiple vehicles ( 1534 ,  1536 ) are operatively coupled to a remote device manager  1502  via a network  1544 . The remote device manager  1502  receives device measurement data  1508  from the vehicles ( 1534 ,  1536 ) and the chargers associated with the vehicles ( 1534 ,  1536 ). The remote device manager  1502  analyzes the device measurement data  1508  and issues one or more commands based at least in part on the analysis. The BMID parameters may be adjusted to optimize charging rates and to reduce battery temperature. The BMID parameters may also be adjusted to maximize battery state-of-charge based at least in part on the charging history. Additionally or as an alternative thereto, unscheduled battery equalization may be initiated to address battery performance issues. 
         [0112]    Turning now to  FIG. 16 , a block diagram that illustrates dynamic control of one or more chargers and one or more vehicles associated with the one or more chargers based at least in part on device measurement data collected from the one or more chargers and the one or more vehicles in accordance with one embodiment of the present invention is presented. As shown in  FIG. 16 , multiple vehicles ( 1634 ,  1636 ) are operatively coupled to a remote device manager  1602  via a network  1644 . The remote device manager  1602  receives device measurement data  1608  from the vehicles ( 1634 ,  1636 ) and the chargers associated with the vehicles ( 1634 ,  1636 ). The remote device manager  1602  analyzes the device measurement data  1608  and issues one or more commands  1636  based at least in part on the analysis. A rotational schedule that maximizes asset life of batteries and vehicles may be recommended. A future asset replacement time may be anticipated based at least in part on battery performance. Vehicle, battery, or charger fault numbers may be recorded and communicated to customer support personnel. Vehicle performance levels may be adjusted to conserve energy, based at least in part on battery usage and state-of-charge data. Battery charging rates may be adjusted based at least in part on historical plug-in times, battery energy usage, and minimum battery state-of-charge data to conserve energy and reduce peak demand costs. A vehicle reduction recommendation or utilization plan may be presented. Customers, operators, or both, may be alerted with respect to compliance issues. Batteries may be automatically watered based at least in part on a water level threshold. 
         [0113]    Turning now to  FIG. 17 , a block diagram that illustrates dynamic control of one or more chargers based at least in part on device measurement data collected from the one or more chargers an in accordance with one embodiment of the present invention is presented. As shown in  FIG. 17 , multiple vehicles ( 1734 ,  1736 ) are operatively coupled to a remote device manager  1702  via a network  1744 . The remote device manager  1702  receives device measurement data  1708  from the vehicles ( 1734 ,  1736 ) and the chargers associated with the vehicles ( 1734 ,  1736 ). The remote device manager  1702  analyzes the device measurement data  1708  and issues one or more commands  1736  based at least in part on the analysis. The BMID parameters may be adjusted to optimize charging rates and to reduce battery temperature. The BMID parameters may also be adjusted to maximize battery state-of-charge based at least in part on the charging history. 
         [0114]    Turning now to  FIG. 18 , a flow diagram that illustrates a method for battery fault management in accordance with one embodiment of the present invention is presented.  FIG. 18  exemplifies issuing user alerts, issuing management recommendations, and automatically controlling attributes or operations of one or more devices based at least in part on device measurement data obtained from the one or more devices. The processes illustrated in  FIG. 18  may be implemented in hardware, software, firmware, or a combination thereof. At  1800 , a determination is made regarding whether a battery is overheating. If the battery is not overheating, at  1802  a determination is made regarding whether the battery has a low state-of-charge. If the battery has a low state-of-charge, at  1820  a determination is made regarding whether the battery has at least one bad cell. If the battery has at least one bad cell, a battery replacement request is sent at  1822 . If the battery does not have at least one bad cell, at  1824  a determination is made regarding whether the battery usage is too high. If the battery usage is too high, at  1826  an alert message is sent, warning that the vehicle performance should be reduced, or the number of vehicles should be increased. If the battery usage is not too high, at  1828  a determination is made regarding whether plug-in compliance procedures are being adhered to. If the plug-in compliance procedures are not being adhered to, at  1830  an alert message is sent. If plug-in compliance procedures are being adhered to, at  1832  the temperature fold back is decreased in small steps, one step per week, until the battery state-of-charge is maintained below a first predetermined limit and the battery temperature does not exceed a second predetermined limit. 
         [0115]    Still referring to  FIG. 18 , if battery overheating is indicated at  1800 , at  1804  a determination is made regarding whether the battery water level is low. If the battery water level is low, at  1806  an alert message is sent. The alert message may be sent to one or more persons or entities. By way of example, the alert message may be sent to one or more of the shift supervisor, the battery supplier, and the supplier of a device associated with the battery. Alternatively or in addition thereto, the battery is automatically watered. If the battery water level is not low, at  1808  a determination is made regarding whether the battery has at least one bad cell. If the battery has at least one bad cell, a battery replacement request is sent at  1810 . The battery replacement request may be sent to one or more persons or entities. By way of example, the battery replacement request may be sent to one or more of a battery service provider, the battery supplier, and the supplier of a device associated with the battery. If the battery does not have at least one bad cell, at  1812  a determination is made regarding whether the battery usage is too high. If the battery usage is too high, at  1814  a determination is made regarding whether plug-in compliance procedures are being adhered to. If the plug-in compliance procedures are not being adhered to, at  1816  an alert message is sent. If plug-in compliance procedures are being adhered to, at  1818  the temperature fold back is increased in small steps, one step per week, until the battery temperature is maintained below the second predetermined limit. 
         [0116]    While the operations shown in  FIG. 18  are illustrated in a specific order, other sequences of the operations are conceivable. For example, one or both of determinations  1804  and  1808  and their associated actions (reference numerals  1806  and  1810 ) may occur after determination  1814 . Additionally, one or more of determinations  1820  and  1824  and their associated actions (reference numerals  1822  and  1826 ) may occur after determination  1828 . 
         [0117]    While embodiments of the present invention have been illustrated with respect to fork lifts having a replenishable battery pack, those of ordinary skill in the art will recognize that any device powered by a replenishable device may be used. 
         [0118]    While embodiments and applications of this invention have been shown and described, it would be apparent to those skilled in the art having the benefit of this disclosure that many more modifications than mentioned above are possible without departing from the inventive concepts herein. The invention, therefore, is not to be restricted except in the spirit of the appended claims.

Technology Category: 4