Refuse vehicle QR code systems and methods

A refuse vehicle system includes a refuse vehicle, a tag, and a user device. The refuse vehicle includes a chassis and a body. The chassis includes a first subcomponent. The body includes a second subcomponent, supported by the chassis, and defines a receptacle. The tag is attached to at least one of the first subcomponent and the second subcomponent. The tag includes an identifier that encodes tag data. The user device includes a sensor configured to interface with the identifier and a user interface including a display. The tag data corresponds to at least one of the first subcomponent and the second subcomponent to which the tag is attached such that, in response to the sensor interfacing with the identifier, the user device is provided with material that is specific to the at least one of the first subcomponent and the second subcomponent to which the tag is attached.

BACKGROUND

The present disclosure relates generally to user safety and instructional information for equipment. More specifically, the present disclosure relates to tags for equipment that include safety and instructional information.

SUMMARY

One exemplary embodiment relates to a refuse vehicle system including a refuse vehicle, a tag, and a user device. The refuse vehicle includes a chassis and a body. The chassis includes a first subcomponent. The body includes a second subcomponent, supported by the chassis, and defining a receptacle for storing refuse therein. The tag is attached to at least one of the first subcomponent and the second subcomponent. The tag includes an identifier that encodes tag data. The user device includes a sensor configured to interface with the identifier of the tag and a user interface including a display. The tag data of the tag corresponds to at least one of the first subcomponent and the second subcomponent to which the tag is attached such that, in response to the sensor interfacing with the identifier, the user device is provided with material that is specific to the at least one of the first subcomponent and the second subcomponent to which the tag is attached.

Another exemplary embodiment relates to a method including receiving, by a processor, tag data from a tag located on at least one of a first subcomponent and a second subcomponent of a refuse vehicle. The method includes matching, by the processor, the tag with material from a tag database. The material relates to the at least one the first subcomponent and the second subcomponent of the refuse vehicle. The method includes providing, by the processor, the material to a user device. The method includes receiving, by the processor, user input. The method includes updating, by the processor, at least one of the tag database and a product performance database. The method includes transmitting, by the processor, a notice to a third-party computing system. The notice includes updates made to the tag database and the product performance database.

Another exemplary embodiment relates a non-transitory computer readable medium having computer-executable instructions embodied therein that, when executed by a processor of a data management controller, causes the data management controller to perform operations. The operations include tag data from a tag located on a component of a refuse vehicle. The operations include matching the tag with material from a tag database. The material relates to the component of the refuse vehicle. The operations include providing the material to a user device. The operations include receiving user input. The operations include updating the tag database and a product performance database. The operations include transmitting a notice to a third-party computing system. The notice includes updates made to the tag database and the product performance database.

DETAILED DESCRIPTION

Manufacturers and operators of equipment (e.g., vehicles, components of vehicles, tools, machinery, etc.) can employ the embodiments of the system disclosed herein to disperse or obtain material (e.g., instructional material, safety material, etc.) regarding such equipment to improve the safety and performance of the equipment operators. The information can include, but is not limited to, how to safely control, operate, install, repair, and maintain the equipment. For example, a vocational vehicle (e.g., refuse vehicle, mixer vehicle, etc.) can have an tag associated with a specific component (or subcomponent) of the vehicle. The tag can be coupled to the vehicle near or on the associated equipment and can be embedded with computer-readable instructions (e.g., quick response (QR) code, radio-frequency identification (RFID) tag, bar code, etc.). When those instructions are read by a device, the tags can provide the associated material to the operator of the device to help the operator perform an intended task. For example, if the operator needs to replace fluid lines of a hydraulic system of a refuse vehicle, the tag associated with the hydraulic system can automatically direct the operator, via the device, to material (e.g., diagrams, manuals, videos, instructions, etc.) related to the hydraulic system to aid the operator in replacing the fluid lines. One embodiment of the system is configured to monitor and collect data on what information is accessed, how often it is accessed, and who accesses it to determine product performance and material effectiveness. The system can also solicit feedback from those who use the system. This data can be provided to third parties (e.g., suppliers, manufacturers, dealers, etc.) to improve both the equipment and the material available via the tags. Among other benefits, the system simplifies operation of equipment and improves operator performance and safety.

According to an exemplary embodiment, as shown inFIG. 1, an instructional system100is configured to receive tag data from a tag located on equipment and to present material (e.g., videos, manuals, operator checks, telematics data, augmented reality, e-commerce data, etc.,) to an operator or another user based on the tag data. For example, the tag data of a tag corresponds to a subcomponent of a refuse vehicle to which the tag is attached such that, in response to a sensor interfacing with an identifier of the tag, a user device is provided with material that is specific to the subcomponent to which the tag is attached. Instructional system100includes a user device102and a data management controller104(e.g., system, control circuit, control module, etc.). The user device102is communicably coupled with the data management controller104via network106. The network106includes any form of wired and/or wireless communications exchange including, for example, a wireless gateway, the internet, or another short range or long range communications format. In other embodiments, the instructional system100includes additional, fewer, and/or different components.

The user device102of instructional system100can be any form of personal computing device such as a cell phone, a tablet, a laptop, or another type of portable computing device. As shown inFIG. 1, the user device102is configured to receive and interpret tag data from at least one tag108located on equipment and/or from a user110. The tag108is a physical tag or a descriptive label that is applied (e.g., affixed, coupled, connected, adhered, etc.) to any type of equipment including, but not limited to, vehicles, machines, tools, components, etc. The tag108may be applied to any type of vehicle, including on-road and off-road vehicles. The tag108may be applied to a commercial truck (e.g., a commercial long haul truck with a cargo carrier, a semi-truck, etc.), off-road construction equipment (e.g., a skid steer loader, a front-end loader, a wheel loader, etc.), an off-road vehicle that includes a cargo body (e.g., vehicles used to transport fill and rocks for mining or construction, etc.), a lift (e.g., a telehandler, a forklift, a boom lift, etc.), or another vehicle type. According to an exemplary embodiment, as shown inFIG. 3A, the vehicle is a refuse vehicle300that is used to transport material from various waste receptacles within a municipality to a storage and/or processing facility (e.g., a landfill, an incineration facility, a recycling facility, etc.). The tag108may also be applied to any type of equipment or component associated with those vehicles, or any other machinery that may require additional instruction to install, operate, fix, replace, etc. For example, a motor, whether or not a part of a larger system (e.g., a vehicle or a lawnmower) may have a tag108attached to it.

The user device102of instructional system100includes a sensor112, a user device network circuit114, a graphical user interface (GUI) circuit116, and an input/output (I/O) circuit118. The user device102is configured to receive and interpret tag data from a tag108located on equipment (e.g., vehicles, machinery, tools, components, etc.). The sensor112is configured to detect a tag108located on equipment and read the tag108. For example, detection includes seeing, or imaging, the tag (e.g., seeing the tag through a lens or scanner, image recognition, etc.), or sensing the tag due to proximity (e.g., being close enough to sense the electromagnetic fields of a radio frequency identification (RFID) tag). Reading the tag108may include any method of deciphering what the tag108corresponds to. For example, a tag108on the side of a truck located near a hydraulic system corresponds to material about how to operate the hydraulic system, including videos, how-to guides, manuals, etc. Instructional system100determines that specific tag108corresponds to those specific materials by the sensor112of the user device102detecting the tag108by imaging or sensing the tag108and deciphering what the tag108says. The information deciphered (e.g., tag data) is then be transmitted to the data management controller104via the user device network circuit114.

According to an exemplary embodiment, the user device network circuit114is configured to facilitate data transmission between the user device102and other systems capable of transmitting data (e.g., devices, entities, etc.). For example, the user device network circuit114transmits data between the user device102and the data management controller104via the network106. The user device network circuit114may also transmit data between the user device102and a third-party computing system (not shown) via the network106. In one embodiment, an input from a tag108is transmitted to the user device102via the user device network circuit114. Data that the user device network circuit114receives, is displayed on the user device102to the user110via the GUI circuit116. The GUI circuit116is configured to present, control, or otherwise manage displays on the user device102. The I/O circuit118facilitates data transfer between the user device102and the user110. The I/O circuit118enables the user110to respond to what is displayed by the user device102or prompt the user device102to display something by providing inputs, and the I/O circuit enables the user110to respond to those inputs and provide outputs to the user110.

According to an exemplary embodiment, as shown inFIG. 2, the sensor112of user device102includes a camera202and an illuminator204. The illuminator204may be any form of light source such as a light emitting diode. To detect and read a tag108, the illuminator204is positioned on the user device102to illuminate an area in the vicinity of the user device102, such as to allow the camera202to detect and read a tag108. For example, the illuminator204emits light onto a QR code so the camera202can detect and read it. The sensor112, in this example, is configured to detect the amount of reflected light from surfaces that are positioned in front of the illuminator204(e.g., the tag108). In other embodiments, the sensor112is another type of ambient light sensor, or a sensor that senses other environmental factors (e.g., electromagnetic fields).

In some embodiments, the sensor112of the user device102is configured to generate an analog signal in response to the intensity of the reflected light from the illuminator204, or in response to sensing other environmental factors. In other embodiments, the user device102includes an analog-to-digital converter to convert the analog signal generated by the sensor112to a digital signal. In further embodiments, the user device102also includes a decoder to interpret the digital signal. For example, the user device includes a decoder to decipher tag data that is associated with an identifier of the tag108(e.g., the tag data associated with the QR code on the tag108). In other embodiments, the user device102includes another type of code detection/identification and decoding device.

According to an exemplary embodiment, user device102, as shown inFIG. 2, includes a user interface206and at least one interactive point208. The GUI circuit116of the user device102configures the user interface206to display outputs and receive inputs. For example, the user interface206is configured to receive commands from a user110such as an operator of the equipment (e.g., a vehicle operator or technician). The user interface206may include one or more controls, displays, speakers, lights, or other computer user interfaces for conveying and receiving information. According to another exemplary embodiment, the user interface206includes a touch-screen display210(e.g., a liquid crystal display (LCD), etc.) for presenting the material to the user110and receiving user inputs. In other embodiments, the user interface can include other types of displays. The user device102includes at least one interactive point208. In one embodiment, the interactive point208is integrated into the touch-screen display210. In other embodiments, the interactive point208is a physical switch, toggle, dial, or other form of actuator to receive user inputs. The user device102may further include a communications interface (e.g., a transceiver), a memory, and/or a processor to facilitate device operations, for example, similar to the data management controller104, as will be described in more detail below.

According to an exemplary embodiment, as shown inFIG. 1, the data management controller104is communicably coupled with the user device102via network106and is configured to exchange data with the user device102. The data management controller104may also communicably coupled with other third-party computer systems (not shown). In particular, the data management controller104is configured to receive the tag data of the tag108from the user device102and to provide material to the user device102based on the tag data. The tag data identifies material associated with the tag108. According to an exemplary embodiment, the data management controller104is a server that is hosted by a supplier and/or manufacturer of the equipment with the tag108(e.g., the refuse vehicle300ofFIG. 3A, the mixer vehicle350ofFIG. 3B). In other embodiments, the data management controller104is a vehicle controller (e.g., a controller associated with the vehicle including material associated with any or all subcomponents of the vehicle), or another type of third-party hosted portal. The material provided to the user device102can come directly from the data management controller104, or the data management controller can redirect the user110of the user device102to a web service link (e.g., a website) that includes the material associated with the tag data.

According to an exemplary embodiment, the data management controller104of the instructional system100includes a processor120and a memory122. The processor120is configured to process, analyze, or otherwise manage data transmitted to the data management controller. For example, if data from a tag108is received from the user device102via the network106, the processor120determines which material in the memory122matches the tag108. The processor also provides the material matching the tag108to the user110of the user device102via the network106. The memory122is configured to store information regarding equipment and the corresponding tags108. The memory122includes a controller circuit124, a tag database126, and a product performance database128. The tag database126stores and manages materials (e.g., videos, user manuals, repair instructions, operator checks, telematics data, e-commerce information, etc.) corresponding to respective tags108. In other embodiments, the tag database126stores information regarding where to find the material and/or how to access the material (e.g., links to websites, etc.), if the material is not stored directly by the tag database126. The tags108may be of different types, may include different text/images, and may be in different locations along the equipment. In some embodiments, the material is subdivided into different applications, where each application is associated with a particular type of tag.

According to an exemplary embodiment, the material includes videos that provide additional information to a user110regarding the operation of one or more vehicle components or subsystems (e.g., safety videos that inform the user of unsafe practices that may result in injury or death). Additionally, the material may also include training information relating to component functionality (e.g., how to operate different vehicle components), best practices, and helpful tips. The material may also provide information regarding vehicle setup before use, or in preparation for maintenance. The material may also provide step-by-step instructions for how to install and remove components such as tooling for the hydraulic system of refuse vehicle300, and other components. The material may also provide step-by-step instructions for testing the various vehicle components such as the hydraulic system for example, during maintenance events. The material may also provide helpful tips such as information relating to the position and operation of emergency-stop switches, oil level and temperature check positions/recommendations, and other vehicle operating information. The material may be organized within the tag database126based on the tag data (e.g., different web addresses/URLs for different material, etc.) or as part of a library that also contains material for other types of tags108. For example, refuse vehicle300may have a tag108for the hydraulic system and another tag108for a lift. Each tag108may have unique tag data. The material associated with the tag data may be organized within the tag database126so that when the lift tag is detected and read, all the material associated with the lift may be easily accessed.

The tag database126of the memory122also includes requests based on user inputs. In an example embodiment, the user device102detects and reads a tag108and the user110receives, via the user device102, the associated material. If the material provided is not helpful, is out-of-date (i.e., stale), or is wrong, or the user110was looking for information that was not included in the material, the user110can submit a request to have the targeted material added, updated, or removed from the tag database126. The tag database126is updated and stores the request. Responsive to the tag database updating to include the request, the data management controller104transmits a notice, by the processor120, to an appropriate third-party computing system (e.g., the supplier or manufacturer of the equipment) requesting updated material in accordance with the request.

The product performance database128of the memory122includes data relating to the performance of equipment (e.g., how long vehicle components and/or subsystems may last before needing repair or replacement). According to an exemplary embodiment, the product performance database128includes product performance indicators (e.g., metrics, indices, etc.) to quantify how well a component of equipment is performing (e.g., operating, etc.). In one embodiment, the product performance indicators are counters that record the number of times a video or other instructional information is accessed for a particular tag type based on the tag data received from multiple users of certain equipment (e.g., for different vehicles and from different vehicle operators, a fleet of vehicles, etc.). In other embodiments, the indicator is a component-specific performance metric that may be obtained from the tag database.

In another exemplary embodiment, the product performance database128also includes product performance data that is determined based on user inputs. In an example embodiment, the material forms a part of an application, and providing the material includes providing the application to the user device102. The application solicits, by the data management controller104via the processor120, feedback from the user110. The feedback is solicited, for example, through a pre-populated questionnaire that is stored in memory122(e.g., the product performance database128), and that is distributed by the data management controller104to the user device102based, in part, on the tag data. The feedback is indicative of product performance. The feedback may include, for example, quality of the equipment, ease of repairing and/or replacing components, additional information that would be helpful to an operator or manufacturer, etc. Responsive to receipt of the feedback, the processor120updates the product performance database128. Responsive to updating the product performance database128, a notice is transmitted to an appropriate third-party computing system (e.g., supplier or manufacturer of the equipment associated with the tag108) indicating the feedback received from the user110. The notice includes the product performance indicator.

According to an exemplary embodiment, memory122includes a non-transitory computer-readable medium configured to store computer-readable instructions for the data management controller104that, when executed by the processor120, causes the data management controller104to provide a variety of functionalities as described herein. For example, the memory122includes a controller circuit124configured to coordinate the exchange of information between the tag database126, the product performance database128, and the user device(s)102, as will be described with reference toFIGS. 8-9.

According to an exemplary embodiment, the processor120is operatively coupled with each of the components of the data management controller104, and is configured to control interaction between the components. For example, the processor120is configured to control the collection, processing, and transmission of tag data from a tag108located on equipment and user inputs from the user device102. Additionally, the processor120is configured to interpret operating instructions from memory122(e.g., the controller circuit124), to provide material to the user110based on the tag data.

The arrangement of the instructional system100described with reference toFIG. 1should not be considered limiting. It will be appreciated that many alterations and combinations are possible without departing from the inventive concepts disclosed herein. For example, in some embodiments, the functionality provided by the data management controller104may be at least partially integrated into the user device102. In particular, the functionality may be provided via an application installed on the user device102directly without interaction with the data management controller104.

According to an exemplary embodiment, as shown inFIG. 3A, the refuse vehicle300includes a chassis302(e.g., frame, etc.) supporting a plurality of tractive elements, wheels304, and a body306. The chassis302includes at least one subcomponent. The body306also includes at least one subcomponent. For example, the body306includes a cabin308disposed toward a front end of the chassis302and a cargo body310disposed toward a rear end of the chassis302behind the cabin308. The refuse vehicle300also includes a prime mover or engine312coupled with the chassis302. The engine312may be configured to provide power to the wheels304, and/or to other systems of the refuse vehicle300(e.g., a pneumatic system, a hydraulic system, etc.). The engine312may be configured to utilize one or more of a variety of fuels (e.g., gasoline, diesel, bio-diesel, ethanol, natural gas, etc.), or utilize energy from an external power source (e.g., overhead power lines, etc.) and to provide the power to the systems of the refuse vehicle300. The refuse vehicle300also includes a transmission configured to transmit energy from the engine to the wheels304. The refuse vehicle300may also include a suspension system, fuel storage system, steering system, brake system and/or other systems to facilitate transport operations for the refuse vehicle300.

According to an exemplary embodiment, the refuse vehicle300includes various application-specific components (e.g., working components, subcomponents, etc.) configured to facilitate loading, storage, and unloading of refuse (e.g., garbage, trash, etc.). Among these are the cargo body310, which defines a receptacle314(e.g., refuse container, etc.) that is configured to receive refuse and store refuse during transit operations. The refuse vehicle300also includes various application-specific components that are movable relative to the cargo body310and/or chassis302, and are configured to facilitate working operations for the refuse vehicle300(e.g., refuse loading operations, refuse compaction operations, refuse unloading operations, etc.). For example, the refuse vehicle300may include a lift system301configured to selectively engage a waste container, the lift system301being movable to reposition the refuse container so as to discharge the contents of the refuse container into the receptacle314. The lift system301may include lift arms used to eject waste/garbage from a temporary holding container into the receptacle314, a hydraulic cylinder to actuate the lift arms, a compactor (e.g., packer, etc.) to compress the refuse within the receptacle314, an ejector to discharge the refuse from the receptacle314(e.g., to unload the refuse), a repositionable tail gate door or receptacle access door, and/or other moving components. The application-specific components may also include components that are stationary relative to the chassis302such as motors and/or pumps used to power and/or control a hydraulic system for the refuse vehicle300.

As shown inFIG. 3A, the refuse vehicle300includes tags108positioned in different areas along the chassis302and body306. The tags108can be attached to the subcomponents of the chassis and the body306. The tags108are often positioned in a highly visible area along the refuse vehicle300, in line-of-sight of the operator such as on exterior panels of the body306. The tags108may be safety tags that provide warning information to an operator and/or alert the operator to particularly hazardous areas around the refuse vehicle300. In one embodiment, the tags108may warn the operator of areas where the lift arms, or other repositionable components (e.g., the application-specific components) seat against other parts of the body306. For example, the tag108may be applied to the refuse vehicle300at a location that is vertically above the lift and/or grabber arm (e.g., tag130) to alert an operator to stand clear of this area when the vehicle is running. Another tag (e.g., tag132) may be positioned near at least one component of the hydraulic system (e.g., a hydraulic fluid manifold, fluid lines, hydraulic fluid tank, etc.) to notify the operator of the risk of injury due to leaking high pressure fluid. In another embodiment, the tags108may provide instructional information to the operator. For example, the tags108may remind the operator to use proper tools when servicing the hydraulic system and/or instruct the operator regarding how to activate/deactivate various application-specific components using levers, control buttons, and/or other vehicle controls. The tags108may also notify the operator about proper fluid levels, temperatures, and other operating conditions to reduce the risk of damage to the vehicle components or subsystems.

As shown inFIG. 3B, a mixer vehicle350(e.g., mixer truck, cement mixer, etc.) is configured as a concrete mixing and delivery vehicle. The mixer vehicle350is configured to transport a cement mixture (e.g., aggregate such as sand or gravel, water, and/or other adhesive compounds) from a quarry or cement production facility to various locations for distribution (e.g., a residence, a commercial property, a construction site, etc.). Similar to the refuse vehicle300ofFIG. 3A, the mixer vehicle350ofFIG. 3Bincludes a chassis352(e.g., frame, etc.) supporting a plurality of tractive elements, shown as wheels354and a body356. As shown inFIG. 3B, the body356includes a cabin358disposed toward a front end of the chassis352and a mixing drum360disposed toward a rear end of the chassis352behind the cabin358. The mixer vehicle350also includes a prime mover or engine coupled to the chassis352, which may be the same or similar to the engine312described with reference toFIG. 3A.

According to an exemplary embodiment, the mixer vehicle350includes various application-specific components (e.g., working components, etc.) configured to facilitate loading, transportation, and delivery of cement. Among these are the mixing drum360, which is moveable relative to the chassis (e.g., rotates relative to the chassis) to mix and/or agitate the cement stored therein and to thereby substantially prevent the cement from hardening while the mixer vehicle350is transporting the cement to the working site. The mixer vehicle350may also include various other application-specific components including, but not limited to, a hydraulic pump and/or motor to rotate the mixing drum360, hydraulic actuators to reposition a delivery chute for the mixer vehicle350, and hydraulic and/or pneumatic actuators to reposition a tag axle of the mixer vehicle350. The mixer vehicle350ofFIG. 3Bincludes tags134and136positioned in different areas along the chassis352and body356. The tags134and136may be safety tags that provide warning information to an operator and/or alert the operator to particularly hazardous areas around the mixer vehicle350. The tags134and136may be the same as or similar to the tags108described with reference toFIG. 3A. In other embodiments, the tags108may be different (e.g., specific to the mixer vehicle350and associated with operations that are exclusive to mixer vehicles350). In the exemplary embodiment ofFIG. 3B, the tag (e.g., tag134) is applied to fluid storage tanks along the mixer vehicle350and provide information regarding the proper fluid levels. Additionally, the mixer vehicle350has at least one tag (e.g., tag136) positioned near a component of the hydraulic system to warn the operator of hazardous conditions to watch out for (e.g., fluid leaks, etc.).

According to an exemplary embodiment, as shown inFIGS. 4-6, tags108, shown as first tag400, second tag500, and third tag600, for the equipment (e.g., refuse vehicle300ofFIG. 3A, mixer vehicle350ofFIG. 3B, among other equipment) are shown, according to various exemplary embodiments. As shown inFIG. 4, first tag400includes an operator facing side402and a backing (not shown) opposite the operator facing side402. The first tag400may be a sticker-type label in which an adhesive layer (e.g., glue, etc.) is applied to the backing. In this way, the first tag400may be applied directly to a surface of the equipment. In other embodiments, the first tag400may be, for example, a thin plate that is riveted to a vehicle panel, may be etched into and/or printed on the equipment (e.g., on chassis302or body306), or may be attached to the equipment by any other means (e.g., magnetically, hung by a hook or string, etc.).

As shown inFIG. 4, the operator facing side402includes information including a descriptive label containing text404and a machine-readable portion, shown as identifier406. According to an exemplary embodiment, the identifier406is a QR code. In other embodiments, the identifier406is another machine-readable optical label such as a one dimensional barcode (e.g., UPC) or two dimensional matrix barcode (e.g., DataMatrix, Grid Matrix, etc.). In other embodiments, the code is be a machine sensible label such as an RFID tag, rather than machine-readable optical label. According to an exemplary embodiment, the identifier406includes tag data (e.g., tracker, etc.), which is used by the user device102and/or data management controller104to identify the tag108(e.g., the tag type, position, what component it is attached to, etc.) and to access the materials associated with the first tag400, as will be further described. The tag data may be encoded in the identifier406. For example, with respect to the QR code shown inFIG. 4, the tag data is decoded from the patterns that are present in both the horizontal and vertical components (e.g., patterns, blocks, etc.) of the image.

The arrangements and designs of the first tag400, second tag500(FIG. 5) and third tag600(FIG. 6) are shown for illustrative purposes only. It will be appreciated that many alternatives and combinations are possible without departing from the inventive concepts disclosed herein. For example, the position of the identifier406relative to the text404may be different in various exemplary embodiments. Additionally, in some embodiments, the tag may only include the identifier406without the text404. In other embodiments, the tags may include multiple identifiers406of the same and/or different type.

According to an exemplary embodiment, as shown inFIG. 7, user interface206includes a display including data corresponding to a tag108. Responsive to a user device102detecting an tag108and generating a signal, either the user device102or the data management controller104decodes the signal, and the data management controller104via the processor120matches the tag data from the tag108with the material in the memory122of the data management controller104. For example, the tag132on the refuse vehicle300is be sensed by the sensor112of the user device102. The tag data is transmitted over the network106via the user device network circuit114to the data management controller104. The processor120decodes the tag data and determines that it corresponds to at least one component of the hydraulic system of refuse vehicle300. For example, tag132may correspond to only one of the fluid lines, the hydraulic fluid manifold, and the hydraulic fluid tank, or tag132may correspond to any combination thereof. The data management controller104transmits data from the memory122, via the processor120, to the user device102to be displayed by the user interface206. The data may include, for example, material, product performance data, and the like. The user interface206generated may be web-based (i.e. a website, etc.) or an application. According to an exemplary embodiment, the user interface206includes a header702and a content area704. The header702contains any information related to identifying the equipment to which the sensed tag108corresponds. For example, the user interface206for tag132includes an image of the identifier of the tag132and a description of the corresponding equipment (e.g., Hydraulic System). Any information deciphered from tag132is included in the header702(e.g., owner of equipment, purchase date of equipment, installation date of equipment, etc.). The content area704includes substantive material706, at least one interactive point708, or a combination thereof. Substantive material706may include any information relating to the equipment the tag108corresponds to (e.g., a diagram showing how a system works, a list of steps to install the equipment, pictures of the components of the equipment, etc.). The interactive point708may be any element that can take input from the user110(e.g., a field for text, selectable buttons, etc.).

The content displayed in the content area704of the user interface206depend, in part, on what information is stored in the memory122of the data management controller104. For example, if the only information stored in the memory122associated with tag132is a diagram of how the hydraulic system works (e.g., substantive material706), then the user interface206may show only the diagram. Alternatively, if the memory122contains videos of installation, how-to manuals for using each component, performance data for each component, among other information, the data management controller104may organize the information into categories and generate a user interface206displaying a plurality of interactive points708corresponding to those categories. According to an exemplary embodiment, user interface206displays three interactive points708, including an Operation button708, a Troubleshoot button708, and a Performance Data button708. Selection of any button708by the user110causes the data management controller104to generate a new user interface with the associated information. For example, selection of the Operation button, causes a user interface to be displayed providing various material relating to the operation of the equipment (e.g., installation video, user manual, instructions for cleaning a system, how to diagram for repairing/replacing components, etc.). Selection of the Troubleshoot button causes a user interface to be displayed providing various material relating to fixing problems associated with the equipment (e.g., list of components to check, diagram for how to take a system apart, list of common issues, etc.). Selection of the Performance Data button causes a user interface to display previous performance data for the equipment, or an option to submit notes or reports regarding the current performance of the equipment. Any information provided via the user interface206of the user device102may be in any format including, but not limited to, videos, documents, recordings, diagrams, pictures, and lists. The information is provided to the user110directly from the memory122of the data management controller104or the data management system may direct the user110to a third-party source via a third-party computing system (e.g., data management controller104may provide the user110a link to take the user110to a third-party website with related equipment information).

According to an exemplary embodiment, as shown inFIG. 8, method800provides operators and/or manufacturers of equipment material associated with a corresponding tag108. The method800may be implemented using the instructional system100ofFIG. 1. As such, reference will be made to instructional system100ofFIG. 1when describing method800. The method800may be implemented using the user device102, for example, through an application installed on the user device102. In another embodiment, the method800may include additional, fewer, and/or different operations.

According to an exemplary embodiment, at operation802, the instructional system100(e.g., data management controller104) receives tag data from a tag108. The identifier of the tag108may be in any form, including but not limited to, QR codes, bar codes, RFID tags, and the like. Operation802may further include interpreting the tag data. In one embodiment, operation802includes the processor120of the data management controller104receiving the tag data from a tag108from the user device102. For example, if the identifier is in the form of a QR code, the user device102can use the camera202of the sensor112to detect and read the QR code. Alternatively, if the identifier is in the form of an RFID tag, the sensor112of user device102can be a sensor that can detect electromagnetic fields (e.g., RFID reader device, etc.).

According to an exemplary embodiment, as shown inFIG. 9, method900obtains tag data from a tag. At operation902, the user device102detects a tag108on equipment. Operation902may include positioning the user device102near the tag108, such that the sensor and illuminator of the user device102are facing the identifier406(e.g., QR code) of the tag. The user device102can be positioned such that the sensor is in alignment with the identifier of the tag. In another embodiment, the user device102only needs to be close enough to the tag108to sense certain environmental factors (e.g., electromagnetic fields) in order to detect the tag108. For example, when close enough to a tag108with an RFID tag, the sensor112of the user device102may be a device that senses electromagnetic fields transmitted by the RFID tag.

According to an exemplary embodiment, at operation904, the user device102reads the tag108to generate a signal at operation906. Operation904, according to one embodiment, includes illuminating the identifier of the tag using the illuminator204and activating the sensor112to detect the light reflected off the tag using the camera202. Additionally, operation904may include holding the sensor112(e.g., camera202) over the tag for a predefined period of time (e.g., allowing the camera202to dwell over the tag) so that an accurate reading of the identifier may be performed. In an example embodiment, the tag108includes a QR code and reading the tag108may include imaging the QR code.

Operations906and908of method900may be performed by either the user device102or the data management controller104. According to an example embodiment, at operation906the user device102and/or the data management controller104generates an analog signal based on the reading of the tag108(e.g., the amount of light reflected off of the identifier or the electromagnetic fields). In some embodiments, operation906includes transmitting the analog signal (e.g., via a user device network circuit114over network106) to the data management controller104. In other embodiments, the tag data obtained from reading the tag108is transmitted to the data management controller104prior to generating a signal. In that case, the processor120of the data management controller104generates the signal.

According to an example embodiment, at operation908, the user device102and/or data management controller104decodes the signal to determine the tag data. Operation908may include converting the analog signal to a digital signal using an analog-to-digital converter. Operation908may further include interpreting the digital signal, for example, using a decoder. The decoder may convert the digital signal to alphanumeric characters such as a hyperlink that may be used to direct the user device102to the material that is associated with the tag108. In other embodiments, operation908includes interpreting the digital signal to obtain identifying information for the product that the tag108is affixed to (e.g., the type of product, etc.). Operation908is performed by the user device102or by the processor120of the data management controller104depending on when data is transmitted from the user device102to the data management controller104.

According to an exemplary embodiment, returning toFIG. 8, method800includes operation804, matching the tag108with material from the tag database126. The matching is based on the tag data from operation908. In one embodiment, operation804includes the processor accessing the tag database126via the controller circuit124to identify the material that is associated with the tag108. According to an exemplary embodiment, operation804includes entering a web address/URL into an internet browser installed on the user device102. The web address is associated with the material for the tag108. In other embodiments, the material matching the tag108forms a part of an application. The material includes a single format of material (e.g., only videos) or multiple formats of material (e.g., videos, manuals, recordings, diagrams, etc., and combinations thereof) that may be presented to the user110to improve operator safety and/or facilitate training regarding equipment operation. In some embodiments, the material also includes links to additional training and/or diagnostic tools (e.g., links to relevant pages of a user/service manual, links to a customer support contact, etc.).

According to an exemplary embodiment, at operation806, the material is provided to the user device102. The material is provided to the user device102via an internet browser installed on the user device102or via an application generated and/or transmitted from the data management controller104to the user device102. Operation806may include generating the application and/or transmitting the application from the data management controller104to the user device102via network106.

According to an exemplary embodiment, the method800also includes continuously monitoring the performance of equipment based on the tag data by storing performance data and providing the performance data to a third party (e.g., supplier, manufacturer, distributor, dealership, etc.). At operation808, the processor120of the data management controller104receives user input from the user110. Operation808includes soliciting user feedback through the internet browser (e.g., supplier web portal) or the application on the user device102. For example, operation808may include presenting the user110with a questionnaire, which may be part of the material or included as a separate module. In some embodiments, the questionnaire may have questions relating to the step-by-step training operation being demonstrated in the material (e.g., “have you placed a drain pan underneath the test port on the hydraulic valve bank?,” “would you like more information regarding this step?,” etc.). The questionnaire may ask the user110to rate the helpfulness of material, or may request that the user specify the particular reasons for accessing the video. Additionally, the questionnaire may include questions related to the type of equipment (e.g., product model number, serial number, etc.) and/or the performance of the equipment (e.g., what are the symptoms of the problem, etc.).

At operation810, the data management controller104updates the tag database126and/or the product performance database128based on the tag data and/or the user input. Operation810may include updating a counter to record/track a number of times that an operator accesses data associated with a certain type of tag108(e.g., increasing the counter by an integer value each time the tag data is received by the data management controller104via the processor120). Additionally, operation810may include compiling user inputs (e.g., from the questionnaire, etc.), which may provide information regarding the effectiveness of the tag108and/or the material that is associated with the tag108. In some embodiments, operation810also includes using the user inputs to help identify the reason why a particular issue is occurring (e.g., if the issue is associated with user error, or as diagnostic information to help a manufacturer determine the root cause of a recurring problem across multiple vehicles of the same type, etc.). In other embodiments, operation810also includes compiling requests from users110to update the information stored in the tag database.

According to an exemplary embodiment, operation812includes transmitting a notice to a third-party computing system (e.g., a remote server hosted by the manufacturer). Operation812include transmitting the product performance indicator, the tag database update request, or other tag data to the supplier of the equipment (e.g., for a vehicle, a dealership, distributor, manufacturer, etc.) or another third-party for further review and analysis. The notice discloses any update made to the databases. In some embodiments, operation812includes transmitting the product performance indicator, tag database request, and the other tag data directly from the user device102to a third-party computing system. In other embodiments, operation812includes transmitting the notice to a customer service representative assigned to the equipment. In some embodiments, method800includes making a recommendation or request for parts and/or service based on the indicator. For example, the method800may include receiving an indicator that relates to a service and/or maintenance operation (e.g., changing oil of a vehicle). The method800may include automatically generating a purchase order and/or service appointment in response to the indicator.

It is important to note that the construction and arrangement of the instructional system as shown in the various exemplary embodiments is illustrative only. Additionally, any element disclosed in one embodiment may be incorporated or utilized with any other embodiment disclosed herein. Although only one example of an element from one embodiment that may be incorporated or utilized in another embodiment has been described above, it should be appreciated that other elements of the various embodiments may be incorporated or utilized with any of the other embodiments disclosed herein.