NON-ELECTRIC VEHICLE FUELING

REFERENCE TO RELATED APPLICATIONS

[0001 ] This application claims priority to U.S. Provisional Application No. 62/523,159, titled "Integrated Management Of Electric Vehicle Charging," filed on June 21 , 2017, hereby incorporated by reference in its entirety.

[0002] This application is related to copending U.S. Patent Application No.

15/222,813, titled "Electric Vehicle Charging System," filed on July 28, 2016, hereby incorporated by reference in its entirety.

BACKGROUND

[0003] Electric vehicle (EV) adoption has hit record highs. According to car sales reports for the first quarter of 2017, sales of EVs of all types were up 89% in March and 74% in the first quarter, with fully electric cars showing the greatest gains. At that time, EVs made up 1.2% of all U.S. car sales, a new record for the U.S. EV market. EVs are also popular worldwide.

[0004] EVs rely on batteries that periodically need to be charged. Electricity is the new fuel for fleets to manage. Electricity has historically been only a bill or departmental allocation for fleet managers. Now, it must be managed like other fuels. To date, however, there has not been a systematic approach to manage electricity as fuel.

[0005] The dynamics of managing electricity as fuel are that delivery and pricing are much different than standard fuels. The electrical infrastructure is already part of a facility's power source, so metering and control for just EVs must be separated from the rest of the power. Electrical power has daily and seasonal pricing differences: summer versus winter rates, and demand charges that are usually based on 15-minute assessments of the peak demand can be a significant part of the utility bill. [0006] A systematic approach to managing electricity as fuel would provide a number of advantages. For example, usage and costs could be closely monitored and controlled, so that performance of the charging system and EVs can be measured, and areas where improvements may be made can be identified.

SUMMARY

[0007] In embodiments according to the present invention, a multivehicle fueling system includes one or more electric vehicle (EV) charging stations and one or more stations for fueling non-electric or hybrid vehicles (referred to herein as a non-charging fueling station). The EV charging station includes a first control unit, a switching unit, and output connections that can be connected to EVs. The non-charging fueling station includes a second control unit and, for example, a liquid fuel pump. An integrated fuel management system is in communication with the EV charging station and the non- charging fueling station. The switching unit can direct a charging current from an input power supply to an output connection in response to commands from the first control unit that are issued according to a charging procedure. The first control unit can send state information for the EV charging station to the integrated fuel management system. The second control unit can send state information for the non-charging fueling station to the integrated fuel management system.

[0008] Thus, embodiments according to the present disclosure provide an integrated fuel management system. The integrated fuel management system combines a flexible platform for managing fuels (e.g., fleet fuels) of all types with technologies for managing electrical power and EV charging management and control. The integrated fuel

management system includes, for example, timely access control, uniform departmental billing, and detailed cloud-based reporting. The technologies for managing electrical power and EV charging management and control include, for example, electrical infrastructure optimization, power metering and control, and a myriad of power utilization reporting tools. The combination integrates EV charging from any charging station into a total fuel management system using controllers and power management systems. The result is a solution that manages electrical power dynamics as part of an integrated, full-featured fuel management system. Consequently, electricity for EV charging can be managed as a standard fleet fuel.

[0009] These and other objects and advantages of the various embodiments according to the present invention will be recognized by those of ordinary skill in the art after reading the following detailed description of the embodiments that are illustrated in the various drawing figures.

BRIEF DESCRIPTION OF DRAWINGS

[0010] The accompanying drawings, which are incorporated in and form a part of this specification and in which like numerals depict like elements, illustrate embodiments of the present disclosure and, together with the detailed description, serve to explain the principles of the disclosure.

[0011 ] Figure 1 is a block diagram showing elements of a multivehicle fueling system in an embodiment according to the invention.

[0012] Figure 2 is a flowchart illustrating a method of charging one or more electric vehicles (EVs) in an embodiment according to the invention.

[0013] Figure 3 is a block diagram illustrating elements of an integrated fuel management system in an embodiment according to the invention.

[0014] Figure 4 is a block diagram further illustrating elements of an integrated fuel management system in an embodiment according to the invention.

[0015] Figure 5 illustrates a control unit and a switching unit of the integrated fuel management system in an embodiment according to the invention.

[0016] Figure 6 illustrates a control unit and a switching unit of the integrated fuel management system in an embodiment according to the invention. [0017] Figure 7 is a block diagram illustrating an example of an implementation of a multivehicle charging system in an embodiment according to the invention.

[0018] Figure 8 is a block diagram illustrating an example of an implementation of a multivehicle charging system in an embodiment according to the invention.

[0019] Figure 9 is a block diagram illustrating an example of an implementation of a multivehicle charging system in an embodiment according to the invention.

[0020] Figure 10 is a block diagram illustrating an example of an implementation of a multivehicle charging system in an embodiment according to the invention.

[0021 ] Figure 1 1 is a flowchart illustrating examples of computer-implemented operations for monitoring and managing a multivehicle fueling system in embodiments according to the invention.

[0022] Figure 12 is a block diagram of an example of a computing device or computer system capable of implementing embodiments according to the invention.

[0023] Figures 13, 14, and 15 illustrate examples of displays that constitute selected elements of a graphical user interface (GUI) that is rendered on a display device in embodiments according to the invention.

DETAILED DESCRIPTION

[0024] Reference will now be made in detail to the various embodiments of the present disclosure, examples of which are illustrated in the accompanying drawings. While described in conjunction with these embodiments, it will be understood that they are not intended to limit the disclosure to these embodiments. On the contrary, the disclosure is intended to cover alternatives, modifications and equivalents, which may be included within the spirit and scope of the disclosure as defined by the appended claims. Furthermore, in the following detailed description of the present disclosure, numerous specific details are set forth in order to provide a thorough understanding of the present disclosure. However, it will be understood that the present disclosure may be practiced without these specific details. In other instances, well-known methods, procedures, components, and circuits have not been described in detail so as not to unnecessarily obscure aspects of the present disclosure.

[0025] Some portions of the detailed descriptions that follow are presented in terms of procedures, logic blocks, processing, and other symbolic representations of operations on data bits within a computer memory. These descriptions and representations are the means used by those skilled in the data processing arts to most effectively convey the substance of their work to others skilled in the art. In the present application, a procedure, logic block, process, or the like, is conceived to be a self-consistent sequence of steps or instructions leading to a desired result. The steps are those utilizing physical

manipulations of physical quantities. Usually, although not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated in a computer system. It has proven convenient at times, principally for reasons of common usage, to refer to these signals as transactions, bits, values, elements, symbols, characters, samples, pixels, or the like.

[0026] It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise as apparent from the following discussions, it is appreciated that throughout the present disclosure, discussions utilizing terms such as "receiving," "directing," "sending," "stopping," "determining,"

"generating," "displaying," "indicating," or the like, refer to actions and processes (e.g., the flowchart 1 100 of Figure 1 1 ) of an apparatus or computer system or similar electronic computing device or processor (e.g., the computer system 1200 of Figure 12). A computer system or similar electronic computing device manipulates and transforms data

represented as physical (electronic) quantities within memories, registers or other such information storage, transmission or display devices. [0027] Embodiments described herein may be discussed in the general context of computer-executable instructions residing on some form of computer-readable storage medium, such as program modules, executed by one or more computers or other devices. By way of example, and not limitation, computer-readable storage media may comprise non-transitory computer storage media and communication media. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform particular tasks or implement particular abstract data types. The functionality of the program modules may be combined or distributed as desired in various embodiments.

[0028] Computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules or other data. Computer storage media includes, but is not limited to, random access memory (RAM), read only memory (ROM), electrically erasable programmable ROM (EEPROM), flash memory (e.g., an SSD or NVMD) or other memory technology, compact disk ROM (CD- ROM), digital versatile disks (DVDs) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the desired information and that can accessed to retrieve that information.

[0029] Communication media can embody computer-executable instructions, data structures, and program modules, and includes any information delivery media. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, radio frequency (RF), infrared and other wireless media. Combinations of any of the above can also be included within the scope of computer-readable media.

[0030] Figure 1 is a block diagram showing selected elements of a multivehicle fueling system 100 in an embodiment according to the invention. The multivehicle fueling system 100 can include a number of different charging stations, such as the charging station 1 10, for charging electric vehicles (EVs). An EV can be any type of vehicle such as, but not limited to, a car, truck, motorcycle, golf cart, or motorized (power-assisted) bicycle. Embodiments according to the invention can be utilized with Level 2 or Level 3 charging stations, although the invention is not limited to such types of charging stations and can be utilized in other types that may come into existence in the future.

[0031 ] The multivehicle fueling system 100 can also include stations 140 (e.g., pumps) that provide liquid fuel (such as, but not limited to, gasoline) to hybrid or nonelectric vehicles. Generally speaking, considering electricity as a fuel, the stations 140 provide fuel other than electricity, and so may be referred to herein as non-charging stations or non-charging fueling stations.

[0032] As will be described below, an integrated fuel management system 106 manages the multivehicle fueling system 100.

[0033] The flowchart 200 of Figure 2 illustrates a charging procedure an

embodiment according to the invention. In block 202, an output connection is selected or accessed. In block 204, a determination is made whether there is a load (an EV) present on the selected output connection. This determination can be made automatically. If not, then the flowchart 200 returns to block 202 and another output connection is selected or accessed in accordance with a charging sequence or procedure. If there is a load present, then the flowchart 200 proceeds to block 206.

[0034]ln block 206, a check is made to determine whether the EV requires a charge. If so, then the flowchart 200 proceeds to block 208; otherwise, the flowchart returns to block 202 and another output connection is selected or accessed.

[0035] In block 208, a charging current is provided to the selected output connection. In block 210, a determination is made whether a condition is satisfied. The condition may be, for example, an interval of time has expired or the charging current to the selected output connection has decreased to a threshold value. [0036] If the condition is satisfied, then the charging current to the selected output connection is stopped in block 212, and then the flowchart 200 returns to block 202 and another output connection is selected or accessed according to the charging sequence or procedure. In an embodiment, a charging current is provided to each of the output connections connected to an EV in round-robin fashion, one output connection at a time. If an output connection is not connected to an EV or if the EV does not require further charging, then the output connection is automatically skipped.

[0037] If the condition is not satisfied, then the flowchart 200 returns to block 208 and the charging current to the selected output connection is continued.

[0038] Figure 3 is a block diagram illustrating elements of the integrated fuel management system 106 in embodiments according to the invention.

[0039] In embodiments, the integrated fuel management system 106 includes a first control unit 304 and a switching unit 306 connected to the first control unit. In

embodiments, the control unit 304 provides, manages, and controls secure, automated access to one or more EV charging stations 110. The control unit 304 can also be in communication with the computer system 1200, either through a wired connection or a wireless connection, directly or over the Internet. The control unit 304 can include, for example, a magnetic stripe card reader, a radio frequency identification (RFID) proximity key and card reader, an alphanumeric keypad, vehicle tags, and a bar code scanner.

[0040] In an embodiment, main power is delivered over a dedicated circuit 331 from an electrical panel 302 (e.g., from the main AC power source 330) to the switching unit 306. Only a single power circuit is illustrated; however, the present invention is not so limited. In other words, multiple such systems can be implemented in parallel.

[0041 ] In the embodiments of Figure 3, the switching unit 306 has four channels: channels 1 , 2, 3, and 4 (1 -4). Depending on the implementation, each channel can be connected to a respective charging station 1 10 (Figure 1 ), or each channel can be connected to a respective output connection.

[0042] In embodiments, the integrated fuel management system 106 also includes a second control unit 314. In embodiments, the second control unit 314 provides, manages, and controls secure, automated access to one or more non-electric fueling stations 140.

[0043] The integrated fuel management system 106 can include more than two control units.

[0044] As mentioned above, communication between the integrated fuel

management system 106 and a computer system 1200 may be implemented using a wired and/or wireless connection, and may occur directly and/or over the Internet or an intranet (e.g., an Ethernet or local area network). Also, the computer system 1200 is connected (wired or wirelessly) to the first control unit 304 and to the second control unit 314. The first control unit 304 provides state information for the EV charging station 1 10 to the computer system 1200, and the second control unit 314 provides state information for the non-electric fueling stating to the computer system.

[0045] In embodiments, the computer system 1200 generates and/or executes a graphical user interface (GUI) 308 using the state information from the first control unit 304 and the second control unit 314.

[0046] The GUI 308 is a browser-based interface that utilizes current basic functions of the browser plus additional functionality that can be used to manage and monitor the multivehicle fueling system 100 (Figure 1 ). Each charging station 1 10 and non-charging station 140 can be monitored and controlled (programmed) over a network.

[0047] The GUI 308 can be accessed by a network administrator and can also be accessed by or pushed to other devices such as smartphones. In general, the state information for the multivehicle fueling system 100 can be cloud-based and available online. [0048] Furthermore, some or all of the GUI 308 can be accessed remotely from another computer system or a device such as a smartphone, or information from the GUI can be pushed to remote devices such as other computer systems and smartphones. Also, in an embodiment, information from a smartphone or computer system, including a computer system or similar type of intelligent device on an EV or non-EV, is received via the browser-based interface and used, for example, to control fueling/charging or to provide billing information to the owner or manager of the multivehicle fueling system 100.

[0049] The GUI 308 presents information based on the analysis of the data provided by the integrated fuel management system 106. For example, a convenient dashboard summary can be implemented to display important fleet data and useful alert messages, comparative usage charts, and inventory information.

[0050] More specifically, the integrated fuel management system 106 collects data from each fuel transaction. Users can look at the data in real time. The fuel management system communicates via network cable or wireless connection to the cloud. This information can be accessed through a user's account on any device using a Web browser. The dashboard provides users with trend graphs depicting fuel usage in, for example, the last 30 days. Customization is available to view the total amount of transactions, product usage, and inventory. This allows users to see any zero quantity or bypass transactions. Each user can customize the time period of transactions (e.g., a year, month, week, day, etc.) and the information that is important for the user to see. Information can be exported to other applications to create custom reports. Users can authorize vehicles and drivers at the press of a button. Administrators can manage active and inactive drivers and vehicles in real time. If needed, an administrator has the ability to remotely (e.g., with an Internet connection) add new vehicles and drivers, so they may be authorized to fuel (e.g., during a holiday). Administrators have the ability to limit volume, dollar amount, and number of fuel transactions per day, week, and month, for example. Periodic (e.g., weekly or monthly) reports that allow for flexible billing, fuel usage summaries, or detailed reports can be received automatically. [0051 ] Thus, the integrated fuel management system 106 combines a flexible platform that can manage fuels of all types (e.g., including liquid fuel such as gasoline) with technologies (e.g., the switching unit 306) that can manage electrical power and EV charging. The integrated fuel management system 106 provides timely access control, uniform billing, detailed cloud-based reporting, power metering and control, and power utilization reporting tools. The integrated fuel management system 106 may perform other functions, such as metering of power usage and storage of information related to charging events.

[0052] Figure 4 is a block diagram further illustrating elements of the integrated fuel management system 106 in embodiments according to the invention. In the example of Figure 4, the switching unit 306 includes a processor (e.g., a central processing unit (CPU)) 402 that can be coupled to control unit 404 via a communication interface 404. The switching unit 306 can be implemented on a single printed circuit board (PCB) that has a low voltage side (e.g., containing the CPU) and a separate high voltage side (the main power side). In an embodiment, the processor 402 is powered by a separate, low voltage (e.g., five volt, 5V) power supply 406. In an embodiment, the switching unit 306 includes memory 401 , which can be used to store information related to charging events, for example.

[0053] The main AC power source 330 is connected to each of the channels 1 -4 by a respective relay R or switch that is individually controlled by the processor 402 in response to switching commands from the control unit 304. A status indicator (e.g., a light- emitting diode) can be associated with each channel to indicate the status of the relay (e.g., open or closed).

[0054] By turning on and off the relay or switch, a charging current is provided to a first one of the channels, the charging current to the first one of the channels is then turned off, a charging current is then provided to a second one of the channels, and so on. More specifically, for example, a charging procedure includes providing a charging current to a first one of the channels, turning off that charging current when an interval of time expires or when a charging threshold is reached, then providing a charging current to a second one of the channels, and so on. Also, in various embodiments, a charging procedure includes providing a charging current to each of the channels one channel at a time in round-robin fashion, and/or a channel is designated as a priority channel, in which case a charging current is provided to the priority channel more frequently than to other channels. Many different charging sequences or procedures can be used.

[0055] In an embodiment, each of the channels 1 -4 includes a respective current sensor CT and a respective voltage sensor VS. Accordingly, the switching unit 306 can detect whether an electrical load (e.g., an EV) is connected to a channel before a charging current is provided to the channel. In an embodiment, the switching unit 306 can also detect a charge signature for an EV connected to a channel before a charging current is provided to the channel; if the charge signature indicates that the EV does not require further charging (e.g., it is fully charged), then the charging current is not provided to the channel.

[0056] Figure 5 illustrates the control unit 304 and the switching unit 306 of the integrated fuel management system 106 in an embodiment according to the present invention. In an embodiment, the control unit 304 and the switching unit 306 are connected by a cable 502 (e.g., an Ethernet RJ45 patch cable).

[0057] In an embodiment, the switching unit 306 includes two subunits 306a and 306b. The cable 502 is connected to the subunit 306a, which is connected to the subunit 306b via the cable 503 (e.g., an Ethernet RJ45 patch cable).

[0058] In embodiments, the control unit 304 and the switching unit 306 are both coupled to the 5V power supply 406. In an embodiment, the subunit 306a is connected to the power supply 406 and powers the subunit 306b via a controller area network (CAN) bus (see Figure 6). The 5V power supply 406 can also be used to power the control unit 304. [0059] Each of the subunits 306a and 306b of Figure 5 includes four channels:

channels 1 -4 and 5-8, respectively. Thus, for example, each of the subunits 306a and 306b is exemplified by the switching unit 306 of Figure 4. However, the invention is not so limited.

[0060] In Figure 5, the lines labeled "input line 1 ," "input line 2," etc., are connected to the main AC power source 330. In the embodiment of Figure 5, each channel is connected via the line labeled "output" to a respective EV and there is a one-to-one correspondence between the input lines and the channels. In another embodiment, a single input line is connected to multiple channels and power is delivered to each channel in, for example, round-robin fashion.

[0061 ] In embodiments, the control unit 304 includes a controller (control board) 510 and, in the example of Figure 5, a card swipe interface 512 (e.g., a magnetic stripe card reader) and a user input keypad/display 514 (e.g., an alphanumeric keypad). The control unit 304 can also include, for example, a radio frequency identification (RFID) proximity key and card reader (not shown). The controller 510 issues switching commands for each channel to the switching unit 306. In an embodiment, the switching commands are initiated by an application 1240 executing on the computer system 1200 (Figure 12) and

communicated to the control unit 304 (the controller 510) over a connection as described above. The switching commands control, for example, the relays in the switching unit 306 (Figure 4). The switching unit 306 executes those commands and reports state information for each channel to the control unit 304. The state information includes, but is not limited to, the switch state of each channel (e.g., on or off), the current or amperage per channel, the voltage per channel, and the frequency per channel. The control unit 304, in turn, can send the state information to the computer system 1200 over a connection as described above. The computer system 1200 can display the state information in the GUI 308

(Figure 4). [0062] In embodiments, the control unit 314 of Figure 3, for example, is configured in a similar manner as the control unit 304. Thus, the control unit 314 used for monitoring and managing non-charging fueling stations can also include a controller (control board), a card swipe interface, and a user input keypad/display.

[0063] Figure 6 illustrates the control unit 304 and the switching unit 306 of the integrated fuel management system 106 in an embodiment according to the present invention. In this embodiment, the control unit 304 and the switching unit 306 are enclosed within a single unit or housing 602. In practice, the control unit 304 and the switching unit 306 are covered by a panel (not shown). As mentioned above in conjunction with Figure 5, in an embodiment, the subunit 306a is connected to the 5V power supply and powers the subunit 306b via a CAN bus 604.

[0064] Figure 7 is a block diagram illustrating an example of an implementation of a multivehicle charging system in an embodiment according to the invention. In the example of Figure 5, a charging station 710 is connected to an electrical panel (the main AC power source 330) via a single (dedicated) circuit 331 , and is also connected to the switching circuit 306. Each of the channels 1 -4 of the switching circuit 306 is connected to a respective one of the output connections 741 , 742, 743, and 744 (741 -744), which in turn are connected to heads 71 1 , 712, 713, and 714 (71 1 -714), respectively. In this

implementation, the integrated fuel management system 106 directs a charging current to the output connections 741 -744, one at a time as described above, and thus also directs a charging current to the heads 71 1 -714, one at a time.

[0065] Figure 8 is a block diagram illustrating an example of another implementation of a multivehicle charging system in an embodiment according to the invention. In the example of Figure 8, the switching circuit 306 is connected to an electrical panel (the main AC power source 330) via a single (dedicated) circuit 331. Each of the channels 1 -4 of the switching circuit 306 is connected to a respective charging station 81 1 , 812, 813, and 814 (81 1 -814), which in turn are connected to heads 851 , 852, 853, and 854 (851 -854), respectively, by a respective output connection 841 , 842, 843, or 844 (841 -844). In the Figure 8 implementation, the integrated fuel management system 106 directs a charging current to the channels 1 -4 one at a time, and hence to the charging stations 81 1 -814 one at a time, and thus also directs a charging current to the output connections 841 -844 and the heads 851 -854, one at a time.

[0066] Figure 9 is a block diagram illustrating an example of an implementation of a multivehicle charging system in an embodiment according to the invention. The Figure 9 embodiment is similar to the embodiment of Figure 7, except that the charging station 910 has at least one output connection (e.g., the output connection 941 ) that has more than one (e.g., two) heads 951 and 952. When the charging current is directed to the output connection 941 , it is split between the heads 951 and 952.

[0067] Figure 10 is a block diagram illustrating an example of another

implementation of a multivehicle charging system in an embodiment according to the invention. The Figure 10 embodiment is similar to the embodiment of Figure 8, except that at least one of the channels in the switching circuit 306 (e.g., channel 1 ) is connected to two charging stations 1010 and 101 1. The charging station 1010 is connected to an output connection 1040, which is connected to the head 1050, and the charging station 101 1 is connected to the output connection 1041 , which is connected to the head 1042. In this embodiment, the integrated fuel management system 106 directs a charging current to the channels 1 -4, one channel at a time. However, when the charging current is directed to channel 1 , that charging current can be split between the charging stations 1010 and 101 1 , and thus ultimately the charging current to channel 1 can be split between the output connections 1040 and 1041 and hence between the heads 1050 and 1051.

[0068] Any combination of the implementations of Figures 7-10 can be deployed within the same multivehicle fueling system.

[0069] Figure 1 1 is a flowchart 1 100 illustrating examples of operations for monitoring and managing a multivehicle fueling system in embodiments according to the present invention. The flowchart 1 100 of Figure 1 1 can be implemented in a multivehicle charging system such as those described above. In embodiments, the operations of the flowchart 1 100 are implemented using the computer system 1200 of Figure 12, specifically by an application 1240 executing on the computer system.

[0070] In block 1 102 of Figure 1 1 , a charging procedure is sent to a first control unit coupled to a switching unit of an EV charging station. The charging stating includes multiple output connections that can be connected to EVs. The switching unit can direct a charging current from an input power supply to an output connection in response to commands from the first control unit that are issued according to the charging procedure.

[0071 ] In block 1 104, state information for the EV charging station is received from the first control unit.

[0072] In block 1 106, state information for a non-charging fueling station is received from a second control unit.

[0073] In block 1 108, the state information for the EV charging station and the state information for the fueling system is analyzed and processed, and a GUI using the state information is generated and displayed.

[0074] Figure 12 is a block diagram of an example of a computing device or computer system 1210 capable of implementing embodiments according to the present invention. The device 1210 broadly includes any single or multi-processor computing device or system capable of executing computer-readable instructions, such as those described above. In its most basic configuration, the device 1210 may include at least one processing circuit (e.g., the processor 1214) and at least one non-volatile storage medium (e.g., the memory 1216).

[0075] The processor 1214 generally represents any type or form of processing unit or circuit capable of processing data or interpreting and executing instructions. In certain embodiments, the processor 1214 may receive instructions from a software application or module (e.g., the application 1240). These instructions may cause the processor 1214 to perform the functions of one or more of the example embodiments described and/or illustrated above.

[0076] The system memory 1216 generally represents any type or form of volatile or non-volatile storage device or medium capable of storing data and/or other computer- readable instructions. Examples of system memory 1216 include, without limitation, RAM, ROM, flash memory, or any other suitable memory device. In an embodiment, the system memory 1216 includes a cache 1220.

[0077] The device 1210 may also include one or more components or elements in addition to the processor 1214 and the system memory 1216. For example, the device 1210 may include a memory device, an input/output (I/O) device such as a keyboard and mouse (not shown), and a communication interface 1218, each of which may be

interconnected via a communication infrastructure (e.g., a bus). The device 1210 may also include a display device 1212 that is generally configured to display a GUI such as those described below. The display device 1212 may also include a touch sensing device (e.g., a touch screen).

[0078] The communication interface 1218 broadly represents any type or form of communication device or adapter capable of facilitating communication between the device 1210 and one or more other devices. The communication interface 1218 can include, for example, a receiver and a transmitter that can be used to receive and transmit information (wired or wirelessly), such as information from and to the charging stations in a multivehicle charging system or network and information from and to other devices such as a smartphone or another computer system.

[0079] The device 1210 can execute an application 1240 that allows it to perform operations including the operations and functions described herein (e.g., the operations of the integrated fuel management system 106, including the operations of Figure 1 1 ). A computer program containing the application 1240 may be loaded into the device 1210. For example, all or a portion of the computer program stored on a computer-readable medium may be stored in the memory 1216. When executed by the processor 1214, the computer program can cause the processor to perform and/or be a means for performing the functions of the example embodiments described and/or illustrated herein. Additionally or alternatively, the example embodiments described and/or illustrated herein may be implemented in firmware and/or hardware.

[0080] The application 1240 can include various software modules that perform the functions that have been described herein. For example, the application can include a user management module 1241 , a system management module 1242, and a GUI module 1243.

[0081 ] The user management module 1241 can perform functions such as, but not limited to: setting up user accounts that authorize users to use the multivehicle fueling system; authenticating users; metering fuel or electrical power consumed by each user; determining fuel efficiency (e.g., miles per gallon, or equivalent miles per gallon for EVs and hybrids); and optionally billing users.

[0082] The system management module 1242 can perform functions such as, but not limited to: monitoring the availability and functionality of fueling system components such as circuits, channels, output connections, heads, charging stations, and liquid fueling stations; controlling (e.g., turning on and off) such components; monitoring charge signatures and charging periods; collecting and logging fueling system information; and performing diagnostics.

[0083] The GUI module 1243 can perform functions such as, but not limited to, generating a GUI that can be accessed by a network administrator and can also be accessed by or pushed to other devices such as smartphones

[0084] Figures 13, 14, and 15 illustrate examples of displays that constitutes selected elements of the GUI 308 (Figure 3) that are rendered on a display device 1212 (Figure 12) in embodiments according to the invention. The displays shown in these examples may be full-screen displays, or they may be windows in a full-screen display. The displays may be displayed individually, or multiple displays may be displayed at the same time (e.g., side-by-side). The displays shown and described below are examples only, intended to demonstrate some of the functionality of the GUI 308. The present invention is not limited to these types or arrangements of displays.

[0085] Figure 13 illustrates an example of a display 1300 that is opened and presented when the tab 1302 (e.g., "Overview") in the GUI 308 is selected. In this example, the display 1300 includes a graph 1304 of the number of fueling transactions per day. The transactions may include both EV charging transactions and non-EV fueling transactions, in which case the data presented in the graph may be separated by the type of transaction as illustrated in the example.

[0086] Figure 14 illustrates an example of a display 1400 that is opened and presented when the tab 1402 and menu item 1404 (e.g., "Transactions" and "Fuel Issues," respectively) in the GUI 308 are selected. More specifically, in this example, when the tab 1402 is selected, a dropdown menu that includes a list of items (e.g., the menu items 1404 and 1406) is displayed. The menu item 1404 can be selected to open the display 1400. The display 1400 includes, for example, a table 1408 that lists fueling transactions by date, vehicle identifier (ID), driver ID, fueling station ID, and quantity. The transactions may include both EV charging transactions and non-EV fueling transactions as illustrated in the table 1408.

[0087] Figure 15 illustrates an example of a display 1500 that is opened and presented when the tab 1502 and menu item 1504 (e.g., "Data" and "Vehicle," respectively) in the GUI 308 are selected. More specifically, in this example, when the tab 1502 is selected, a dropdown menu that includes a list of items (e.g., the menu items 1504 and 1506) is displayed. The menu item 1504 can be selected to open the display 1500. The display 1500 includes a table 1508 that lists vehicles that are in the fleet or are otherwise authorized to use the stations in the multivehicle fueling system. The table 1508 also includes, for example, the capacity of each vehicle and the quantity of fuel (electric or other) obtained in the most recent fueling transaction.

[0088] Embodiments according to the present invention thus provide an integrated fuel management system for EV charging and non-EV fueling. The integrated fuel management system combines a flexible platform for managing fuels (e.g., fleet fuels) of all types, including electrical power. The integrated fuel management system includes timely access control, uniform departmental billing, and detailed cloud-based reporting. The technologies for managing electrical power and EV charging management and control include electrical infrastructure optimization, power metering and control, and a myriad of power utilization reporting tools. The combination integrates EV charging from any charging station into a total fuel management system using controllers and power management systems. The result is a solution that manages all electrical power dynamics as part of an integrated, full-featured fuel management system. Consequently, electricity for EV charging can be managed as a standard fleet fuel.

[0089] While the foregoing disclosure sets forth various embodiments using specific block diagrams, flowcharts, and examples, each block diagram component, flowchart step, operation, and/or component described and/or illustrated herein may be implemented, individually and/or collectively, using a wide range of hardware, software, or firmware (or any combination thereof) configurations. In addition, any disclosure of components contained within other components should be considered as examples because many other architectures can be implemented to achieve the same functionality.

[0090] The process parameters and sequence of steps described and/or illustrated herein are given by way of example only and can be varied as desired. For example, while the steps illustrated and/or described herein may be shown or discussed in a particular order, these steps do not necessarily need to be performed in the order illustrated or discussed. The various example methods described and/or illustrated herein may also omit one or more of the steps described or illustrated herein or include additional steps in addition to those disclosed. [0091 ] While various embodiments have been described and/or illustrated herein in the context of fully functional computing systems, one or more of these example

embodiments may be distributed as a program product in a variety of forms, regardless of the particular type of computer-readable media used to actually carry out the distribution. The embodiments disclosed herein may also be implemented using software modules that perform certain tasks. These software modules may include script, batch, or other executable files that may be stored on a computer-readable storage medium or in a computing system. These software modules may configure a computing system to perform one or more of the example embodiments disclosed herein. One or more of the software modules disclosed herein may be implemented in a cloud computing environment. Cloud computing environments may provide various services and applications via the Internet. These cloud-based services (e.g., storage as a service, software as a service, platform as a service, infrastructure as a service, etc.) may be accessible through a Web browser or other remote interface. Various functions described herein may be provided through a remote desktop environment or any other cloud-based computing environment.

[0092] Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the disclosure is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the disclosure.

[0093] Embodiments according to the invention are thus described. While the present disclosure has been described in particular embodiments, it should be appreciated that the invention should not be construed as limited by such embodiments, but rather construed according to the following claims.