Waste management system having service confirmation

A system is disclosed for managing waste services performed by a service vehicle. The system may have at least one sensor disposed onboard the service vehicle and configured to generate a first signal indicative of a waste service being completed by the service vehicle. The system may also have a computing device in communication with the at least one sensor. The computing device may be configured to determine, based on the second signal, that the waste service has been performed. The computing device may also be configured to selectively generate an electronic response based on performance of the waste service.

TECHNICAL FIELD

The present disclosure relates generally to a management system and, more particularly, to a waste management system having service confirmation.

BACKGROUND

Commercial and residential waste service providers typically dispatch service vehicles to customer properties according to a predetermined pickup schedule assigned to each vehicle. The pickup schedule for each service vehicle is often designed to provide waste services within a particular geographical area and at a particular frequency (e.g., once per week). After completion of the waste services, the vehicle operator may report the completion to a back office, which updates the operator's schedule and an account record for the customer. Customers that subscribe to these waste services are then billed based on the account record.

In some instances, it may be difficult to confirm that the scheduled pick was completed and/or completed in a manner desired by the customer (e.g., on a desired day, at a desired time, etc.). In particular, the only method used to verify the completion is self-reporting of the vehicle operator, who may make a mistake in performing the pickup service or otherwise introduced errors in reporting of the service. In addition, no automated mechanism currently exists to provide remedial action for a waste service that cannot be completed in the manner desired by the customer.

The disclosed system is directed to overcoming one or more of the problems set forth above and/or other problems of the prior art.

SUMMARY

In one aspect, the present disclosure is directed to a system for managing waste services performed by a service vehicle. The system may include at least one sensor disposed onboard the service vehicle that is configured to generate a second signal indicative of a waste service being completed by the service vehicle. The system may further include a computing device in communication with the at least one sensor. The computing device may be configured to determine, based on the first signal, that the waste service has been performed. The computing device may also be configured to selectively generate an electronic response based on performance of the waste service.

In another aspect, the present disclosure is directed to a method for managing waste services performed by a service vehicle. The method may include generating a first signal indicative of a waste service being completed by the service vehicle. The method may also include determining, based on the first signal, that the waste service has been performed. The method may further include selectively generating an electronic response based on performance of the waste service.

In yet another aspect, the present disclosure is directed to a non-transitory computer readable medium containing computer-executable programming instructions for performing a method of waste management by a service vehicle. The method may include generating a first signal indicative of a location of the service vehicle, and determining that the service vehicle has stopped based on the first signal. The method may also include generating a second signal only when the service vehicle is determined to be stopped, the second signal being one of a force signal, a motion signal, and an acoustic signal. The method may further include determining that the waste service has been performed at a target location based on the first signal and based on a comparison of the second signal with known data corresponding to expected waste services normally performed by a service vehicle. The method may additionally include selectively generating an electronic response based on performance of the waste service, making a determination that the service vehicle cannot complete a waste service at one of a plurality known customer locations based on the first signal, and selectively adjusting a schedule of stops for the service vehicle based on the determination.

DETAILED DESCRIPTION

FIG. 1illustrates an exemplary waste management environment (“environment”)10, at which one or more service vehicles12are providing waste services. Environment10may include a retail store, a factory, a government building, a residential address, or another location having one or more receptacles14that require the service of service vehicle(s)12. The service may include, for example, the removal of waste materials from inside of receptacle(s)14, the replacement of receptacle(s)14, and/or the placement of new or additional receptacles14.

Service vehicle12may take many different forms. In the example shown on the right inFIG. 1, service vehicle12is a hydraulically actuated, front-loading type of service vehicle. Specifically, service vehicle12may include a bed16supported by a plurality of wheels18, a cab20located forward of bed16, and a lifting device22extending forward of cab20. Lifting device22may consist of, among other things, one or more lift arms24configured to engage and/or grasp receptacle14, and one or more actuators26powered by pressurized oil to raise and tilt lift arms24(and receptacle14) up past cab20to a dump location over bed16. After dumping of receptacle14, pressurized oil may be released from hydraulic actuator(s)26to allow lowering of lift arms24and receptacle14back to the ground in front of service vehicle12.

In other examples, lifting device22may be located to pick up receptacles14from a side and/or a rear of service vehicle12. In yet other examples, receptacles14may be manually lifted and dumped into bed16. In any of these examples, bed16could be outfitted with a compactor (not shown) to compact the waste material after the material is dumped into bed16, and/or a door (not shown) configured to close an opening of bed16through which the waste material is dumped. Other configurations may also be possible.

In the example shown on the left inFIG. 1, service vehicle12is a hydraulically actuated flatbed or roll-off type of service vehicle. Specifically, service vehicle12may include a bed16supported by a plurality of wheels18, a cab20located forward of bed16, and a lifting device22extending rearward of cab20. Lifting device22may consist of, among other things, one or more actuators26powered by pressurized oil to raise and tilt receptacle14up onto bed16for transportation of receptacle14away from environment10. After dumping of receptacle14at a landfill (or swapping a full receptacle14for an empty receptacle14), receptacle14may be returned to environment10and lowered back to the ground behind service vehicle12(e.g, by releasing pressurized oil from hydraulic actuator(s)26).

As each service vehicle12moves about environment10, a satellite28or other tracking device may communicate with an onboard controller30(shown only inFIG. 2) to monitor the movements of service vehicle12and the associated changes made to environment10(e.g., pickup, dumping, placement, etc.). As will be explained in more detail below, onboard controller30, or a separate offboard controller32(e.g., a controller32located in a back office34or other service facility—shown only inFIG. 2), may then manage future operations of service vehicle12(and other similar service vehicles12) based on these movements and changes.

Both of onboard and offboard controllers30,32may include means for monitoring, recording, storing, indexing, processing, communicating, and/or controlling other onboard and/or offboard devices. These means may include, for example, a memory, one or more data storage devices, a central processing unit, or any other components that may be used to run the disclosed application. Furthermore, although aspects of the present disclosure may be described generally as being stored in memory, one skilled in the art will appreciate that these aspects can be stored on or read from different types of computer program products or computer-readable media such as computer chips and secondary storage devices, including hard disks, floppy disks, optical media, CD-ROM, or other forms of RAM or ROM.

As shown inFIG. 2, onboard controller30may form a portion of a waste management system (“system”)36that is configured to track, assist, and/or control movements of service vehicle(s)12(shown only inFIG. 1). In addition to onboard controller30, system36may also include a locating device38, and at least one of a manual input device40and a sensor42mounted or otherwise located onboard each service vehicle12. In some embodiments, system36includes both manual input device40and one or more sensors42. In other embodiments, sensor42(and/or onboard controller30) may be internal to manual input device40. Onboard controller30may be in communication with each of these other components and/or with offboard controller32at back office34(e.g., via a communication device44), and configured to determine, based on signals from these components and based on other known information stored in memory, the location of each service vehicle12and characteristics and locations of receptacles14being moved by and/or in a vicinity of each service vehicle12.

Locating device38may be configured to generate signals indicative of a geographical position and/or orientation of service vehicle12relative to a local reference point, a coordinate system associated with environment10, a coordinate system associated with Earth, or any other type of 2-D or 3-D coordinate system. For example, locating device38may embody an electronic receiver configured to communicate with satellites28(referring toFIG. 1), or a local radio or laser transmitting system used to determine a relative geographical location of itself. Locating device38may receive and analyze high-frequency, low-power radio or laser signals from multiple locations to triangulate a relative 3-D geographical position and orientation. In some embodiments, locating device38may also be configured to determine a location and/or orientation of a particular part of service vehicle12, for example of lift arms24(shown only inFIG. 1). Based on the signals generated by locating device38and based on known kinematics of service vehicle12, onboard controller30may be able to determine in real time, the position, heading, travel speed, acceleration, and orientation of service vehicle12and lift arms24. This information may then be used by onboard and/or offboard controllers30,32to update the locations and conditions of service vehicle(s)12and/or receptacles14in an electronic map or database of environment10.

It is contemplated that locating device38may take another form, if desired. For example, locating device38could be an RFID reader configured to interact with an RFID tag located within environment10(e.g., at a customer location, on receptacle14, etc.), or another type of scanner configured to read another type of indicia (e.g., a barcode) within environment10. Based on the reading of the RFID tag or other indicia, the location and/or orientation of service vehicle12may be linked to the known location of the RFID tag or other indicia within environment10.

Manual input device40may provide a way for an operator of service vehicle12to input information regarding observances made while traveling around environment10. For example, the operator may be able to enter a type and/or condition of waste observed at a particular location, an amount of waste in or around receptacle14, a fill status of a particular receptacle14, a condition of receptacle14, a location of receptacle14, and or other information about the receptacle and waste engaged by, loaded into, or otherwise processed by service vehicle12. The information may be input in any number of ways, for example via a cab-mounted touch screen interface, via one or more buttons, via a keyboard, via speech recognition, via a mobile device (e.g., a smartphone or tablet) carried by the operator, or in another manner known in the art. In some embodiments, the operator may also be able to respond to inquiries received via input device40, if desired. In addition to receiving manual input from an operator, input device40may also be capable of displaying information, for example the electronic map of environment10, instructions from back office34, scheduling, receptacle information (e.g., ID, configuration, location, weight, etc.), payload information (e.g., weight and/or volume), questions, etc.

In some embodiments, input device40may be configured to execute an application. For example, when input device40is a mobile device (for example a smartphone), the application can be a mobile app (“app”). The app can provide a graphical user interface (GUI) that displays information about a waste handling operation to an operator of service vehicle12; and that receives input from the operator used to configure acquisition of operational data by sensor(s)42, to transmit the operational data to controllers30,32, to receive and display information about a current operation (e.g., as monitored by sensor(s)42), etc.

Sensors42may be any type of sensing and/or transducing device configured to monitor parameters associated with the waste material loaded into service vehicle12and/or the associated receptacles14being moved by service vehicle12(e.g., moved by lift arms24), and to generate corresponding signals indicative thereof. Each of these sensors42may be any type of device known in the art, and located anywhere on or in service vehicle12. In one example, sensor42may embody a lift sensor, such as any one or more of a load cell, a force gauge, a pressure sensor, a motion sensor, or another type of lift sensor associated directly with lift arms24, with actuator(s)26, with receptacle14, and/or with a strut46supporting bed16. In this example, the signals generated by sensor(s)42may correspond with strain on lift arms24, with a force applied to lift arms24by actuator(s)26, with a payload weight of bed16, with a motion of receptacle14, with a weight of waste contained inside receptacle14, etc.

Alternatively, one or more sensors42may be associated with a power source or drivetrain of service vehicle12, and configured to generate signals indicative of an amount of power used to propel service vehicle12, to drive the hydraulics of actuators26, to move the in-bed compactor, or to shut the associated door. Other types of sensors42(e.g., optical sensors such as cameras, spectrometers, IR sensors, RADAR sensors, LIDAR sensors, etc.) may also be utilized to determine characteristics (e.g., load profile, volume, and/or shape) of the waste material inside receptacles14or of receptacles14themselves. In yet further examples, sensor42could be an acoustic sensor (e.g., one or more microphones), an accelerometer, or another similar type of sensor configured to detect engagement conditions and/or cycle completion of lift arms24, the in-bed compactor, the door, etc. during lifting, dumping, and/or shaking of receptacle14. Other types of sensors42(e.g., proximity sensors) may alternatively or additionally be utilized. Signals generated by these sensors42may be communicated to onboard and/or offboard controllers30,32, and the appropriate controller may use the signals to determine conditions surrounding receptacles14(and/or the waste inside receptacles14) before, during, and/or after servicing by service vehicle12. As described above, any one or more of sensors(s)42may form an integral portion of input device40(e.g., the smartphone or tablet carried by the operator) or be a standalone component in wired or wireless communication with controllers30,32and/or input device40, as desired.

Onboard controller30may be configured to manage communications between other onboard components and offboard controller32located at back office34. For example, onboard controller30may receive signals from locating device38, input device(s)40, and sensor(s)42, and correlate the signals, filter the signals, buffer the signals, record the signals, or otherwise condition the signals before directing the signals offboard via communication device44.

Communication device44may be configured to facilitate communication between onboard controller30and offboard controller32. Communication device44may include hardware and/or software that enable the sending and/or receiving of data messages through a communications link. The communications link may include satellite, cellular, infrared, radio, and any other type of wireless communications. Alternatively, the communications link may include electrical, optical, or any other type of wired communications, if desired. In one embodiment, onboard controller30may be omitted, and offboard controller32may communicate directly with locating device38, input device(s)40, and/or sensor(s)42via communication device44, if desired. Other means of communication may also be possible.

Onboard and/or offboard controllers30,32, based on the information received from onboard service vehicles12and also based on information received from other sources (e.g., from the Internet, from input at back office34, etc.), can be configured to execute instructions stored on computer readable medium to perform methods of waste management at environment10. For example, onboard and/or offboard controllers30,32may be configured to monitor when service vehicle12is nearing a target location (e.g., based on the known address and signals from locating device38), when service vehicle12has stopped, when service vehicle12is servicing receptacle14, when service vehicle12is filled with waste to a maximum capacity, etc. This monitoring may then be used to determine route assignments for service vehicle12, determine business costs and efficiencies, determine service opportunities, make route adjustments, etc. An exemplary process is illustrated inFIG. 3, and will be explained in more detail in the following section to further illustrate the disclosed concepts.

FIGS. 4-12represent exemplary Graphical User Interfaces (GUIs) that may be shown on any input device40or otherwise used to access system36.FIGS. 4-12will also be discussed in greater detail below to further illustrate the disclosed concepts.

INDUSTRIAL APPLICABILITY

The disclosed system may be applicable to the waste service industry, where service monitoring can affect profitability and efficiency. The disclosed system may be able to automatically monitor movement of a service vehicle12and detect completion of an assigned waste service in a manner desired by a customer. In addition, the disclosed system may be able to determine when the assigned waste service cannot be completed in the manner desired by the customer, and to selectively implement a remedial action. Operation of system36will now be described with reference toFIG. 3.

As shown inFIG. 3, operation of system36may begin with receipt of service related information (Step300). This information may be received by any one or more of the computing devices of system36(e.g., onboard controller30, offboard controller32, and/or manual input device40) and include, among other things, existing contracts for service, adjustments to the existing contracts, and new contracts. The contracts may detail locations at which a particular customer desires waste services to be performed, a timing (e.g., date, day, time, and/or frequency) of the services, and details about the service (e.g., a number, configuration, and/or size of receptacles14at the customer location that require service; a type of waste; and/or instructions regarding access to receptacles14). In addition, the service-related information obtained at step300may include details about service vehicles12that are available to perform the services. These details may include a number, type, size, location, capacity, and availability of service vehicles12. The contract and/or service vehicle information may be received directly from the customer(s), from representatives of the service provider of system36, from contracted service providers, from the operator of service vehicle12, and/or from an electronic data storage, memory, or database of system36.

Based on the service-related information received at step300, different routes of service stops may be determined and assigned to different available service vehicles12(Step305). The assignments may be determined and/or assigned manually (e.g., by a manager at back office34) or automatically (e.g., by offboard controller32), and communicated to the operator of each service vehicle12by way of communication device44. The route assignments may be determined based on a comparison of service needs with available service resources. For example, any one or more of the corresponding computing device(s) of system36(e.g., onboard controller30, offboard controllers32, and/or input device40) may marry the details of a specific customer location; service time; and receptacle size, configuration, and weight with an appropriately sized and configured service vehicle12available within the general area at the desired time of service. The stops within each assignment may be sequentially arranged into a route according to any strategy known in the art. For example, the stops may be arranged according to geographical location, distances between locations, expected amounts of waste to be picked up at each location, urgency, waste type, desired service times, traffic conditions, anticipated vehicular speeds, etc. The routes may then be stored, for example, within onboard controller30and/or any one of input devices40.

The operator may follow the assigned route and perform waste services at each customer location in the route in the sequential order provided. In particular, a target location of a next customer in the route may be automatically determined for the operator (Step310). The target location determination may be made, for example, by any computing device(s) of system36based on a correlation between a current time and a time listed for a next scheduled service stop. Alternatively, the service vehicle operator could manually select a target location from a list of locations on the assigned route, if desired. For example, the operator could override input device40and choose a target location that is not listed as the next location in the provided sequence. Alternatively or additionally, back office34may override input device40and inform the operator (e.g., via a dispatch call) of a target location that is not listed as the next location in the provided sequence. Once the target location is relayed to, and/or selected by, the operator of a particular service vehicle12, subsequent travel of service vehicle12toward the target may be monitored. In particular, the current location and speed of service vehicle12may be tracked, for example by way of locating device38(Step315).

Based on the monitored travel of service vehicle12(e.g., a monitored location and/or speed) and a scheduled time of the next service to be completed at a target location in the route assigned to service vehicle12, then the computing device(s) of system36may be configured to determine if service vehicle12is capable of completing the next scheduled waste service (Step320). For example, if it is determined that service vehicle12is within a threshold distance and/or anticipated travel time of the next target location, the computing device(s) may determine that the service is possible at the desired time. Otherwise, the computing device(s) may determine that it is not possible to complete the scheduled service within the desired time.

In one embodiment, the computing device(s) may be configured to continually determine and/or adjust the distance threshold and/or anticipated travel time used in the comparison of step320, in order to reduce the likelihood of making a premature determination regarding service vehicle12being capable of timely completing the assigned waste service at the target location. For example, the distance threshold can be continually adjusted based on the changing location and speed of service vehicle12, and can be progressively reduced as service vehicle12approaches the target location. On the other hand, the distance threshold and/or anticipated travel time can also be progressively increased (or remain unchanged), when service vehicle12is determined to be moving away from the target location. In some cases, in addition to the travel direction affecting the radius threshold and/or time used for comparison purposes in step320, other factors, such as a deviation between an actual trajectory and a scheduled trajectory, actual traffic conditions and expected traffic conditions, etc., can also have an effect.

When it is determined that a particular service vehicle12will be unable to perform an assigned waste service at a scheduled time (step320:N), the computing device(s) of system36may be configured to determine if another service vehicle12may be able to assume the scheduled waste service at the target location in the route of the particular service vehicle12(Step325). For example, the computing device(s) may determine if the other service vehicle12has a correct configuration (e.g., a configuration and/or remaining fill capacity required to service the particular receptacles14at the target location), if the other service vehicle12has enough time within its assigned schedule, and/or if the other service vehicle12is within the distance threshold and/or travel time of the target location to take over the scheduled service from the particular service vehicle12. When this is true (step325:Y), control may return to step304where the target location will be transferred from the assigned route of the particular service vehicle12to the assigned route of the other service vehicle12.

In some instances, the other service vehicle12may not have the right configuration and/or be immediately available to introduce an additional service stop into its existing route of assigned stops. For example, the other service vehicle12may be too full and/or not in the general vicinity of the additional service stop and/or not have enough time between already scheduled stops for insertion of the additional stop. In these instances, the computing device(s) of system36may determine if the target location that the particular service vehicle12is not capable of timely servicing should be rescheduled or if a particular service vehicle12should continue travel toward the target location and still complete the assigned waste service (Step330), even though the service will be late. In some situations, keeping the target location in the existing schedule, even though the particular service vehicle12will be late in performing the service, may cause all remaining service stops in the assigned route to also be late. When this is unacceptable, control may return to step305where the corresponding service stop will be reassigned to another day, another time, and/or another service vehicle12. A status update regarding this reassignment may be recorded in the corresponding customer's account and/or communicated to the customer, as desired. When continuing to the particular target location and performing the waste service in a delayed manner is acceptable and/or will not cause the remaining service stops in the route of service vehicle12to also be delayed, control may instead proceed to a step335.

At step335, after determining that service vehicle12will be able to provide the assigned waste service (on time or late), any one or more of the computing devices of system36may determine (e.g., based on the monitored travel speed and/or changing location) if service vehicle12has stopped (e.g., not moved more than about ten meters) for at least a minimum amount of time (Step335). Many different strategies may be used to determine if service vehicle12has stopped. In one example, the location signal alone may be used to make this determination, for example based on a change in location being less than a threshold amount (e.g., less than about 10 miles), within a predetermined period of time. Alternatively, a tracked speed being less than a threshold speed may be used to determine stopping of service vehicle12. In another embodiment, a change in payload (e.g., weight and/or volume), as indicated via signals from sensors(s)42may indicate that service vehicle12is likely to be stopped and/or performing a service. Stopping may also be determined in other ways, if desired. As long as it is determined that service vehicle12is still traveling (step335:N), control may loop back through step315.

The computing device(s) of system36may require service vehicle12to be stopped for at least the minimum amount of time, in some applications, to help filter out inconsequential stops, such as stops at traffic lights, stops caused by congestion or road work, etc. In one embodiment, the minimum amount of time is about 15-30 seconds. It should be noted, however that other minimum amounts of times may be used, as desired.

Other filters may additionally or alternatively be used to help filter out inconsequential stops during travel toward a target location, in some applications. In particular, the traveled distance and/or speed may be used in conjunction with the location of service vehicle12to determine if the stop of service vehicle12is consequential. For example, when service vehicle12is determined to no longer be moving, but also located at a traffic light, on the freeway, at a road work location, etc., the stop may be determined to be part of normal travel toward the target location. As long as it is determined that service vehicle12is still traveling toward its target location (step315:N), control may loop back through step310.

When it is determined that service vehicle12has made a consequential stop or is otherwise no longer following a travel path toward its target location (step335:Y), data collection may be initiated (Step340). The data collection may include, among other things, the collection of signals generated by sensor(s)42. For example, a force, strain, motion, and/or sound associated with movement of lift arms24, the in-bed compactor, the bed door, etc. may be captured. By collecting this data only when it is determined that service vehicle12has stopped for at least the minimum amount of time, an amount of collected data and a corresponding size of memory required to hold and/or process the data may be reduced. In addition to collecting data following completion of step335, a current location of service vehicle12may be compared to the target location of the next stop to determine if the current stop coincides with the target location (Step345). It should be noted that, although step345is shown inFIG. 3as occurring after step340, step345could alternatively occur before or at the same time as step340, as desired.

It is contemplated that additional and/or other ways could be used to determine that service vehicle12has arrived at the target location, if desired. In particular, the data collected by sensor(s)42could be used to confirm the arrival, if desired. For example, a bar code affixed to a particular receptacle14at the customer location could be scanned and compared to an expected bar code. In another example, an image of the location and/or receptacle14could be captured and compared with one or more images stored in memory. In yet another example, the operator of service vehicle12could push a button, check a box, or otherwise electronically confirm arrival at the target location. Other methods may also be implemented.

When the stop of service vehicle12detected at step335is determined at step345to have occurred at the target location of the next customer in the assigned route of service vehicle12, the computing device(s) of system36may determine if a waste service has been performed at that stop (Step350). The waste service may include, among other things, the emptying of receptacle14into bed16at the target location. The determination of whether the waste service has been performed may be made based on the data collected at step340. In particular, if the collected data corresponds with forces, strains, motions, weight changes, volume changes, and/or sounds normally experienced by service vehicle12during performance of typical waste services, it can be concluded that a waste service has been performed. Values of the forces, strains, motions, weights, volumes, and/or sounds normally experienced by service vehicle12during performance of the typical waste services may be stored in the memory of the computing device(s) of system36for comparison purposes.

In the disclosed example, sensor42is an acoustic sensor configured to capture vibrations associated with the emptying of receptacle14. The relevant captured vibrations could be associated, for example, with any one or more of the activation of actuators26(referring toFIG. 1), the lifting movement of arms24, the shaking of receptacle14, the banging of a receptacle lid or bed door, the movement of the in-bed compactor, the falling of waste from receptacle14into bed16, etc. Specifically, a sound profile (e.g., a frequency signature) consisting of sequences or patterns of vibrations having particular amplitudes, frequencies, and/or spacing may be captured and then compared to data stored in memory. The stored sound profiles may be unique to each service vehicle12, to a type of service vehicle12, to a size of service vehicle12, to a configuration of service vehicle12, to a particular receptacle14, to a type of receptacle14, to a size of receptacle14, etc. As an illustrative example, it can be pre-determined that when actuators26of lift arms24of a certain front-loading type of service vehicle12are activated, the acoustic signals produced by sensor42will include a frequency component within the range of 6,000-7,000 Hz. Accordingly, when a frequency component within this range is detected at step350, the corresponding waste service may be confirmed by the computing device(s) of system36. In some embodiments, the frequency of the signals generated by sensor42may first be filtered and/or processed (e.g., via Fourier Fast Transform) before comparison with the stored sound profiles, if desired. It is contemplated that the vibrational data collected via sensor42could be used in another way to determine that a particular service has been performed by service vehicle12.

When it is determined at step350that a waste service has been performed at the target location (step350:Y), information associated with the stop and the service may be logged into system36(Step355). As is known in the art, the logged information may then be used to bill the customer, pay the service provider, adjust future service routes, etc.

After the completion of each waste service, the computing device(s) of system36may determine if service vehicle12is within a threshold amount (e.g., within 10%) of being filled to capacity (Step360). This determination may be made in any number of ways. For example, based on a current weight of waste material inside bed16, as measured by sensor(s)42, and based on a maximum allowed weight stored in memory, the computing device(s) may be able to calculate if the current weight is within the threshold amount. Alternatively, a tare weight of each receptacle14may be determined each time receptacle14is emptied into bed16. A running total of the tare weights may then be compared to the maximum allowed weight to determine if service vehicle12is filled to within the threshold amount. In yet another embodiment, captured images of the profile of waste inside bed16may be compared to profiles of bed16filled with a maximum amount of material to make the determination of step360. Other ways may also be utilized.

When it is determined that service vehicle12is filled to within the threshold amount of its capacity, the computing device(s) may set a landfill location as the next target location (Step365) in the route of scheduled stops for service vehicle12. It is contemplated that a landfill stop may already be scheduled within the route of service vehicle12, at a point where service vehicle12is predicted to be filled or nearly filled to capacity. In some embodiments, the actual fill rate may substantially match the predicted fill rate, and service vehicle12may be directed to the landfill at the time already scheduled within its route. In other instances, however, service vehicle12may fill at a faster or slower rate. In these instances, the landfill stop may need to be moved up or back in the lineup of other scheduled stops based on the determination made in step365. Accordingly, control may proceed from step360through step365to step315or from step360to step310, depending on the actual fill rate of service vehicle12. When the landfill stop needs to be moved up or back in the lineup of other stops, the other stops may be rescheduled to accommodate the change. When rescheduling occurs, the account records of the customer may need to be adjusted and/or the customer may need to be alerted based on the rescheduling. It should be noted that, when the next target location is the landfill stop, the determination made at step350may be associated with unloading of service vehicle12rather than with emptying of receptacle14into bed16.

In some embodiments, unloading of service vehicle12at the landfill may include emptying of bed16. Thereafter, service vehicle12may continue to a next target location corresponding with another customer and emptying of another receptacle14into bed16. In other embodiments, however, service vehicle12may carry receptacle14from the customer location to the landfill for emptying of receptacle14. In these embodiments, the empty receptacle14may need to be returned to the same customer location, before a different customer location can be serviced. Accordingly, in some instances, the next target location, after leaving the landfill stop, may be a return to the previous target location. It is contemplated that the schedule of assigned routes may account for both embodiments. Additionally or alternatively, the operator of service vehicle12may be able to indicate the need for return to the same customer location for deposition of the emptied receptacle14, and the need may be accommodated by the computing device(s) of system36with a schedule adjustment, as desired.

Returning to step350, when it is determined that a waste service has not yet been performed (step350:N), a time elapsed since service vehicle12stopped may be determined and compared to a threshold time (Step370). As long as the elapsed time is less than the threshold time (step370:N), control loop back through step315. The threshold time used at step370may be an amount of time expected to elapse during a normal service event at the given location. In some embodiments, the threshold time may also include a buffer that accounts for minor unexpected delays or efficiency differences between operators and/or service vehicles12. When it is determined at step370that the elapsed time exceeds the threshold time (step370:Y), any number of responses may be automatically implemented (Step375). For example, a fault may be electronically logged into system36in association with the particular service vehicle12, with the particular operator, with the particular location, etc.; the operator may be provided with an electronic notice (e.g., via input device40) and/or a request for input explaining the delay; back office34may be electronically notified; the customer may be notified; etc. In one instance, in addition to the notice being provided to the operator of service vehicle12, the operator may also be provided with selectable options to explain the delay such as, “report an incident”, “equipment malfunction”, “request help”, “provide instructions”, “stopped for fuel”, “on break”, etc.

Based on the feedback received from the operator at step375, steps may be taken to ensure that the waste service is still performed at the corresponding customer location. This may include, for example, assigning the task to another service vehicle12(i.e., control may loop back to step305). Alternatively, assistance (e.g., a repair technician, a tow truck, additional manpower, etc.) may be directed to the customer location in an attempt to facilitate completion of the assigned waste service by the service vehicle12already at the location. For instance, service vehicle12may have broken down or receptacle14may be oriented such that service vehicle12cannot properly lift and dump receptacle14. In this situation, the dispatched repair technician or additional manpower may be able to remedy the breakdown or move receptacle14to a better position for lifting.

Returning to step345, when it is determined that the stop detected at step355does not coincide with the target location of the next customer in the assigned route, control may proceed to a step380that is substantially identical to step350described above. That is, a determination may be made regarding performance of a waste service at the stop location, even though the stop location does not correspond with a subscribing customer. When it is determined that a waste service was made at the stop location (e.g., based on the data collected at step340), the computing device(s) of system36may electronically log a fault and store corresponding information associated with the stop and the service performed while at the stop (Step385). Control may then return to step315, allowing the operator of service vehicle12to continue the assigned route and travel to the target location of the next scheduled customer. In some embodiments, the computing device(s) of system36may additionally adjust the schedule of the remaining customers in the assigned route based on delays caused by the unscheduled stop, if desired. In yet other embodiments, the computing device(s) can also be configured to automatically assign one or more of any remaining waste-service tasks and/or scheduled stops to another service vehicle12and operator (e.g., based on the other service vehicle's progress of a different assigned route), such that the delay caused by the unscheduled stop and service does not continue to impact the rest of the day's scheduled services.

At step380, when it is determined that a waste service has not yet been performed at the non-customer location (e.g., based on the data captured at step340), a time elapsed since the stop of service vehicle12may be determined and compared to a threshold time (Step390). As long as the elapsed time is less than the threshold time (step390:N), control may return to step315. The threshold time used at step390may be the same or a different amount of time used at step370, as desired. In some embodiments, the threshold time used at step390may be an amount of time normally required to perform a standard waste service that is less than an amount of time associated with other expected delays (e.g., a time for the operator to obtain and consume lunch) that are sometimes encountered during completion of the assigned route. When it is determined at step390that the elapsed time is greater than the threshold time (step390:Y), it can be concluded that the unscheduled stop is not associated with a service activity and the captured data may be discarded (Step395). Control may then return from step395to step315.

FIGS. 4 and 5show exemplary GUIs400and500, respectively, that may be used to facilitate the process that is described above and shown inFIG. 3. GUIs400and500(as well as the other GUIs ofFIGS. 6-12) may be shown on any onboard input device40(referring toFIG. 2) and, as can be seen inFIGS. 4 and 5, may correspond with steps305-315in the flowchart ofFIG. 3. In particular, via GUIs400and500, the operator of service vehicle12may be provided with visual representations of a unique route assigned to service vehicle12. The representations may include a listing of scheduled stops, along with an indication of which stops have been completed and a target location for a next stop. In addition, a map may be provided showing the stop locations, along with a representation of a current location of service vehicle12. Addresses and/or turn-by-turn directions may be provided, along with service instructions for each location. In some embodiments, the operator may be able to provide input during travel to and/or service at each location in the assignment. For example, the operator may be able to manually indicate arrival at a location and/or completion of the assigned service. In addition, in some embodiments, the operator may be able to select a particular location shown on GUI400, and receive additional information about the selection via GUI500. For example, the map may zoom in to the selected location, and directions specific to that location may be shown. It is contemplated that the zoomed-in view and/or details from GUI500could be automatically shown to the operator based on a proximity to the target location, if desired.

FIGS. 6-8show exemplary GUIs600,700, and800that may also be used to facilitate the process ofFIG. 3. Specifically, GUIs600-800may correspond with steps340-355and375in the flowchart ofFIG. 3, and provide an operator with information regarding a service performed at a customer location. The service information may include, for example, an identification of a receptacle14to be serviced, and/or a weight of the waste dumped from receptacle14into bed16of service vehicle12. In some embodiments, GUI600may provide the operator with the receptacle identification information. In other embodiments, however, GUI600may provide the opportunity to detect and/or capture (e.g., via still image) the receptacle identification information. GUI700may provide the option for the operator to adjust the displayed information and/or to provide a reason for delayed servicing. For example, the operator may be able to update a record, overwrite a pickup weight or volume, and/or report a problem. Via GUI800, the operator may then be able to provide details regarding any problem experienced when attempting to service receptacle14. Exemplary problems reportable via GUI800may include, among others, that receptacle14cannot be found, that receptacle14is inaccessible, or that other problems have occurred. It is contemplated that the details from GUIs600-800could be automatically shown and/or made available to the operator based on a detected arrival at the target location, if desired.

FIG. 9illustrates an exemplary GUI900that may be shown in connection with completion of step305and/or steps360and365. Specifically, when a route assignment is made consisting of multiple different service stops, information about each stop and/or just a next stop may be relayed to the operator. For example, the information may instruct the operator to empty the receptacle14found at the customer site into bed16and/or to pick up receptacle14and carry it to a landfill. After emptying of the carried receptacle14to the landfill, the instructions may indicate that the emptied receptacle14should be returned to its original location. The operator may indicate understanding of the instructions by depressing a button indicating readiness to initiate operation. Additionally or alternatively, when it is determined at steps360and365that a target location of a next scheduled stop should be a landfill, the operator may then be instructed what services are required during and/or after the landfill visit.

During completion of steps315-350, following completion of step365(i.e., during travel toward the landfill as the next target location), GUI1000shown inFIG. 10may be presented to the operator. GUI1000may illustrate a map and/or navigation information for assisting the operator to drive service vehicle12to a particular landfill (Landfill A). It is contemplated that GUI1000may be automatically displayed based on the current weight in service vehicle12, based on completion of a previous waste service known to supersede travel to the landfill, or based on the detected approach of service vehicle12to the landfill; or based on manual input, as desired. Upon arriving at Landfill A and performing its assigned waste service (i.e., after dumping the contents of bed16), GUI1100ofFIG. 11may be displayed. GUI1100may provide an indication of the weight of the waste contents disposed at Landfill A, and a way for the operator to update a status of the waste service. GUI1100may be similar to GUI700, and allow the operator to also overwrite the weight of the deposited waste and/or to report a problem (e.g., via GUI800).

A final GUI1200is illustrated inFIG. 12and associated with detection of an unscheduled stop, as described in reference to steps380-390described above. Specifically, after detection of an unscheduled stop and/or of performance of a waste service at the unscheduled stop, GUI1200may appear on input device40. GUI1200may include in a background the map and/or directions to the next scheduled stop in the assigned route. In addition, GUI1200may include in a foreground a pop-up window notifying the operator that the unscheduled stop has been detected and asking the operator to confirm that service is being performed at the unscheduled stop. This may alert the operator in some instances of an error made by the operator in stopping and/or providing service at the current location.

The interfaces illustrated inFIGS. 4-12are exemplary only and are provided to highlight certain aspects of the disclosed system. Other views and functionality are contemplated, as would be understood by one of skill in the art. It will be apparent to those skilled in the art that various modifications and variations can be made to the disclosed system. Other embodiments will be apparent to those skilled in the art from consideration of the specification and practice of the disclosed system. It is intended that the specification and examples be considered as exemplary only, with a true scope being indicated by the following claims and their equivalents.

The disclosed system may provide tools that can be used to confirm performance of waste services and/or to account for waste services that cannot be performed. By detecting when a waste service has occurred and whether the service has been provided in accordance with the assigned schedule, the disclosed system may allow for efficient management of associated duties (e.g., billing, scheduling, payments, etc.). In addition, the disclosed system, based on confirmation that a particular waste service cannot be performed, may be able to selectively implement a remedial action that ensure customer satisfaction. All of these things may ultimately result in greater profitability for the service provider.