SERVICE OPTIMIZATION

CROSS-REFERENCE TO RELATED APPLICATION

[0001] This application claims the benefit of U.S. Provisional Patent Application No. 62/361,333 entitled "PRIME MOVER NETWORK COMMUNICATION SYSTEM AND SERVICE OPTIMIZATION," filed July 12, 2016, which is incorporated herein by reference in its entirety.

TECHNICAL FIELD

[0002] The present disclosure relates to the determination and implementation of an optimization routine with a group of prime movers or a subset of prime movers within the group of prime movers.

BACKGROUND

[0003] A prime mover (e.g., a vehicle, such as a semi-tractor truck) operating at a theoretical optimal behavior for that prime mover may nevertheless operate sub-optimally when considered against a group of similar prime movers (e.g., a fleet of semi-tractor trucks). In this regard, even improved performance of an individual prime mover within a group of prime movers may either still be considered sub-optimal relative to the performance of the group of similar prime movers or, worse set, be counter-productive to an identified goal of the group of similar prime movers. For example, an operator of a prime mover may have set one or more settings of the prime mover to increase a power output from the prime mover at the cost of fuel economy despite a fleet manager for the group indicating that minimization of fuel consumption is a goal for the group. Thus, group-wide benefits may be lost or sacrificed due to the actions of one or more individuals (i.e., prime movers) within the group. SUMMARY

[0004] One embodiment relates to an apparatus for communicating with and selectively controlling a group of prime movers. The apparatus includes a communication circuit structured to communicate with a group of prime movers, and a performance analytics circuit communicably coupled to the communication circuit, the performance analytics circuit structured to: receive an indication of a desired operating parameter for the group of prime movers; interpret a cost index function based on the desired operating parameter; and determine an optimization routine for the group of prime movers responsive to the cost index function. In one embodiment, the apparatus also includes a control circuit structured to implement the determined optimization routine with the group of prime movers, wherein the optimization routine is structured to cause operation of the group prime movers to collectively move towards achievement of the desired operating parameter.

[0005] Another embodiment relates to method. The method includes receiving, by a controller, data regarding operation of each prime mover in a plurality of prime movers; determining, by the controller, a performance analytic for the plurality of prime movers based on the data; interpreting, by the controller, a cost index function based on the performance analytic; determining, by the controller, an optimization routine based on the cost index function; and implementing, by the controller, the optimization routine with at least one prime mover in the plurality of prime movers to improve performance of the group of prime movers based on cost index function.

[0006] Yet another embodiment relates to a system. The system includes a plurality of prime movers; and a controller communicably and operatively coupled to each prime mover within the plurality of prime movers, the controller structured to: receive data regarding operation of the plurality of prime movers; interpret a cost index function based on the received data regarding operation of the plurality of prime movers; determine an optimization routine based on the interpreted cost index function; and implement the optimization routine with at least one prime mover in the plurality of prime movers to improve operation of the plurality of prime movers in accordance with the cost index function.

[0007] These and other features, together with the organization and manner of operation thereof, will become apparent from the following detailed description when taken in conjunction with the accompanying drawings.

BRIEF DESCRIPTION OF THE FIGURES

[0008] FIG. 1 is a schematic diagram of a prime mover network communication system, according to an example embodiment.

[0009] FIG. 2 is a schematic diagram of a controller for the prime mover network communication system of FIG. 1, according to an example embodiment.

[0010] FIG. 3 is a flow diagram of a method of providing and implementing an optimization routine with one or more prime movers in a group of prime movers, according to an example embodiment.

DETAILED DESCRIPTION OF VARIOUS EMBODIMENTS

[0011] For the purposes of promoting an understanding of the principles of the disclosure, reference will now be made to the embodiments illustrated in the drawings and specific language will be used to describe the same. It will nevertheless be understood that no limitation of the scope of the disclosure is thereby intended, any alterations and further modifications in the illustrated embodiments, and any further applications of the principles of the disclosure as illustrated therein as would normally occur to one skilled in the art to which the disclosure relates are contemplated herein.

[0012] Referring to the Figures generally, the various embodiments disclosed herein relate to systems, methods, and apparatuses structured to identify a group of prime movers, interpret data regarding operation of each prime mover within the group, receive an indication of a desired operating parameter for the group of prime movers, interpret a cost index function based on the desired operating parameter, and determine an optimization routine for the group of prime movers responsive to the cost index function. The optimization routine then may then be provided or implemented with one or more prime movers within the group of prime movers. For example, the optimization routine may include a recommendation, which may be provided to an input/output device (e.g., a display device) of a prime mover for selective implementation by an operator that prime mover. The optimization routine may include a control parameter adjustment, which causes an adjustment of an operation setting of at least one component of the prime mover (e.g., adjusting a shift schedule of the transmission). In one embodiment, the control parameter adjustment may be performed automatically without user input to transform or adjust operation of the prime mover. In another embodiment, the control parameter adjustment may be performed responsive to receiving a user input to implement the control parameter adjustment (i.e., semi-automatic implementation). The optimization routine may still further include a combination of a recommendation and an adjustment to one or more control parameters.

[0013] Based on the foregoing, an example implementation of the systems, methods, and apparatuses disclosed herein may be described as follows. A controller may identify a group of power generators as a prime mover network. In this example, the prime movers that form the prime mover network may be power generators or gensets that are identified as a "group" based on a unifying characteristic(s). For example, the unifying characteristic may be the make and model of each generator being the same. During operation of each generator, the controller may receive or interpret data regarding operation of each generator. The received data may be stored and categorized (e.g., date/time, associated generator, data type, etc.). Based on the received data, the controller may determine one or more performance analytics associated with either i) a generator individually or ii) the prime mover network of generators as a whole (i.e., a fleet level metric). The one or more performance analytics may include, but are not limited to, an average power output per a unit of time, a maximum or minimum power output over a predefined time range, an average emissions characteristic per unit of time (e.g., amount of nitrous oxide emissions), a last oil change for each generator, etc. Such performance analytics may be provided to a display device associated with the controller, whereby a manager or fleet operator of the prime mover network may identify one or more operating parameters to optimize (e.g., minimize fuel consumption). In response to this identification, the controller may identify a cost index function and perform or apply the cost index function with the data associated with the prime mover network. For example, the cost index function may identify various calibration settings of one or more prime movers within the group of prime movers that are at a sub-optimal setting. Further, application of the cost index function may generate an improved or optimal calibration setting (i.e., the optimization routine) for the one or more prime movers. In other words and upon application of the cost index function, the controller may determine an optimization routine that indicates one or more modifications to implement with the one or more prime movers of the group of prime movers (e.g., operate three of the prime movers at seventy-five percent power output and the remaining two prime movers at thirty percent power output, schedule an oil change in three weeks, etc.), which may then be implemented with the one or more prime movers. As a result, the one or more prime movers may operate closer to the desired characteristic of the fleet manager (e.g., minimizing fuel consumption for the prime mover network as a whole).

[0014] Beneficially, the systems, methods, and apparatuses of the present disclosure may facilitate real-time or substantially real-time implementation of optimization routines across a group of prime movers, transform operation of one or more prime movers within a group of prime movers to improve operation of the group of prime movers as whole, and various other features and benefits described herein below. As a result of the optimization routines described herein, improvements including, but not limited to, fuel economy, total cost of ownership, system wear, route income, and/or selected combinations of these or other parameters may be realized by the owner or operator of a prime mover in the group of prime movers and/or a fleet operator or manager of the group of prime movers overall.

[0015] As used herein, the term "operating parameter" refers to settable "trim parameters" and

"calibration parameters" for a prime mover as well as other "operating parameters" for the prime mover. A "trim parameter" refers to an electronic operational setting for a prime mover or a component thereof that may be adjustable by an operator or a technician of the prime mover. In comparison, a "calibration parameter" or "calibration setting" is typically a setting that is non-adjustable by either the operator or a technician of the prime mover. An example of a calibration parameter is an allowable engine temperature before causing at least one of shutting the engine down, a derate event, and triggering an indicator light. Another example of a calibration parameter may include an operating condition prescribed by a local, state, or federal mandate (e.g., an acceptable emissions level before causing an engine derate condition). In comparison, a non-exhaustive list of trim parameters includes: various parameters relating to cruise control (e.g., an upper droop amount, a lower droop amount, etc.); a road speed governor limit (i.e., the maximum allowable road speed of the vehicle); an idle shut down parameter (e.g., an amount of time before an idle engine shuts down); a load based speed control parameter (e.g., a predefined engine speed for certain operating conditions, such as load); a gear down protection parameter for a light load vehicle speed and a heavy load vehicle speed (e.g., maintain the vehicle in the light load or heavy load vehicle speed to promote increased fuel economy by minimizing downshifts to promote operation of the vehicle in a top gear); and, a vehicle acceleration management feature (e.g., to limit acceleration in certain conditions to improve fuel economy). While the aforementioned list of operating parameters and calibration parameters are relevant to a vehicle (i.e., the prime mover is a vehicle in this instance), this list is not meant to be limiting as the present disclosure contemplates a variety of different types of prime movers (e.g., a power generator), such that the operating parameters and calibration parameters may differ for each type of prime mover. Moreover, as mentioned above, an "operating parameter" also includes other parameters for the prime mover in addition to various electronic control settings (e.g., trim parameters and calibration parameters). Particularly, the "operating parameter" may also include various other operating characteristics not otherwise captured by the aforementioned "operating parameter" group. Accordingly, operating parameters may also include, but are not limited to, an aftertreatment utilization value, a replacement schedule for one or more components of a prime mover (e.g., an oil filter), a utilization value of a consumable of the prime mover (e.g., oil), other maintenance events/schedules, a route plan for one or more prime movers, and so on.

[0016] As also used herein, the term "optimization" as used herein in regard to "optimization routines" is meant to be broadly understood. In particular, the term "optimization" refers to an improvement of one or more operating parameters for the group of prime movers (e.g., total fuel economy of the group, total emissions of the group, etc.). Accordingly, an "optimization" of an "operating parameter" may include, but is not limited to, a delivery time optimization of the group, a desired aftertreatment system utilization of the group (e.g. to extend service life and/or provide for duty cycle rotation to ensure proper regeneration), a desired battery or other consumable device utilization of the group, a provided route for selected vehicles that allows for service that is minimally disruptive to the service capability of the entire group, an improved replacement schedule for the prime movers in the group, and any combinations of these (e.g. through a cost or weighting function).

[0017] Referring now to FIG. 1, a schematic diagram of a prime mover network communication system is shown according to one embodiment. The prime mover network communication system 10 is an environment, system, or ecosystem that allows the exchange of information or data (e.g., communications) between a group of prime movers (and individual prime movers within the group) and a prime mover network communication center. In operation and as described herein, through the exchange of information and application of a cost index function, an optimization routine may be implemented with a group of prime movers to improve operation of the group of prime movers relative to a desired operating characteristic of the group. As shown, the prime mover network communication system 10 generally includes a plurality of prime mover networks, shown as a first prime mover network 100, a second prime mover network 200, and a third prime mover network 300, and a prime mover network communication center 400 having a controller 450. The plurality of prime mover networks are communicably and operatively coupled to the prime mover network communication center 400 and controller 450 over a network 50.

[0018] In one embodiment, the network 50 includes any wireless protocol that enables wireless communications between the prime mover network 100, 200, and 300 and/or individual prime movers within the prime mover network 100, 200, and 300 with the prime mover network communication center 400 and controller 450. Beneficially, the use of a wireless network or protocol facilitates remote transmission and implementation of optimization routines with the prime mover network. The wireless network may be any type of wireless network, such as Wi-Fi, WiMax, Geographical Information System (GIS), Internet, Radio, Bluetooth, Zigbee, satellite, radio, Cellular, Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), Long Term Evolution (LTE), light signaling, etc. In another embodiment, the network 50 may be a wired network whereby data exchange (e.g., optimization routines) is accomplished through a direct, physical connection with the controller 450. In this regard, the wired network may include a data communication cable that connects a prime mover with the controller 450, whereby the data communication cable may include any type of data communication cable (e.g., USB, fiber optics, RS-232, etc.). In yet another embodiment, the network 50 may be structured as any combination of wired and wireless networks. In this regard and advantageously, data communication may be accomplished in "dead zones" (e.g., where a wireless network may be unavailable).

[0019] As shown, the system 10 includes a first prime mover network 100, a second prime mover network 200, and a third prime mover network 300. The prime mover networks 100, 200, and 300, also referred to as a "group of prime movers," represents a group of prime movers that are considered together or related. In this regard and as used herein, a "group of prime movers" may include, but is not limited to, an associated fleet of trucks, a genset network at a location, a group of engines together at a location performing off-road work (e.g. mining, drilling, fracking, construction), a group of rail or marine engines, etc. The group of prime movers may have the same owner, or may have distinct owners but are nevertheless being considered together as a group. In one example, non-owned engines (i.e., prime movers) may subscribe to a prime mover network, such as the system 10 with the prime mover network communication center 400 and controller 450, and share the cost savings between members of the group (i.e., a collaboration). In the example depicted, the first prime mover network 100 represents a group of vehicles 101, the second prime mover network 200 represents a group of generators 201, and the third prime mover network 300 represents a group of off-road engines 301. Of course, in other embodiments, more or less prime mover network networks may be included with the system 10. Further, in certain embodiments, a controller 450 may be implemented with each distinct prime mover network, rather than a single controller 450 useable with each of the depicted three prime mover networks 100, 200, and 300. [0020] Referring to the prime mover network 100, a group of vehicles 101 make-up or form the network 100. An example illustration of a vehicle 101 within the group 100 is shown in FIG. 1, according to an example embodiment. While the vehicle 101 may be any type of vehicle that can be considered grouped together by, for example, by one or more unifying traits or characteristics (e.g., same engine type, same type of vehicle, same owner/operator, etc.), in this example, the vehicle 101 is structured as an on-road vehicle, which may include, but is not limited to, line-haul trucks, mid-range trucks (e.g., pick-up truck), full electric vehicle, hybrid electric vehicle, etc. However, in other embodiments, the vehicle 101 may be structured as an off-road vehicle (e.g., tanks, airplanes, etc.), which is depicted in the group 200. As shown, the vehicle 101 includes a powertrain system 110, an exhaust aftertreatment system 120, an operator input/output (I/O) device 130, a controller 140, and a telematics unit 60, where the controller 140 is communicably coupled to each of the aforementioned components. Of course, this depiction is not meant to be limiting as the vehicle 101 may include any of a variety of other components, such as an electrically driven/controlled air compressor, an electrically driven/controlled engine cooling fan, an electrically driven/controlled heating venting and air conditioning system, an alternator, etc., where the controllability may stem from the controller 140.

[0021] The powertrain system 110 facilitates power transfer from the engine 111 to power and/or propel the vehicle 101. The powertrain system 110 includes an engine 111 operably coupled to a transmission 112 that is operatively coupled to a drive shaft 113, which is operatively coupled to a differential 114, where the differential 114 transfers power output from the engine 111 to the final drive (shown as wheels 115) to propel the vehicle 101. As a brief overview, the engine 111 receives a chemical energy input (e.g., a fuel such as gasoline or diesel) and combusts the fuel to generate mechanical energy, in the form of a rotating crankshaft. As a result of the power output from the engine 111, the transmission 112 may manipulate the speed of the rotating input shaft (e.g., the crankshaft) to achieve or substantially achieve a desired drive shaft 113 speed. The rotating drive shaft 113 is received by a differential 114, which provides the rotation energy of the drive shaft 113 to the final drive 115. The final drive 115 then propels or moves the vehicle 101. [0022] The engine 111 may be structured as any internal combustion engine (e.g., compression-ignition or spark-ignition), such that the engine 111 can be powered by any fuel type (e.g., diesel, ethanol, gasoline, etc.). Similarly, the transmission 112 may be structured as any type of transmission, such as a continuous variable transmission, a manual transmission, an automatic transmission, an automatic-manual transmission, a dual clutch transmission, etc. Accordingly, as transmissions vary from geared to continuous configurations (e.g., continuous variable transmission), the transmission can include a variety of settings (gears, for a geared transmission) that affect different output speeds based on the engine speed. Like the engine 111 and the transmission 112, the drive shaft 113, differential 114, and final drive 115 may be structured in any configuration dependent on the application (e.g., the final drive 115 is structured as wheels in an automotive application and a propeller in an airplane application). Further, the drive shaft 103 may be structured as a one-piece, two-piece, and a slip-in-tube driveshaft based on the application.

[0023] As also shown, the vehicle 101 includes an exhaust aftertreatment system 120 in fluid communication with the engine 111. The exhaust aftertreatment system 120 may receive exhaust gas from the combustion process in the engine 101 and transform/reduce the emissions from the engine 111 to less environmentally harmful emissions (e.g., reduce the nitrous oxide (NOx) amount, reduce the emitted particulate matter amount, etc.). The exhaust aftertreatment system 120 may include any component used to reduce diesel exhaust emissions, such as a selective catalytic reduction catalyst, a diesel oxidation catalyst, a diesel particulate filter, a diesel exhaust fluid doser with a supply of diesel exhaust fluid, and a plurality of sensors for monitoring the system 120 (e.g., a NOx sensor). It should be understood that other embodiments may exclude an exhaust aftertreatment system and/or include different, less than, and/or additional components than that listed above. All such variations are intended to fall within the spirit and scope of the present disclosure.

[0024] The operator input/output device 130 enables an operator of the vehicle to communicate with the vehicle 101 and the controller 140 (and, in certain instances, with the controller 450). For example, the operator input/output device 130 may include, but is not limited, an interactive display (e.g., a touchscreen, etc.), an accelerator pedal, a clutch pedal, a shifter for the transmission, paddle input devices, a cruise control input setting, etc. Via the input/output device 130, the operator can designate preferred characteristics of one or more desired operating parameters (e.g., an upper cruise control droop amount).

[0025] As shown, the controller 140 is communicably and operatively coupled to the powertrain system 110, the exhaust aftertreatment system 120, the telematics unit 60, and the operator input/output device 130. Communication between and among the components may be via any number of wired or wireless connections. For example, a wired connection may include a serial cable, a fiber optic cable, a CAT5 cable, or any other form of wired connection. In comparison, a wireless connection may include the Internet, Wi-Fi, cellular, radio, etc. In one embodiment, a CAN bus provides the exchange of signals, information, and/or data. The CAN bus includes any number of wired and wireless connections. Because the controller 140 is communicably coupled to the systems and components in the vehicle 101 of FIG. 1, the controller 140 is structured to receive data (e.g., instructions, commands, signals, values, etc.) from one or more of the components shown in FIG. 1. Because the components of FIG. 1 are shown to be embodied in a vehicle 101, the controller 140 may be structured as an electronic control module (ECM). The ECM may include a transmission control unit and any other control unit included in a vehicle (e.g., exhaust aftertreatment control unit, engine control module, powertrain control module, etc.).

[0026] Before turning to the description of the telematics unit 60, each prime mover within prime mover networks 200 and 300 are firstly described. As shown, the prime mover network

200 is formed from a group or a plurality of power generators or gensets 201. The group of generators 201 may be considered a group due to one or more unifying features (like the vehicles 101), such as a similar owner/operator, a similar location, a similar make or model, a similar engine size, etc. The generator 201 may be implemented or used in commercial, residential, and/or mobile settings/situations. Further, the generator 201 may be of any shape, size, and configuration. A non-exhaustive list of components included with the generator 201 is: an engine (e.g., a gas, diesel, or any other type of fuel-powered engine), a governor, a lubrication system including an oil filter, a starter, a coolant heater, an aftertreatment system structured to reduce emissions from the generator 201, an electrical transfer system (e.g., a system designed to transfer electrical energy from the generator 201 to a receiver of the electrical energy, such as an outlet or a meter), one or more energy storage devices, and a control system, such as control system 210. In one embodiment, the group 200 may be a group of power generators and energy storage devices, such that the methods, systems, and apparatuses described herein may be implemented/or useable with renewable energy-based integrated systems for base-load power generation. The energy storage devices can be any device such as, a thermal energy storage device, a pumped hydro-energy storage device, an electro-chemical, a chemical and electromagnetic energy storage device, etc. The control system 210 may be structured to control various operating parameters of the generator 201 and to generally monitor operation of the generator 201. In this regard, the generator 201 may include various sensors (e.g., engine speed sensor, engine temperature sensor, emissions sensor such as a nitrous oxide sensor, coolant temperature sensor, coolant flowrate sensor, electrical sensor (e.g., power output), etc.) that acquire data (e.g., information, values, etc.) indicative of operation of the generator 201. The acquired data may be provided to the control system 210 whereby the control system 210 is structured to control operation of the generator 201 based, at least in part, on the acquired data. For example, if the engine temperature is above a preset threshold upper limit, the control system 210 may automatically derate the engine to reduce the temperature.

[0027] As shown, the prime mover network 300 includes a group of engines 301. In this particular example, the group of engines 301 represents a group of off-road engines 301. The group of off-road engines 301 refers to a group of engines used at a particular location (e.g., mining, marine engines, rail engines such as locomotives, etc.) in a non-road application. Each engine 301 in the network 300 is shown to include a control system 310. The control system 310 may set and implement various operating parameters with the engine 301 as well as track various operating characteristics or data of each engine 301. For example, the control system 310 may acquire data indicative of an engine speed, an engine temperature, an hours of operation of the engine, a frequency of use of the engine, a maintenance schedule for the engine, and so on. [0028] As shown, each of the vehicle 101, generator 201, and engine 301 includes a telematics unit 60. The telematics unit 60 may be structured as any type of telematics unit. Accordingly, the telematics unit 60 may include, but is not limited to, a location positioning system (e.g., a global positioning system) to track the location of the prime mover, such as the vehicle 101 (e.g., latitude and longitude data, elevation data, etc.), one or more memory devices for storing the tracked data, one or more electronic processing units for processing the tracked data, and a communications interface for facilitating the exchange of data between the telematics unit 60 and one or more remote devices (e.g., a provider/manufacturer of the telematics device, etc.), such as the controller 450. In this regard, the communications interface may be configured as any type of mobile communications interface or protocol including, but not limited to, Wi-Fi, WiMax, Internet, Radio, Bluetooth, Zigbee, satellite, radio, Cellular, GSM, GPRS, LTE, and the like. The telematics unit 60 may also include a communications interface for communicating with the controller 140 of the vehicle 101, the control system 210 of generator 201, and the control system 310 of engine 301. The communication interface may include any type and number of wired and wireless protocols (e.g., any standard under IEEE 802, etc.). For example, a wired connection may include a serial cable, a fiber optic cable, an SAE J1939 bus, a CAT5 cable, or any other form of wired connection. In comparison, a wireless connection may include the Internet, Wi-Fi, Bluetooth, Zigbee, cellular, radio, etc. In one embodiment, a controller area network (CAN) bus including any number of wired and wireless connections provides the exchange of signals, information, and/or data between the controller 140, control system 210, and control system 310 with an associated telematics unit 60. In other embodiments, a local area network (LAN), a wide area network (WAN), or an external computer (for example, through the Internet using an Internet Service Provider) may provide, facilitate, and support communication between the associated telematics unit 60 and the controller 140, control system 210, and control system 310.

[0029] In one embodiment and as mentioned above, the prime mover network communication center 400 is structured to communicate wirelessly with the group of prime movers 100, 200, and/or 300 (e.g., one or more prime movers within each group). In this regard, wireless communications may be provided and supported by the telematics unit 60 of each prime mover in each group 100, 200, and 300 and the controller 450.

[0030] However, in another embodiment, the prime movers may not include a telematics unit. In this configuration, various other communication protocols and systems may be implemented to enable communication exchange with the controller 450. For example and as mentioned above, in one embodiment, the controller 450 may be included with the prime mover such that the controller 450 receives data regarding operation of the associated prime mover readily. In this case, the controller 450 may then need to be connected to or hooked up to a service diagnostic tool at the prime mover network communication center 400 to enable the center 400 to download or receive all the acquired data and then to determine an optimization routine. Thus, those of ordinary skill in the art will appreciate the wide range of communication protocols that may be implemented with the system 10 to enable the exchange of information or data to, in turn, determine and implement optimization routines.

[0031] Still referring to FIG. 1, the prime mover network communication center 400 is shown to include a controller 450 that is communicably and operatively coupled to each group 100, 200, and 300. In one embodiment, the prime mover network communication center 400 represents a call center or operations center for an associated prime mover network; in this case, for each of the prime mover networks 100, 200, and 300. The center prime mover network communication center 400 may include one or more technicians, operators, or works that are able to communicate with each group over the network 50. In another embodiment, the prime mover network communication center 400 represents any type of remote monitoring, managing, and/or operational control center for an associated group of prime movers. In this regard, the prime mover network center 400 may include the owner of the group of prime movers 100, 200, and 300, may be the operator or manager of the group of prime movers 100, 200, and 300, may be a third-party service provider structure to provide optimization routines as described herein, or any combination thereof.

[0032] As shown, the controller 450 is included with the prime mover network communication center 400. In this regard, the controller 450 may be operatively coupled to one or more input/output devices (e.g., display screen, keyboard, touchscreen, etc.) and structured to enable the providing and receiving of information between one or more of the groups 100, 200, and 300 (e.g., a prime mover within the group) and an operator or attendant of the input/output device (e.g., an employee of the prime mover network communication center 400). As described herein below, the controller 450 may be structured to interpret data regarding operation of each group of prime movers 100, 200, or 300, apply a cost function to the data to determine an optimization routine, and responsive to the determination, implement the optimization routine with an associated group of prime movers or provide the optimization routine to be implemented with the group of prime movers.

[0033] As also shown in FIG. 1 and alluded to above, optionally, a controller 450 may be implemented with each prime mover (i.e., vehicle 101, generator 201, and engine 301) in each group 100, 200, or 300. In this embodiment, the operations described herein may be implemented directly with one or more select prime movers within each group of prime movers 100, 200, or 300 by an associated controller 450 for each prime mover within each group of prime movers. In the case where a controller 450 is implemented with each prime mover within the group of prime movers, communication between the controllers 450 of each prime mover may be accomplished through any suitable wired or wireless network, as described above with regard to the network 50. For example, the network 50 may facilitate the exchange of information and data between the prime movers within the group. The controller 450 may then use this information to determine and apply an optimization routine with the associated prime mover of the controller 450.

[0034] While the prime mover implementation embodiment is an example application of the controller 450, as mentioned above and shown in FIG. 1, the controller 450 is shown with the prime mover network communication center 400 and, therefore, separate from each group. In either implementation embodiment - separate from each prime mover, such as with a prime mover communication center 400 or with each prime mover within each group - an example structure of the controller 450 is shown in FIG. 2. [0035] Accordingly, referring now to FIG. 2, the function and structure of the controller 450 is shown according to an example embodiment. The controller 450 is shown to include a processor 451 and a memory 452. The processor 451 may be implemented as any type of processor including an application specific integrated circuit (ASIC), one or more field programmable gate arrays (FPGAs), a digital signal processor (DSP), a group of processing components, or other suitable electronic processing components. The one or more memory devices 452 (e.g., NVRAM, RAM, ROM, Flash Memory, hard disk storage, etc.) may store data and/or computer code for facilitating the various processes described herein. Thus, the one or more memory devices 452 may be communicably connected to the processor 451 and provide computer code or instructions for executing the processes described in regard to the controller 450 herein. Moreover, the one or more memory devices 452 may be or include tangible, non-transient volatile memory or non-volatile memory. Accordingly, the one or more memory devices 452 may include database components, object code components, script components, or any other type of information structure for supporting the various activities and information structures described herein.

[0036] As shown, the controller 450 includes various circuits for completing the activities described herein. In one embodiment, the circuits of the controller 450 may utilize the processor 451 and/or memory 452 to accomplish, perform, or otherwise implement various actions described herein with respect to each particular circuit. In this embodiment, the processor 451 and/or memory 452 may be considered to be shared components across each circuit. In another embodiment, the circuits (or at least one of the circuits) may include their own dedicated processing circuit having a processor and a memory device. In this latter embodiment, the circuit may be structured as an integrated circuit or an otherwise integrated processing component. In yet another embodiment, the activities and functionalities of circuits may be embodied in the memory 452, or combined in multiple circuits, or as a single circuit. In this regard and while various circuits with particular functionality are shown in FIG. 2, it should be understood that the controller 450 may include any number of circuits for completing the functions and activities described herein. For example, the activities of multiple circuits may be combined as a single circuit, as an additional circuit(s) with additional functionality, etc. Further, it should be understood that the controller 450 may further control other activity beyond the scope of the present disclosure.

[0037] Certain operations of the controller 450 described herein include operations to interpret and/or to determine one or more parameters. Interpreting or determining, as utilized herein, includes receiving values by any method known in the art, including at least receiving values from a datalink or network communication, receiving an electronic signal (e.g. a voltage, frequency, current, or PWM signal) indicative of the value, receiving a computer generated parameter indicative of the value, reading the value from a memory location on a non-transient computer readable storage medium, receiving the value as a run-time parameter by any means known in the art, and/or by receiving a value by which the interpreted parameter can be calculated, and/or by referencing a default value that is interpreted to be the parameter value.

[0038] As shown, the controller 450 includes a communication circuit 453, a database 454, an operator interface circuit 455, a performance analytics circuit 456, and a control circuit 457. Through the circuits 453 and 455-457 and database 454, the controller 450 is structured to identify a group of prime movers, interpret data regarding operation of the group of prime movers, receive a desired operating characteristic for the group of prime movers, apply a cost index function to the data based on the desired operating characteristic, and provide or implement an optimization routine with the group of prime movers based on the application of the cost index function.

[0039] The communication circuit 453 is structured to facilitate, enable, maintain, and otherwise provide a communication channel between the controller 450 and each group of prime movers 100, 200, and 300 to enable the exchange of communications (e.g., data, values, information, etc.) between the controller 450 and each group of prime movers 100, 200, and 300. The exchange of information may be between the controller 450 and a representative prime mover for each group, between each prime mover in each group and the controller 450, between a control center associated with each group and the controller 450, and/or between a subset of prime movers (e.g., one or more) within each group and the controller 450. Thus, the communication circuit 450 is structured to include any type of wired and/or wireless network communication protocols or interfaces for connecting to the group over the network 50. For example, the communication circuit 453 may include an Ethernet card and port for sending and receiving data via an Ethernet-based communications network and/or a Wi-Fi transceiver for communicating via a wireless communications network. The communication circuit 453 may be structured to communicate via local area networks or wide area networks (e.g., the Internet, a building WAN, etc.) and may use a variety of communications protocols (e.g., IP, LON, Bluetooth, ZigBee, radio, cellular, etc.). In this regard, the communication circuit 453 is structured to facilitate, support, and enable communications through any combination of wired connection protocols (e.g., a serial cable, a fiber optic cable, a CAT5 cable, or any other form of wired connection) and/or wireless connection protocols (e.g., the Internet, Wi-Fi, cellular, Bluetooth, ZigBee, radio, etc.).

[0040] Through the communication circuit 453, the database 454 is structured to receive and store, hold, and otherwise serve as a repository for operation data received from each prime mover within the group of prime movers 100, 200, and 300. The database 454 may also include one or more classification and/or categorization functions (e.g., logic processing, etc.). The classification function may sort, categorize, or otherwise classify each piece of received operation data from each prime mover (or each transmitting prime mover) within the groups 100, 200, or 300. For example, engine speed data for a vehicle 101 over a predefined time range may be stored in section associated with the group 100 and in a further sub-section dedicated to that particular vehicle 101. As another example, the classification function may categorize all similar types of data in a similar location (e.g., folder). For example, maintenance schedule information (e.g., oil filter change dates, etc.) for all the vehicles 101 in the group 100 may be stored in a separate and designated folder of the database 454. Beneficially, the storage and classification of data by group, by type, and/or by associated individual prime mover may facilitate relatively fast and efficient uses of said data to thereby implement an optimization routine in real-time or substantially real time.

[0041] In some embodiments, the database 454 may be a separate component relative to the controller 450. For example, due to the potential high volume or quantity of data stored by the database 454, the database 454 may be formed or constructed from two or more server-based storage components stored over two or more remote geographic locations. In this embodiment, the database 454 may simply receive, store, and classify/categorize the received operational data. Further, in this configuration, a controller 450 may be implemented with each prime mover within the group 100, 200, and 300, such that generation and implementation of the optimization routine may be performed through the controller 450 requesting and retrieving desired operation data stored in the remote database 454. Thus, those of ordinary skill in the art will recognize and appreciate the vast implementation applications of the database 454.

[0042] The operator interface circuit 455 may be structured to facilitate and provide communications between the controller 450 and an operator and the controller 450. Accordingly, in one embodiment, the operator interface circuit 455 may include an operator input/output device, such as a graphical user interface. In another embodiment, the operator interface circuit 455 includes communication circuitry for facilitating the exchange of information between the controller 450 and an operator input/output device. In yet another embodiment, the operator interface circuit 455 includes machine-readable media and any combination of hardware (e.g., communication circuitry) for facilitating the exchange of information between the controller 450 and an attendant, operator, or manager of the controller 450.

[0043] Through the operator interface circuit 455, an operator, attendant, and/or fleet manager or other responsible party may define a desired operating parameter for the vehicle 100. As described herein, the desired operating parameter or desired operating characteristic of the group of prime movers 100, 200, or 300 refers to how an operator (or a fleet manager) would like the group 100, 200, or 300 to operate as a whole. For example, a desired operating parameter may be to minimize fuel consumption. As another example, a desired operating parameter may be to incrementally improve fuel economy. Incremental improvement may refer to a numerical increase (e.g., 8.2 miles-per-gallon (MPG) to 8.3 MPG is an incremental increase), a predefined percent increase (e.g., one percent, two percent, ten percent, etc.), or any other metric understood by those of ordinary skill in the art to represent an incremental increase. In this regard, "incremental increase" may be a momentary occurrence (e.g., less than thirty seconds) or be required to exist for a predefined time period or distance (e.g., three minutes, five miles, etc.). As still another example, a desired operating parameter may be to improve an acceleration characteristic (i.e., remove or lower various fuel consumption trim parameters to enable an operator to receive a maximum or near maximum amount of acceleration when desired). As yet another example, a desired operating parameter may be to minimize or reduce a specific exhaust gas emissions characteristic (e.g., CO, NOx, etc.). As still another example, a desired operating parameter may be to reduce DEF dosing in an exhaust aftertreatment system, such as the exhaust aftertreatment system 120. As yet another example, a desired operating parameter may be to perform efficient service events by, e.g., grouping multiple prime movers together for a group service event in order to minimize interruption and scheduling challenges caused by individually scheduling maintenance for each prime mover. It should be understood that the aforementioned list is not meant to be limiting as the present disclosure contemplates further and additional desired operating parameters intended to fall within the scope of the present disclosure.

[0044] The performance analytics circuit 456 is structured to analyze the operation data to determine various performance analytics or performance analytics data, interpret a cost index function based on the desired operating parameter, and determine or generate an optimization routine based on the cost index function. The analyzed operation data (i.e., the performance analytics) may be provided to the operator interface circuit 456 for displaying the analyzed data to an operator, attendant, or manager of the group 100, 200, or 300. In one embodiment, the performance analytics circuit 456 includes processing electronics capable of performing one or more algorithms, formulas, operations, and the like to facilitate and enable determination of the performance analytics. In another embodiment, the performance analytics circuit 456 includes machine-readable media or a combination of machine-readable media and processing electronics capable of performing one or more algorithms, formulas, operations, and the like to facilitate and enable determination of the analytics data.

[0045] Regarding the performance analytics or performance analytics data, the performance analytics circuit 456 may utilize one or more formulas, algorithms, processes, or operations to at least one of provide a prediction, a trend analysis, other statistical representations, and the like of various acquired data for a group of prime movers. Accordingly, the performance analytics circuit 456 may include model predictive controls algorithm(s), statistical algorithms (e.g., averages, standard deviations, etc.), and any other type of formula or algorithm for generating a desired analytic of the received operation data for the group 100, 200, or 300.

[0046] While the performance analytics circuit 456 may generate and provide a vast amount of performance analytics data, specific examples are provided below. In this regard, examples relating to any of the groups 100, 200, or 300 include, but are not limited to: a current aftertreatment system state (e.g. soot filter of vehicle X is full or nearly full); using trend data to predict and change aftertreatment or electrical devices; using predictive diagnostics in utilization planning (e.g., which vehicles 101 of the group 100 should be utilized in the upcoming mission (e.g., delivery of freight) and which vehicles 101 of the group 100 should be serviced); and, use of load profile trending data to make a prediction about maintenance, oil change interval, etc., which can be applicable with any of the groups 100, 200, or 300 or substantially any other networks of prime movers. Another example may include turning on the prime mover (e.g., genset 201) early and pre-loading the battery for a job (any scheduled job or duty operation that is predictable is amenable to this activity, such as fracking, drilling, road hauling, daily cycling of genset loads, etc.). Yet another example may include determining a spark plug utilization value and duty cycle data. For example, the spark plug utilization value may represent a number of hours of operation of the vehicle, a number of "fires," an hours of usage value, a time since last replacement, another preset definition of usage for the spark plug (e.g., two-years), etc. In response, the performance analytics circuit 456 may determine a plan for re-gapping or a replacement schedule. This activity may be beneficial due to the high commercial value of this activity: oil changes and other maintenance routines are often planned around spark plug re-gapping, such as wear-out prediction based on voltage monitoring or other information.

[0047] Regarding the group 100 of vehicles 101, additional examples of performance analytics data include, but are not limited to, a capability and state-of-health of an electronic propulsion system (if any, for example, if the vehicle 101 is configured as a hybrid electric vehicle); a current route plan and duty cycle; various aftertreatment system requirements, such as a regeneration event, a filter change, etc.; various electronic propulsion system requirements, such as the need to recharge the battery to a predefined state-of-charge threshold level; current vehicle 101 service requirements for each vehicle 101 in the group of vehicles 100, which can be matched with the current route plan and duty cycle of each associated vehicle 101 in order to maximize efficiency of the service requirements (e.g., minimize downtime); etc.

[0048] Thus, the performance analytics data determined and/or generated by the performance analytics circuit 456 is meant to be broadly interpreted and highly configurable based on the prime mover network 100, 200, or 300 (or any other group of prime movers). In certain embodiments, the determinations and output of the performance analytics circuit 455 may be sufficient to meet a desire of an operator of the group (e.g., groups 100, 200, or 300). For example, an operator or attendant of the group may desire to simply observe trends and make predictions. However, in other embodiments and as explained below, the operator or attendant may desire to effect change in various operating parameters of a prime mover within the group and of the group overall, which may be accomplished through an optimization routine described herein below.

[0049] Regard the interpretation of a cost index function, the performance analytics circuit 456 is structured to interpret a cost index function responsive to a desired operating parameter. The cost index function is structured to optimize the desired characteristic or operating parameter, as received by the operator input/output circuit 455. In this regard, the cost index function may represent a function, algorithm, process, operation, optimization function, and/or any other method for optimizing or substantially optimizing the desired operating parameter.

[0050] In one embodiment, the cost index function represents the performance analytics circuit 456 identifying the "best" performing prime mover within the group of prime movers 100, 200, or 300 for the desired operating parameter. For example, if the desired operating parameter is minimizing fuel consumption, the performance analytics circuit 456 may be structured to identify the top one or a few vehicles 101 in the group 100 that are achieving the relatively best fuel consumption. In response, the performance analytics circuit 456 may extract various operating parameter data for those identified vehicles 101 (e.g., fuel injection timing and quantity, calibration parameters, operating parameter settings, make/model of various components included with the prime mover, maintenance schedule for the identified prime mover(s), and the like).

[0051] In another embodiment and as mentioned above, the cost index function represents the performance analytics circuit 456 selecting a cost index function or algorithm for application and implementation. Because of the wide variety of prime mover networks (such as the generators 201, engines 301, and vehicles 101), the cost index function may take a variety of forms. Non-limiting examples include: a formula for minimizing fuel consumption, a formula for minimizing a cost of a component (e.g., cargo time delivery cost, vehicle wear cost, etc.); a formula for minimizing an emissions cost; a formula for minimizing a component wear value; etc. Additional exemplary cost index functions may include, but are not limited to: an income strategy to, e.g., maximize income (e.g. incentive based delivery); an algorithm to increase a value provided to a customer account based on certain customer costs (e.g. ton-miles delivered) to, e.g., minimize a ratio (e.g., owner cost:ton-mile cost or costvalue delivered, etc.).

[0052] Thus, due to the wide variety of prime mover networks, those of ordinary skill in the art will readily appreciate the high configurability of the cost index function as utilized by the performance analytics circuit 456. In this regard, the cost index function may be specific to a certain type of prime movers. For example, the cost index functions useable with the group 100 may differ from that of the group 200. In this regard and if different controllers 450 are used with each group 100 and 200, the structure and configuration of each controller 450 may be tailored to the particular prime mover group that the controller is implemented or associated with. Such a benefit may result in controllers of different sizes and shapes that are tailored to their particular application.

[0053] In certain embodiments, the cost index function may include one or more predefined constraint values. For example, an operator may define a constraint value that the "aftertreatment must regenerate with 2 hours or before 25 grams of soot accumulate," etc. Another example of a constraint is that fuel consumption may only be decreased to a certain predefined preset threshold because any further decreases may adversely affect performance of the prime mover. Yet another example of a constraint is identifying a route of each vehicle 101 within the group. In this example, the cost index function is limited to surroundings that may near or substantially near the vehicle 101 on the route (e.g., charge stations for an electric vehicle). In still yet another example of a constraint is a maximum operating time of a power generator. In still yet a further example of a constraint is a maximum temperature for an engine (e.g., engine 301). It should be understood that the aforementioned list of constraints is not meant to be exhaustive as many different and other types of constraints may be utilized by the performance analytics circuit 456.

[0054] The performance analytics circuit 456 may identify or select a cost index function for use based on a variety of factors. In one embodiment, the selected cost index function is based on the desired operating characteristic. For example, minimizing fuel consumption may correspond with a different cost index function than minimizing CO emissions. In another embodiment, the selected cost index function is based on the type of prime mover in the group of prime movers. For example, the selected cost index function for the vehicle 101 may differ from that of the generator 201. In yet another embodiment, the selected cost index function is based on an explicit user input (e.g., via the operator input/output circuit 454). For example, an operator may define an algorithm to use with a particular prime mover network. Thus, many different may be used to select a cost index function with all such factors intended to fall within the scope of the present disclosure.

[0055] Responsive to the selected cost index function, the performance analytics circuit 456 is structured to determine an optimization routine for the group of prime movers. The "optimization routine" refers to the performance of the cost index function to generate or determine a recommendation output for the associated group of prime movers. For example if the cost index function is implementing the operating parameters of the identified "best" prime movers, the optimization routine for that group of prime movers may represent a set of data or information corresponding to the "best" prime mover, which may be implemented (selectively) with the remaining members of the group of prime movers. Various additional non-limiting recommendation outputs are described below. [0056] Responsive to the desired operating parameter being to schedule maintenance events together (filter changes, aftertreatment service, spark plugs, oil changes, even engine rebuilds), the optimization routine may include a preferred maintenance schedule for a prime mover network whereby most of or substantially most of the maintenance events are grouped together at each scheduled maintenance event in order to minimize visits of each group member to the technician or service station. Further and in this regard, not all maintenance events need to be on the same time constant - slower events can still be scheduled to end with one of the faster events which still reduces number of maintenance shutdowns overall. As a further iteration of this example, the optimization routine may include a preferred maintenance schedule that schedules maintenance and/or component swaps for the fleet (e.g., group 100) or genset group (e.g., group 200) through duty cycle management of the vehicles 101 or gensets 201. For example, the preferred maintenance schedule may schedule maintenance on a particular vehicle 101 or genset 201 to end at the same time or staggered according to a plan (e.g. to meet the capacity of the maintenance shop, to meet a scheduled maintenance visit to a remote location, to keep a certain number of trucks on the road or gensets operating during maintenance, etc.). As a result of this optimization routine, a maintenance facility may have improved operations (e.g., by scheduling customer maintenance intervals for better utilization of the maintenance facility). In some instances, savings may be shared with customers or the benefits may be realized by the customers through improved access to the maintenance facility and reduced downtime.

[0057] Responsive to the desired operating parameter being more efficient route planning for the group, the optimization routine may include a route plan coordinated to various other desired operating parameters (e.g., minimize fuel consumption, minimize emissions, etc.). For example, the optimization routine may include a route plan between two vehicles in the group 100 to improve an aftertreatment requirement match, an electronic propulsion system match, and/or a vehicle current service requirement match. As another example, the optimization routine may include a change in a route plan and/or duty cycle for two or more vehicles in the group 100 to, e.g., transfer a load between them, switch which vehicle is going to be utilized, etc. in order to improve an aftertreatment requirement match, an electronic propulsion system match, and/or a vehicle current service requirement match.

[0058] Responsive to the desired operating parameter being an indication to use components of each prime mover in a group more efficiently (i.e., reduce wear to prolong usage), an optimization routine may include a recommendation to change one or more components in two prime mover systems of the group. For example, the recommendation may include, but is not limited to: to swap an aftertreatment component between two prime movers such as a soot filter; to swap an electronic propulsion system component two prime movers (e.g., two vehicles 101), such as a battery; to make a cost neutral change with an engine manufacturer such as swapping load ratings (e.g., swapping a 425 FIP calibration and a 450 FIP calibration - could be with notice to the manufacturer or other provider that the total horsepower in the fleet is unchanged); and/or to improve an aftertreatment requirement match, an electronic propulsion system match, a vehicle current service requirement match, and/or, to more optimally meet the overall route plan for the fleet. In another embodiment, the recommended change in one or more prime mover systems is not cost neutral, such as with an agreed transaction with the engine manufacturer (e.g., increase a rating to more optimally meet a route plan, with an agreed transaction with the manufacturer, improving overall fleet performance, for one or more routes). Another example of a recommended component change incudes changing one or more prime mover systems (e.g., vehicle systems, genset systems, etc.) at design time (i.e., before addition of the prime mover to an existing group of prime movers) based on the route plan to, in turn, optimize or improve the fleet performance by, and in regard to the group 100, changing the engine, gear ratios, driveline parameters, electronic propulsion system, and/or aftertreatment system of one or more vehicles 101 in the fleet of vehicles 100.

[0059] Responsive to the desired operating parameter being a more efficient match of supply to demand of operation of the power generators 201, an optimization routine may include various operational changes. For example, an operational change of the generators 201 in the group 200 may include a calibration change in real time or substantially real time that avoids operating an extra genset for a period of time through a calibration change while allowing the currently operating gensets to meet the demand. Such an optimization routine may be based on a predicted load period, how close the current operating gensets are to meeting the predicted load, a genset owner entered criteria (e.g. based on the cost of the calibration increase, the maintenance interval resulting from the change [e.g. reduced spark plug gap maintenance time, reduced oil change interval, etc.]); etc.

[0060] Responsive to the desired operating parameter being an indication of an improvement in an aftertreatment system, the optimization routine may include various operating parameter adjustments and/or recommendations. For example and in regard to the group 200, an adjustment may include selecting which genset is running; changing an optimal load point considering the operational dynamics of aftertreatment system; and/or, dynamically altering a decision point for which genset and how many that are currently shut down and which generators of the group may regenerate at the current load level, etc. As another example, the optimization routine may include a recommendation output that indicates a selected prime mover load point to avoid undesirable operating conditions, such as wet stacking, DEF deposit buildup, unavailability of aftertreatment regeneration. The work balance across the network of prime movers may be shifted to avoid undesired operating conditions for those prime movers performing the work.

[0061] Thus, the optimization routine may take a wide variety of forms from recommendations (e.g., that are provided to a display device for selective implementation by an operator of the prime mover or a fleet manager) to an operating parameter adjustment (e.g., change this operating parameter setting of this prime mover within this group to level X). Further, the optimization routine may be highly variable based on the desired operating parameter, which controls selection of the cost index function. Of course, it should be understood that the aforementioned list is not meant to be limiting as the present disclosure contemplates a wide variety of additional and/or different other types of optimization routines that may be generated by the performance analytics circuit 456.

[0062] Furthermore and because each prime mover network 100, 200, and 300 refers to different prime movers, in certain embodiments where the controller 450 is specific to only a certain prime mover network, the structure and configuration and performance analytics circuit 456 may differ based on the prime mover network that the circuit 456 is utilized with. For example, because the vehicle 101 is not stationary while the generator 201 may be stationary, certain formulas, algorithms, and processes used to analyze various route data for the vehicle 101 may be excluded in the controller 450 used with the generator 201 prime mover network 200 (in the embodiment, where each group includes its own separate and dedicated controller). Beneficially, such a configuration enables the tailoring and customization of the controller 450 to each prime mover network. As a result, superfluous functionality may be excluded to maximize processing capability for the controller 450 for each application.

[0063] Responsive to the determination of the optimization routine, the control circuit 457 is structured to implement the optimization routine with the associated prime mover network. If the optimization routine is a recommendation (e.g., swapping components between prime movers, using alternate routes, etc.), the recommendation may be provided to one or more input/output devices associated the prime mover network. For example, the recommendation may be provided to a prime mover network's manager's input/output device (e.g., as an email, as a text message, as a phone call, as an audio/visual message, etc.). In another example, the recommendation may be provided to one or more individual operators associated with certain prime movers within the group. In this example, the recommendation may be tailored to the prime movers that are determined to have possible change(s) implemented therewith. This type of targeted messaging may decrease bandwidth requirements and facilitate relatively faster implementations of the routines.

[0064] In another embodiment, if the optimization routine represents various operating parameter adjustments, the control circuit 457 may be structured to provide the adjustments directly to the selected one or more prime movers for implementation. For example and in regard to the vehicles 101, the control circuit 457 may, via the communication circuit 453, provide the adjustments to the controller 140 for implementation with one or more selected vehicles 101. Beneficially, such adjustments facilitate remote modifications to achieve or substantially achieve the desired operating parameter. [0065] Based on the foregoing, various benefits including, but not limited to, improved or optimized operation of the group of prime movers as a whole may be achieved. Further, such benefits may be achieved from a remote location thereby alleviating the need for each member of the group to visit an analytics center, which may require substantial sums of time, energy, and costs. Additional specific benefits may include, but are not limited to, incremental cost savings over competitors; an improvement in fuel economy perception of a class of engines if the engines are a high fraction of a fleet (in terms of ton-miles per unit of fuel); a reduction in the usage of dedicated haulers; an improvement to the service life of an aftertreatment system component, a battery or electrical system component; etc.

[0066] Referring now to FIG. 3, a flow diagram of a method of providing and implementing an optimization routine with one or more prime movers in a group of prime movers is shown, according to an example embodiment. Because method 500 may be implemented with the controller 450 and in the system 10, reference may be made to one or more features of the controller 450 and the system 10 to explain method 500.

[0067] At process 501, data for a plurality of prime movers is received. If a group of prime movers is not previously identified, process 501 may further include identifying a group of prime movers based on the data. For example, the data may include certain bibliographic type data, such as engine make/model and the like, whereby the controller 450 may group similar make/model engines into a prime mover network. In another example, the data may include ownership or management information indicative of an owner or manager of various prime movers. Similar make/model prime movers that are managed or owned by similar owners or operators may be grouped into a prime mover network by the controller 450. Many different grouping mechanisms or functions may be used to identify and group prime movers.

[0068] At process 502, the received data is interpreted to determine one or more performance analytics. As mentioned above, various performance analytics data may include, but are not limited to: a performance value for vehicles in the group of vehicles - potentially current and potential performance where performance is flexible over a telematics-delivered recalibration (e.g. torque curve, fuel economy and emissions performance, state of the aftertreatment system, state of the electronic propulsion system, service information); determined vehicle-based information (gear ratios, driveline information, tires); load information (loads on-board and/or that need to be picked up with pickup and dropoff information, load requirements or costs (e.g. refrigeration settings, hazmat, permitting costs, etc.)); system constraints (times to destination, speed limits hi/low, required rest periods); and the like. Additional performance analytics may include, but are not limited to, various fleet-level information, such as an availability of re- calibration of an operating system of the prime mover, a driver identity, a re-stocking point(s), a service point(s), a fleet policy(ies) (e.g. maximum speeds, stop times, driver logs), etc.

[0069] At process 503, a cost index function is interpreted based on the determined performance analytics. Process 503 may include receiving an indication of a desired operating parameter for the group (e.g., minimize fuel economy, minimize emissions, etc.) based on the determined performance analytic. For example, a fleet manager may observe trend data that fuel emissions for the group are consistently above a certain threshold and, in response, desire to minimize total emissions for the group. In response, the cost index function may represent either i) an identification and selection of a prime mover within the group that is operating the "best" or substantially the "best" based on the desired operating parameter for the group (i.e., the prime mover(s) best achieving the desired operating parameter based on the received data), and/or ii) a selection and implementation of an algorithm, formula, process, and the like that may be implemented with the data to achieve or substantially achieve the desired operating parameter (e.g., an algorithm to minimize fuel consumption for the vehicles 101 based on one or more constraints, etc.).

[0070] At process 504, an optimization routine is determined based on the cost index function.

As mentioned above, the optimization routine may include at least one of recommendation and an operating parameter adjustment, whereby the recommendation is provided to an input/output device for acknowledgement and selective implementation and the operating parameter adjustment may be automatically selectively implemented with or without prime mover operator input. Optimization routines may include route-level optimizations (e.g., do vehicles have the correct loads, calibrations, drivers, aftertreatment components (if swappable), electronic components (if swappable), routing), service level optimizations (where and when should vehicles be serviced), and design level optimizations (permanent or semi-permanent calibration changes, changes in the gear ratios, changes in the driveline system, changes in the aftertreatment or electronic propulsion package of a more permanent nature than swapping components, and/or engine-level changes, including entire vehicle system swapouts and replacements). Route-level, service level, and design level optimizations may be run on the same or distinct time scales. For example, one system may run a route-level optimization daily, a service level optimization weekly, and a design level optimization monthly for a given fleet. In another example, a system may run a route-level optimization continuously (e.g. even checking routes and remaining service events as the vehicles are in service, especially in a telematics enabled fleet), a service level optimization daily, and a design level optimization for each vehicle when it reaches a service life value selected for that vehicle to see if it still belongs in an "optimal" configuration for that fleet. In one example, a system may have selectable menus where the fleet operator can configure how to run the various optimization levels for their fleet, and could, for example, run any optimization at any time.

[0071] At process 505, the optimization routine is at least one of provided to an input/output device or automatically or semi-automatically implemented with the group of prime movers. For example, certain optimization routines may require operator or fleet management adjustment, such as the swapping of components, such that these optimization routines are provided to an input/output device associated with the particular prime mover network. In another example, certain optimization routines may be implemented automatically or semi- automatically with one or more prime movers in the group of prime movers. For example, if an operating parameter adjustment is determined and such operating parameter adjustment does not require an affirmative action on behalf of an operator (e.g., restarting of the control system), this operating parameter may be provided by the controller 450 to the associated prime mover control system for automatic implementation. If however the adjusted operating parameter requires an operator input, the adjusted operated parameter may be provided to an input/output device of the prime mover in the form of a message: "at your convenience, please shut down your prime mover and re-start your prime mover in order to gain performance in accord with your fleet manager's desired operating parameter of minimizing fuel economy." In still certain embodiments, the optimization routine may be provided as a message in addition to an automatic implementation. All such variations are intended to fall within the scope of the present disclosure.

[0072] It should be understood that no claim element herein is to be construed under the provisions of 35 U.S.C. § 112(f), unless the element is expressly recited using the phrase "means for." The schematic flow chart diagrams and method schematic diagrams described above are generally set forth as logical flow chart diagrams. As such, the depicted order and labeled steps are indicative of representative embodiments. Other steps, orderings and methods may be conceived that are equivalent in function, logic, or effect to one or more steps, or portions thereof, of the methods illustrated in the schematic diagrams. Further, reference throughout this specification to "one embodiment", "an embodiment", "an example

embodiment", or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, appearances of the phrases "in one embodiment", "in an

embodiment", "in an example embodiment", and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment.

[0073] Additionally, the format and symbols employed are provided to explain the logical steps of the schematic diagrams and are understood not to limit the scope of the methods illustrated by the diagrams. Although various arrow types and line types may be employed in the schematic diagrams, they are understood not to limit the scope of the corresponding methods. Indeed, some arrows or other connectors may be used to indicate only the logical flow of a method. For instance, an arrow may indicate a waiting or monitoring period of unspecified duration between enumerated steps of a depicted method. Additionally, the order in which a particular method occurs may or may not strictly adhere to the order of the corresponding steps shown. It will also be noted that each block of the block diagrams and/or flowchart diagrams, and combinations of blocks in the block diagrams and/or flowchart diagrams, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and program code. [0074] Many of the functional units described in this specification have been labeled as circuits, in order to more particularly emphasize their implementation independence. For example, a circuit may be implemented as a hardware circuit comprising custom very-large- scale integration (VLSI) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A circuit may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.

[0075] As mentioned above, circuits may also be implemented in machine-readable medium for execution by various types of processors, such as the processor 451 of FIG. 2. An identified circuit of executable code may, for instance, comprise one or more physical or logical blocks of computer instructions, which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified circuit need not be physically located together, but may comprise disparate instructions stored in different locations which, when joined logically together, comprise the circuit and achieve the stated purpose for the circuit. Indeed, a circuit of computer readable program code may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices. Similarly, operational data may be identified and illustrated herein within circuits, and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different storage devices, and may exist, at least partially, merely as electronic signals on a system or network.

[0076] The computer readable medium (also referred to herein as machine-readable media or machine-readable content) may be a tangible computer readable storage medium storing the computer readable program code. The computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. As alluded to above, examples of the computer readable storage medium may include but are not limited to a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a portable compact disc read-only memory (CD-ROM), a digital versatile disc (DVD), an optical storage device, a magnetic storage device, a holographic storage medium, a micromechanical storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, and/or store computer readable program code for use by and/or in connection with an instruction execution system, apparatus, or device.

[0077] Computer readable program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages.

[0078] The program code may also be stored in a computer readable medium that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions which implement the function/act specified in the schematic flowchart diagrams and/or schematic block diagrams block or blocks.

[0079] Accordingly, the present disclosure may be embodied in other specific forms without departing from its spirit or essential characteristics. The described embodiments are to be considered in all respects only as illustrative and not restrictive. The scope of the disclosure is, therefore, indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.