Monitoring of logistics vehicles
By using a material handling vehicle feature monitoring system to monitor and manage the use of technical features in real time, the problem of untrained or misused operators is solved, vehicle efficiency and lifespan are improved, and proper use and maintenance are ensured.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- CROWN EQUIP CORP
- Filing Date
- 2021-05-28
- Publication Date
- 2026-05-26
Smart Images

Figure CN115605891B_ABST
Abstract
Description
Technical Field
[0001] Various aspects of this disclosure generally relate to the use of technical features on material handling vehicles, and more specifically to the monitoring, management, control, modification, and combinations thereof of material handling vehicles, technical features on material handling vehicles, and the working environment supporting such technical features. Background Technology
[0002] Material handling vehicles are commonly used for picking in warehouses and distribution centers. These vehicles typically include a power unit and load-carrying components, which may include load-bearing forks. The vehicles also have control structures for controlling their operation and movement. Furthermore, various enterprises are deploying wireless strategies to improve operational efficiency and accuracy.
[0003] For example, in a typical warehouse implementation, forklifts are equipped with communication devices that link the corresponding forklift operator to a management system running on an associated computer enterprise via a wireless transceiver. Essentially, the communication devices are used as an interface to the management system to guide the forklift operator's tasks, for example, by instructing the forklift operator where and / or how to pick, pack, store, move, segment, handle, or otherwise manipulate items within the facility. Summary of the Invention
[0004] According to various aspects of this disclosure, a process for implementing a technical monitor for material handling vehicles is provided. The method includes wirelessly receiving electronic vehicle records from a fleet of material handling vehicles. Each electronic vehicle record includes technical feature data recorded by a controller on the associated material handling vehicle. Typically, electronic vehicle records are generated in response to the operation of a corresponding technical feature on the material handling vehicle in the working environment; however, other triggers may cause the generation of electronic vehicle records. Furthermore, each electronic vehicle record may include an operator identifier of the operator of the material handling vehicle at the time the technical feature data was recorded. The process also includes generating an electronic measurement for each operator based on a comparison of expected technical feature usage (e.g., a threshold) with the technical feature data received in the electronic vehicle records associated with the corresponding operator. The process further includes outputting a graphical representation of the generated measurement to a dashboard.
[0005] According to a further aspect of this disclosure, a process for implementing a technical monitor for material handling vehicles is provided. The process includes wirelessly receiving electronic vehicle records from a fleet of material handling vehicles. Each electronic vehicle record includes technical feature data recorded by a controller on the associated material handling vehicle, for example, in response to a corresponding technical feature being operated on the material handling vehicle. Each electronic record may include an operator identifier of the operator of the material handling vehicle at the time the technical feature data was recorded. The process also includes generating electronic measurements for each operator based on a comparison of expected technical feature usage data with the electronic vehicle records associated with the operator. Furthermore, the process includes outputting a graphical representation of the generated measurements to a dashboard. In some embodiments, the process further includes determining whether there is a detectable equipment problem based on the measurements generated from rule analysis extracted from a rule engine, which could adversely affect the comparison for at least one operator. Further, the process includes automatically generating electronic signals to resolve the detected equipment problem.
[0006] According to various aspects of this disclosure, a process is provided for implementing a feature monitor for material handling vehicles. The process includes wirelessly receiving electronic vehicle records from a fleet of material handling vehicles. In this regard, each electronic vehicle record includes driving-related data recorded by a controller on the associated material handling vehicle environment, and an operator identifier for the corresponding operator of the material handling vehicle. The process also includes parsing the vehicle records for each vehicle operator to extract dashboard data. Here, the dashboard data may include the distance traveled by the material handling vehicle, for example, the total distance traveled by the material handling vehicle within a predetermined time period in response to the corresponding operator using remote driving functionality within that time period. The process also includes establishing an expected distance traveled under remote control relative to the total distance traveled within the predetermined time period. Furthermore, compared to the remotely controlled distance recorded relative to the total distance traveled within the predetermined time period, the process includes generating an electronic measurement of the expected remotely controlled distance for each operator relative to the total distance traveled within the predetermined time period, and outputting a graphical representation of the generated measurement to the dashboard.
[0007] According to another aspect of this disclosure, a material handling vehicle is provided, suitable for use with a material handling vehicle feature monitor. The material handling vehicle includes a power unit having a traction motor controller coupled to a traction motor driving at least one steering wheel of the material handling vehicle. The material handling vehicle also includes technical features, such as a remote control receiver paired with a wireless remote control device. The material handling vehicle also includes a transceiver for wireless communication with a remote server computer. Furthermore, the material handling vehicle includes a controller found on industrial vehicles, coupled to a memory.
[0008] In an example embodiment, the controller executes program code stored in memory to receive commands from a remote control receiver to perform functions in response to the remote control receiver communicating with a paired remote control device, and transmits the commands to the traction motor controller to cause the material handling vehicle to move automatically in response to the commands, thereby achieving remote-controlled driving functionality. The controller also executes program code to generate vehicle records, which include data related to the material handling vehicle's movement associated with the remote-controlled driving functionality, and transmits the generated vehicle records to a remote server via an information link device to record the use of the remote-controlled driving functionality.
[0009] In some embodiments, feedback and control are performed in response to monitoring feature usage to modify the corresponding material handling vehicle. Modifications may be initiated by a remote server or by a processor on the material handling vehicle itself. As a non-limiting example, compared to the distance traveled under remote control relative to the total distance traveled over a predetermined time period, the remote server may analyze electronic measurements of the expected distance traveled under remote control relative to the total distance traveled over a predetermined time period, and in response, for example, by adjusting technical features or operating parameters of the material handling vehicle itself, initiate modifications to the material handling vehicle. As another non-limiting but illustrative example, the processor on the material handling vehicle may monitor the usage of features (e.g., remotely controlled driving function features). For example, by querying task information, if the next picking operation is too far from the current location of the material handling vehicle, the processor may reject the remote start / remote drive command. Similarly, if the next picking operation is too close to the current location of the material handling vehicle, the processor may reject the remote start / remote drive command. Other examples are provided, as described in more detail herein. Attached Figure Description
[0010] Figure 1 This is a schematic diagram of the operating environment for material handling vehicles;
[0011] Figure 2 It is a side view of a material handling vehicle with the technical features to enable remote control of its driving function;
[0012] Figure 3 This is a schematic diagram of several electrical components of a material handling vehicle that supports one or more technical features;
[0013] Figure 4 It is a block diagram of a system for monitoring and controlling usage and usage trend technical characteristics;
[0014] Figure 5 This is the process used to implement a feature monitor for material handling vehicles;
[0015] Figure 6This is a schematic diagram of a display that can be installed on a material handling vehicle, in which a graphical user interface presents a dashboard of technical feature measurements;
[0016] Figure 7 It is a schematic diagram showing a dashboard of technical feature metrics presented by a graphical user interface;
[0017] Figure 8 It is a system block diagram used for monitoring and controlling usage and usage trend technical characteristics;
[0018] Figure 9 This is a schematic diagram of an in-vehicle display whose output points to the dashboard of a small component representing the technical characteristics of the material handling vehicle and / or the operator.
[0019] Figure 10 This is a schematic diagram of a flat panel display whose output is directed to a small component indicating the technical characteristics of a specific fleet and / or operator of material handling vehicles.
[0020] Figure 11 It is a block diagram of a system used for monitoring and controlling the characteristics of skilled technicians;
[0021] Figure 12 It is a block diagram of a system used for monitoring and controlling the status of technical features;
[0022] Figure 13 This is a block diagram of a system for monitoring and controlling technical feature map versions; and
[0023] Figure 14 This is a block diagram of a computer system having a computer-readable storage medium for implementing the functions according to various embodiments as described in more detail herein.
[0024] In the following detailed description of the illustrated embodiments, reference is made to the accompanying drawings, which form a part of the present invention, wherein specific embodiments that may be practiced are shown by way of illustration rather than limitation. It should be understood that other embodiments may be utilized and changes may be made without departing from the spirit and scope of the various embodiments of the present disclosure. Detailed Implementation
[0025] Material handling vehicles may be equipped with one or more “technical features”. As used herein, a technical feature is any one or more of the following: vehicle capacity that the operator may choose to use or not use; vehicle capacity that the operator may choose when to use (e.g., if fully used), such as during the performance of a task; vehicle capacity that the operator may choose to influence the way the material handling vehicle is operated (e.g., when in use); vehicle capacity that the operator must actively activate, actuate, operate, etc., to participate in, enable, or otherwise use or in combination thereof.
[0026] In this regard, the proper use of this technical feature can bring one or more benefits, which may include increased vehicle battery life (including increased time between charging needs), reduced wear and tear on material handling vehicles, increased time between servicing or maintenance needs, reduced operator fatigue, and combinations thereof. Similarly, the improper use of this technical feature may lead to one or more negative consequences, which may include shortened battery life (e.g., shortened time between charging needs), reduced time between servicing or maintenance needs, increased operator fatigue, and combinations thereof.
[0027] Introduction: Assistive Technology Functions
[0028] As an illustrative example, industrial vehicles may be equipped with technical features such as auxiliary systems that provide autonomous operation, semi-autonomous operation, remote control operation, or a combination thereof. However, these auxiliary systems must be used correctly to be effective.
[0029] In short, the example includes a remotely controlled driving function. To use the remotely controlled driving function, the operator presses a button on the wireless transmitter, which causes the associated material handling vehicle to move forward based on predetermined guidelines without the operator being physically present on and operating the vehicle. This allows the operator to walk alongside or behind the material handling vehicle to prepare for the next task. Because this is a remotely controlled operation, the operator can choose to use (or not use) the remotely controlled driving function.
[0030] Introduction: Features of Automatic Positioning Technology
[0031] As another illustrative example, material handling vehicles can be equipped with technical features such as an Automated Positioning System (APS). The APS automatically plans and then controls the material handling vehicle to automatically follow a predefined route from the current location to the next location, adhering to the most efficient path calculated to integrate lifting and driving functions to optimize the time and / or energy efficiency required to reach and automatically stop at the next shelf location. In this respect, the APS can take into account features such as travel distance, travel path, and lifting height to optimize the path.
[0032] However, operators can typically choose to use or not use an APS. Furthermore, in some embodiments, operators may be able to control when to engage the APS relative to the destination location. For example, an operator may initiate automatic positioning to travel to the next location by manually programming the next location, or the material handling vehicle may automatically acquire the next location, for example, by interacting with a warehouse management system on a remote server.
[0033] Introduction: Features of Aisle End Control Technology
[0034] As another illustrative example, material handling vehicles can be equipped with technical features such as End Aisle Control (EAC). End Aisle Control automates the response of material handling vehicles as they approach the end of an aisle, approach an intersection, or other operating areas designated by the EAC. In short, when a vehicle enters a boundary defined or otherwise identified by the EAC, the vehicle's processor controls the vehicle's power controls (e.g., traction control modules, braking modules, etc.) to control the material handling vehicle, such as stopping or decelerating within the designated boundaries.
[0035] For example, in some embodiments, the EAC can stop the material handling vehicle when it reaches a designated location (such as the end of an aisle). In other embodiments, the EAC can slow down the material handling vehicle, for example, when traveling across an intersection. For example, the EAC can slow the material handling vehicle to a selectable speed. In still other embodiments, the EAC can be a selectable feature, for example, slowing down or stopping the material handling vehicle in response to approaching an EAC boundary. Moreover, the EAC can be activated by operator-initiated control or action, so the material handling vehicle's response to an EAC boundary can be dynamic, for example, depending on when the EAC is activated.
[0036] Introduction: Features of Automatic Fence Technology
[0037] Another example of a technical feature is the automated fence feature. Automated fence (AF) capabilities, when enabled, utilize geographic features, such as RFID tags, ultra-wideband badges, environment-based location tracking, virtual markers (e.g., mapped to physical locations within a facility), and combinations thereof, to define controlled areas. Automated fences enable a variety of uses, such as setting speed or height zones, automatically slowing down vehicle speeds, stopping or limiting lift height based on a vehicle's position within a designated area, etc. In some embodiments, the AF can be activated by operator-initiated controls or actions; therefore, the response of material handling vehicles to AF geographic features can be dynamic.
[0038] Introduction: Technical Features of Shelf Height Selection
[0039] Another example of a technical feature is the rack height selection (RHS) feature, which allows for pre-programming of various fork height settings so that, during controlled operation, the forks of the material handling vehicle are raised to the pre-programmed height. In short, the operator can repeatedly raise the vehicle's forks to a known height (e.g., corresponding to various rack heights) by selecting the corresponding preset in the rack height selection interface. Again, the operator can choose whether or not to use rack height selection.
[0040] Introduction: Technical Features of Multitasking Controller
[0041] Another example of a technical feature is a multi-tasking control handle, which, for example, combines hydraulic control and traction control functions. For instance, the operator can "mix" traction and lifting, for example, initiating the raising of the forks on the material handling vehicle as the vehicle approaches the destination box so that the forks are at or near the correct height when the vehicle reaches its destination. This is an example of a technical feature where the operator can choose "when" to use it (if any), because the operator's interactive control with the multi-tasking handle "mixes" when this begins, and the ratio of lifting to traction (the speed at which the load is raised or lowered versus the speed at which the vehicle approaches its destination) is controlled by the operator's interaction with the multi-tasking handle.
[0042] Brief Introduction: Technical Characteristics of Driving Speed
[0043] Another example of a technical feature is the "turtle / hare" travel speed switch, which allows a material handling vehicle to have a travel setting (turtle) that is easier for the operator to control, and a travel setting (hare) for situations requiring relatively less control within a given travel path. The maximum travel speed is increased compared to the turtle setting. The travel speed switch is an example of how the operator can select how vehicle capabilities affect the operation of a material handling vehicle, as the operator can control the position of the switch and when to change it.
[0044] Other examples of technical features can be implemented within the spirit of this disclosure. For example, during normal use of a material handling vehicle, the operator can access and control certain technical features. Such uses may involve or otherwise affect vehicle movement, restrictions on control (e.g., adjusting setpoints), automated or semi-automated temporary interactions (e.g., automated or semi-automated aisle maneuvers), etc. Such uses may alter or control the vehicle's load-carrying capacity, such as lifting height, load weight limits, traction capacity, etc. This technology can also be operator-centric, for example, by selecting and / or customizing technical feature performance, control information indicators (such as lights), dashboard outputs, display outputs, etc.
[0045] It is important to note that a given technical feature must be used correctly to be effective. Furthermore, the technical features on each material handling vehicle in the fleet must be adequately maintained to ensure consistent and effective operation. In this regard, conventional technical features do not provide any means of monitoring usage, for example, by individual operators or groups of operators. Consequently, if operators are not adequately trained on how to operate the technical features in the context of the task at hand, the technical features will largely be underused, overused, or misused. Moreover, conventional technical features do not provide any means of monitoring health, operability, proper calibration, tuning, wear, or other usability conditions. Consequently, maintenance and service of the technical features can be neglected, rendering them inoperable.
[0046] In view of the above, this paper discloses a material handling vehicle feature monitor for monitoring the usage of material handling vehicle features. This paper also discloses a material handling vehicle technology system that monitors, manages, controls, modifies (e.g., tunes technical features to a specific set of conditions, optionally including dynamic conditions such as environmental conditions, operator conditions, etc.), and combinations thereof, the usage of material handling vehicle technical features. In practical applications, the material handling vehicle technical feature monitor is implemented as a control center that actively monitors one or more technical features of the entire fleet. The control center monitors how operators use the technical features. Based on this information, the control center provides information on operator usage of technical features, the evolution of operator usage of technical features over time, technical problems preventing operators from using technical features, and their combinations.
[0047] In some embodiments, the control center also provides feedback based on the monitored information. For example, feedback may be directed to the operator (e.g., in real-time, during use). Feedback may also be directed to the material handling vehicle, for example, modifying the vehicle's controls, changing setpoints, altering performance tuning, etc. Furthermore, feedback may be directed to the technical features of the associated material handling vehicle itself, for example, based on actual measured usage (or the absence of such usage), such as to achieve updated, "tuned" performance of the technical features (e.g., by modifying setpoints, operating parameters of specific technical features, etc.), including the ability to control the technical features to take a certain action, as will be described in more detail herein.
[0048] In yet another embodiment, the control center provides feedback to monitor, program, control, modify, or otherwise influence the environment in which the technical features are used, as will be described in more detail herein.
[0049] According to other embodiments described herein, the correct use of technical features can lead to further improvements, including operational efficiency, which in turn results in increased productivity. Conversely, the inappropriate use of these technical features can lead to decreased operational efficiency, which in turn results in decreased productivity.
[0050] System Overview
[0051] Now refer to the attached diagram, especially the reference... Figure 1 The schematic diagram illustrates a material handling vehicle system 100, which includes multiple hardware-equipped processing devices 102 linked together via one or more networks 104.
[0052] Network 104 provides communication links between various processing devices 102 and can be supported by network components 106 interconnecting the processing devices 102. Network components 106 include, for example, routers, hubs, firewalls, network interfaces, wired or wireless communication links and corresponding interconnections, cellular stations and corresponding cellular conversion technologies (e.g., conversion between cellular and TCP / IP, etc.). Moreover, network (one or more) 104 can include intranets, extranets, local area networks (LANs), wide area networks (WANs), wireless networks (WiFi), the Internet (including the World Wide Web), ad hoc networks, localized networks, mesh networks (e.g., between two or more processing devices 102), cellular and / or other arrangements for enabling communication between processing devices 102, etc.
[0053] The processing device 102 may be implemented as a server, personal computer, laptop computer, tablet computer, purpose-driven appliance, Internet of Things (IoT) device, dedicated computing device, cellular device including smartphone, information processing device in vehicle, information processing device on machine (fixed or mobile), or other device capable of communicating via network 104.
[0054] Specifically, the processing device 102 is provided on one or more material handling vehicles 108. In the illustrated example configuration, the processing device 102 on the material handling vehicle 108 communicates wirelessly via one or more technologies, such as via Wi-Fi access point 110 to a corresponding networking component 106, which serves as a connection to one or more networks 104. As another example, the material handling vehicle 108 may be equipped with cellular or other suitable wireless technologies, which allow the processing device 102 on the material handling vehicle 108 to communicate directly with remote devices (e.g., via one or more networks 104).
[0055] System 100 also includes processing devices implemented to support platform 114 and corresponding data sources (collectively referred to as data source 116) and servers 112 (e.g., web servers, file servers, and / or other processing devices). In an example embodiment, platform 114 may be used to implement a control center (feature monitor), as described more fully herein. For example, material handling vehicles 108 typically operate in work environments such as warehouses, distribution centers, retail establishments, etc. Accordingly, platform 114 provides material handling vehicle monitoring, management, control, or a combination thereof.
[0056] As more fully noted herein, the material handling vehicle 108 may be equipped with one or more technical features that require training and experience to operate effectively. Accordingly, the platform 114 provides, for example, monitoring, management, control, or a combination thereof of the technical features in response to their use (and optionally in response to their absence or lack of use).
[0057] In the illustrative example, data source 116 does not need to be located in the same place and does not include a database that links processes performed for the benefit of the enterprise from multiple different domains. In the illustrated example, data source 116 includes material handling vehicle information data source 118, which collects data from the operation of material handling vehicles 108 in, for example, the material handling vehicle domain. For example, the material handling vehicle information database may store electronic vehicle records, such as those wirelessly received from a fleet of material handling vehicles. In this respect, each electronic vehicle record may include data related to driving, operational data, maintenance data, observation data, configuration data, component status data, measured sensor data, impact data, or other information recorded by processing device 102 on the associated material handling vehicle 108. Each electronic vehicle record may also include an operator identifier for the corresponding operator of the material handling vehicle.
[0058] Data source 116 may also include management system data source 120, such as a warehouse management system (WMS). The WMS associates information with the movement and tracking of goods within the work environment within the WMS domain. Accordingly, in some embodiments, WMS data (alone or in combination with data from one or more other data sources, such as material handling vehicle information data source 118) can be used to select, define, refine, and otherwise influence operational characteristics affecting technical features, such as thresholds or threshold ranges characterizing travel distances for remote control of the work environment, and other examples that will be described in more detail herein.
[0059] Furthermore, data source 116 may include one or more other data sources 122 required by the work environment, such as a workforce management system (LMS). In some embodiments, the system may also include a data source such as a geolocation system 124 that stores information relating to geographic features, geographic capabilities, and / or, for example, limitations imposed on material handling vehicles via technical features or otherwise. Geolocation data may also include location-related data within the environment, for example, via an environment-based location tracking system. The list above is not exhaustive and is intended to be illustrative only.
[0060] Material handling vehicles
[0061] Material handling vehicles may include, for example, low-bay picking carts, forklifts, reach trucks, narrow-aisle trucks, stacker cranes, pallet trucks, tractors, picking machines, etc. In this regard, material handling vehicles may include raised and lowered forks. In other exemplary embodiments, material handling vehicles may include trolleys with hooks or other coupling structures for pushing and / or pulling loads.
[0062] Example low-position picking cart
[0063] Now for reference Figure 2 Material handling vehicle 208 is illustrated as a low-position picking cart. Material handling vehicle 208 is a derivative of material handling vehicle 108. Figure 1 One such example is the material handling vehicle 108, and similar elements are therefore shown higher with similar reference numeral 100. Figure 1 The description of ) is applied by analogy to material handling vehicle 208 ( Figure 2 Therefore, the different or specific characteristics of low-position picking carts will be described in detail.
[0064] The illustrated material handling vehicle 208 includes a load handling assembly 232 extending from the power unit 234.
[0065] The load handling assembly 232 includes a pair of forks 236, each fork 236 having a load support wheel assembly 238. The load handling assembly 232 may include other load handling features besides or replacing the illustrated arrangement of the forks 236.
[0066] The power unit 234 shown includes a stepping operator station 240 separating a first end (opposite to the load handling assembly 232) and a second end (proximity to the load handling assembly 232) of the power unit 234. The stepping operator station 240 includes a platform 242 on which an operator can stand to drive the material handling vehicle 208, for example, using a controller 244, and / or providing positions for various included features (e.g., controls 244) on which the operator can operate the material handling vehicle 208.
[0067] In some embodiments, a presence sensor 246 may be provided to detect the presence of an operator located within the operator station 240. For example, the presence sensor 246 may be located on, above, below, or a combination thereof on the platform 242, or otherwise provided around the stepper operator station 240.
[0068] Processing device 202 equipped with hardware (similar to reference) Figure 1 The processing device 102 (described herein) is positioned on the material handling vehicle 208, for example, within the power unit 234. When deployed on the material handling vehicle 208, the processing device 202 equipped with hardware is also referred to herein as an information linking device 202, as will be described more fully herein.
[0069] In the example low-position picking cart, pole 250 extends vertically from power unit 234 and includes one or more antennas 252. For example, one or more antennas 252 may be provided for receiving control signals from a corresponding wireless remote control device. One or more antennas 252 may also be used to connect information linking device 202 and / or material handling vehicle 208 to a remote computer device, such as server 112. Figure 1 One or more antennas 252 are schematically shown and may actually be integrated into the rod 250. In other example embodiments, one or more antennas 252 may be positioned at any physical location on the material handling vehicle 208.
[0070] The light 254 can be positioned on the pole 250, for example, at the top of the pole 250. The light 254 can be used as part of a situational awareness system to provide feedback to vehicle operators and / or pedestrians near the material handling vehicle 208.
[0071] Furthermore, the display 256 can be mounted at or near the pole 250 or power unit 234. The display 256 provides a graphical user interface that allows the operator to interact with the functions of the material handling vehicle 208 via the information link device 202 using programming and data exchange with a remote server 112. Figure 1 Interactions, their combinations, etc.
[0072] The material handling vehicle 208 also includes one or more non-contact obstacle sensors 258. The obstacle sensors 258 are operable to define one or more detection zones, such as the three detection zones Z1, Z2, and Z3 shown in the figure. For example, when the material handling vehicle 208 travels in response to a wirelessly received travel request, at least one detection zone can define an area at least partially ahead of the material handling vehicle 208 in its forward travel direction, as described more fully herein.
[0073] Obstacle sensor 258 may include any suitable proximity detection technology, such as ultrasonic sensors, image capture devices, infrared sensors, laser scanner sensors, etc., which are capable of detecting the presence of an object / obstacle or generating signals that can be analyzed to detect the presence of an object / obstacle within one or more predefined detection areas.
[0074] Remote control features
[0075] According to various aspects of this disclosure, system 260 includes material handling vehicle 208, remote control device 262, and optionally remote server 112. Figure 1 For example, wireless communication via information link device 202. The system enables technical features such as remote-controlled driving.
[0076] The remote control device 262 can be manually operated by an operator, for example by pressing a button or other control, to cause the remote control device 262 to wirelessly transmit a signal specifying a driving request to the material handling vehicle 208.
[0077] In some embodiments, before the material handling vehicle 208 accepts a driving request, the remote control device 262 may be required to pair with the corresponding controller on the material handling vehicle 208, for example using Bluetooth, ultra-wideband or other wireless communication technologies.
[0078] Although remote control device 262 is Figure 2 While shown as a wearable structure for fingers, the remote control device 262 can be implemented in various ways, including, for example, a glove structure, a lanyard, or a window sash mounting structure. A pairing system / protocol ensures that the material handling vehicle responds only to driving messages from a paired wireless remote control device. In some embodiments, pairing is performed using a PIN code or other authentication, including authentication using near field communication (NFC), physical electrical contact, etc.
[0079] In this respect, the material handling vehicle 208 connects to the remote server 112 via a first wireless connection (e.g., via an information link device 202 using Wi-Fi). Figure 1It communicates with the remote control device 262 via a second wireless connection (e.g., Bluetooth, UWB, etc.) that is different from the first wireless connection.
[0080] Information link devices integrated with material handling vehicles
[0081] refer to Figure 3 The block diagram illustrates a material handling vehicle 308 (e.g., Figure 1 Material handling vehicle 108 and / or material handling vehicle 208 Figure 2 The electronic control arrangement of any one of the following. The material handling vehicle 308 has a processing device 302, which is implemented as a dedicated specific computer (further specified herein as information link device 302) mounted to or otherwise integrated with the material handling vehicle 308. In practical applications, the processing device 302 is the processing device 102 ( Figure 1 ) and / or processing equipment 202 ( Figure 2 Example implementation of ).
[0082] Information linking device 302 includes components that enable communication with material handling vehicle 308 and with server 112. Figure 1 The necessary circuitry for wireless communication, data and information processing, and wired (and optionally wireless) communication, for example, via access point 110 ( Figure 1 ), cellular, and other wireless technologies, etc.
[0083] The illustrated information link device 302 includes a transceiver 304 for wireless communication. While a single transceiver 304 is illustrated for convenience, in practice, one or more wireless communication technologies may be provided. For example, the transceiver 304 may span multiple wireless communication technologies. Figure 1 Access point 110 connects to a remote server (e.g., via 802.11.xx) via 802.11.xx. Figure 1 The transceiver 304 communicates with server 112 and supports other wireless communications (e.g., cellular, Bluetooth, infrared (IR), ultra-wideband (UWB), or any other technology) or combinations thereof. Furthermore, the transceiver 304 can be implemented as a separate component on a material handling vehicle, communicating with information link device 302 across a suitable connection (e.g., a bus connection).
[0084] The information link device 302 also includes a control module 306 having a processor coupled to memory for implementing computer instructions, including computer-implemented processes or aspects thereof, as more fully illustrated and described herein. For example, the control module 306 utilizes a transceiver 304 to communicate with a remote server 112 ( Figure 1 Exchange information to control the operation of material handling vehicle 308.
[0085] In some embodiments, the information linking device 302 also includes a power-enabled circuit system 308 controlled by the control module 306 to selectively enable or disable the material handling vehicle 308 (or alternatively, selectively enable or disable specific control module or vehicle functions, such as hydraulics, traction, etc.). For example, the control module 306 may control the power-enabled circuit system 308 to provide power to the material handling vehicle 308 via power line 310, to provide power to selected components of the material handling vehicle 308, to provide power to selected vehicle functions, such as based on operator login, detected geographic features, etc.
[0086] In some embodiments, the information linking device 302 includes a monitoring input / output (I / O) module 312 for communicating via wired or wireless connections with peripheral devices (such as sensors, meters, encoders, switches, lights, etc. (collectively indicated by reference numeral 314)) attached to or otherwise mounted on the material handling vehicle 308. Module 312 may also connect to other devices, such as third-party devices 316, such as RFID scanners, displays, meters, etc. This allows the control module 306 to acquire and process information monitored, collected, or otherwise sensed on the material handling vehicle 308.
[0087] The information link device 302 is coupled to and / or communicates with other industrial vehicle system components via a suitable vehicle network 318. The vehicle network 318 is any wired or wireless network, bus, or other communication capability that allows the electronic components of the material handling vehicle 308 to communicate with each other. As an example, the vehicle network 318 may include a Controller Area Network (CAN) bus, a Local Interconnect Network (LIN), a Time Triggered Data Bus Protocol (TTP), an RS422 bus, or other suitable communication technology.
[0088] In the example configuration, the control module 306 of the information link device 302 connects to, understands, and is able to communicate with native vehicle electronic components (such as traction controllers, hydraulic controllers, modules, devices, bus-enabled sensors, displays, lights, light bars, sound generation devices, input / output devices, etc. (collectively indicated by reference numeral 320)).
[0089] In some embodiments, the material handling vehicle 308 may also include features / capabilities supporting one or more technical features, such as an optional environment-based location tracking system 322, an optional remote control receiver 324, an optional badge communicator 328, an optional display 330, or a combination thereof.
[0090] Optional environment-based location tracking device 322 enables material handling vehicle 308 to spatially know its location within a dimensionally limited environment, such as a mapped portion of an industrial enterprise. Accordingly, environment-based location tracking device 322 can be supplemented by technical features such as AF, APS, and other technical features that utilize or can be enhanced by location information. Here, environment-based location tracking device 322 may include a local awareness system that utilizes markings including reference markers, RFID, beacons, lights, reflectors, ultra-wideband badges, other external devices, and combinations thereof to allow spatial awareness within industrial environments (e.g., warehouses, manufacturing plants, etc.). Furthermore, local awareness can be achieved through machine vision guidance systems, such as using one or more cameras, inertial sensors, vehicle sensors, encoders, accelerometers, gyroscopes, etc.
[0091] If the material handling vehicle 308 implements technical features such as remote-controlled driving capabilities, then the material handling vehicle 308 may optionally include a remote control receiver 324. In alternative embodiments, the remote control receiver 324 may be integrated with or otherwise combined with the information linking device 302. Similarly, in some embodiments, the information linking device 302 may be integrated into the remote control receiver 324.
[0092] Remote control receiver 324 includes a remote control device 362 (e.g., similar to...) that is appropriately configured. Figure 2 The remote control device 362 is a transceiver for short-range communication. In some illustrative embodiments, the remote control device 362 is worn or otherwise carried by an operator and can communicate with the remote control receiver 324, for example, as a non-limiting example, when within a range of approximately 20-35 meters. The remote control receiver 324 can communicate using any proprietary or standardized communication protocol, including Bluetooth (via IEEE 802.15.1), Ultra Wideband (UWB, via IEEE 802.15.3), ZigBee (via IEEE 802.15.4), Wi-Fi (via IEEE 802.11), WiMax (via IEEE 802.16), etc.
[0093] In some illustrative embodiments, the remote control receiver 324 includes at least two or three antennas 326. The availability of multiple antennas not only allows for signal detection but also allows for location within the detection area. In any case, the remote control receiver 324 can calculate its position (or distance) via time-of-flight calculation, phase calculation, received signal strength calculation, time difference of arrival, trilateration, multilateral measurement, combinations thereof, and / or other techniques.
[0094] As shown in the figure, the remote control receiver 324 can transmit information related to the interaction with the corresponding remote control device 362 to the control module 306 of the information link device 302. The control module 306 of the information link device 302 (or the remote control receiver 324) can then process the received information, send commands to the vehicle controller and module 320, take action based on the known position of the material handling vehicle 108 via information collected from the environment-based location tracking device 322 and / or other sensors on the material handling vehicle 108, and transmit the collected information to a remote server (e.g., Figure 1 Server 112), takes actions based on information received from a remote server, such as combinations thereof.
[0095] In an example embodiment, in response to an operator actuating a control on remote control device 362 (e.g., pressing a button), the circuitry within remote control device 362 wirelessly transmits control signals to remote control receiver 324. Remote control receiver 324 then transmits the received control signals to a controller (e.g., a dedicated controller within remote control receiver 324, control module 306, or other processing equipment within material handling vehicle 308). Regardless of its location, the controller responds appropriately to received commands to execute technical features. Information linking device 302 can also send corresponding vehicle records to server 112 (…). Figure 1 (as described more fully in this article).
[0096] The controller's response to wirelessly received commands (e.g., wireless transmissions via remote control device 362) can trigger the material handling vehicle 308 to take one or more actions or refrain from action, depending on the logic being implemented. Active actions may include controlling, adjusting, or influencing one or more components of the material handling vehicle 308. The controller may also receive information from other inputs, such as from sensors 314 (e.g., presence sensor 242). Figure 2 ), obstacle sensor 258 ( Figure 2 This includes switches, load sensors, encoders, and other devices / features that can be used by the material handling vehicle 108 to determine appropriate actions in response to commands received from the remote control device 362. For example, in some embodiments, sensors communicate directly across the vehicle network 318. Therefore, sensor data read across the vehicle bus 318 (e.g., the current state of the sensor, obstacle sensor 258, etc.) Figure 2 The current state of (e.g.,) can affect, cancel, change, or otherwise influence other appropriate commands from the remote control device 362.
[0097] In an exemplary arrangement, remote control device 362 is operable to wirelessly transmit control signals representing a first-type signal, such as a driving command, to a remote control receiver 324 on the material handling vehicle 108. The driving command is also referred to herein as a “driving signal,” “driving request,” or “departure signal.” Upon confirmation of the driving request, the controller interacts directly or indirectly with one or more controllers 320 (e.g., a traction motor controller, a steering controller, a brake controller, a combination thereof, etc.), for example, via a vehicle network, to propel the material handling vehicle.
[0098] In an example embodiment, a travel request is used, for example, to initiate a travel request to the material handling vehicle 308 whenever a travel signal is received by the remote control receiver 324 and / or sent by the remote control device 362. As another example, a travel request can be configured to initiate a request for the material handling vehicle 308 to travel a predetermined amount, such as to cause the material handling vehicle 308 to travel a limited distance in a first direction, or to travel for a limited time.
[0099] Furthermore, the controller can be configured to "time out" and stop the material handling vehicle 108 from traveling based on a predetermined event (such as exceeding a predetermined time period or travel distance), regardless of the detection of the maintaining actuation of the corresponding control on the remote control device 362.
[0100] Stopping the material handling vehicle 308 can be achieved, for example, by allowing the material handling vehicle 308 to coast to a stop or by initiating a braking operation to bring the material handling vehicle 308 to a stop. In an example configuration, the controller communicates via vehicle network 318 with one or more controllers 320 (e.g., traction motor controller, steering controller, brake controller, combinations thereof, etc.) to terminate the remotely controlled movement of the material handling vehicle. For example, the brake controller controls the vehicle brakes to decelerate, stop, control the speed of the material handling vehicle 308, or otherwise allows the material handling vehicle 308 to coast to a stop.
[0101] The remote control device 362 can also operate to transmit a second type of signal, such as a "stop signal," which specifies that the material handling vehicle should brake and / or otherwise stop. The second type of signal can also be implied, for example, after a "drive" command has been executed, such as after the material handling vehicle has traveled a predetermined distance, a predetermined time, etc., under remote control in response to the drive command. If the controller determines that the wirelessly received signal is a stop signal, then the controller sends a signal to the traction motor controller, brake controller, and / or other vehicle electronics to stop the material handling vehicle. Alternatively to the stop signal, the second type of signal may include a "coasting signal" or a "controlled deceleration signal," which specifies that the material handling vehicle should coast and eventually decelerate to a stop.
[0102] The time required for a material handling vehicle to come to a complete stop can vary, depending on factors such as the intended application, environmental conditions, the specific capabilities of the material handling vehicle, the load on the vehicle, and other similar factors. For example, after a proper jogging movement, it may be desirable to allow the material handling vehicle to "glide" a distance before coming to a stop, allowing it to come to a gradual stop. This can be achieved by using regenerative braking to decelerate the material handling vehicle to a stop. Alternatively, braking can be applied after a predetermined delay time to allow additional travel within a predetermined range of the material handling vehicle 308 after the stop operation is initiated. For example, if an object is detected in the material handling vehicle's path or if an immediate stop is desired after a successful jogging operation, it may also be desirable to stop the material handling vehicle relatively quickly. For example, a controller can apply a predetermined torque to the braking operation. Under such conditions, the controller can instruct the braking controller to apply the brakes to stop the material handling vehicle. For example, all such parameters can be adjusted in response to a workflow, examples of which are described more fully herein.
[0103] Furthermore, if the material handling vehicle 108 travels under remote control (or is instructed to travel) in response to a travel request, the controller can be configured to perform various actions. For example, the material handling vehicle 308 can detect one or more of the detection zones (e.g., detection zones Z1, Z2, Z3). Figure 2 Stop after encountering an obstacle in the material handling vehicle 308. For example, if the operator is on the material handling vehicle 308 (e.g., as indicated by the presence sensor 146), the vehicle will stop. Figure 2 If the obstacle sensor 258 (is certain), then the controller can refuse to acknowledge the received driving request. Similarly, if the obstacle sensor 258 (is certain), then the controller can refuse to acknowledge the received driving request. Figure 2 If an object, including the operator, is detected in the detection zone of the material handling vehicle 108, the controller may refuse to acknowledge the driving request from the remote control device 362.
[0104] In some example embodiments, the information linking device 302 may include a badge communicator 328. The badge communicator 328 includes a transceiver for short-range communication with an electronic badge appropriately positioned in the vicinity of the badge communicator 328, for example, by a non-limiting example, within a range of approximately 15-20 meters or less. The badge communicator 328 may communicate using any proprietary or standardized communication protocol, including Bluetooth (via IEEE 802.15.1), Ultra Wideband (UWB, via IEEE 802.15.3), ZigBee (via IEEE 802.15.4), Wi-Fi (via IEEE 802.11), WiMax (via IEEE 802.16), RF for interacting with badges implemented as RFID tags, etc.
[0105] In some illustrative embodiments, electronic badges will be worn by pedestrians, workers, material handling vehicle operators, etc. Furthermore, electronic badges can be attached to mobile equipment, material handling vehicles, or other moving objects. On the other hand, some electronic badges can be fixed, such as being attached to the end of an aisle, on a shelf, above a doorway or near a break room, along the floor to a crumb path, or in other cases where the electronic badge is not intended to be moved.
[0106] In some illustrative embodiments, the badge communicator 328 includes at least three antennas 326. The availability of multiple antennas 326 not only allows for signal detection but also allows for location within the detection area. Here, the badge communicator 328 calculates its position via time-of-flight calculation, phase calculation, received signal strength calculation, time difference of arrival, trilateration, multilateral measurement, combinations thereof, and / or other techniques.
[0107] As shown in the figure, display 330 is coupled to vehicle network system 318. Display 330 provides the operator with information via transceiver 304 that can be obtained from analysis engine 114 by control module 306 via one or more components (e.g., module 320). Figure 1 The information generated (e.g., displaying truck data from material handling vehicle data source 118, displaying WMS data from WMS data source 120, displaying labor data from LMS data source 122, displaying geographic-based event data from GEO data source 124, etc.). In an example embodiment, display 330 provides a graphical user interface that enables the operator to interact with the functions of material handling vehicle 308, and to communicate with remote server 112 via information link device 302 using programming and data exchange. Figure 1 Interactions, their combinations, etc.
[0108] Material handling vehicle feature monitor
[0109] refer to Figure 4 According to various aspects of this disclosure, a process 400 for implementing a feature monitor for material handling vehicles is provided. Process 400 is applicable to the technical features described throughout this disclosure.
[0110] Process 400 includes receiving electronic vehicle records wirelessly from the fleet of material handling vehicles at point 402.
[0111] Process 400 also includes parsing the vehicle records for each vehicle operator at 404 to extract dashboard data.
[0112] Process 400 also includes establishing the intended use case at 406.
[0113] Process 400 also includes generating electronic measurements for each operator at 408, for example, based on specific technical features implemented.
[0114] Furthermore, process 400 includes outputting results at 410. For example, process 400 may output a graphical representation of the generated measurements to a dashboard, trigger a workflow, take other actions, etc., as described in more detail herein.
[0115] Usage status technical features monitoring - remote control driving function
[0116] refer to Figure 5 The usage and / or usage trend block diagram 500 illustrates an example of communication between a material handling vehicle and a remote server according to various aspects of this document, in order to perform aspects of monitoring and automating material handling vehicle control in response to technology usage monitoring. The block diagram 500 shown is applicable to technical features such as remotely controlled driving functions, but can also be applied to other technical features. Furthermore, Figure 500 provides a suitable implementation... Figure 4 The process is a 400-step solution.
[0117] Block diagram 500 can be, for example, via material handling vehicle 108 ( Figure 1 ); Material handling vehicles 208 Figure 2 Material handling vehicle 308 Figure 3 For example, via information link device 102 ( Figure 1 Information linking equipment 202 ( Figure 2 Information linking device 302 ( Figure 3 ) and remote server 112 ( Figure 1 This is achieved through communication.
[0118] As shown in the figure, the electronic components in the material handling vehicle 508 are connected via, for example, across network 504 (similar to...). Figure 1 Network 104) wireless communication to communicate with the analysis engine 514 (e.g., similar to Figure 1 Platform 114) communication.
[0119] During normal operation, the vehicle operator can use technical feature 540, for example, to activate the remote control receiver ( Figure 3 324) Remote control button for communication ( Figure 2 Remote control 262; Figure 3 (362) to request remote control driving function.
[0120] In response, various modules on the material handling vehicle 508 respond to perform their technical functionalities. In this regard, information and message passing are transmitted across the vehicle network 518.
[0121] As an illustration, vehicle network 518 (similar to vehicle network 318) Figure 3 ) Facilitates multiple control modules 520 (similar to) Figure 3 Communication between control modules 520 and 520A. For example, optional control module 520A may include sensor control module (SCM) 520A or other suitable control module or other network-enabled device. Optional control module 520B may include traction control module (TCM) 520B, which controls the movement of material handling vehicle 508. The system may also optionally include other network-enabled devices, such as, schematically shown as control module 520C, such as steering module, braking module, etc. Moreover, one or more additional electronic components may also function, see reference. Figure 3 Examples describing these electronic components.
[0122] As schematically shown, technical feature 540 itself may include electronics acting as a boundary intermediary, for example, to control the flow of information related to the use (or lack thereof) of the technical feature between the corresponding material handling vehicle 508 and the remote server 514. In other embodiments, this functionality may be provided by other electronics (e.g., information linking device 302, as referenced). Figure 3 As described above, technical feature 540 (or other devices) interacts with control module 520 and / or other vehicle electronics to collect information, send commands, send reports to remote server 514, receive returned information from remote server 514, perform technical features, etc. For example, in an example embodiment, technical feature 540 collects and / or reads sensor activity status information from SCM 320A, speed information from TCM 320B, and information from sources such as remote control receivers via communication across vehicle network 518 (e.g., CAN bus). Figure 3 The remote control usage of modules such as 324).
[0123] Technical feature 540 also wirelessly communicates with remote server 514 via remote module server 550 (e.g., via Wi-Fi, cellular, etc.) (directly or via transceiver, information linking device, etc.). Information transmitted to module server 550 may include information collected from various modules 520A-520C or other devices on the material handling vehicle, as well as other information measured, calculated, recorded, received, or otherwise obtained by or for technical feature 540. For example, in an example of remotely controlled driving functionality, technical feature 540 may report guided usage by including the distance the vehicle traveled under remote control, the distance traveled without using remote control, operator ID, vehicle ID, time, other relevant data, or combinations thereof. In some embodiments, technical feature 540 may report information that may include information regarding the non-use of the corresponding technical feature.
[0124] In some embodiments, feature 540 may send records at predetermined intervals, every X seconds (where X is any integer) (e.g., every minute, every 5 minutes, every 30 minutes, every hour), each time used, each time logged in, each time logged out, whenever new data is available, conditionally dynamically, etc. The specific configuration will likely determine and control the timing.
[0125] Module server 550 can be implemented as a module server running on a remote server as part of an analytics engine (e.g., similar to...). Figure 1 The analysis engine 114). Module server 550 feeds an Extract, Transform, Load (ETL) pipeline, which includes a set of processes that extract data from input received from feature 540. The processes in the ETL pipeline collectively transform the data and then load it to an output destination for reporting, analysis, and data synchronization.
[0126] For example, the ETL process may include a usage percentage process 552A that extracts data from data collected by module server 550, the percentage corresponding to the percentage of each operator using the relevant technology feature. From the collected data, a usage trend process 552B extracts trends in technology usage (e.g., trends in remote driving usage). The output of usage percentage process 552A and / or usage trend process 552B is a usage percentage trend widget 552C. The usage percentage trend widget 552C may include graphical widgets, visual outputs, interactive outputs, drill-down reports, etc. In this regard, the widget can be used as a dashboard by displaying real-time (or near real-time) updates to the data collected by the ETL pipeline.
[0127] In some alternative embodiments, data collected at 552A during the percentage usage process can also be evaluated, such as through an above / below target process 554, which compares the percentage usage determination to one or more established thresholds(s). In an example implementation, the above / below target process 554 receives input from a usage target setting 556 to evaluate the percentage usage measurement recorded in the percentage usage process 552A. In this regard, the above / below target process 554 outputs a usage widget 558, the output of which includes widgets for drill-down, reporting, and combinations thereof.
[0128] Usage Percentage Trend Widget 558 provides one or more visual metaphors that graphically illustrate usage and trend information. For example, a circle chart can illustrate a measurement of the percentage of operators meeting programmed target usage compared to those operators below the target for an automation feature (e.g., operators underutilizing the feature). Trend charts can be expanded to correspond to average utilization across a predetermined range of data (within the target compared to below the target). Data associated with Technical Feature 540 can also enable the system to track interruptions to the associated automation feature (e.g., lost connection to a remote (or other external) device; user deactivation of the tracked automation feature; unexpected deactivation, such as due to low battery, technical malfunction; unexpected stoppage, such as due to obstacle detection or pedestrians near the AGV, etc.).
[0129] Furthermore, the output of the processing at the server can trigger workflow 560, which is described in more detail in this article.
[0130] Widgets offer technological advantages, enabling visualization not only of feature usage but also of trends (including trends among operator groups, such as those based on operator shifts, operator departments, or facilities in which operators work) and problems with feature usage. For example, in some embodiments, the system provides feedback commands to material handling vehicle 508. Feedback can be provided to tune specific features, such as performing software upgrades, calibrations, tuning, setting setpoints, establishing operating ranges, adjusting frequencies, or other parameters that affect feature performance. In some embodiments, feedback commands are provided to the operating environment, such as performing software upgrades, calibrations, tuning, setting setpoints, establishing operating ranges, adjusting frequencies, or adjusting other parameters that affect feature performance or otherwise controlling peripherals that assist associated features. For example, poor performance detected in a remotely controlled driving function could be due to poor Bluetooth signal strength, the need for calibration, etc.
[0131] In some embodiments, feedback commands are provided to provide guidance, feedback, and trigger workflows to achieve remediation, performance optimization, and improve the functionality of the corresponding material handling vehicle itself, such as controlling speed or increasing height by adjusting the controller setpoint.
[0132] Here, the material handling vehicle can interact with the module server 550 to transmit information back to the material handling vehicle by interacting with the workflow 560, for example, by communicating directly with a remote server, remote controller, remote maintenance scheduler, or remote equipment (e.g., RFID tags, UWB badges, repeaters, mesh processors, positioning system components (such as environmental location-based markers deployed in the work environment)) to invoke maintenance, equipment performance tuning, disable equipment, enable equipment, and combinations thereof.
[0133] For example, the root cause of underutilization of a given technological feature (such as remote-controlled driving) can be traced back to poor transmitter health (e.g., remote control) that affects performance. Figure 2 262; Figure 3 (In the 362 cases, there are issues such as insufficient battery power, antenna damage, and poor pairing stability). Low transmitter health can be an aspect that is difficult or otherwise undetectable, which is missing from this paper. Accordingly, the utilization of technical features can actually facilitate the improvement of auxiliary technologies in the operating environment of material handling vehicles. Moreover, interruptions or trends in technology use can indicate equipment problems, such as mechanical defects that may not be detectable solely through electronic events / error codes.
[0134] Remote-controlled driving example
[0135] As this article points out more fully, remote-controlled operation can help operators of devices such as low-position picking machines improve productivity and reduce fatigue through remote control of associated picking machines. Without changing any other behavior, operators who correctly use wireless remote control technology can pick significantly more boxes per hour. This productivity increase can be measured using the corresponding warehouse management system (WMS). However, understanding when to ideally use wireless remote control technology (rather than stepping onto the operator platform to drive the picking machine) requires some expertise, which is typically acquired through onboarding and experience.
[0136] As an example, and not a limitation, suppose the vehicle's travel distance to the next picking location is less than a first threshold. In this case, the correct response is for the operator to remotely control the material handling vehicle to proceed to the appropriate destination using a remote control device. Conversely, if the travel distance to the next picking location is equal to or exceeds the first threshold, the correct response is for the operator to board and drive the material handling vehicle to the destination in a standard manner. The distance of the first threshold can vary based on many factors, including environment, truck performance tuning and / or characteristics, operator skill, etc.
[0137] Similarly, in some applications, a travel distance to the next picking location below a second threshold should require the operator to walk to the next picking location. However, a travel distance equal to or greater than the second threshold (and optionally lower than the first threshold) to the next picking location should be traveled using wireless remote control technology. In yet another embodiment, when the distance to the destination falls within, for example, a range defined between the first and second thresholds (minimum and maximum travel distances), the remote control device should be used to remotely control the material handling vehicle to proceed to the appropriate destination. Therefore, the correct response is for the operator to use the remote control device to remotely control the material handling vehicle to proceed to the appropriate destination. Again, the distance of the second threshold can vary based on multiple factors, including environment, truck performance tuning and / or characteristics, operator skill, etc.
[0138] In some embodiments, feedback from workflow 560 can be information for the operator, such as guidance. For example, suppose an operation is performed inappropriately, such as operating a remotely controlled driving function for a distance that is too short or too long to the next picking point. Here, the operator should have already walked or ridden to the last picking point, so instructions can be given, for example, to return from workflow 560 to a display on the material handling vehicle (retrospective). In another embodiment, an application on the material handling vehicle (e.g., a material handling vehicle feature monitor) consults the WMS, and the system informs the operator, for example via prompts, tones, lights, messages, etc., whether to walk or ride (proactive). That is, the application is dynamic, checking the status of the next (upcoming) picking operation so that the operator can receive real-time, on-demand guidance on how to use the remote control feature. In yet another alternative embodiment, the system uses WMS data and current operation data to allow / deny / override operator actions. Here, the system can refuse to allow the vehicle to jog when the application deems jogging not the most efficient operation. Optional warnings can be provided here, for example via messages, lights, sounds, tactile responses, etc. On the other hand, where the operator should use the remote control feature, the application can remind the operator that the next option provides an opportunity to use the remote control feature.
[0139] If all operators of picking machines use wireless remote control technology correctly, the overall productivity of the facility will increase. Conversely, insufficient or incorrect use of wireless remote control technology will reduce (or in some cases eliminate) the achievable productivity gains associated with it. Currently, in this regard, distribution center (DC) managers or team leaders lack data to identify operators who are not using wireless remote control technology adequately or correctly.
[0140] Furthermore, insufficient or incorrect use of the wireless remote control technology can result from an operator using a material handling vehicle with wireless remote control technology but failing to pair the remote control with the vehicle. Insufficient or incorrect use can also be caused by an operator pairing the remote controller but not operating it. Further, insufficient or incorrect use can be caused by an operator operating the remote controller too infrequently or too frequently. Technical problems (e.g., low remote battery power, pairing issues, mechanical wear and tear on switches or other components) can also lead to insufficient or incorrect use of the wireless remote control technology.
[0141] As an example, if an application running on a material handling vehicle detects that the vehicle is moving without being paired with a corresponding remote control receiver, the system can take actions such as tuning the vehicle's performance to operate differently, issuing a message, or requesting pairing. For instance, features can be added or removed, such as providing performance incentives for pairing.
[0142] To give another example, if the application detects that the pairing is inactive, but the material handling vehicle has moved or done something, the system can take action (e.g., by outputting to the operator, modifying the truck's capabilities via performance tuning, providing some kind of indicator that the truck is not being used correctly, etc.).
[0143] If the application detects connectivity issues, such as low battery, charging failure, or failed pairing attempts, the platform can initiate automatic remedial actions (e.g., reprogramming features to operate over shorter distances to save power, reducing the range of the remote control, limiting the number of times the remote control can be operated, etc.) to extend battery life. The application can also attempt to remedy pairing problems, for example, by modifying the discovery process. For instance, if pairing is initiated by an operator making a pairing request on the display, then pressing a button on the remote control to pair and the request failing, for example, due to too many operators attempting to pair the device, the discovery process can be reconfigured, for example, to allow the truck to begin automatic pairing, for example, by searching for the remote controller with the strongest signal (e.g., via RSSI). If the remote controller's signal strength is greater than a predetermined threshold, then the system can pair.
[0144] Go back to reference Figure 4 In an example embodiment, each electronic record received at 402 may include travel-related data, such as data recorded by the controller on an associated material handling vehicle operated by the corresponding operator in the work environment, as per [reference to...]. Figures 1-3 and Figure 5 As described above. Each record may also include the operator's identifier for the corresponding operator of the material handling vehicle.
[0145] As some additional illustrative examples, an electronic vehicle recorder can indicate whether the movement of a corresponding material handling vehicle occurred when the remote control device was not paired with the remote control receiver, whether the movement of a corresponding material handling vehicle occurred when the remote control device was paired with the remote control receiver, and so on. The electronic vehicle recorder can also enable determination that the movement of a corresponding material handling vehicle occurred due to the operation of a control feature on the remote control device paired with the remote control receiver of the corresponding material handling vehicle, thereby achieving remotely controlled movement functionality. The electronic vehicle recorder can also be used to indicate the amount of time the remote control device was paired with the remote control receiver of the corresponding material handling vehicle.
[0146] In some embodiments, the received electronically recorded data is parsed at 404 as the distance traveled by the material handling vehicle in response to the corresponding operator using the remotely controlled driving function within a predetermined time period and / or the total distance traveled by the material handling vehicle within the predetermined time period.
[0147] The process at 406 can establish anticipated usage by establishing the remotely controlled driving distance relative to, for example, the total driving distance over a predetermined time period. In some embodiments, the anticipated remotely controlled driving distance established at 406 relative to the total driving distance can include establishing the anticipated remotely controlled driving distance relative to the total driving distance as a range of ratios of driving distance to total driving distance. In this regard, outputting a graphical representation of the generated measurement to the dashboard can include outputting a remote control usage trend graph showing the trend of operator use of control features on a remotely controlled device paired with a remote control receiver of the corresponding material handling vehicle to achieve remotely controlled driving functions over time, compared to this range. As an example, the graph can provide a graphical representation of the historical development of average operator use of the remotely controlled device. Moreover, the dashboard can graphically output details of the graphs provided for each individual, as well as comparative graphs defining other individuals or averages for all operators within user-configured filter settings. Here, usage targets can be visually highlighted (e.g., using color, shading, or other markings) to distinguish when targets were achieved and when they were not achieved.
[0148] In some embodiments, underlying data and / or computation can be used to drive the gamification process, for example, enabling operators to directly compare their performance with target performance.
[0149] The process at 408 may include, for each operator, generating an electronic measurement of the expected distance traveled under remote control relative to the total distance traveled within a predetermined time period, compared with the recorded distance traveled under remote control relative to the total distance traveled within a predetermined time period.
[0150] In some embodiments, the measurement generated at 408 may include the expected remotely controlled distance relative to the total distance traveled, calculated by establishing the expected remotely controlled distance traveled relative to the total distance traveled as a range of the ratio of the remotely controlled distance traveled to the total distance traveled. For example, an example range could be the expected remotely controlled distance traveled as 57%–83% of the total distance traveled. Of course, the above example range is purely exemplary.
[0151] As another example, the range of the ratio of remotely controlled distance traveled to total distance traveled can be set by programming different ranges of the ratio based on metadata associated with received electronic vehicle records. For example, the range could be 57%–83% for the first shift operator, but only 15%–40% for the second shift operator. As another example, the range could be 30%–45% for operators working in the first part of the warehouse, and 55%–75% for operators working in the second part of the warehouse, and so on. Therefore, the programmed ratio range can be based on at least one of the following: different locations, different shifts, different time ranges, different date ranges, different operator skill levels, or combinations thereof.
[0152] In some embodiments, the material handling vehicle feature monitor outputs a dashboard at 410 as a graphical representation of the generated measurements. As an illustrative example, the graphical representation may include generating a dome chart to differentiate: for an operator operating a remotely controlled driving function at a level above a target range, the operator is above the target range indicated by a first symbol; for an operator operating a remotely controlled driving function below the target range, the operator is below the target range indicated by a second symbol different from the first symbol; for an operator operating a remotely controlled driving function within the target range, the operator is within the target range indicated by a third symbol different from the first and second symbols, or a combination thereof.
[0153] In some example embodiments, the dashboard implements a graphical representation of the generated measurements, characterizing the use of control features compared to the time the remote control device and remote control receiver have been paired. In another example, the dashboard may output graphical representations of users who have paired but not operated the remote control device, users who use control features too infrequently compared to the target usage scenario, users who use control features too frequently compared to the target usage scenario parameters, combinations thereof, etc.
[0154] In another example embodiment, the system creates "user personas." For instance, user personas can be created as a measure of how well an actual user identifies characteristic use cases and uses the system accordingly ("competency"). Based on a user's individual competency, the corresponding WMS / ERP system assigns picking orders to individuals whose expertise matches the nature of the corresponding picking journey. For example, for users who often fail to identify opportunities to use characteristics (e.g., using remote control characteristics based on distance to the next picking location), only journeys with a large number of long inter-picking distances can be assigned. As another example, operators exhibiting a tendency to overuse characteristics can be assigned picking routes with a high percentage of short inter-picking distances. In this way, user weaknesses can be mitigated or even turned into assets through characteristic usage.
[0155] In another example embodiment, the material handling vehicle feature monitor receives feedback from an operator via a graphical user interface. The operator selects usage details through operator reports, which causes the dashboard to output a graphical representation of a list of operators. This list may include measurements of their operation of control features on a remote control device paired with a remote control receiver to enable remote control of the driving function of the corresponding material handling vehicle. The list may also include measurements of the percentage of time the operator operates the material handling vehicle when the remote control device is paired with the remote control receiver, compared to the time the operator operates the material handling vehicle when the remote control device is not paired with the remote control receiver. The list may also include usage and pairing time values as aggregated averages over a user-selected time period.
[0156] The dashboard can also output graphical representations of technical problems encountered when a remote control device is paired with the corresponding remote control receiver of a material handling vehicle to enable remote-controlled driving. Example technical problems include pairing failures, the number of material handling vehicles currently operating without a paired remote, and the number of remote controls reporting low battery levels. By pairing dashboard data with predictive maintenance, the system can automatically order maintenance / repair parts, enabling rapid resolution of technical problems based on automated workflows.
[0157] As an introduction and summary, platform 114 can perform a process of parsing vehicle records for each vehicle operator to extract dashboard data. Here, dashboard data includes the distance traveled by a material handling vehicle under remote control, for example, within a predetermined time period in response to the corresponding operator using the remote control's driving function, and the total distance traveled by the material handling vehicle within the predetermined time period. The process also includes establishing a projected distance traveled under remote control relative to the total distance traveled within the predetermined time period. As mentioned above, the projected value can be user-defined and / or can be derived by platform 114 from material handling vehicle information data source 118, management system data source 120, (one or more) other data sources 122, combinations thereof, etc.
[0158] Furthermore, the process implemented by platform 114 may include generating an electronic measurement of the expected remotely controlled distance for each operator, comparing it with the recorded total distance traveled within a predetermined time period, and outputting a graphical representation of the generated measurement to a dashboard. The dashboard can output to a display on a material handling vehicle, desktop computer, or similar device.
[0159] Furthermore, platform 114 can collaborate with processors on corresponding material handling vehicles to perform one or more of the functions, features, capabilities, etc., described more fully herein. In this regard, platform 114 can act as a supervisor, offload processing to processors on material handling vehicles, share processing responsibilities with processors on material handling vehicles, and so on, examples of which are described in more detail herein.
[0160] In some embodiments, the material handling vehicle feature monitor can send feedback to the material handling vehicle in response to analysis of data displayed on the dashboard. Feedback can be output to a display (e.g., the dashboard). Feedback can be via situational awareness, for example, by flashing lights, outputting guidance information to the display, etc.
[0161] Furthermore, the feedback can take the form of controls. Here, controls can influence the performance of the material handling vehicle, for example, by tuning the vehicle's performance, such as changing the driving speed, acceleration, braking, sensor sensitivity, etc., under remote control, modifying the setpoint, or otherwise improving the vehicle's operation. In a further embodiment, the feedback can be tuning the remote control system itself, for example, by setting ranges such as modifying the driving distance under remote control, modifying jogging operations, modifying the setpoint, control characteristics, speed limits, braking requirements, usage rules, etc.
[0162] For example, a material handling vehicle feature monitor can send commands back to the material handling vehicle reporting a technical problem to modify its performance to remedy the issue. A graphical representation of the technical problem can also / cannot be described as a real-time view, without showing historical data.
[0163] In another example, based on the operator's records and pace, the system can dynamically adjust remote driving operations to adapt to the operator's physical condition, thereby reducing operator fatigue, stress, and strain.
[0164] In some embodiments, the material handling vehicle feature monitor reviews the warehouse management system database and extracts picking metrics from it. For example, picking metrics may include at least one of average picking interval distance, aisle length, picking pattern, historical picking list, and combinations thereof. Reviewing the warehouse management system may also include automatically evaluating warehouse management data for each picking run. This data can be used to modify the distance traveled under remote control, for example, as a dynamic, real-time update, or via a fixed-distance update.
[0165] In this regard, in some embodiments, the remote server can analyze the electronic measurement of the expected remotely controlled distance traveled relative to the total distance traveled within a predetermined time period, compared to the recorded remotely controlled distance traveled relative to the total distance traveled within a predetermined time period. In response, the workflow can route commands back to the material handling vehicle, for example, to initiate modifications to the material handling vehicle. For example, by querying task information, if the next picking operation is too far from the current location of the material handling vehicle, the processor can, for example, reject the remote start / remote travel command. Similarly, if the next picking operation is too close to the current location of the material handling vehicle, the processor can reject the remote start / remote travel command. For example, the picking operator can walk to the next location more efficiently.
[0166] In an example embodiment, a user interacting with the dashboard via a graphical user interface can select within the dashboard view to activate a graphical representation of usage details by operator, filtering which records contribute to the dashboard view so that the usage and the paired time values output to the dashboard are averages over a time period selected by the user interacting with the filter. Records can be selected for the dashboard view based on at least one of the selected location, shift, department, operator skill level, time frame, or a combination thereof.
[0167] In yet another embodiment, the material handling vehicle feature monitor electronically ranks dashboard data, sorts it by operator identification, and displays the ranked dashboard data graphically so that the ranked dashboard data reveals whether the operator is using remotely controlled driving too much or too little.
[0168] For a specific example, see Figure 6 and Figure 7 They display dashboards on the monitors of material handling vehicles for operator interaction. Figure 6 ), and displaying a dashboard display on a computer monitor (e.g., desktop computer monitor, smartphone display, flat panel display, etc.) for administrators ( Figure 7 )wait.
[0169] Work Example
[0170] For example, features applied in fleet management software (e.g., running on platform 114 - Figure 1 The program runs on the control module 306 of the material handling vehicle. Figure 3 Electronic vehicle records are collected (e.g., see 402-). Figure 4 Electronic vehicle records can include characteristic-specific (e.g., driving-related) information collected from the corresponding material handling vehicle. Example driving information could include the total driving distance for each logged-in operator in response to total remote driving distances in both remote control and manual driving distances. The characteristic application then uses these two datasets to generate a usage percentage. For example, when run by a server, platform 114 can calculate the usage percentage for each operator. Example usage scenarios could be established as Usage. Feature =d remote / d total .
[0171] By conducting an initial assessment of warehouse and representative WMS data, the feature application can establish a projected ratio of remotely controlled trips to total trips for any facility. This information can be an estimate. In this regard, the feature application can optionally add an error margin around this value to create location-specific usage target areas. For example, a company's usage target for location A could be 25%–38%, while its target for location B could be 12%–20%.
[0172] The feature application then compares the feature usage percentage for each individual operator to the feature usage target for that location, and also calculates the average usage value for operator groups (e.g., teams or shifts).
[0173] Feature applications can visualize data in widgets and related detail pages. Brief Reference Figure 6 Display (e.g., Figure 3 The graphical user interface 600 on the display 330 illustrates two small components visible on the material handling vehicle. In comparison, Figure 7The illustration shows a graphical user interface 700 on a display, which illustrates widgets on computing devices such as tablet computers, laptop computers, computer monitors, and smartphone displays.
[0174] Feature usage widget
[0175] General reference Figure 6 and Figure 7 For example, the first widget on the left side of the display visualizes a donut chart that breaks down the usage of all operator characteristics within the selected location, shift, department, and time frame into the following groups:
[0176] a) Above Target: The operator remotely moves their material handling vehicle beyond the expected range. Since this only slightly reduces the productivity gain associated with the feature, this group is illustrated with the first notation, for example, the color code shown in yellow in the application.
[0177] b) Below Target: The operator remotely moves their material handling vehicle less than expected or not at all. Because this results in significant productivity losses, this group is represented by a second symbol different from the first symbol; for example, this group is displayed in red in the application.
[0178] c) Target Usage: All operators remotely move their material handling vehicles within the target percentage. This is indicated by a third symbol, different from the first and second symbols; for example, this group is displayed in green in the application as a color code.
[0179] In the sample user experience, clicking any number takes the user to the operator usage details section. The operator usage details section provides a list of operators and their respective characteristic sets and the percentage of time spent pairing (“What is the total recorded time for the operator to pair the remote controller with the truck?”). The combination of these two values helps the user identify the reasons for low usage (or low WMS productivity).
[0180] For example, operators with a low expected pairing time percentage may have a low usage value, so a supervisor might talk to the operator and educate them on the benefits of the feature and why they should use it appropriately. On the other hand, operators with a high pairing time percentage but low usage may require additional training to understand how to best use the feature.
[0181] For example, algorithms that calculate usage details can access WMS data and automatically calculate the theoretical maximum productivity measure for any given picking machine. The theoretical maximum productivity measure can be fed back to the picking machine and used as the basis for scoring the picking machine, gamifying tasks by presenting "beat score" or "match score," or presenting visual metaphors that allow picking machines to track their actual performance against ideal performance, or a combination thereof.
[0182] As another example, by utilizing the calculated theoretical maximum value, the work rhythm can be presented to the picking machine, which provides a visual means of maintaining the picking pace.
[0183] For example, in additional embodiments, the calculated theoretical value can be used as a baseline “walking speed,” which can be displayed to the operator on a screen, or the walking speed can be represented by pulse, tone of voice, etc. Here, the algorithm can automatically tune / throttle / detune or otherwise change the theoretical maximum value relative to a particular operator’s ability, external factors, physiological factors, or a combination thereof. Examples of operator ability include variables that track operator experience, knowledge and understanding of the task, experience operating remote controls, etc. Examples of external factors include task difficulty, warehouse layout, characteristics of the material handling vehicles logged in by the operator, shift requirements, etc. Examples of physiological requirements can include variables representing biometrics, such as the number of steps taken, the number of bends, the total weight lifted, average heart rate, etc., measured at any interval (e.g., per hour, per shift, etc.).
[0184] By presenting a "pacing," the rhythm / pacing of the picking machine is set by an algorithm. In this respect, the algorithm can be dynamic and updated on a shift basis. In an example embodiment, the algorithm can tune the behavior of technical characteristics based on biometric limitations, capabilities, constraints, etc., so that the picking machine maintains a stable output over a duration (e.g., a shift) while remaining within the physiological constraints set by the algorithm.
[0185] Therefore, algorithm tuning doesn't have to be entirely based on productivity. Rather, we can see technological improvements as the algorithm is tuned relative to the operator's capabilities. This kind of pacing information can also be pushed back to the WMS to manage picking assignments.
[0186] In one implementation of the feature, a direct link can exist between automation usage and picking machine productivity. In this case, by accessing WMS data, the system can automatically calculate the theoretical maximum picking / task value for any given picking machine. This value is output to the operator, for example, via a display on the truck. Gamification can be provided in this regard, allowing the operator to see, aim, and attempt to beat the theoretically high score. Here, all usage and pairing time values can be averages over a time period selected by a timeframe filter above the list / widget.
[0187] Features, usage trends, widgets and details
[0188] As another illustrative example, the Feature Usage Trends widget and details can present all individual data points for comparing averages in the Usage Trends widget and details. The Feature Usage Trends widget and details can show the historical progress of average usage across all operators, while the details can provide graphs and comparison charts for each individual (other individuals within the filter settings or averages across all operators). Usage targets can be highlighted to easily identify when targets were achieved and when they were not. In some embodiments, trends for operator groups can be calculated based on operator shifts, operator departments, or facilities in which operators work, etc.
[0189] Connecting widgets and details
[0190] Because technical issues can limit operator access to a feature (e.g., pairing failures, etc.) and thus ultimately reduce overall productivity, another example widget provides information on the number of material handling vehicles currently operating without a paired remote and / or the number of remote controllers reporting low battery (which, over time, will cause them to disconnect from the remote control receiver of the material handling vehicle). Details of this widget provide information about the associated operators so they can be addressed and the problem resolved. In some embodiments, this feature provides a real-time view (e.g., which may be limited based on the browser's refresh rate). Assuming no technical limitations, this could occur in real time, notifying the administrator of current changes, such as operator IDs corresponding to operators XYZ now being paired, etc.
[0191] Report
[0192] In some embodiments, the data files (e.g., comma-separated value (CSV) files) generated for average usage and usage trends of operators can be exported to third-party tools, spreadsheets, for direct comparison with data extracted from the WMS, etc.
[0193] Usage status technical characteristics monitoring
[0194] refer to Figure 8 The usage and / or usage trend diagram 800 illustrates an example of communication between a material handling vehicle and a remote server, according to various aspects of this document, to perform various aspects of technology usage monitoring, and automated material handling vehicle control in response to technology usage monitoring. Diagram 800 can be, for example, via... Figure 2 Information link device 202 Figure 3 Information link device 302 and Figure 1Remote server 112 communication Figure 1 108 material handling vehicles; Figure 2 208 material handling vehicles; Figure 3 The material handling vehicle 308 is used to achieve this.
[0195] Figure 800 is largely similar to Figure 5 Figure 500. In this respect, with Figure 5 compared to, Figure 8 Similar structures are illustrated using a higher, similar reference numeral 300. Accordingly, Figure 5 The publicly available information was combined with Figure 8 The details are described in detail, and only those changes or differences are described in detail.
[0196] like Figure 8 As shown, the electronics in the material handling vehicle 808 communicate wirelessly (e.g., across network 804) in a manner similar to that about Figure 1 The described method communicates with the analysis engine 814.
[0197] Within the electronics of the material handling vehicle 808, during normal operation, the vehicle operator can use technical features 840 to, for example, activate the Automatic Positioning System (APS), activate the Automatic Fence (AF), perform mixing, press the remote automation button, operate remotely controlled driving functions, and perform technical features described more fully herein. In response, various modules on the material handling vehicle 808 respond to perform the functionality of the technical features. In this regard, information and messages are exchanged across the vehicle network 818 in the control module 820, technical features 840, and optional other vehicle electronics (e.g., reference...). Figure 3 The data is transmitted between the modules described. Example control module 820 includes sensor control module (SCM) 820A, traction control module (TCM) 820B, guidance control module (GCM) 820C, etc.
[0198] Furthermore, the industrial health monitor 842 can be communicatively coupled to the vehicle network 818. Figure 5 Unlike other embodiments, here the industrial health status monitor 842 acts as a boundary intermediary, for example, controlling the information flow related to the use (or non-use) of technical features between the corresponding material handling vehicle and the remote server. The industrial health status monitor 842 is connected to the control module 820 (and optionally, see reference 1). Figure 3The industrial health monitor 842 interacts with other vehicle electronics (described above) to collect information, send commands, and interact with control modules. For example, in an example embodiment, the industrial health monitor 842 collects technical information from various control modules, such as automation activity status information from SCM 820A, speed information from TCM 820B, and guidance acquisition status information from GCM 820C, by communicating across vehicle network 818 (e.g., CAN bus). In this respect, the industrial health monitor 842 can serve as a common boundary intermediary for one or more technical features 840 and / or other electronics on a material handling vehicle, thereby allowing for scalability and the ability to easily add technical features.
[0199] The Industrial Health Monitor 842 also communicates wirelessly with the remote module server 850, similar to the reference... Figure 5 As described. For example, in an APS system example, the Industrial Health Monitor 842 can report guidance usage by including the distance the vehicle travels online, the online distance using automatic positioning, operator ID, vehicle ID, time, other relevant data, and combinations thereof. In some embodiments, the Industrial Health Monitor 842 can report information that may include information regarding the non-use of corresponding technical features.
[0200] In some embodiments, the industrial health monitor 842 may query the control module to collect vehicle information. As another example, the industrial health monitor 842 may receive or otherwise read information circulating on a vehicle network (e.g., a CAN bus) that is part of the vehicle network 818. Furthermore, the industrial health monitor 842 may read the current value of vehicle status data actively collected and stored in memory (e.g., in a data object model), indicating the usage (or lack thereof) of corresponding technical features, etc.
[0201] In an example embodiment, the industrial health monitor 842 may include an onboard processor and memory and may communicate across vehicle network 818. This configuration allows the industrial health monitor 842 to collect and process any data that can be extracted across vehicle network 818. The industrial health monitor 842 may also be able to process received information, for example, based on a program loaded into memory, and then send the processed (or unprocessed) data to a server.
[0202] Module server 850 can be implemented as analysis engine 814 (e.g., similar to...) Figure 1The analysis engine 114) is part of a module server running on a remote server. The module server 850 feeds an Extract, Transform, Load (ETL) pipeline, which includes a set of processes for extracting data from input received from the industrial health monitor 842. Except for the corresponding technical features, the processes in the ETL pipeline can be similar to those in the reference... Figure 5 It runs as described.
[0203] For example, the ETL process may include a usage percentage process 852A that extracts data from data collected by module server 850, corresponding to the percentage of each operator using an associated technology feature. From the collected data, a usage trend process 852B extracts a trend in technology usage. The output of usage percentage process 852A and / or usage trend process 852B is a usage percentage trend widget 852C, for example, similar to... Figure 5 Small components, but for the associated technical features.
[0204] In some alternative embodiments, data collected at 852A during the percentage usage process can also be evaluated, such as through an above / below target process 854, which compares the percentage usage determination to one or more established thresholds(s). In an example implementation, the above / below target process 854 receives input from a usage target setting 856 to evaluate the percentage usage measurement recorded in the percentage usage process 852A. In this regard, the above / below target process 854 outputs a usage widget 858, the output of which includes widgets for drill-down, reporting, and combinations thereof.
[0205] Usage Percentage Trend Widget 858 provides one or more visual metaphors that graphically illustrate usage and trend information. For example, a circle chart can illustrate a measurement of the percentage of operators meeting programmed target usage compared to operators below the target for an automation feature (e.g., operators underutilizing the feature). Trend charts can be expanded to correspond to average utilization within a predetermined data range (within target compared to below target). Data from the Industrial Health Monitor 842 can also enable the system to track outages of associated automation features (e.g., loss of connection with remote controllers (or other external devices); user deactivation of the tracked automation feature; unexpected deactivation, such as due to low battery, technical malfunction; unexpected stoppage, such as due to obstacle detection or pedestrians near the AGV).
[0206] Furthermore, the output of the processing at the server can trigger workflow 860, which is described in more detail in this article.
[0207] Widgets offer technological advantages, enabling visualization not only of feature usage but also of trends and issues associated with feature usage. For example, in some embodiments, the system provides feedback commands to material handling vehicles. Feedback can be provided to tune specific features, such as performing software upgrades, calibrations, tuning, setting setpoints, establishing operating ranges, adjusting frequencies, or other parameters that affect feature performance. In some embodiments, feedback commands are provided to the operating environment, such as performing software upgrades, calibrations, tuning, setting setpoints, establishing operating ranges, adjusting frequencies, or adjusting other parameters that affect feature performance, or otherwise controlling peripheral devices that assist associated features. For example, poor performance detected in the APS could be due to poor RFID signal strength, the need for calibration, etc.
[0208] In some embodiments, feedback commands are provided to trigger workflows to achieve remediation, performance optimization, and improvements to the functionality of the corresponding material handling vehicle itself, such as controlling speed, acceleration, braking, lifting height, and geographic feature recognition by adjusting controller setpoints.
[0209] Here, the material handling vehicle can interact with the module server 850 to transmit information back to the material handling vehicle through interaction with the workflow 264, for example, by communicating directly with a remote server, remote controller, remote maintenance scheduler, or remote equipment (e.g., RFID tags, UWB badges, repeaters, mesh processors, positioning system components (such as environmental location-based markers deployed in the work environment)) to invoke maintenance, adjust equipment performance, disable equipment, enable equipment, or combinations thereof.
[0210] For example, a root cause of underutilization of a given technical feature (such as APS) could be low RFID tag health, affecting automatic positioning performance. Low RFID health can be aspects that are difficult or otherwise undetectable. Accordingly, utilization of technical features can actually spur improvements in auxiliary technologies within the operating environment of material handling vehicles. Furthermore, interruptions or trends in technology usage (including trends based on operator shifts, operator departments, or operator groups within the facilities in which operators work) can indicate equipment problems, such as mechanical defects that might be undetectable solely through electronic events / error codes.
[0211] Another example is APS movement interruption, such as when the operator cancels picking, cancels the APS, or deactivates interlocking devices (such as disconnecting sensors such as hand or foot sensors, requesting braking during APS movement, etc.).
[0212] In view of the above, the process for implementing a technical monitor for material handling vehicles includes wirelessly receiving electronic vehicle records from a fleet of material handling vehicles. Technical feature data is recorded by a controller on the material handling vehicle in response to a corresponding technical feature on the associated material handling vehicle being operated by an operator in the work environment. Each electronic vehicle record also includes an operator identifier of the operator of the material handling vehicle at the time the technical feature data is recorded.
[0213] For example, as shown in the figure, each material handling vehicle instance includes an industrial health status monitor 842, which transmits electronic vehicle records across network 804 to a module server 850 of the analysis engine 814. Each electronic vehicle record includes technical feature data recorded by at least one controller on the material handling vehicle in response to a corresponding technical feature being operated by an operator in the work environment. For example, in Figure 8 In the example, SCM module 820A transmits automated activity data to IHM 842. Furthermore, TCM 820B transmits speed data to IHM 842. Additionally, GCM transmits acquired guidance information to IHM 842. IHM 842 compresses the collected information into an electronic vehicle record, which characterizes information related to technical features, such as the distance traveled on the line and the distance traveled on the line when using APS, by sending these to module server 850.
[0214] In some embodiments, it may be desirable to track operator usage of technical features. In this case, each industrial health monitor 842 also transmits to the module server 850 the operator identifier of the material handling vehicle operator who was operating the material handling vehicle at the time the technical feature data was being recorded.
[0215] The process generates electronic measurements for each operator based on a comparison between expected technical feature usage (e.g., expressed as a threshold, such as above / below target 854) and technical feature data received in the electronic vehicle record associated with the corresponding operator (e.g., via usage process 852A and usage trend process 852B in this example).
[0216] The process also includes (for example, outputting a graphical representation of the generated measurements to the dashboard via usage percentage and trend widget 852C, usage widget 858, etc.)
[0217] In some embodiments, the system and corresponding processes may perform proactive processes, such as analyzing the generated measurements to detect the presence of equipment problems that adversely affect comparisons by at least one operator, and automatically generating electronic signals that trigger workflows at 860 to resolve detected equipment problems.
[0218] In this regard, an automatically generated workflow can be executed at point 860 to resolve the detected equipment problem by wirelessly transmitting signals to the material handling vehicle associated with the detected equipment problem to perform performance tuning on the material handling vehicle, particularly its technical characteristics or combinations thereof. Messages can also be returned as maintenance items or maintenance lists, for example, requesting the operator to re-pair, reconnect, or change settings. For example, a stream returned to module server 850 can trigger module server 850 to communicate across network 804 with the associated industrial health monitor 842, which can push any updates to the relevant control module 820.
[0219] The automatic generation of an electronic signal that triggers a workflow at 860 to resolve a detected equipment problem can also and / or alternatively be performed by wirelessly transmitting a signal to a material handling vehicle associated with the detected equipment problem to disable the technical feature. For example, a flow returning to module server 850 can trigger module server 850 to communicate across network 804 with an associated industrial health monitor 842, which can push any updates to technical feature 840, including commands to disable technical feature 840, request diagnostic data, error codes, etc.
[0220] Furthermore, the automatic generation of electronic signals that trigger workflows at 860 to address detected equipment problems can also and / or alternatively be performed by wirelessly transmitting signals to processors or devices in the work environment to perform performance tuning on equipment interacting with the technical features of the material handling vehicle. For example, the flow to workflow 860 can update electronic devices deployed in the work environment (e.g., tags, UWB badges, electronic beacons, mesh dots, communication equipment, machines, etc.).
[0221] For example, for technical features such as APS, in some embodiments, the travel path available for the automated positioning system can be defined by the guidance system. In an example implementation, sensors mounted on the material handling vehicle are used to control the vehicle's steering to detect electronic signals, such as those transmitted via wires embedded in the floor by a line driver; by positioning markers, such as RFID tags, ultra-wideband badges, reflectors and / or laser scanning systems, environmentally based position tracking devices or other navigation systems, position triangulation, dead reckoning, or combinations thereof, controlled via track guidance, etc. Here, workflow 860 can tune the material handling vehicle steering sensors, one or more guidance system devices, or combinations thereof, for example, to improve reliability, signal strength, tracking, synchronization, etc.
[0222] Furthermore, the automatic generation of electronic signals that trigger workflows at 860 points to resolve detected equipment issues can also and / or alternatively include wirelessly transmitting signals to processors in the work environment to disable equipment interacting with technical features on material handling vehicles. For example, certain features such as RFID tags or UWB badges can be programmed, reprogrammed, disabled, enabled, etc.
[0223] refer to Figure 9 The illustration shows an example dashboard output 900. The example dashboard is displayed on the screen of the material handling vehicle itself. This example demonstrates the automatic positioning technology features that diagnose low RFID health and equipment problems. Furthermore, usage trends are illustrated. Because the example dashboard output is used for display on the material handling vehicle, the graphically displayed data is directed to a specific instance of the material handling vehicle, the operator, or a combination thereof. This information enables the operator to take remedial action. In this respect, the system can distinguish between operator deficiencies in utilizing the technical features and electronic deficiencies in the corresponding technical features.
[0224] refer to Figure 10 Example dashboard output 1000 is shown on a tablet computer. Figure 9 The view and Figure 10 The difference in the view is Figure 9 The view is specific to the operator and / or the specific material handling vehicle on which the display is installed. Figure 10 The view is displayed on a tablet computer and represents data collected by multiple operators operating multiple different material handling vehicles (e.g., a fleet). Here, trends for operator groups can be calculated based on operator shifts, operator departments, or facilities in which operators work.
[0225] Comprehensive reference Figure 9 and Figure 10 Operators can see their specific statistics, identify problems with the equipment being operated, and take action to correct any detected issues. Similarly, managers can see the entire fleet or a subset of the fleet, see their specific statistics, identify problems with the equipment being operated, and take action to correct any detected issues. In some embodiments, the action to correct detected problems can be automated. For example, in some embodiments, the system learns patterns of technology usage and suggests actions to operators whose usage patterns differ from the learned system patterns. In a sense, the system acts as a coach.
[0226] Based on the dashboard, the use and trends of monitoring technologies can be used to determine how frequently / how much associated technical features (e.g., autopositioning) are used. This can trigger guidance / training activities to allow correlations to be established across technology usage scenarios, studying the ability of one or more material handling vehicles to travel the total distance on the line, to assess the percentage of the total distance traveled using the autopositioning system, and the percentage of the total distance traveled without using the autopositioning system (e.g., operating in manual mode). As a further example, the view can display usage trends to determine if changes are needed to autopositioning hardware, etc. In some embodiments, guidance is performed via onboard / dynamic guidance driven by automation computer technology. However, in some embodiments, guidance can be performed by triggering notifications to entities such as supervisors for person-to-person guidance.
[0227] As some illustrative examples, workflow 864 ( Figure 8 It can trigger and fix problems that prevent the use of technical features (e.g., for APS), identify RFID health issues, generate alerts for material handling vehicles that have not been used for a predetermined period of time, and so on.
[0228] For example, analysis of output dashboards (widgets) can reveal whether fleet-level technology feature usage trends are changing. Moreover, this visibility extends to the entire fleet, operators, or both. By establishing trends, technological elements such as layout can be correlated with changes in technology feature usage to trigger workflows.
[0229] Proficiency technical feature monitoring
[0230] refer to Figure 11 Block diagram 1100 illustrates, for example, aspects of communication between a material handling vehicle and a remote server to perform technology usage monitoring, and examples of automated vehicle control in response to technology usage monitoring, according to various aspects of this document. Figure 2 Information link device 202 Figure 3 Information link device 302 and Figure 1 Remote server 112 communication Figure 1 108 material handling vehicles; Figure 2 208 material handling vehicles; Figure 3 The material handling vehicle 308 is used to achieve this.
[0231] Figure 1100 is largely similar to Figure 5 Figure 500 and / or Figure 8 Figure 800. Similar structures exist in this regard. Figure 11 Chinese usage ratio Figure 8The high-resolution version is shown by reference numeral 300, and in Figure 11 Chinese usage ratio Figure 5 A similar figure to 600 is shown. Accordingly, Figure 5 and Figure 8 Combined with publicly available content Figure 11 The details are described in detail, and only those changes or differences are described in detail.
[0232] like Figure 11 As shown, the electronics of the material handling vehicle 1108 include multiple control modules communicatively coupled to the vehicle network 1118. For example, in the illustrated example, the control modules include a sensor control module (SCM) 220A, which outputs data such as whether a hand is on a presence sensor, whether a task is being performed, whether automation is active, and whether picking is active. The control modules may also include a vehicle control module (VCM) 1120B. VCM 220B outputs data such as indications about whether a pedal is pressed or a door is closed.
[0233] The electronics of the material handling vehicle 1108 also include technical features 1140, such as mixing, APS, remote control, shelf height selection, etc., as described more fully in this article.
[0234] Furthermore, the industrial health status monitor 1142 is communicatively coupled to the vehicle network 1118. Figure 8 Similar to that described herein, the industrial health monitor 1142 acts as a boundary intermediary, for example, controlling the flow of information between corresponding material handling vehicles and remote servers (e.g., module server 1150). The industrial health monitor 1142 collects technical information from various control modules 1120, such as skill level event types, operator identification, vehicle identification, timestamps, etc. Furthermore, the industrial health monitor 1142 communicates with the module server 1150 across communication paths (such as Wi-Fi), as shown in network 1104.
[0235] Module server 1150 feeds an ETL pipeline comprising a set of processes that extract data from input received from industrial health monitor 1142. The processes in the ETL pipeline collectively transform the data and then load it to an output destination for reporting, analysis, and data synchronization. For example, an ETL process may include an event proficiency process 1152, whose output is to a proficiency widget 1154. In some embodiments, proficiency widget 1154 also provides drill-down reports to visualize underlying data contributing to the widget's output on a display.
[0236] The proficiency widget 1154 generates widget data that can trigger workflows based on proficiency. For example, the proficiency widget 1154 can communicate with the module server 1150 (e.g., the module server 1150 can read the widget's value and / or drill down for details) and send commands back to the material handling vehicle 1108 based on the data values, such as performing performance tuning on the vehicle, performing performance tuning on the associated technical feature 1140, updating or repairing the technical feature, locking the vehicle, or taking some other action to improve the operation of the technical feature.
[0237] In some embodiments, communication from module server 1150 back to material handling vehicle via industrial health monitor 1142 may include instructions, training or other operator driving tips to improve operator interaction with technical feature 1140.
[0238] The output of the proficiency widget 1154 can also drive workflow 1164, enabling improvements, repairs, or other modifications to the technical feature 1140 via electronic control of the operating environment in which it operates. For example, feedback and workflow can be used to diagnose and repair problems hindering the use of the technical feature. For instance, the system can immediately identify and resolve RFID tag health issues, Location Information Module (LIM) problems (e.g., updating RFID readers, slot maps, tag map logic for automated positioning systems, logic for automated fence systems, etc.), and send alerts to vehicles and / or management systems to indicate that the technical feature 1140 of a material handling vehicle has not been used for a period of time.
[0239] In some embodiments, feedback is directed back to the operator, for example, via instruction, affirmative confirmation, correction, or other appropriate messaging. Feedback may be based on comparison with baseline data. Here, because the entire fleet has been evaluated, the system knows which operators to instruct and what to instruct them on based on collected technology usage data.
[0240] As a non-limiting example, by understanding the relative relationships between technical feature interruptions (e.g., sensors instructing operators to remove their hands from necessary controls, feet from necessary pedals, tasks being cancelled, doors opening, etc.), these interruptions can then be counted, organized, evaluated, and presented back to the operator (e.g., via a truck display). Figure 9 ) or returned to the administrator (e.g., via tablet computer) Figure 10 ).
[0241] System status
[0242] refer to Figure 12Block diagram 1200 illustrates, for example, aspects of communication between a material handling vehicle and a remote server to perform technology usage monitoring, and examples of automated vehicle control in response to technology usage monitoring, according to various aspects of this document. Block diagram 1200 can be, for example, via... Figure 2 Information link device 202 Figure 3 Information link device 302 and Figure 1 Remote server 112 communication Figure 1 108 material handling vehicles; Figure 2 208 material handling vehicles; Figure 3 The material handling vehicle 308 is used to achieve this.
[0243] Figure 1200 is largely similar to Figure 5 Figure 500 Figure 8 Figure 800 Figure 11 Figure 1100 or a combination thereof. In this respect, similar structures exist in... Figure 12 Chinese usage ratio Figure 11 The higher one is shown with similar reference numeral 100; in Figure 12 Chinese usage ratio Figure 8 The higher one is shown by reference numeral 400, and in Figure 12 Chinese usage ratio Figure 5 A similar figure to 700 is shown. Accordingly, Figure 5 , Figure 8 and Figure 11 Combined with publicly available content Figure 12 The details are described in detail, and only those changes or differences are described in detail.
[0244] like Figure 12 As shown, the electronics of the material handling vehicle 1208 include multiple control modules 1220 communicatively coupled to a vehicle network 1218. For example, in the illustrated example, the control modules include a sensor control module (SCM) 1220A, which outputs data such as whether picking has been accepted. The control module 1220 may also include a location information module (LIM) 1220B. The LIM 1220B outputs data such as whether a module malfunction has occurred, tag health status indications, etc.
[0245] Furthermore, the industrial health status monitor 1242 is communicatively coupled to the vehicle network 1218. Similar to other embodiments, the industrial health status monitor 1242 serves as a boundary intermediary, for example, controlling the flow of information between the corresponding material handling vehicle and a remote server (e.g., module server 1250).
[0246] The industrial health monitor 1242 is connected to various control modules 1220 (and optionally, see reference 1220). Figure 3Other vehicle electronics described collect technical information, such as proficiency event types, operator identification, vehicle identification, timestamps, etc.
[0247] The module server 1250 collects information from the industrial health monitor 1242, such as information related to whether picking has been accepted and associated timestamps, fault conditions, tag IDs, tag health status, etc.
[0248] Module server 1250 also feeds an ETL pipeline comprising a set of processes that extract data from inputs received from industrial health monitor 1242. For example, the ETL process may include a last pick acceptance process 1252, whose output indicates the last pick accepted by each material handling vehicle. The ETL may also include module status 1254, which outputs status information regarding technical feature 1240. Furthermore, the ETL includes an environmental status process 1256. The environmental status process outputs the status of electronic equipment deployed in the operating environment supporting the corresponding technical feature. For example, in the context of an automated positioning system, environmental status process 1256 may collect and output data related to RFID tags, UWB badges, etc., which work in conjunction with automated positioning controls on the corresponding material handling vehicle.
[0249] Finally, the selection process 1252, module status process 1254, and environment status process 1256 are each output to the system status widget 1258. In some embodiments, the system status widget 1258 may also output a drill-down report to visualize underlying data that contributes to the widget's output on a display, as described more fully herein.
[0250] The system status widget 1258 generates widget data that can trigger workflows based on the system status of the corresponding technical feature 1240. For example, the system status widget 1258 can communicate with the module server 1250 (e.g., the module server 1250 can read the widget's value and / or drill down for details) and send commands back to the material handling vehicle 1208 based on the data values, such as performing performance tuning on the vehicle, performing performance tuning on the associated technical feature 1240, updating or repairing the technical feature, locking the vehicle, or taking some other action to improve the operation of the technical feature.
[0251] In some embodiments, communication from module server 1250 back to material handling vehicle 1208 via industrial health monitor 1242 may include instructions, training or other operator driving tips to improve operator interaction with technical feature 1240.
[0252] The output of the system status widget 1258 can also drive workflow 1260, enabling improvements, repairs, or other modifications to the technical feature 1240 via electronic control of the operating environment in which the technical feature 1240 operates. For example, feedback and workflows can be used to diagnose and repair problems hindering the use of the technical feature in a manner similar to that described in more detail herein. For example, the system can identify and resolve issues such as RFID tag health status, UWB badge health status, LIM problems, and generate alarms when a technical feature on an associated material handling vehicle 1208 is not used for a predetermined amount of time.
[0253] In practical applications, the widget can output drill-down information such as alarm status (e.g., new, old, resolved, etc.). The widget's drill-down information can also include the date and the type of health issue. As a non-limiting example, in the case of an automated positioning system, health issues can be presented as location-based problems (e.g., location information mode failure), vehicle electronics failures (e.g., steering control mode failure), load handling automation health issues (e.g., hydraulic automation control mode failure), identifying recurring similar event codes, etc.
[0254] As another example, output drill-down can identify the type of environmental asset supporting onboard technology features (e.g., RFID tags, UWB badges) and the status of the asset. For instance, drill-down can list RFID tags, the identifier used for those RFID tags, the tag location, and the most recent events associated with the asset (e.g., depleted health, low battery, poor communication, etc.). Drill-down can also identify technology feature issues, such as by outputting the identifier of the technology feature, the vehicle on which the technology feature is mounted, the location of the material handling vehicle associated with the technology feature, and the most recent event code associated with the technology feature (e.g., lost connection to industrial vehicle data (see [link]). Figure 1 118), loss of connection to the warehouse management system (see [link]). Figure 1 WMS data 120), connection to LIM data lost (see WMS data 120), connection ... Figure 1 LMS data 122), loss of connection with location information (see LMS data 122), and loss of connection with location information (see LMS data 122). Figure 1 (Geographic data 124). The output can also identify module faults with technical characteristics, such as module fault data of sensors or controllers on material handling vehicles that supply data to the IVM1240.
[0255] Map Status
[0256] refer to Figure 13 Block diagram 1300 illustrates an example of communication between a material handling vehicle and a remote server according to various aspects of this document. Block diagram 1300 can be, for example, via... Figure 2 Information link device 202 Figure 3 Information link device 302 and Figure 1 Remote server 112 communication Figure 1 108 material handling vehicles; Figure 2 208 material handling vehicles; Figure 3 The material handling vehicle 308 is used to achieve this.
[0257] Figure 1300 is largely similar to Figure 5 Figure 500 Figure 8 Figure 800 Figure 11 Figure 1100 Figure 12 Figure 1200 or a combination thereof. In this respect, similar structures exist in... Figure 13 Chinese usage ratio Figure 12 The high-resolution version is shown by reference numeral 100, in Figure 13 Chinese usage ratio Figure 11 The higher similar reference numeral 200 is shown, in Figure 13 Chinese usage ratio Figure 8 The high-resolution version is shown by reference numeral 500, and in... Figure 13 Chinese usage ratio Figure 5 A similar figure to 800 is shown. Accordingly, Figure 5 , Figure 8 , Figure 11 and Figure 12 Combined with publicly available content Figure 13 The details are described in detail, and only those changes or differences are described in detail.
[0258] like Figure 13 As shown, the electronics of the material handling vehicle 1308 include multiple control modules 1320 communicatively coupled to the vehicle network 1318. For example, in the illustrated example, the control module includes a Location Information Module (LIM) 1320A. The LIM 1320A outputs data such as a time-slot map version, an RFID tag map version, an ultra-wideband badge map version, etc., utilized by the material handling vehicle 1308.
[0259] Furthermore, the industrial health status monitor 1342 is communicatively coupled to the vehicle network 1318. Similar to other embodiments, the industrial health status monitor 1342 serves as a boundary intermediary, for example, controlling the flow of information between the corresponding material handling vehicle and a remote server (e.g., module server 1350).
[0260] The industrial health monitor 1342 collects technical information from the electronics of the industrial vehicle 1308, such as information from the control module 1320A, including timeslot map versions, RFID tag map versions, and ultra-wideband badge versions. Furthermore, the industrial health monitor 1342 communicates with the module server 1350 across communication paths (such as Wi-Fi), as shown in network 1304.
[0261] The module server 1350 collects information from the industrial health monitor 1342, such as information related to whether picking has been accepted and associated timestamps, fault status, tag IDs, tag health status, etc.
[0262] The module server 1350 also feeds an ETL pipeline, which includes a set of processes that extract data from inputs received from the industrial health monitor 1342. For example, the ETL process may include a map versioning process 1352, which outputs indications of time-slot map versions, RFID tag map versions, ultra-wideband badge map versions, etc.
[0263] Map versioning process 1352 outputs to map versioning widget 1354. In some embodiments, map versioning widget 1354 may also output a drill-down report to visualize underlying data that contributes to the widget's output on a display, as described more fully herein.
[0264] Map version widget 1354 generates widget data that can trigger workflows based on the system status of the corresponding technical feature 1340. For example, map version widget 1354 can communicate with module server 1350 (e.g., module server 1350 can read widget values and / or drill down for details) and send commands back to material handling vehicle 1308 based on the data values, such as performing performance tuning on the vehicle, performing performance tuning on the associated technical feature 1340, updating or repairing the technical feature, locking the vehicle, or taking other actions to improve the operation of the technical feature.
[0265] In some embodiments, communication from module server 1350 back to material handling vehicle 708 via industrial health monitor 1342 may include instructions, training or other operator driving tips to improve operator interaction with technical feature 1340.
[0266] The output of the map version widget 1354 can also drive workflow 1360, enabling improvements, repairs, or other modifications to the technical feature 1340 via electronic control of the operating environment in which the technical feature 1340 operates. For example, feedback and workflow can be used to diagnose and repair problems hindering the use of the technical feature. For example, the system can immediately identify and resolve problems such as map issues, environmental positioning problems of electronic tags (e.g., location information of RFID tags, UWB badges, etc.). This workflow also ensures that each material handling vehicle 1308 has a correct and updated map using an automated electronic allocation mechanism. In this way, the merged dashboard view visualizes data that confirms each material handling vehicle with the associated technical feature 1340 has the correct map loaded into the local memory of the vehicle controller.
[0267] Physiological input for technical feature tuning
[0268] In some embodiments, the system described herein uses specific operator data (e.g., data that may be collected by wearable trackers, alert monitors, health trackers, etc., as tracker data) to fine-tune the system, for example, for close-range communication between walking or cycling to determine when automation or remote control should be implemented, etc.
[0269] For example, the system can weigh whether to provide guidance, assistance, automation, remote control, etc., depending on the operator's health tracker data, and optionally other data, such as at what point in the shift the operator is. For instance, if the system identifies that the operator slows down while walking due to fatigue later in the shift (e.g., based on pace extracted from generated records collected during the shift), then the operating parameters of technical features such as remotely controlled driving can be adjusted. Moreover, the operator's physical condition, mental alertness, their combination, and other factors can be used not only to "tune" when to use or not use a feature (e.g., remotely controlled driving function), but also to "tune" how the function operates, for example, by tuning acceleration, braking, speed limits, etc., to perform optimally within the operator's capabilities.
[0270] Therefore, this paper brings about technical improvements in intelligent equipment control, which is based on the operator's physiological state to adjust the technical characteristics of the operation.
[0271] diversity
[0272] Various workflows (e.g., Figure 5 Workflow 560 Figure 8 Workflow 860 Figure 11 Workflow 1160 Figure 12 Workflow 1260 Figure 13 Workflow 1360 and other actions (e.g., initiated by a controller on a material handling vehicle) can be executed based on decisions made using a rules engine. Here, the rules engine can encode actions based on input conditions to trigger outputs in a consistent manner. For example, the rules engine on the server, the material handling vehicle (or both) can define parameters for evaluating the use of technical features relative to correct usage, define remedial measures, define messages including instructions and guidance messages, the display of control information on widgets, and so on.
[0273] Various aspects of this disclosure enable managers to immediately access their characteristic usage data in a clear and concise manner. Visually comparing operators to targets helps end users easily and promptly identify operators requesting assistance with technical characteristics. Moreover, in some embodiments, the visual format of the dashboard's graphical user interface is designed for access from mobile devices, thereby facilitating individual discussions with operators. Automation and integration with remote servers also enable workflows to correct errors, malfunctions, and problems that are not directly related to operator use / misuse / non-use.
[0274] Various aspects of this disclosure provide new feature usage targets. In some embodiments, the process identifies the percentage area of feature usage targets based on an assessment of facility-specific factors such as average picking room distance, aisle length, and picking patterns, as well as historical WMS data (picking lists). If this data is provided via a gateway between material handling vehicle data and the WMS, this assessment can also be performed automatically on each picking run. This allows for environment-based customization.
[0275] The various aspects of this paper also provide browsable information about operator usage above / below / target levels. Furthermore, the dashboard facilitates operator grouping based on usage, thereby enabling operator identification with additional training requirements. The various aspects of this paper also provide a "pairing time" metric, which measures the duration of recorded time periods, and operators also have remote controls paired with corresponding material handling vehicles.
[0276] In some embodiments, the system can use vehicle data and intelligence to distinguish where the use of technical features should be considered. In this embodiment, travel where the use of technical features is not appropriate (e.g., remotely controlled travel) is not counted in the total travel. For example, if steering wheel data indicates that a material handling vehicle is traveling in an arc, then an application on the material handling vehicle can infer that the operator has reached the end of an aisle and is entering an adjacent aisle. Here, remotely controlled travel is not appropriate. Accordingly, this distance is not counted as a percentage of the total travel distance on those dashboards (e.g., Figure 6 , Figure 7As another example, if location tracking positions a material handling vehicle in a non-picking area, the distance traveled in that non-picking area is not counted. Furthermore, geographic features can be used to mark picking aisles. Here, as the material handling vehicle enters the aisle and encounters a geographic feature, the system begins to accumulate the travel distance as a "total distance," etc.
[0277] In other embodiments, the range used to construct the dashboard can elicit feedback to material handling vehicles to modify their performance. For example, the range can tune the feedback to material handling vehicles, such as setting maximum remote control travel distance, travel speed, limiting the number of times features are used, etc. Therefore, dynamic tuning can enhance dynamic guidance.
[0278] Material handling vehicle perspective
[0279] As noted in more detail herein, the controller on the material handling vehicle runs program code to generate a vehicle log, which includes data related to the material handling vehicle, such as driving data, technical feature usage data, sensor data, etc. For example, the vehicle controller can read odometer data, for instance, by reading data transmitted across the vehicle network from the traction controller. Vehicle-related driving data may also include pairing status (whether the material handling vehicle is paired with a wireless remote control, the battery level of that control, etc.). Feature activation can be detected by recognizing commands such as pressed instruction buttons, starting to stand still by counting, driving, and then returning to stand still under remote control. Moreover, in some embodiments, the operator must log in to the material handling vehicle before it can be properly operated. Accordingly, usage can be associated with the operator rather than the material handling vehicle itself.
[0280] In the example embodiment, a record is created each time the material handling vehicle moves. This record may include measured data, calculated data, combinations thereof, etc. The controller is also programmed to transmit the generated vehicle record to a remote server to document this usage.
[0281] In some embodiments, for example, when implementing a remotely controlled driving function, the controller is also programmed to detect material handling driving in response to the interruption of the remotely controlled driving function (because the obstacle sensor on the material handling vehicle detects an obstacle in the material handling vehicle's driving path, causing the material handling vehicle to stop). Here, the controller generates a vehicle record consisting of material handling vehicle driving data associated with the remotely controlled driving function and obstacle detection, and transmits the generated vehicle record to a remote server to record the activation of the obstacle sensor on the material handling vehicle.
[0282] In other embodiments, the controller is also programmed to receive reports from a remote server and output the received reports to a display mounted on the material handling vehicle. Here, the report graphically displays a representation of the usage of the remotely controlled driving function over a predetermined time period. In some embodiments, the graphical representation of the usage of the remotely controlled driving function includes a graphical visualization of the total distance traveled by the material handling vehicle in response to the remotely controlled driving function and the total distance traveled by the material handling vehicle without using the remotely controlled driving function. Furthermore, in some embodiments, the graphical representation includes a graph of the distance traveled in the total travel distance of the material handling vehicle over the predetermined time period. For example, the graphical representation may be expressed as a percentage of travel distance in response to the remotely controlled driving feature relative to the total travel distance.
[0283] In another example embodiment, the controller is also programmed to receive reports from a remote server and output the received reports to a display mounted on the material handling vehicle. Here, the report graphically outputs a trend of the remote-controlled driving function's usage over a predetermined time period to the display on the material handling vehicle, wherein this trend overlaps with a target area range defined by the expected range of remote-controlled driving in total driving, extracted from warehouse management system data.
[0284] In a further embodiment, the controller is also programmed to receive reports from a remote server and output the received reports to a display mounted on the material handling vehicle. Here, the report is graphically displayed on the display on the material handling vehicle, representing the time for which the operator will maintain the remote control device paired with the remote control receiver for a predetermined period of time.
[0285] Furthermore, in a further embodiment, the controller is also programmed to receive instructions from a remote server to modify the performance parameters of the material handling vehicle in response to vehicle records associated with the operator within a predetermined time period, and to transmit commands to at least one electronic control module via cross-vehicle network messages to modify the performance of the material handling vehicle.
[0286] observe
[0287] The aspects of this article can be applied to any additional technologies or auxiliary systems equipped on material handling vehicles. Data and metrics regarding technology usage (e.g., frequency of auxiliary system use) can be compared with other productivity metrics (e.g., pallets moved from the WMS per hour). This comparison can help identify underutilization of auxiliary technologies as a root cause of poor operator performance.
[0288] refer to Figure 14The diagram depicts a block diagram of a data processing system according to the present disclosure. The data processing system 1400 includes one or more processors 1410 connected to a memory 1420 across a system bus 1430. A bus bridge 1440 is connected to the system bus 1430 and provides an interface to any number of peripheral devices, for example via an I / O bus 1450. Example peripheral devices include a storage device 1460 (e.g., a hard disk drive), a removable media storage device 1470 (e.g., a tape drive, CD-ROM drive, flash drive, etc.), I / O 1480 (e.g., a keyboard, mouse, monitor, etc.), a network adapter 1490, or a combination thereof.
[0289] Memory 1420, storage device 1450, removable medium storage 1460, or combinations thereof, can be used to implement a computer-usable storage medium on which computer-usable program code is implemented. The computer-usable program code is read out and processed to implement any aspect of this disclosure, for example, to implement any aspect of any method and / or system component illustrated in the preceding figures.
[0290] As those skilled in the art will recognize, aspects of this disclosure can be implemented as systems, methods, or computer program products. Furthermore, aspects of this disclosure can take the form of computer program products implemented on one or more computer-readable storage media having computer-readable program code implemented thereon.
[0291] The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code, including one or more executable instructions for implementing one or more specified logical functions. In some alternative implementations, the functions marked in the blocks may not appear in the order indicated in the figures.
[0292] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit this disclosure. As used herein, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that, when used in this specification, the terms “comprising” and / or “including” specify the presence of the stated features, integers, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.
[0293] All components or steps in the following claims, plus the corresponding structures, materials, actions, and equivalents of the functional elements, are intended to include any structure, material, or action for performing a function in combination with other claimed elements as specifically claimed.
Claims
1. A process for implementing a technical monitor for material handling vehicles, comprising: Electronic vehicle records are wirelessly received from material handling vehicles with technical features. Each electronic vehicle record includes: Technical feature data recorded by the controller on the material handling vehicle in response to the operator selecting engagement technical features while the material handling vehicle is being operated in the work environment; and Operator identification of the material handling vehicle operator when recording technical characteristic data; Electronic measurements are generated based on a comparison between the expected technical feature usage targets and the technical feature data in the received electronic vehicle records; Output a graphical representation of the generated measurements to the display on the material handling vehicle; and When the technical feature data deviates from the expected technical feature usage target by a predetermined threshold, an automated action is performed to correct the deviation.
2. The process as described in claim 1, wherein: The expected usage target for a technical feature is defined by a target usage threshold representing the percentage of time a specified technical feature is used; and The target usage threshold is defined as the percentage of time a technical feature is correctly used, as specified by the rule engine, which defines parameters for evaluating technical feature usage as correct usage. The process also includes: Based on the target usage threshold, the system detects that the operator recorded at least one instance of incorrect use of the technical feature; and When the operator has recorded at least one instance of incorrect use of the technical feature, a guidance message providing instructions on how to use the technical feature is output to the display on the material handling vehicle.
3. The process of claim 1, wherein the technical features include an automatic positioning system that requires the operator to engage controls on the material handling vehicle, the controls being coupled to a control module that communicates across a vehicle network.
4. The process of claim 3 further includes detecting errors in the automatic positioning system based on the generated measurements.
5. The process of claim 3 further includes detecting performance errors of vehicle components of a material handling vehicle with an automatic positioning system based on the generated measurements.
6. The process as described in claim 3, wherein: The technical characteristic data recorded by the controller on the material handling vehicle includes at least one of the following: the distance the material handling vehicle travels under wired guidance, the distance the material handling vehicle travels under wired guidance using an automatic positioning system, or the distance the material handling vehicle travels under wired guidance in manual mode without using an automatic positioning system. as well as The generation of electronic measurements includes: calculating the automatic positioning system usage based on the distance traveled by associated material handling vehicles using the automatic positioning system under wired guidance relative to the distance traveled under wired guidance, and comparing the calculated automatic positioning system usage with a pre-programmed target usage percentage.
7. The process of claim 1, further comprising: Calculate trends for operators, material handling vehicles, or both; as well as The calculated trend is compared with the expected trend parameters to identify deviations from the operator's trend.
8. The process of claim 7, wherein: Calculating trends for operators, material handling vehicles, or both also includes calculating trends for groups of operators based on operator shifts, operator departments, or facilities in which operators work.
9. The process of claim 8, further comprising: Output a message to the display on the material handling vehicle: If the operator's trend deviates positively, then the message includes positive reinforcement information; as well as If the operator's trend deviates negatively, then the message includes negative reinforcement information.
10. The process of claim 8, further comprising: When the operator's trend deviates negatively, a message is output to the display on the material handling vehicle, the message including a training message instructing the operator to operate the material handling vehicle correctly.
11. The process of claim 1, wherein: The technical feature data recorded by the controller on the material handling vehicle includes at least one of the following: Collect activation information from the sensor control module; Speed information is collected from the traction control module; or Collect boot information from the boot control module; and The process also includes calculating at least one of usage or usage trends based on predetermined usage target settings.
12. The process of claim 1, further comprising: Analyze the generated measurements to detect any detectable equipment problems that could adversely affect comparisons by at least one operator; as well as An electronic signal is automatically generated, which triggers a workflow to resolve detected equipment problems through the following operations: The signal is wirelessly transmitted to the material handling vehicle associated with the detected equipment problem in order to perform performance tuning of the technical features. or The signal is wirelessly transmitted to the material handling vehicle associated with the detected equipment problem to disable the technical feature.
13. The process of claim 1, wherein performing the automated action comprises: Issue an electronic command to modify at least one operating parameter of the technical feature.
14. The process of claim 13, wherein: Issuing a command includes issuing a command to execute at least one of the following: Software update; calibration; Tuning; Set up the set points; Set the operation scope; or Adjust the frequency.
15. A process for implementing a monitor for a material handling vehicle with remote control features, comprising: Electronic vehicle records are wirelessly received from the material handling vehicle being operated by the corresponding operator in the work environment. Each electronic vehicle record includes: Data related to the movement recorded by the controller on the material handling vehicle; and Operator identification for the corresponding operator of the material handling vehicle; Parse vehicle records within a predetermined time period to extract dashboard data, which includes: The first distance traveled by the material handling vehicle within a predetermined time period in response to the corresponding operator using the remote-controlled driving function; and The total distance traveled by material handling vehicles within a predetermined time period; Establish the expected driving distance under remote control relative to the total driving distance within a predetermined time period; An electronic measurement of the expected remotely controlled driving distance is generated by comparing the recorded total driving distance within a predetermined time period with the remotely controlled driving distance; and Output a graphical representation of the generated measurements to the dashboard.
16. The process of claim 15, further comprising: The electronic measurement of the distance traveled under remote control relative to the total distance traveled within a predetermined time period, compared with the recorded distance traveled under remote control relative to the total distance traveled within a predetermined time period, is analyzed by the corresponding operator. Based on the analysis, modifications were selected to the material handling vehicle control; and Modifications to the material handling vehicle's control are wirelessly transmitted to the material handling vehicle, which then automatically implements these modifications to affect its operation.
17. The process of claim 15, wherein: Wirelessly receiving electronic vehicle records from material handling vehicles includes receiving electronic vehicle records indicating whether: Driving occurs when the remote control device is paired with the remote control receiver; and Travel occurs due to the operation of a remote control device paired with a remote control receiver of a material handling vehicle to enable remote control of the driving function; as well as Outputting graphical representations of the generated measurements to the dashboard also includes outputting the following graphical representations: Operators of control features who have been paired but are not operating remote control devices; Compared to the target usage, the operators use the control features too infrequently; Operators who use control features too frequently compared to the target usage parameters; or The amount of time required for the remote control device to pair with the remote control receiver of the corresponding material handling vehicle.
18. The process of claim 15, further comprising: The instructions provide guidance on a technical problem concerning the implementation of remote-controlled driving functionality by a remote control device paired with a remote control receiver of a material handling vehicle, wherein the guidance on the technical problem includes at least one of the following: Pairing failed; Operating material handling vehicles without remote pairing; as well as The number of remote controls reporting low battery levels; as well as The command is sent back to the material handling vehicle that reported the technical problem, so that the performance of the material handling vehicle can be modified to remedy the technical problem.
19. The process of claim 15, wherein: Establishing the expected driving distance under remote control relative to the total driving distance includes establishing the expected driving distance under remote control relative to the total driving distance as a range of ratios of driving distance under remote control to total driving distance. as well as The graphical representation of the generated measurements output to the dashboard includes an output remote control usage trend graph, which shows the trend of operator use of control features on a remote control device paired with a remote control receiver of a corresponding material handling vehicle to enable remote control driving functions over time.