Method and apparatus for monitoring and managing the operation of a loading dock

Abstract

A method and apparatus for monitoring and managing loading dock operations is disclosed. The exemplary apparatus includes a sensor feedback analyzer for analyzing feedback from sensors associated with a dock of a material handling facility and determining, based on the feedback, a duration for completion of a task in a sequence of operations associated with loading or unloading a trailer at the dock. The apparatus also includes an efficiency analyzer for comparing the duration to a target threshold associated with the task. The apparatus further includes a user interface generator for generating a user interface indicative of at least one of the duration or the target threshold.

Description

Field of Disclosure

[0001]

[0001] This disclosure generally relates to loading docks, and more particularly to methods and apparatus for monitoring and managing the operation of loading docks. Background

[0002]

[0002] A loading dock provides an area for a vehicle (e.g., a truck, trailer, etc.) to move next to a high platform of a building (e.g., a material handling facility) so that goods can be easily transferred between the vehicle and the building. Some loading docks include equipment such as dock levelers, vehicle restraint devices, and / or dock doors, all of which can be associated with one or more sensor / monitoring systems.

Brief Description of the Drawings

[0003] [Figure 1] A diagram showing an exemplary material handling facility in which the teachings disclosed herein can be implemented. [Figure 2] A diagram showing the exemplary loading dock of FIG. 1 as seen from outside the material handling facility. [Figure 3] A diagram showing the exemplary loading dock of FIG. 1 as seen from inside the material handling facility with a trailer parked at the dock. [Figure 4] A cross-sectional side view showing the exemplary loading dock of FIG. 1 together with the associated trailer of FIG. 3. [Figure 5] A diagram showing an exemplary user interface that can be provided via the local status indicator of FIG. 3 when consecutive tasks in an operation sequence associated with loading and / or unloading a trailer at a particular dock are completed. [Figure 6] A diagram showing an exemplary user interface that can be provided via the local status indicator of FIG. 3 when consecutive tasks in an operation sequence associated with loading and / or unloading a trailer at a particular dock are completed. [Figure 7]This figure shows an exemplary user interface that can be provided via the local status indicator in Figure 3 when a series of tasks in an operational sequence associated with loading and / or unloading a trailer at a specific dock are completed. [Figure 8] This figure shows an exemplary user interface that can be provided via the local status indicator in Figure 3 when a series of tasks in an operational sequence associated with loading and / or unloading a trailer at a specific dock are completed. [Figure 9] This figure shows an exemplary user interface that can be provided via the local status indicator in Figure 3 when a series of tasks in an operational sequence associated with loading and / or unloading a trailer at a specific dock are completed. [Figure 10] This figure shows an exemplary user interface that can be provided via the local status indicator in Figure 3 when a series of tasks in an operational sequence associated with loading and / or unloading a trailer at a specific dock are completed. [Figure 11] This figure shows an exemplary user interface that can be provided via the local status indicator in Figure 3 when a series of tasks in an operational sequence associated with loading and / or unloading a trailer at a specific dock are completed. [Figure 12] This figure shows an exemplary user interface that can be provided via the local status indicator in Figure 3 when a series of tasks in an operational sequence associated with loading and / or unloading a trailer at a specific dock are completed. [Figure 13] This is a block diagram of an exemplary implementation of the exemplary controller shown in Figure 1. [Figure 14] Figure 1 is a block diagram of an exemplary implementation of the main server. [Figure 15] This figure shows an exemplary graphical user interface that can be generated by the main server in Figure 1 and / or Figure 14. [Figure 16]This figure shows an exemplary graphical user interface that can be generated by the main server in Figure 1 and / or Figure 14. [Figure 17] This figure shows an exemplary graphical user interface that can be generated by the main server in Figure 1 and / or Figure 14. [Figure 18] This figure shows an exemplary graphical user interface that can be generated by the main server in Figure 1 and / or Figure 14. [Figure 19] This figure shows an exemplary graphical user interface that can be generated by the main server in Figure 1 and / or Figure 14. [Figure 20] This figure shows an exemplary graphical user interface that can be generated by the main server in Figure 1 and / or Figure 14. [Figure 21] This figure shows an exemplary graphical user interface that can be generated by the main server in Figure 1 and / or Figure 14. [Figure 22] This figure shows an exemplary graphical user interface that can be generated by the main server in Figure 1 and / or Figure 14. [Figure 23] This figure shows an exemplary graphical user interface that can be generated by the main server in Figure 1 and / or Figure 14. [Figure 24] This flowchart shows exemplary machine-readable instructions that can be executed to implement the exemplary main server in Figure 1 and / or Figure 14. [Figure 25] This flowchart shows exemplary machine-readable instructions that can be executed to implement the exemplary main server in Figure 1 and / or Figure 14. [Figure 26] This flowchart shows exemplary machine-readable instructions that can be executed to implement the exemplary main server in Figure 1 and / or Figure 14. [Figure 27] This flowchart shows exemplary machine-readable instructions that can be executed to implement the exemplary main server in Figure 1 and / or Figure 14. [Figure 28] This is a block diagram of an exemplary processing platform configured to implement the exemplary main server in Figure 1 and / or Figure 14 by executing the instructions in Figure 3. Detailed explanation

[0004]

[0013] These figures are not proportional to actual size. Instead, the thickness of these layers or regions may be enlarged in these drawings. Generally, the same reference numeral is used to refer to the same or similar part throughout the drawings and accompanying specification. When used in this patent, a description that any part (e.g., a layer, film, area, region, or plate) is in any way above another part (e.g., positioned above, located above, placed above, or formed above) indicates that the referenced part is in contact with the other part, or that the referenced part is above the other part and that one or more intermediate parts are located between them. References relating to connections (e.g., attached, joined, connected, and joined) should be interpreted broadly and may include intermediate members between a group of elements and relative movement between elements unless otherwise indicated. Thus, a reference to connections does not necessarily presume that two elements are directly connected and in a fixed relationship with one another. A description that any part is "in contact" with another part means that there is no intermediate part between these two parts. These diagrams depict layers and regions with clear lines and boundaries, although some or all of these lines and / or boundaries may be idealized. In reality, boundaries and / or lines may be unobservable, fused, and / or irregular.

[0005]

[0014] In this specification, descriptive terms such as “first,” “second,” and “third” are used to identify multiple elements or components that may be referred to separately. Unless otherwise specified or understood based on the context in which they are used, such descriptive terms are not intended to imply any meaning of priority, physical order or arrangement in a list, or temporal order, but are used solely as labels to refer to multiple elements or components separately in order to facilitate understanding of the examples disclosed. In some examples, the descriptive term “first” may be used to refer to a certain element in the detailed description, but the same element may also be referred to by different descriptive terms such as “second” or “third” in the claims. In such cases, it should be understood that such descriptive terms are used solely to facilitate reference to multiple elements or components.

[0006]

[0015] Figure 1 shows an exemplary material handling facility 100 that can implement the teachings disclosed herein. The material handling facility 100 can be associated with, for example, a storage warehouse, distribution center, manufacturing plant, retail store, etc. In the example described, the material handling facility 100 includes a number of loading docks 102 (two shown) that provide a platform for trucks to back up their trailers (or truck beds) to load and / or unload materials between the inside of the trailer and the material handling facility 100. Figure 2 shows an exemplary loading dock 102 viewed from the outside of the material handling facility 100. Figure 3 shows an exemplary loading dock 102 viewed from the inside of the material handling facility 100 with a trailer 300 parked in the dock 102. Figure 4 shows a cross-sectional side view of the exemplary loading dock 102 with the associated trailer 300. As shown in Figures 1 to 4, the exemplary dock 102 includes a door 104, an entrance / exit barrier 106, a dock leveler 108, a vehicle restraint device 110, a presence / motion detector 112, and / or a notification system 114. In some examples, the dock 102 may be associated with and / or include other equipment such as fans, lights, door seals, shelters, trailer stands, etc. In the examples described, each of the docks 102 includes a dock controller 116 for monitoring and / or controlling the operation of the corresponding door 104, the corresponding entrance / exit barrier 106, the corresponding dock leveler 108, the corresponding vehicle restraint device 110, the corresponding presence / motion detector 112, the corresponding notification system 114, and / or other equipment associated with the dock. In some examples, the dock controller 116 includes a display screen 117 for displaying information associated with the components being monitored and / or controlled by the controller 116. The display screen 117 may be a touchscreen that allows the user to input commands and / or instructions for controller operation and / or access to specific information associated with the controller, dock, or operations associated with the dock.In some examples, the display screen 117 can be integrated into a different device that is separate from the dock controller 116 but communicates with the dock controller 116. Although a single controller 116 is shown controlling all the equipment associated with the dock 102, in some examples, each dock 102 can be associated with multiple controllers configured to control and / or monitor different of the doors 104, entrance / exit barriers 106, dock levelers 108, vehicle restraint devices 110, presence / motion detectors 112, notification systems 114, and / or other equipment associated with the dock.

[0007]

[0016] The door 104 associated with the dock 102 is movable between an open position and a closed position to selectively open or close the entrance between the interior 118 of the material handling facility 100 and the external environment 120. Thus, when a trailer 300 or truck bed is parked in the dock 102, the door 104 provides access to the trailer when it is in the open position and prevents such access when it is in the closed position.

[0008]

[0017] In some examples, door 104 is associated with one or more sensors and / or a door monitoring system to facilitate monitoring and / or control of the operation of door 104. For example, one or more door state sensors can monitor and / or detect the state of door 104 (e.g., whether the door is fully open, fully closed, partially open, partially closed, opening, or closing), one or more impact sensors can monitor and / or detect when something (e.g., a material handling vehicle (e.g., a forklift)) hits door 104, one or more photoelectric eyes disposed on either side of door 104 can monitor and / or detect when a person or object passes through the doorway when the door is open, one or more motion and / or presence sensors can monitor and / or detect activity within the area near the doorway, one or more radio frequency identification (RFID) sensors can monitor and / or detect identification information of personnel, equipment, and / or materials passing through the doorway, one or more temperature sensors can monitor and / or detect temperature on one or both sides of door 104, one or more airflow sensors can monitor and / or detect the flow of air passing through door 104 (e.g., air passing through the door in an open position or a partially open position, and / or air leaking through the door when closed in a closed position), one or more other environmental sensors can monitor and / or detect pressure, humidity, contaminants, particles, chemicals, etc., one or more actuator sensors can monitor and / or detect the energy consumption and / or operation of a door actuator (e.g., a motor) used to open and close the door, and one or more image and / or video sensors (e.g., a camera) can be implemented to monitor and / or detect a particular state of the dock based on image / video analysis. In some examples, dock controller 116 receives output signals from these sensors to monitor and / or control the operation of door 104.

[0009]

[0018] In some examples, the entrance / exit barrier 106 is constructed to provide a barrier extending to the entrance / exit associated with the door 104. The entrance / exit barrier 106 can prevent passage through the entrance / exit even when the door 104 is in the open position. In this way, the entrance / exit barrier 106 can be used as a safety precaution, for example, when the door 104 is open, as shown in Figure 2, but no trailer is parked in the dock 102, or when a trailer in the dock 102 is not restrained. The entrance / exit barrier 106 can also extend to the entrance / exit in front of the door 104 inside the material handling equipment 100 118 to protect the door 104 by reducing the possibility of material handling equipment colliding with the door 104 when the door 104 is closed. In some examples, the entrance / exit barrier 106 is associated with a barrier sensor 302 (Figure 3), which outputs a signal to the dock controller 116 to indicate the state of the entrance / exit barrier 106 (for example, whether the barrier is actively in use and blocking the entrance / exit (shown in Figure 2), retracted to provide passage for the entrance / exit (shown in Figures 3 and 4), or in an intermediate state). In some examples, the barrier sensor 302 and / or other sensors detect impacts (e.g., forces) on the barrier 106, and such impacts may indicate a collision with the barrier.

[0010]

[0019] Often, when a truck bed or trailer (e.g., trailer 300 shown in FIGS. 3 and 4) is parked at dock 102, a gap can be located between the trailing edge of the truck bed or trailer and the outer surface of the platform of dock 102. The dock leveler 108 provides an adjustable bridge spanning this gap, and material handling equipment can travel across this bridge between the interior 118 of the material handling facility 100 and the trailer of the vehicle parked at dock 102. Further, the dock leveler 108 can be vertically adjustable to act as a ramp to compensate for trailers having different heights relative to the platform of dock 102. In some examples, the dock leveler 108 includes one or more sensors to facilitate monitoring and control of the operation of the dock leveler 108. For example, a level sensor can produce an output signal indicating whether the dock leveler 108 is in an active state (extended to bridge the gap between the dock platform and the trailer as shown in FIGS. 3 and 4), a non-active state (the leveler is in the stowed position as shown in FIG. 2), or an intermediate state. In some examples, it is detected by a limit switch when the trailer is being pulled away from dock 102 while the dock leveler 108 is in the active state (e.g., detecting the drop of the leveler when the extended end is no longer supported by the trailer). In such examples, the output of the limit switch can trigger the dock controller 116 to retract the dock leveler 108 to the non-active stowed position.

[0011]

[0020] A vehicle restraint device 110 associated with each dock 102 is positioned in the external environment 120 to engage with some part of a vehicle parked in the dock 102 (e.g., a trailer 300) to reduce accidental vehicle movement (e.g., the vehicle moving as a result of material handling equipment moving around in the trailer, and / or the driver prematurely removing the vehicle from the platform). In some examples, the vehicle restraint device 110 restrains the vehicle by engaging with the vehicle's rear impact guard (e.g., an ICC bar 400 shown in Figure 4). In some examples, the vehicle restraint device 110 engages with the tires and / or any other suitable part of the vehicle. In some examples, the vehicle restraint device 110 includes one or more sensors to facilitate monitoring and / or control of the operation of the vehicle restraint device 110. For example, a restraint sensor may produce an output signal indicating that the vehicle restraint device 110 is in a locked position (e.g., a fixed position for engaging / restraining the vehicle) or an unlocked position (e.g., retracted away from the vehicle). Alternatively or in addition, a restraint sensor(s) may generate an output signal indicating the position of the restraint device relative to a reference point and / or the force(s) applied to the restraint device, in order to determine whether the restraint device is actively engaging / restraining the vehicle.

[0012]

[0021] In the example illustrated in Figure 1, the presence / motion detector 112 represents one or more presence and / or motion detector systems. In some examples, the presence / motion detector 112 includes a presence detector system to detect the presence of a trailer 300 located at the dock 102. The term “trailer” refers to a trailer, whether or not it is coupled to a tractor, or, alternatively, a vehicle having a cargo compartment or platform, for the purposes of discussion relating to the sensing of its presence or motion. In some examples, the presence of the trailer 300 is detected via one or more trailer sensors 202 (Figure 2) positioned in the external environment 120 in and / or near the building of the material handling facility 100. The trailer sensors 202 may be implemented using any suitable sensors, such as photoelectric eyes, proximity sensors, motion sensors, guided loop sensors, or light sensing ranging (LIDAR) systems. In some examples, the presence / motion detector 112 may include a presence detector system to detect the presence of personnel / equipment (e.g., a person walking and / or operating material handling equipment, an autonomous vehicle, etc.) inside a trailer 300 parked in the loading dock 102 (e.g., during loading and / or unloading of cargo) or outside the facility at the entrance to the dock 102. In some examples, the presence of personnel / equipment inside the trailer 300 is detected based on a motion sensor 204 (Figures 2-4) facing the trailer from its position within the material handling facility 100. Additionally or alternatively, the presence / motion detector 112 may include a presence detector system to detect the presence of personnel / equipment / materials on the platform of the leveler 108, inside the leveler pit 402, and / or elsewhere in the vicinity of the dock 102. In some cases, the presence of personnel / equipment within material handling equipment 100 adjacent to dock 102 is detected based on motion sensors 304 (Figures 3 and 4) facing the leveler 108 and / or the surrounding area. Additionally or alternatively, the presence of personnel / equipment / materials can be detected in the leveler pit 402 (Figure 4) below the dock leveler 108 based on one or more presence / motion sensors 404 in the leveler pit 402 (for example, when the leveler is stored in a vertical upright position).In addition to detecting the presence of vehicles, personnel, or material handling equipment, any one of the presence / motion systems represented by the presence / motion detector 112 in Figure 1 can enable the determination of the movement (e.g., speed, direction, etc.), position (e.g., proximity, orientation, etc.), size, shape, etc., and combinations thereof of vehicles, personnel, equipment, or other things (e.g., products, materials), and can enable the distinction of these things.

[0013]

[0022] The notification system 114 in the example described may include several separately functioning notification systems, including one or more visual indicators (e.g., lights, display screens, etc.) and / or one or more audible indicators (e.g., horns, bells, sirens, speakers, etc.), to inform personnel near dock 102 of specific situations, warnings, events, and / or other conditions associated with any manner or state of dock 102 and / or vehicles located in dock. In addition or alternatively, some of the visual indicators may be lights intended to improve illumination and / or visibility of areas associated with dock 102, rather than indicating any specific situation or condition associated with dock. Depending on the purpose of the indicators, the visual and / or audible indicators of the notification system 114 may be located inside the material handling facility 100 118 and / or in the external environment 120 outside the material handling facility 100.

[0014]

[0023] In some examples, at least several indicators within the material handling equipment are positioned and / or oriented toward the external environment 120 (e.g., the end of an arm associated with motion sensor 204 shown in Figures 2–4) so ​​as to be visible from inside the trailer and / or audible from inside the trailer, so as to illuminate the interior of the trailer parked in dock 102 when the door 104 is open. Such indicators can provide additional visibility to personnel entering the trailer for loading and / or unloading cargo. Such indicators can also warn personnel inside the trailer of potential safety risks, such as when the vehicle restraint device 110 is not engaged, and / or the presence of persons near the platform of dock 102 that may not be visible from inside the trailer. Other indicators within the material handling equipment 100 can be positioned and / or oriented toward areas inside the equipment 118 (e.g., the dock platform and / or surrounding areas) so as to be visible from and / or audible from those areas, so as to illuminate those areas. Some such indicators can serve as warnings of potential safety risks, such as when the vehicle restraint device 110 is not engaged, and / or the presence of a person in the trailer that may appear unexpectedly. In addition or otherwise, the indicators can show the operational status of equipment associated with the dock 102.

[0015]

[0024] In some examples, the notification system 114 in Figure 1 includes a local status indicator 306 (Figure 3) positioned next to the door 104 so as to be visible from within the material handling equipment 100, to display information indicating the status and / or progress of tasks to be performed with respect to the corresponding dock 102 and / or a particular trailer 300 located in that dock. In some examples, the local status indicator 306 includes a timing indicator 308 to indicate how long the trailer has been parked in dock 102. In this way, staff can be informed of how many hours remain before overdue and / or parking charges begin to accrue. In some examples, the local status indicator 306 is implemented via a display screen 117 associated with the dock controller 116. In some examples, the timing indicator 308 of the local status indicator 306 can count down instead of count up. In some examples, when a timing indicator reaches a threshold, the timing indicator 308 and / or other forms of status indicators 306 may change their appearance (e.g., change in color, start flashing) and / or activate another indicator to indicate to personnel that it is nearing the end time related to a specific operational constraint (e.g., the need to quickly complete the loading and / or unloading of trailers). In some examples, the timing indicator 308 and / or local status indicators 306 may indicate that the loading and / or unloading of trailers in the corresponding dock 102 takes precedence over the loading and / or unloading of other trailers in other docks 102 (e.g., based on color, flashing, etc.). In some such examples, prioritization may be based on the expected time allocation and / or expected cost incurrence across multiple docks 102 of the material handling facility 100, taking into account available operational resources (e.g., personnel on hand, available material handling equipment, loading status, cross-dock order status, etc.).

[0016]

[0025] In some examples, one or more indicators are positioned outside the material handling equipment 100 so as to be visible from and / or audible from the area outside the dock 102, to illuminate the area outside the dock 102. In some examples, such indicators may be lights that illuminate the area to provide greater visibility to persons in the external environment 120 (e.g., a driver backing a trailer into dock 102). In addition or alternatively, in some examples, the indicators may be lights that provide warning and / or guidance to persons in the external environment 120. For example, as shown in Figure 2, the light indicator 206 outside the equipment 100 includes a red light and a blue light to guide truck drivers when a trailer (e.g., trailer 300 in Figures 3 and 4) can be backed into an area adjacent to dock 102 and / or when a trailer can be moved out of dock 102. In some examples, lights and / or audible indicators can be used to show the driver when the vehicle restraint device is in override mode, when dock equipment is being serviced, or when there are people / objects in or near the trailer's path. These conditions can be communicated through separate indicators that utilize different states or combinations of common indicators (such as changes in color / tone, flashing / sound patterns). Furthermore, in some examples, indicators associated with dock 102 include lights and / or audible alarms that indicate to a person standing near the dock entrance that the truck is reversing.

[0017]

[0026] In some examples, the dock controller 116 controls different indicators associated with the notification system 114 based on one or more signals received from various sensors associated with the door 104, entrance / exit barrier 106, dock leveler 108, vehicle restraint device 110, and / or presence detector 112. For example, in some such examples, the dock controller 116 causes the light indicator 206 to provide a red signal (e.g., red light) whenever the restraint signal indicates that the vehicle restraint device 110 is active and engaged with the trailer. In another example, if the presence detector 112 does not detect a trailer parked in the dock 102, and the door sensor indicates that the door 104 is open, there is a risk that the open door will cause the trailer to fall off the dock platform. Therefore, in some such examples, the dock controller 116 may turn on a warning indicator to alert nearby individuals about the exposed fall. However, in some such cases, the dock controller 116 may not trigger the warning indicator when the barrier sensor 302 provides a signal indicating that the entrance / exit barrier 106 is in active use to prevent passage through an open entrance / exit. Therefore, different signals output from different of the various sensors can be combined to trigger the activation or change of state of indicators associated with the notification system 114, providing warnings, notifications, and / or guidance to persons in the area associated with the dock 102.

[0018]

[0027] In the example described in Figure 1, each of the dock controllers 116 associated with a different dock 102 communicates with the main server 122. In the example described, the main server 122 is shown to be located at the material handling facility 100, but in other examples, the main server 122 may be located away from the material handling facility 100. In some examples, the main server 122 may be integrated with and / or implemented by one of the dock controllers 116.

[0019]

[0028] In some examples, the dock controller 116 transmits values ​​corresponding to operation and / or state parameters controlled and / or monitored by the controller 116, such values ​​may be based on feedback from one or more of the following: the door 104, entrance / exit barrier 106, dock leveler 108, vehicle restraint device 110, presence detector 112, notification system 114, and / or sensors associated with any of the above. In this way, the main server 122 aggregates all available data associated with different docks 102 within the material handling facility 100 in one place. By aggregating data from heterogeneous sources, the main server 122 is able to analyze and / or integrate the controller data to identify relationships that would not normally be possible. As will be discussed in more detail later, in some examples, the main server 122 organizes the aggregated controller data for presentation to end users via one or more dashboards or graphical user interfaces (GUIs) that target specific interests of end users. The GUI may be presented by one or more web pages, apps, applets, applications, etc.

[0020]

[0029] In some examples, the graphical user interface can be configured to provide virtually real-time (e.g., with a delay of less than 5 seconds) information regarding the operations of one or more of the docks 102. More specifically, in some examples, the graphical user interface can provide a display of the progress and timing of the operation sequences associated with the arrival, parking, loading, unloading, and / or departure of trucks and / or trailers in a particular dock 102. By providing virtually real-time information regarding the timing of tasks associated with trailers to be loaded or unloaded at the dock, dock managers or other personnel can manage / coordinate the work associated with a particular trailer to ensure that it does not take longer than the amount of time scheduled or allocated for the work on the trailer. For example, the typical amount of time given for a trailer to be loaded or unloaded is 2x. In many cases, if loading and / or unloading of a trailer takes more than 2 hours, delay and / or stabling charges may be incurred.

[0021]

[0030] While the majority of the 2 hours (or other time units) allocated to the trailer typically involves loading and unloading cargo from the trailer, there are other tasks that must be performed both before and after the cargo is moved, which also contribute to the duration the trailer remains at a particular dock 102. In particular, there is a general sequence of actions or tasks associated with the trailer's arrival before loading and / or unloading takes place. Furthermore, after the loading and / or unloading of the trailer is complete, there is another general sequence of actions or tasks associated with the trailer's departure. Thus, the tasks or actions associated with the work to be performed with respect to the trailer 300 at dock 102 (collectively referred to herein as the loading / unloading process) can be divided into three general categories or stages, including the arrival phase, the material handling phase, and the departure phase.

[0022]

[0031] In some examples, the arrival phase involves an operational sequence that includes the driver arriving at the facility 100 with the trailer 300, followed by the driver checking in and being guided to a specific dock 102, followed by the trailer 300 being positioned in the dock 102, followed by the activation of the vehicle restraint device 110, followed by the opening of the dock barrier 106, followed by the opening of the dock door 104, followed by the activation (e.g., extension) of the dock leveler 108. In some examples, one or more of the above operations may be omitted from the entire sequence (e.g., driver arrival and check-in if the trailer is already at the site), and / or one or more of the above operations may be performed in a different order (e.g., opening the door 104 before opening the entrance / exit barrier 106). In some examples, the operational sequence in the above sequence is implemented by a controller 116 (e.g., an interlocking device). For example, if the vehicle restraint device 110 is not engaged with the trailer 300, the controller 116 may prevent the dock door 104 from opening. Similarly, if the dock door 104 is not open, the controller 116 can prevent the leveler 108 from being activated.

[0023]

[0032] In some examples, the departure phase includes tasks substantially similar to those in the arrival phase, except that they are performed in the reverse order. That is, in some examples, the departure phase includes stopping (e.g., retracting) the dock leveler 108, followed by closing the dock door 104, followed by closing the dock barrier 106, followed by disengaging the vehicle restraint device 110, followed by the trailer being taken out of the dock 102, followed by the driver checking out, followed by the trailer leaving the facility. Similar to the arrival phase, in some examples, one or more tasks in the sequence of operations for the departure phase may be omitted from the entire sequence, and / or one or more tasks may be performed in a different order. Furthermore, in some examples, the order of operations in the above sequence is carried out by the controller 116.

[0024]

[0033] Between the arrival and departure phases, a material handling phase takes place. The material handling phase involves loading and / or unloading materials from the trailer. In some examples, the material handling phase involves the majority of the time the trailer remains at the material handling facility 100. That is, in some examples, the material handling phase is longer than both the arrival and departure phases. The specific duration of the material handling phase depends on the size of the cargo to be moved (e.g., the number of pallets). Furthermore, the duration of the material handling phase may vary depending on the number of personnel working to load and / or unload the trailer 300. For example, two workers are likely to be able to move a set amount of cargo in about half the time it would take one worker to do it alone.

[0025]

[0034] The material handling phase typically takes more time than the arrival or departure phase, but each task in the operational sequence associated with the arrival and departure phases also takes a certain amount of time. Many such tasks are inherently mechanical (e.g., engaging / unengaging the vehicle restraint device 110, opening and closing the door 104, extending / retracting the leveler 108, etc.). Therefore, the duration of individual tasks in the arrival and departure phases is often relatively predictable and consistent. However, such tasks typically need to be initiated by a person working at the dock 102. As a result, there can be fluctuations in the time between the completion of one task and the start of the next in the operational sequence, which can ultimately amount to a considerable amount of time. Delays in the initiation and / or completion of specific tasks in the operational sequence for the arrival and departure phases may result from the person designated to perform the task being busy performing some other task, facing problems related to the task that require correction (e.g., a trailer in an abnormal position, equipment malfunction, etc.), and / or being distracted and / or held back for some other reason. Such delays may increase the likelihood of delays and / or stabling charges by reducing the time available to load and / or unload the trailer 300 during the material handling phase.

[0026]

[0035] Several examples disclosed herein involve monitoring the duration and / or timing of tasks associated with the arrival, material handling, and departure phases in substantially real time. In some examples, such timing information is presented to the dock manager or other personnel via a GUI, enabling the dock manager to identify when the unloading and / or loading of a particular trailer is scheduled to be completed in a timely manner, or how much the loading and unloading is behind schedule. In some examples, the duration and / or timing of different tasks being monitored in substantially real time is compared to a target threshold period for the individual task and / or group of two or more tasks. In some such examples, both real-time timing information and the target threshold period are displayed in the GUI, making it easier for the dock manager or other personnel to gain an understanding of how much a particular trailer is behind schedule and which tasks may have contributed to such delays. Similarly, the GUI can assist personnel in determining when work at a particular dock 102 associated with a particular trailer will be on schedule or ahead of schedule.

[0027]

[0036] In addition or alternatively, in some examples, a timing indicator 308 located at the dock 102 provides a display of the duration elapsed from a specified start time until a particular task is started or completed. In some examples, the start time for the timing indicator 308 corresponds to the completion of a task (e.g., a previous task) and / or the start of a task (e.g., a previous or current task) in a specified operational sequence, where the task to be completed is the next task in the operational sequence. For example, opening the dock door 104 (e.g., the door 104 being activated and opened, or the door reaching its open limit switch) can trigger the timing indicator 308 to start counting up and show how much time has elapsed until the dock leveler 108 is positioned to allow the trailer 300 to be loaded and unloaded. In some such examples, positioning the dock leveler 108 (e.g., starting or stopping the activation of the dock leveler 108) can trigger the timing indicator 308 to restart counting and provide a display of the time elapsed since the trailer was first available for loading and unloading. Therefore, in some examples, the timing indicator 308 can restart in response to the completion of each task and continue counting until the next scheduled task is started or completed. In other examples, the timing indicator 308 can be started and / or reset based on some trigger other than the start and / or completion of a particular task (e.g., based on user input and / or some other event). For illustrative purposes, an example is provided that details the completion of a particular task. By providing such a counter at the location of dock 102, personnel at the dock can quickly and easily determine whether the operational sequence is progressing in a timely manner or whether delays associated with a particular task are occurring. In some examples, the display of the timing indicator 308 can change its appearance (e.g., change of color, flashing, etc.) to indicate that the task is taking longer than expected to complete when the elapsed time exceeds a target threshold corresponding to a particular task.

[0028]

[0037] In other examples, instead of counting up to represent elapsed time, the timing indicator 308 may count down to represent the amount of time remaining before the next task is expected to start or complete. For example, suppose a target threshold window of 3 minutes is given to extend the dock leveler 108 after opening door 104. In such an example, after door 104 is opened, the timing indicator 308 is triggered and begins counting down from 3 minutes. In this way, personnel at dock 102 can quickly and easily determine how much time remains before the next task needs to start or complete (for example, activating the leveler 108 in this example) in order to proceed as planned. In some examples, the countdown may change its appearance (e.g., change color, flash, etc.) when it reaches zero and / or when it reaches a time limit near zero. In some examples, if the task has not yet started or completed after the time has reached zero, the timing indicator 308 may start counting up, based on a target threshold specified for that task, to represent how much time has elapsed since the task was expected to start or complete.

[0029]

[0038] In some examples, the countdown or countup of the timing indicator 308 can correspond to two or more tasks. For example, in some examples, the threshold period can be defined for all tasks in the arrival phase from the time the trailer 300 is positioned at the dock 102 until the dock leveler 108 is in position and the material handling phase can begin. In such examples, as soon as the trailer 300 is detected at the dock 102, the timing indicator 308 begins counting (up or down) and continues counting until the dock leveler 108 is extended to the starting position. The timing indicator 308 can be configured to provide timing information for any other group of the aforementioned tasks.

[0030]

[0039] In some examples, in addition to displaying timing information (e.g., a countdown or elapsed time), the local status indicator 306 may also provide a display of the task(s) that need to be completed in relation to that timing information. In some examples, this display includes an audible prompt, text identifying the last task to be completed within the relevant period, and / or an icon representing such a task. Thus, if each new task is associated with a separate timing threshold and time is measured independently by the local status indicator 306, each time the timing indicator 308 of the local status indicator 306 is restarted (based on the start or completion of a previous task), the local status indicator 306 also updates to include an audible prompt, icon, image, and / or text identifying the next task to be started or completed. In contrast, if the timing threshold corresponds to a series of multiple tasks, the local status indicator 306 may include an audible prompt, icon, image, and / or text identifying the last task in that series. In such examples, an employee looking at the local status indicator 306 should be able to see which intervention tasks need to be performed before completing the final task specified in the local status indicator 306. In other examples, the local status indicator 306 may identify the next task to be executed, the final task in a series of tasks, and / or all intervention tasks. In addition or alternatively, in some examples, the local status indicator 306 may also identify completed tasks or a subset of completed tasks (e.g., the last completed task). In some examples, the local status indicator 306 may display multiple timers corresponding to different tasks and / or a group of task sequences to be completed.As one specific example, a first timer may indicate the time until the next specific task in the arrival phase begins or is completed, a second timer may indicate the time until the arrival phase is completed and / or until the material handling phase begins, and a third timer may indicate the total loading / unloading time for a particular trailer currently in dock 102. In some examples, two or more of the multiple timers may be displayed simultaneously along with each other. In other examples, different timers of the multiple timers may be displayed over different periods (for example, the local status indicator 306 may cycle through each of the timers one at a time).

[0031]

[0040] As a specific example, Figures 5–12 show exemplary user interfaces 500, 600, 700, 800, 900, 1000, 1100, and 1200 that can be provided via a local status indicator 306 during a series of tasks in an operational sequence associated with the arrival, material handling, and departure phases of the loading / unloading process for a particular trailer 300. In this example, the first user interface 500 shown in Figure 5 is triggered in response to the detection of the presence of the trailer 300 at the corresponding dock 102. In some examples, confirmation of the presence of the trailer 300 at the dock 102 can be provided by a text-based trailer presence confirmation 502 and / or a trailer presence icon 504. Furthermore, in some examples, the next (e.g., current) task to be completed to secure the trailer by engaging the vehicle restraint device 110 can be indicated. In some examples, the activation or engagement of the vehicle restraint device 110 as the next task to be completed is indicated within the user interface 500 by a notification 506 based on suitable text and / or a restraint device lock icon 508. In some examples, a timing indicator 308 is started to count up or count down against a specified threshold (i.e., target) period (for example, 5 minutes in the described example) for the vehicle restraint device 110 to secure the trailer 300.

[0032]

[0041] After a sensor associated with the vehicle restraint device 110 indicates that the trailer 300 is secured, the local status indicator 306 updates the second user interface 600, including a trailer securing confirmation 602 and / or a restraint device lock icon 508, to indicate that the task has been completed. Furthermore, in this example, a notification 604 based on new text and / or a door open icon 606 are provided to identify that the next / current task to be completed is opening the dock door 104. In addition, in this example, in response to the vehicle restraint device 110 engaging and securing the trailer 300, the timing indicator 308 is reset to correspond to a new threshold period specified for the task of opening the door 104 (for example, 2 minutes in the described example). A similar user interface 700 after the door has been opened is shown in Figure 7, which includes a text-based notification 702 and / or a door open icon 606 to indicate that the door 104 has been opened, and a separate notification 704 and / or a leveler engage icon 706 to indicate that the next / current task to be completed is to place the dock leveler 108 into the trailer 300.

[0033]

[0042] After it is confirmed that the dock leveler 108 has been extended into the trailer 300, the arrival phase is complete and the dock-related activities proceed to the material handling phase. Figure 8 shows an exemplary user interface 800 displayed by the local status indicator 306 during the material handling phase. In this example, both text-based notifications 802 and trailer activity icons 804 are provided to indicate that the current task at hand is to load and / or unload the trailer 300. Furthermore, as shown in the example described, the timing indicator 308 is also reset in this case to a specified threshold period (for example, 2 hours in this example) assigned to the completion of the material handling phase of the loading / unloading process. In some examples, the entire period from when the presence of the trailer 300 in the dock is detected (Figure 5) to when the trailer 300 leaves the dock 102 (Figure 12) may have an overall threshold period of 2 hours. In such examples, the threshold period specific to the material handling phase (its progress is shown in Figure 8) should be reduced accordingly. In some examples, the user interface 800 in Figure 8, associated with the material handling phase, may include additional information about a particular trailer being loaded and / or unloaded. For example, the user interface 800 may indicate the number of cargo units (e.g., pallets) to be moved. In some examples, the user interface 800 may indicate the number and / or timing of individual trailer activity events detected as determined by the motion sensor 204 whenever motion is detected within the trailer 300.

[0034]

[0043] After the loading and / or unloading of the trailer 300 is complete, the departure phase begins, reversing the sequence of actions performed during the arrival phase, with similar user interfaces provided for each separate task. For example, the user interface 900 in Figure 9 includes a text notification 902 and a loading complete icon 904 to indicate that the loading and / or unloading of the trailer 300 has been confirmed. Furthermore, in some examples, the user interface 900 includes a separate notification 906 and / or a leveler disengage icon 908 to indicate the next / current task to be performed, along with a timing indicator 308 being reset based on an associated threshold period. The user interface 1000 in Figure 10 includes a text notification 1002 and a leveler disengage icon 908 to indicate that the dock leveler 108 has been removed from the trailer 300. Furthermore, in some examples, the user interface 1000 includes a separate notification 1004 and / or a door closed icon 1006 to indicate the next / current task to be performed, along with the timing indicator 308 being reset based on an associated threshold period. The user interface 1100 in Figure 11 includes a text notification 1102 and a door closed icon 1006 to indicate that the door 104 has been closed. Furthermore, in some examples, the user interface 1100 includes a separate notification 1104 and / or a restraint device unlock icon 1106 to indicate the next / current task to be performed, along with the timing indicator 308 being reset based on an associated threshold period. After the vehicle restraint device 110 is unlocked (e.g., disengaged), the timing indicator 308 can also be reset in this case, based on a threshold period associated with the expected time for the trailer 300 to leave the dock 102. Similar text-based notifications 1202 and / or a trailer departure icon 1204 may also be provided to give context to the timing indicator 308.

[0035]

[0044] As described above, the user interfaces 500-1200 in Figures 5-12 are displayed by local status indicators 306 located in the corresponding docks 102 to provide information on the progress of work to be completed in dock 102. In some examples, the same information is provided to other personnel located away from dock 102 (e.g., dock managers or other personnel in other parts of facility 100) via a GUI generated by the main server 122, which will be described further later. In addition or alternatively, in some examples, the GUI provided by the main server can provide other information based on the aggregation of data and / or other types of data from different docks 102 within facility 100. Furthermore, in some examples, the main server 122 not only aggregates the data in substantially real time to provide substantially real-time information on the status, timing, and / or progress of activities in different docks, but the main server also archives such data for display to personnel after appropriate processing and analysis. In other words, in some examples, tasks associated with activity at dock 102 are monitored by dock controller 116 and reported to main server 122, so that main server 122 can archive such data along with associated timestamps and retrieve the duration and / or timing of each task for later re-examination and / or analysis. In some examples, the timestamps may correspond to the start of a particular task, the completion of a particular task, and / or sensor triggers indicating any action associated with a particular task and / or operation on dock 102.

[0036]

[0045] In some examples, the threshold (i.e., target) period specified for each task and / or group of tasks is based on an analysis of historical timing information. For example, the threshold period assigned to extend the dock leveler 108 after door 104 is opened may be specified to correspond to the average amount of time taken to complete such a task each time a trailer was loaded or unloaded at the corresponding dock over a specified period in the past (e.g., a week, a month, a year, etc.). In some examples, the threshold period may be based on the average amount of time for a task measured at multiple or all docks 102 within the material handling facility 100 over a time frame. In some examples, the threshold period may be based on the average amount of time for a task measured at docks of multiple different facilities over a time frame. In some examples, the threshold period may also be defined based on statistical metrics other than the mean, such as the minimum, maximum, and / or median (and possibly some degree of variance) of the amount of time taken to perform the task with respect to the dock in question (e.g., a single specific dock, a specific group of docks, all docks of a facility, docks of multiple facilities, etc.). In some examples, historical timing information associated with performing tasks related to dock activity is periodically reviewed (e.g., every 30, 60, or 90 days), prompting the user to update the target threshold period, recommending an update, or automatically updating the target threshold period. In some examples, artificial intelligence is implemented to analyze the data and determine a suitable adjustment to the target threshold period based on recently collected historical data (e.g., showing improvements in efficiency for specific tasks and / or tasks where efficiency is declining).

[0037]

[0046] In some cases, the target threshold period can be defined independently of historical timing information. For example, the target threshold period can be based on industry standards independently of historical archive data. In some cases, the target threshold period is defined by the user (e.g., manually entered).

[0038]

[0047] Beyond providing a basis for setting suitable target threshold periods to enable virtually real-time tracking of the progress of tasks associated with trailer loading and unloading, historical timing information for such tasks can also be used to reduce the frequency and / or impact of potential delays. For example, analysis of historical timing data over a long period may reveal specific trends indicating that the time required to perform a particular task exceeds its corresponding target threshold more frequently than other tasks. Such trends may reveal the need to provide training for that particular task to reduce recurring delays. In some examples, analysis of historical timing data may reveal that one or more specific docks 102 within facility 100 are associated with delays more frequently than other docks 102 within facility 100. In such examples, the situation of the less efficient dock can be analyzed to make appropriate adjustments to improve efficiency. By analyzing historical data to identify other types of inefficiencies, and determining when (e.g., hourly, shift-wise, or daily) and where (e.g., shipping or receiving, docks assigned to specific workers) delays occur most frequently, dock managers can implement better responses to reduce the occurrence and / or duration of such delays in the future.

[0039]

[0048] Some delays that occur cannot be predicted or anticipated in advance based on the analysis of historical data. However, in some cases, historical data can still be used to mitigate the impact of such delays by enabling dock managers and / or other personnel to identify delays earlier (e.g., by identifying trends) and to appropriately reallocate resources (e.g., workers, material handling equipment, etc.) to compensate for lost time. More specifically, in some cases, the amount of resources that should be allocated to loading and / or unloading a trailer that is behind schedule can be estimated based on how long it took to complete loads of similar size in the past, as represented in the historical data. Such a decision depends on having load information that indicates the size of such loads. Accordingly, in some cases, in addition to tracking and archiving timing information regarding the completion of specific tasks, load information for each trailer that is loaded and / or unloaded is also tracked and recorded. In some cases, cargo information includes the size of the cargo (e.g., the number of pallets to be moved), as well as other relevant characteristics of the cargo (e.g., whether the cargo is undamaged or has fallen, whether the cargo is frozen, the carrier associated with the cargo, etc.). Furthermore, as mentioned above, the speed at which a particular trailer is loaded or unloaded may depend on the amount of resources allocated to that trailer for unloading. Accordingly, in some cases, resource allocation information is collected for each trailer that is loaded or unloaded. In some cases, resource allocation information includes the number of workers assigned to a particular dock or group of docks, worker identification information, time (specific), the number and / or type of material handling equipment used, and how many other docks are simultaneously handling loading or unloading activities.

[0040]

[0049] In some cases, delays can be avoided before they occur and / or efficiency can be improved based on which dock 102 a particular trailer is assigned to for loading and unloading. In many cases, trailer assignment to loading docks is often based on whether the trailer is associated with a shipment or a receipt. However, the examples disclosed herein allow personnel to assign a particular trailer to a particular dock by relying on the aspects of historical data outlined above (e.g., timing information, cargo information, resource allocation information, etc., for different tasks at different docks). More specifically, in some examples, historical data is analyzed to identify the use, utilization rate, and logistical characteristics of different docks. Some specific factors that can be obtained from the analysis of historical data include dock equipment utilization rate, carrier efficiency, the number of loads completed at a particular dock within a given time frame, the size of the loads, the time (e.g., time of day, specific work shift, etc.), dock efficiency, and personnel working at a particular dock. Dock equipment utilization rate refers to how frequently (e.g., number of cycles) equipment associated with a particular dock is used. Carrier efficiency refers to the efficiency with which cargo associated with a particular carrier is completed compared to cargo associated with other carriers. Similarly, dock efficiency refers to the efficiency with which cargo at a particular dock is completed compared to cargo associated with other docks.

[0041]

[0050] In some cases, deterministic laws and / or artificial intelligence can be implemented to determine which carriers, docks, and / or dock personnel are most efficient and / or least efficient. In some cases, the analysis of historical data can be updated periodically to reflect new data associated with additional trailers loaded and / or unloaded at facility 100, and thus the efficiency calculated for different carriers, docks, and / or personnel can be adjusted over time. Based on such decisions, specific trailers can be automatically assigned to specific docks to improve efficiency. For example, a trailer with a small load (e.g., only one pallet) during busy times can be assigned to a dock and / or personnel associated with relatively high efficiency. On the other hand, when the situation is not so busy, smaller loads can be assigned to less efficient docks, and relatively larger loads to more efficient docks. In another example, a carrier determined to be less efficient than others can be assigned to a more efficient dock to offset the carrier's inefficiency. As another example, more important cargo and / or cargo associated with higher late charges can be assigned to more efficient docks. In some cases, docks are assigned based on equipment utilization (equipment cycle) so that equipment utilization is relatively consistent across different docks, thereby reducing overuse and / or premature wear of equipment associated with a particular dock. Alternatively, in some cases, equipment utilization can be concentrated among a subset of docks within the facility, so that servicing and / or replacement of equipment to different groups of docks is distributed over time.

[0042]

[0051] In the example described in Figure 1, the main server 122 can communicate with one or more remote servers 126 that are not located in the material handling facility 100. In some examples, the remote servers 126 correspond to additional servers equivalent to the main server 122 and are located elsewhere in other material handling facilities and / or in connection with the company operating the material handling facility 100 in Figure 1. In addition or alternatively, in some examples, the remote servers 126 may correspond to servers maintained by the equipment manufacturer associated with one or more of the docks 102.

[0043]

[0052] In the example illustrated in Figure 1, the material handling facility 100 includes one or more management servers 124 that facilitate the management of various aspects of the equipment assets and / or operational behavior of the material handling facility 100. In some examples, the management servers 124 communicate with a main server 122 via a bus, a local area network (LAN), and / or a wide area network (e.g., the Internet). Exemplary management servers 124 may include a dock / yard management system, an inventory control system, a video management system (VMS), a warehouse management system (WMS), an enterprise resource planning (ERP) system, and the like. In addition or alternatively, in some examples, one or more of the management servers may be combined with and / or implemented by the main server 122.

[0044]

[0053] In some examples, the main server 122 includes and / or is associated with a web server 128 that hosts one or more web pages accessible by users via a client device 130. The client device 130 can be any suitable computing device having a browser for accessing the web pages hosted by the web server 128. Thus, the client device 130 can correspond to one or more worker stations located within the material handling facility (e.g., within the facility's logistics office). In some examples, the client device can be a portable device (e.g., a tablet, smartphone, etc.) carried by staff throughout the material handling facility 100 and / or away from the facility. Furthermore, some client devices 130 can be portable devices used by truck drivers transporting trailers in and out of the material handling facility 100 and / or by yard jockeys repositioning trailers within the dock 102 and / or the yard of the material handling facility 100.

[0045]

[0054] Different web pages may include different GUIs designed to present different types of information in an easily understandable format that facilitates users to recognize the relationships between data collected from different docks 102 within the material handling facility 100. In some examples, the main server 122 automatically updates one or more web pages via web-based communication 132 whenever new data relevant to a particular web page is collected. In this way, the data presented on the web pages represents substantially real-time data. While GUIs are disclosed herein in relation to web pages, graphical user interfaces may also be presented using something other than web pages (e.g., via apps, applets, applications, etc.). In some examples, the main server 122 communicates with client devices 130 independently of the web server 128 using other forms of network communication 134, such as email messages, SMS (Short Message Service) messages, push notifications, etc.

[0046]

[0055] Figure 13 is a block diagram showing an exemplary implementation of the exemplary dock controller 116 of Figure 1. As shown in Figure 13, the exemplary dock controller 116 includes an exemplary device interface 1302, an exemplary main server interface 1304, an exemplary time stamper 1306, an exemplary data logger 1308, an exemplary sensor feedback analyzer 1310, an exemplary target threshold determination unit 1312, an exemplary motion controller 1314, and an exemplary memory 1316.

[0047]

[0056] The exemplary device interface 1302 enables communication between the controller 116 and devices associated with one or more of the following: the door 104, the entrance / exit barrier 106, the dock leveler 108, the vehicle restraint device 110, the presence detector 112, and the notification system 114. That is, in some examples, the controller 116 can provide commands and / or instructions to different devices associated with the corresponding dock 102 via the device interface 1302. Furthermore, the controller 116 can receive feedback from sensors associated with the devices via the device interface 1302. In some examples, the device interface 1302 includes a user interface that allows a user to provide input to the controller 116 to instruct its operation.

[0048]

[0057] The exemplary main server interface 1304 enables communication between the controller 116 and the main server 122. Specifically, in some examples, the controller transmits or reports sensor feedback and / or other information to the main server 122 via the main server interface 1304. Furthermore, in some examples, the controller 116 can receive information, instructions, and / or commands from the main server 122 via the main server interface 1304.

[0049]

[0058] The exemplary time stamper 1306 times-stamps sensor feedback data acquired via the instrument interface 1302 and stores such data in the exemplary memory 1316. The exemplary data logger 1308 logs the sensor feedback data to the memory 1316 along with the associated time stamp provided by the exemplary time stamper 1306. In addition or by alternative means, the exemplary data logger 1308 may provide the times-stamped sensor feedback data to the main server 122 via the main server interface 1304.

[0050]

[0059] The exemplary sensor feedback analyzer 1310 analyzes feedback from sensors associated with equipment located in the dock 102, enabling the controller 116 to determine the equipment status and / or conditions based on the reported equipment status and / or conditions, and to provide appropriate commands and / or instructions to the equipment. More specifically, in some examples, the sensor feedback analyzer 1310 determines when a particular task associated with loading and / or unloading a trailer is completed according to a specified operation sequence. In some examples, the operation sequence to be performed is stored in exemplary memory 1316. Additionally or alternatively, in some examples, the sensor feedback analyzer 1310 analyzes timestamped sensor feedback data generated by the time stamper 1306 and logged by the data logger 1308 to determine the duration associated with the completion of a particular task and / or group of tasks associated with an operation sequence for a particular trailer. Furthermore, in some examples, the sensor feedback analyzer 1310 compares the duration of a particular task(s) to a corresponding target threshold set for that task(s). In some such examples, the sensor feedback analyzer 1310 determines that a particular task is progressing as planned toward a target threshold, that the duration of the current task is approaching the target threshold, and / or that the duration of the current task has exceeded the target threshold.

[0051]

[0060] The exemplary target threshold determination unit 1312 determines a suitable value for a target threshold for a particular task(s). In some examples, the target threshold determination unit 1312 determines the target threshold based on an analysis of the durations of previously completed tasks archived in memory 1316. That is, in some examples, the target threshold can be adapted over time according to the specific circumstances and associated efficiency of the task in a particular dock. In some examples, the target threshold determination unit 1312 determines a value for the target threshold based on the average of the historical durations for the corresponding task. In other examples, different statistical measures can be used to determine a suitable target threshold, including minimum duration, maximum duration, and / or median duration (which may take into account some variance in duration). In some examples, the target threshold determination unit 1312 automatically updates the target threshold after a specific period (e.g., every 30 days, every 60 days, every 90 days, etc.).

[0052]

[0061] The exemplary motion controller 1314 controls the operation of the equipment associated with the dock 102. That is, in some examples, the motion controller 1314 generates instructions and / or commands for the equipment based on the output of the sensor feedback analyzer 1310. In some examples, the motion controller includes a GUI generator 1318 for controlling and / or defining the user interface displayed by the local status indicator 306. For example, in some examples, the GUI generator 1318 generates the user interface to be displayed by the local status indicator 306 (e.g., user interfaces 500 to 1200 in Figures 5 to 12). In addition or by alternative means, the GUI generator 1318 provides the relevant data to the local status indicator 306 so that the local status indicator 306 can generate and display such a user interface. As mentioned above, in some examples, the user interface includes the display of one or more of the timing indicators 308 associated with the last completed task, the next task to be completed, a series or group of tasks to be completed, and the tasks(s) to be completed. In some examples, the timing indicator 308 can count down from a starting value corresponding to a target threshold for a task(s) defined by the target threshold determination unit 1312. Such a timing indicator provides a display of the amount of time remaining to complete the corresponding task within the target threshold period. In other examples, the timing indicator 308 can start from zero and count up to show the current amount of time spent on the task(s) in question. In some examples, if the duration to complete a task(s) exceeds the corresponding threshold, the GUI generator 1318 changes the appearance of the output of the timing indicator 308 (e.g., a change in color, blinking, etc.).In some examples, the GUI generator 1318 changes the appearance of the local status indicator 306 to provide a warning that the target window for completing the task(s) is nearing its end, even though the duration of the current task(s) to be completed is approaching the target threshold period, but before the target threshold period has elapsed. In some such examples, whether the duration of the current task is "near" the target threshold can be defined by a specific time frame (e.g., 2 minutes, 5 minutes, 15 minutes, etc., before the target threshold) and / or based on a percentage of the duration of the target threshold period (e.g., when 20%, 10%, 5%, etc., of the target threshold period remains).

[0053]

[0062] An exemplary implementation of the dock controller 116 of Figure 1 is shown in Figure 13, but one or more of the elements, processes, and / or devices shown in Figure 13 can be combined, split, rearranged, omitted, removed, and / or implemented in any other way. Furthermore, the exemplary instrument interface 1302, exemplary main server interface 1304, exemplary time stamper 1306, exemplary data logger 1308, exemplary sensor feedback analyzer 1310, exemplary target threshold determination unit 1312, exemplary motion controller 1314, exemplary memory 1316, exemplary GUI generator 1318, and / or, more generally, the exemplary dock controller 116 of Figure 1 can be implemented by hardware, software, firmware, and / or any combination of hardware, software, and / or firmware. Therefore, for example, any of the exemplary device interface 1302, exemplary main server interface 1304, exemplary time stamper 1306, exemplary data logger 1308, exemplary sensor feedback analyzer 1310, exemplary target threshold determination unit 1312, exemplary motion controller 1314, exemplary memory 1316, exemplary GUI generator 1318, and / or more generally, exemplary dock controller 116 may be implemented by one or more analog or digital circuits, logic circuits, programmable processors, programmable controllers, graphics processing units (GPUs), digital signal processors (DSPs), application-specific integrated circuits (ASICs), programmable logic devices (PLDs), and / or field-programmable logic devices (FPLDs).When reading any of the claims of the apparatus or system of this patent that pertain purely to implementations of software and / or firmware, at least one of the exemplary device interface 1302, exemplary main server interface 1304, exemplary time stamper 1306, exemplary data logger 1308, exemplary sensor feedback analyzer 1310, exemplary target threshold determination unit 1312, exemplary motion controller 1314, exemplary memory 1316, and / or exemplary GUI generator 1318 is expressly defined herein as including a memory containing software and / or firmware, a non-temporary computer-readable storage device or storage disk such as a digital versatile disc (DVD), compact disc (CD), or Blu-ray disc. Furthermore, the exemplary dock controller 116 in Figure 1 may include, in addition to or instead of, those shown in Figure 13, one or more elements, processes, and / or devices, and / or two or more of any or all of the elements, processes, and devices shown. In this specification, the term “communicate,” including its variations, encompasses direct communication and / or indirect communication through one or more intermediate components, and does not require direct physical (e.g., wired) communication and / or continuous communication, but rather includes, additionally, selective communication at periodic intervals, scheduled intervals, non-periodic intervals and / or one-time events.

[0054]

[0063] Figure 14 is a block diagram showing an exemplary implementation of the exemplary main server 122 of Figure 1. As shown in Figure 14, the exemplary main server 122 includes a web server 128, an exemplary network communication interface 1402, an exemplary dock controller interface 1404, an exemplary time stamper 1406, an exemplary data logger 1406, an exemplary sensor feedback analyzer 1410, an exemplary target threshold determination unit 1412, an exemplary efficiency analyzer 1414, an exemplary utilization analyzer 1416, an exemplary dock allocation analyzer 1418, an exemplary GUI generator 1420, and an exemplary memory 1422.

[0055]

[0064] The exemplary network communication interface 1402 in Figure 14 enables communication with client devices 130 independently of the web server 128. For example, the network communication interface 1402 can send email messages and / or SMS messages to one or more client devices 130. In addition, in some examples, the network communication interface 1402 can send data to and from local management servers 124 and / or remote servers 126. In some examples, data received from servers 124 and 126 is stored in exemplary memory 1422.

[0056]

[0065] The exemplary dock controller interface 1404 in Figure 14 enables communication with the dock controller 116. Specifically, the dock controller interface 1404 receives sensor feedback data collected by the controller 116 and / or any other type of data reported by the controller 116. Such data can be aggregated and stored in memory 1422 for later analysis and / or processing. Additionally or alternatively, in some examples, the dock controller interface 1404 transmits instructions, commands, and / or other types of information to the dock controller 116.

[0057]

[0066] The exemplary time stamper 1406 in Figure 14 provides similar functionality to the time stamper 1306 of the dock controller 116 described in relation to Figure 13. In some examples, the time stamper 1406 in Figure 14 is a duplicate of the time stamper 1306 in Figure 13. In some examples, the time stamper 1306 can be omitted from the dock controller 116 in Figure 13. In some examples, the time stamper 1406 can be omitted from the main server 122 in Figure 14. In some examples, regardless of whether the data is time-stamped by the exemplary time stamper 1306 in Figure 13 or by the exemplary time stamper 1406 in Figure 14, the exemplary data logger 1406 in Figure 14 logs the time-stamped data to the exemplary memory 1422. In some examples, the data logger 1406 logs other types of data, such as cargo information and / or resource allocation information (for example, provided by the management server 124).

[0058]

[0067] The exemplary sensor feedback analyzer 1410 in Figure 14 provides similar functionality to the sensor feedback analyzer 1310 of the dock controller 116 described in relation to Figure 13. In addition, in some examples, the sensor feedback analyzer 1410 in the main server 122 shown in Figure 14 also analyzes and / or compares aggregated sensor feedback data from different dock controllers 116 associated with different docks 102. In some examples, the sensor feedback analyzer 1410 in Figure 14 is a duplicate of the sensor feedback analyzer 1310 in Figure 13. In some examples, the sensor feedback analyzer 1310 can be omitted from the dock controller 116 in Figure 13. In some examples, the sensor feedback analyzer 1410 can be omitted from the main server 122 in Figure 14.

[0059]

[0068] The exemplary target threshold determination unit 1412 in Figure 14 provides similar functionality to the target threshold determination unit 1312 of the dock controller 116 described in Figure 13. In addition, in some examples, the target threshold determination unit 1412 in the main server 122 shown in Figure 14 also analyzes and / or compares the task duration and / or other parameters output by sensor feedback analyzers 1410 associated with multiple different docks to determine a common value for the target threshold of different docks 102. Thus, in some examples, the same target threshold can be defined for a specific task(s) to be completed in different docks 102. In other examples, different docks 102 can be associated with different target thresholds. In some examples, the target threshold determination unit 1412 in Figure 14 is a duplicate of the target threshold determination unit 1312 in Figure 13. In some examples, the target threshold determination unit 1312 can be omitted from the dock controller 116 in Figure 13. In some examples, the target threshold determination unit 1412 can be omitted from the main server 122 in Figure 14.

[0060]

[0069] The exemplary efficiency analyzer 1414 analyzes the duration (determined by the sensor feedback analyzer 1410) of tasks performed in relation to the loading and / or unloading of trailers in a particular dock 102 to determine the efficiency of such tasks being performed in relation to other docks within the facility 100. In some examples, the efficiency of tasks in a particular dock is measured with respect to target thresholds for various tasks associated with the operational sequence of trailer arrival, loading and / or unloading, and departure in that particular dock. In some examples, the efficiency analyzer 1414 can analyze the collected data to generate statistics, which can be provided to the user to enable the user to identify potential inefficiencies (associated with a particular task, date and time, and / or a particular dock) that can be improved, and to identify relatively efficient docks that can handle more trailers and / or trailers with larger or more significant loads. For example, in some cases, the efficiency analyzer 1414 can track and / or log the number of trailers associated with each dock where delays occur (e.g., the duration required to complete the operational sequence of loading and / or unloading a trailer extends beyond the target threshold). In some examples, the exemplary efficiency analyzer 1414 can track and / or calculate the average amount of delay and / or excess time experienced by each dock and / or multiple (e.g., all) docks within the facility 100.

[0061]

[0070] An exemplary utilization analyzer 1416 monitors, tracks, and / or analyzes the utilization of a particular dock 102 within the facility 100. Hereinafter, “utilization” of a dock refers to how frequently a particular dock is used. In some examples, utilization is quantified based on the number of trailers loaded and / or unloaded within a given period (e.g., the number of completed trailer loads per day). In some examples, utilization can be normalized and expressed as a percentage of the number of trailers that could be loaded or unloaded at dock 102 during a specified period (e.g., one day), assuming that each trailer load is completed in a timely manner during the specified period and dock 102 is constantly in use. That is, a dock has a 100% utilization if it is operating at full capacity (always loading or unloading trailers) and efficiently (completing each trailer load on time). A utilization rate of less than 100% indicates that the dock has extra capacity to handle more trailers. A utilization rate greater than 100% indicates that the dock is completing more trailer loads than expected for the dock when it is operating efficiently at full capacity, which may suggest that the number of trailer loads designated as capable of being completed at full capacity may be too low. In some cases, this number can be specified by the dock manager and / or other staff. In some cases, this number can be calculated based on an analysis of historical data stored in memory 1422.

[0062]

[0071] The exemplary dock allocation analyzer 1418 analyzes efficiency and / or utilization information generated by the efficiency analyzer 1414 and / or utilization analyzer 1416 to facilitate dock / yard managers and / or other personnel in assigning specific trailers to specific docks. For example, if the efficiency analyzer 1414 determines that a particular dock is highly efficient, the dock allocation analyzer 1418 may decide to assign extra trailers and / or trailers with larger loads to that particular dock. In addition or alternatively, the dock allocation analyzer 1418 may identify specific docks associated with relatively low utilization rates and assign new trailers more frequently to them so that equipment in other docks associated with relatively high utilization rates does not wear out quickly. That is, in some examples, the dock allocation analyzer 1418 may facilitate the uniform distribution of trailers across all docks in order to maintain relatively consistent utilization rates across all docks. In another example, the dock allocation analyzer 1418 can identify a particular dock for more frequent use at a given time based on the expected maintenance schedule for the equipment associated with such docks, and can identify different sets of docks at different times.

[0063]

[0072] In some examples, the GUI generator 1420 in Figure 14 provides similar functionality to the GUI generator 1318 of the dock controller 116 described in relation to Figure 13. That is, in some examples, the GUI generator 1420 of the exemplary main server 122 controls and / or defines the user interface displayed by the local status indicator 306. In some such examples, the GUI generator 1318 can be omitted from the dock controller 116 in Figure 13. In addition or alternatively, in some examples, the GUI generator 1420 of the example described in Figure 14 generates a GUI for display on a web page hosted by the web server 128. In some examples, the GUI generator 1420 generates GUIs for other apps, applets, applications, etc., that are accessible by the client device 130 independently of the web server 128. The GUI generated by the exemplary GUI generator 1420 may be based on one or more outputs from the sensor feedback analyzer 1410, the target threshold determination unit 1412, the efficiency analyzer 1414, the utilization analyzer 1416, and / or the dock allocation analyzer 1418, as will be further described with respect to Figures 15 to 23.

[0064]

[0073] An exemplary implementation of the main server 122 in Figure 1 is shown in Figure 14, but one or more of the elements, processes, and / or devices shown in Figure 14 can be combined, split, rearranged, omitted, removed, and / or implemented in any other way. Furthermore, the exemplary web server 128, exemplary network communication interface 1402, exemplary dock controller interface 1404, exemplary time stamper 1406, exemplary data logger 1406, exemplary sensor feedback analyzer 1410, exemplary target threshold determination unit 1412, exemplary efficiency analyzer 1414, exemplary utilization analyzer 1416, exemplary dock allocation analyzer 1418, exemplary GUI generator 1420, exemplary memory 1422, and / or, more generally, the exemplary main server 122 in Figure 1 can be implemented by hardware, software, firmware, and / or any combination of hardware, software, and / or firmware. Therefore, for example, an exemplary web server 128, an exemplary network communication interface 1402, an exemplary dock controller interface 1404, an exemplary time stamper 1406, an exemplary data logger 1406, an exemplary sensor feedback analyzer 1410, an exemplary target threshold determination unit 1412, an exemplary efficiency analyzer 1414, an exemplary utilization analyzer 1416, an exemplary dock allocation analyzer 1418, an exemplary GUI generator 1420, an exemplary memory 1422, and / or more generally, an exemplary main server 122 Any of these may also be implemented by one or more analog or digital circuits, logic circuits, programmable processors, programmable controllers, graphics processing units (GPUs), digital signal processors (DSPs), application-specific integrated circuits (ASICs), programmable logic devices (PLDs), and / or field-programmable logic devices (FPLDs).When reading any of the claims of the present invention relating purely to implementations of software and / or firmware, at least one of the exemplary web server 128, exemplary network communication interface 1402, exemplary dock controller interface 1404, exemplary time stamper 1406, exemplary data logger 1406, exemplary sensor feedback analyzer 1410, exemplary target threshold determination unit 1412, exemplary efficiency analyzer 1414, exemplary utilization analyzer 1416, exemplary dock allocation analyzer 1418, exemplary GUI generator 1420, and / or exemplary memory 1422 is expressly defined herein as including a memory containing software and / or firmware, a non-temporary computer-readable storage device or storage disk such as a digital versatile disc (DVD), compact disc (CD), or Blu-ray disc. Furthermore, the exemplary main server 122 in Figure 1 may include, in addition to or instead of, those shown in Figure 14, one or more elements, processes, and / or devices, and / or two or more of any or all of the elements, processes, and devices shown.

[0065]

[0074] Figure 15 shows an exemplary productivity GUI 1500 that can be generated by the GUI generator 1420 of Figure 14. The productivity GUI 1500 provides summary statistics generated by one or more of the sensor feedback analyzer 1410, efficiency analyzer 1414, utilization analyzer 1416, and / or dock allocation analyzer 1418 relating to the operation, efficiency, and / or utilization of docks 102 within the material handling equipment 100. The exemplary GUI 1500 in Figure 15 includes a live productivity summary block 1502, a utilization summary block 1504, and a loading time summary block 1506.

[0066]

[0075] The Live Productivity Summary block 1502 provides substantially current (e.g., live) statistics (e.g., updated substantially in real time) associated with the handling of trailers at dock 102 on a given day. In other examples, the Live Productivity Summary block 1502 may provide statistics associated with a different period other than the current day (e.g., the current week, the current month, etc.). In this example, the Productivity Summary block 1502 includes a Load Completion Indicator 1508 showing the total number of loads completed during that period (e.g., the current day). As used herein, the term “load” refers to the loading and / or unloading of a particular trailer. Thus, “completed load” means that a particular trailer has gone through the arrival, material handling, and departure phases at a particular dock 102. In some examples, “load” may exclude some or all of the arrival and departure phases (e.g., load may specifically refer to the material handling phase where the cargo is being loaded and / or unloaded from the trailer). In some examples, the live productivity summary block 1502 includes an efficiency indicator 1510 to show the number and / or percentage of loads completed in a timely manner (e.g., within a target threshold corresponding to delays and / or detention charges) of loads completed during the period (e.g., the day).

[0067]

[0076] In addition to completed loads, the exemplary live productivity summary block 1502 includes a load in progress indicator 1512 to show the number of trailers at dock 102 currently going through the loading and / or unloading process (e.g., one of the arrival, material handling, or departure phases). In some examples, the live productivity summary block 1502 includes additional data indicating delays in the progress of such loads in progress. For example, a delayed indicator 1514 shows the number of loads in progress that have already exceeded the time set for delay and / or leniency charges (e.g., 2 hours). Furthermore, in some examples, a threshold exceeding indicator 1516 indicates that one or more tasks associated with loading and unloading a trailer took longer than the target threshold associated with that task (e.g., defined by the target threshold determination unit 1412).

[0068]

[0077] The exemplary utilization summary block 1504 includes an indication 1518 of the total number of docks in the material handling facility 100 (which may or may not include docks that are not in operation), an indication 1520 of the number of shifts available for dock personnel to work on loads, and a designated trailer capacity 1522 for each of the docks 102 within the facility 100. The trailer capacity 1522 represents the number of trailers that can be loaded or unloaded at dock 102 during a specified period, assuming that each load is completed in a timely manner during the specified period and dock 102 is always in use. In this example, the specified period corresponds to one day. In other examples, the specified period may be defined as a single shift. The exemplary utilization summary block 1504 includes a facility capacity indicator 1524 to show the total number of loads that can be completed within a specified period if all docks were operating at their respective trailer capacity 1522. Therefore, in this example, if there are 38 docks and each dock has a trailer capacity of 8 trailers per day, the total capacity is 38 × 8 = 288 trailers per day. In some examples, the utilization summary block 1504 includes an actual utilization metric 1526 that shows the actual number of completed loads (e.g., trailers) during a specific period as a percentage of the available trailer capacity. In some examples, it may also show the actual number of completed trailer loads. In some examples, the user can specify a particular period as any period in question (e.g., today, last week, current week, current month, etc.).

[0069]

[0078] An exemplary loading time summary block 1506 includes a total completed loading indicator 1528 for a specific period (for example, the same period selected for the utilization summary block 1504). In some examples, the loading time summary block 1506 includes a loading delay indicator 1530 to show the number of trailer loadings that exceeded the time allocated to them during the period in question. A cumulative delay time indicator 1532 shows the total amount of time that loadings associated with the loading delay indicator 1530 exceeded the target threshold for those loadings. In some examples, an average loading time indicator 1534 shows the average time to completion for all loadings associated with the total completed loading indicator 1528.

[0070]

[0079] In some examples, the GUI 1500 in Figure 15 includes a dock-specific summary block 1536 that provides information similar to that outlined above in the live productivity summary block 1502, the utilization rate summary block 1504, and the loading time summary block 1506, except that the information is specific to each particular dock 102 within the facility 100 and / or a particular subset of docks within the facility.

[0071]

[0080] Figure 16 shows an exemplary utilization analysis GUI 1600 that can be generated by the GUI generator 1420. The utilization analysis GUI 1600 provides the results of an analysis by the utilization analyzer 1416 regarding the utilization rates of different docks 102 in facility 100. In some examples, the utilization analysis GUI 1600 includes a utilization heatmap 1602. The exemplary utilization heatmap 1602 includes dock icons 1604 representing each individual dock, along with corresponding utilization indicators 1606. In this example, the appearance (e.g., color, intensity, etc.) of the utilization indicators 1606 differs based on the utilization rate of the corresponding dock. In this particular example, the different appearances of the utilization indicators 1606 include five different groups corresponding to different utilization rates outlined in the legend 1608. The utilization heatmap 1602 allows the user to quickly and easily identify which docks are underutilized and / or overutilized in order to assist in the future allocation of trailers to specific docks. In some examples, the utilization heatmap 1602 can be generated based on historical data corresponding to any user-specified period. In some examples, the utilization analysis GUI 1600 includes a utilization summary block 1504, which is included in the productivity GUI 1500 in Figure 15, to provide context for the utilization heatmap 1602. In the example described in Figure 16, the actual utilization metric 1526 differs from that in Figure 15 because the data represented corresponds to a different period. The actual utilization metric 1526 in Figure 15 corresponds to a single day, while the actual utilization metric 1526 in Figure 16 reflects dock utilization over two weeks.

[0072]

[0081] In some examples, individual dock icons 1604 and / or utilization indicators 1606 can be selected by the user to access more detailed utilization information for a selected dock. In particular, Figure 17 shows an enlarged portion of the utilization GUI 1600 from Figure 16, along with a dock-specific utilization window 1702 opened for a specific dock (in this example, dock number 06). In some examples, the dock-specific utilization window 1702 shows the trailer capacity 1704 assigned to the dock, the average completed load 1706 for the period, and the utilization rate 1708 for the period. Furthermore, in some examples, the dock-specific utilization window 1702 includes a graph 1710 of the number of completed loads (e.g., per day) during the period. In some examples, the dock-specific utilization window 1702 and / or any of the information displayed in the window can be generated independently of the main server 122 by the GUI generator 1318 of the operation controller 1314 of the dock controller 116 corresponding to a specific dock. In some such examples, such information can be drawn for display via the display screen 117 and / or the local status indicator 306.

[0073]

[0082] Figure 18 shows an exemplary efficiency analysis GUI 1800 that can be generated by the GUI generator 1420. The efficiency analysis GUI 1800 provides the results of an analysis by the efficiency analyzer 1414 regarding the efficiency of different docks 102 in facility 100 across different tasks in operation sequences associated with a particular trailer in one dock over a user-specified period. That is, in some examples, the user can select any specific date range 1802 and any specific operation sequence 1804 (by defining the first and last tasks in the sequence of interest) and obtain efficiency information associated with docks in facility for the selected date range and operation sequence. In particular, in some examples, the efficiency analysis GUI 1800 includes an efficiency heatmap 1806. The exemplary efficiency heatmap 1806 in Figure 18 is similar to the utilization heatmap 1602 in Figure 16, except that the appearance (e.g., color, intensity, etc.) of the efficiency indicator 1808 differs based on the average duration for completing a specific operation sequence in each dock during a specific date range specified by the user. In some cases, efficiency indicators 1808 associated with docks having an average sequence duration below a target threshold for that sequence share different common visual characteristics than efficiency indicators 1808 associated with docks having an average sequence duration exceeding the target threshold. For example, in some cases, efficiency indicators 1808 for docks with an average sequence duration below the target threshold can all be the same color (e.g., blue), but can have different intensities (e.g., different shades of blue) depending on how much below the target threshold the average sequence duration for each dock falls. On the other hand, efficiency indicators 1808 for docks with an average sequence duration exceeding the target threshold can be a different color (e.g., red). In this way, docks associated with particularly low efficiency (e.g., average sequence duration exceeding the target threshold) can be quickly and easily identified by the user.In other examples, the efficiency indicator 1808 is associated with consistent or absolute efficiency, and therefore, even if the average sequence duration for a particular dock is less than the target threshold for the selected parameter (e.g., a specific group or set of tasks selected), the appearance of the corresponding efficiency indicator 1808 should be important if even one threshold in the sequence is exceeded. In some examples, the appearance of the efficiency indicator 1808 is based on the most inefficient task (e.g., the task with the longest delay exceeding the target threshold in question) within a particular sequence of tasks selected by the user.

[0074]

[0083] In some examples, the efficiency analysis GUI 1800 includes an efficiency summary block 1810 similar to the loading time summary block 1506 in the productivity GUI 1500 in Figure 15, except that the information in the efficiency summary block 1810 in Figure 18 is based on a specific subset of tasks in an operation sequence selected by the user, rather than the complete loading (including the complete operation sequence for a particular trailer). In the example described in Figure 18, the particular operation sequence includes the duration from when the presence of the vehicle is detected during the arrival phase to when the first loading activity occurs during the material handling phase.

[0075]

[0084] Furthermore, in some examples, the efficiency analysis GUI 1800 includes an efficiency percentage indicator 1814 representing the change in efficiency primarily caused by loads exceeding the target threshold, a display 1816 showing the average length of time that a user-selected action sequence exceeds the target threshold period for a sequence of loads exceeding the target threshold, and an efficiency statistics block 1812 that displays the number of separate trailer loads that exceeded the time and when (e.g., in which shift) such exceedances occurred.

[0076]

[0085] In some examples, the user can select a specific dock (for example, within the efficiency heatmap 1806) and access more specific information regarding the historical efficiency of that particular dock. In particular, Figure 19 is an exemplary dock-specific efficiency GUI 1900 that can be generated by the GUI generator 1420 in response to the user choosing to access additional details regarding the efficiency of a particular dock. In some examples, the additional details provided include a list 1902 of loads completed at a particular dock during a period in which the time limit was exceeded (for example, the duration to completion exceeded a target threshold, or at least one target threshold associated with a particular task or group of tasks in the loading / unloading process was exceeded). Furthermore, in some examples, the user can select any one of the time-exceeded loads identified in the list 1902 and view an operation sequence timeline 1904 showing the actual timing for each task performed on the load. In some examples, the timeline 1904 can be one-dimensional. In other examples, the timeline 1904 can be two-dimensional. More specifically, as illustrated in the example described, the activities and / or tasks associated with the arrival phase 1906 descend vertically while advancing along the horizontal time dimension, the activities and / or tasks associated with the material handling phase 1908 extend horizontally along the time dimension, and the activities and / or tasks associated with the departure phase 1910 ascend vertically while continuing to extend horizontally along the time dimension.

[0077]

[0086] In some examples, each point on the timeline 1904 represents the completion of a particular task (and the corresponding start of the duration for completing the next task). In some examples, a task icon representing each task is provided adjacent to the corresponding point on the timeline 1904 to facilitate user recognition of what each point on the timeline represents. In some examples, the task icons are the same icons used in user interfaces 500-1200 in Figures 5-12 described above. As shown in the examples described, there are multiple points on the timeline 1904 associated with the material handling phase 1908. In some examples, each point within the material handling phase represents a different point in time when activity was detected in the trailer, as determined by a sensor (e.g., motion sensor 204) associated with the presence detector 112 described above with respect to Figures 1-4. By indicating each time activity is detected in the trailer, the user can identify the time distribution of such activity in the material handling phase 1908.

[0078]

[0087] In some examples, the dock-specific efficiency GUI 1900 includes an efficiency target timeline 1912 along with the timeline 1904. In some examples, the efficiency target timeline 1912 has a different appearance (e.g., different color, different intensity, different thickness, dashed and solid lines, etc.) from the timeline 1904 to allow the user to distinguish them from each other. The efficiency target timeline 1912 represents a target threshold defined for the operation sequence in the timeline 1904. In this way, by providing a timeline 1904 along with the efficiency target timeline 1912 that represents the actual completion time / duration of different tasks, the user can quickly and easily identify a particular task(s) that may have caused a particular cargo to exceed its time limit (e.g., exceed the target threshold period for a completed cargo). In this particular example, a quick glance at timeline 1904 against efficiency target timeline 1912 would allow the user to recognize that the significant delay in completing this particular load was due to the engagement and release of the vehicle restraint device 110 (represented by restraint device lock icon 508 and restraint device unlock icon 1106) exceeding the associated target threshold for such tasks. In some examples, task icons (e.g., lock icons 508, 1106) associated with tasks that took longer to complete than the corresponding target threshold have a different appearance (e.g., different color, different intensity) compared to other icons associated with tasks completed within the allocated time (e.g., target threshold). In some examples, only the icon associated with the longest delay changes its appearance.

[0079]

[0088] In some examples, the dock-specific efficiency GUI 1900 provides target thresholds 1914 for different tasks and / or combinations of tasks tracked with respect to a particular dock. Additionally or alternatively, in some examples, actual durations 1916 are represented for different tasks and / or combinations of tasks recorded for a particular trailer's cargo. As shown in the examples described, both the target thresholds 1914 and actual durations 1916 are provided to each other to enable comparison of these values. Furthermore, in some examples, the specific task(s) associated with each target threshold 1914 and actual duration 1916 is identified by including a task icon representing the possible tasks in the complete operational sequence associated with the trailer, along with the target threshold and actual duration (for example, above them). In this particular example, the task icons include a driver arrival icon 1918, a driver check-in icon 1920, a trailer presence icon 504 (discussed above in Figure 5), a vehicle restraint lock icon 508 (discussed above in Figure 5), a barrier open icon 1922, a door open icon 606 (discussed in Figure 6), a leveler engagement icon 706 (discussed above in Figure 7), a trailer activity icon 804 (discussed above in Figure 8), a load completion icon 904 (discussed above in Figure 9), a leveler disengagement icon 908 (discussed above in Figure 9), a door close icon 1006 (discussed above in Figure 10), a barrier close icon 1924, a restraint unlock icon 1106 (discussed above in Figure 11), a trailer departure icon 1204 (discussed above in Figure 12), and a driver check-out icon 1926. In the examples described, some of these icons are grayed out because they are not available for the specific dock represented within the dock-specific efficiency GUI1900.

[0080]

[0089] In some examples, a user can select a specific task (for example, by selecting the corresponding icon) to view the task threshold details 1928. In this example, the task threshold details 1928 include the set target threshold for the task, the actual duration required to complete the task for the cargo of the represented trailer, and the amount of time the task duration exceeded the target threshold. In other examples, all tasks or groups of tasks that exceeded the target threshold for the cargo selected from list 1902 (or all cargoes in list 902) are identified in the task threshold details 1928.

[0081]

[0090] In some examples, some or all of the information represented within the dock-specific efficiency GUI 1900 can be generated independently of the main server 122 by the GUI generator 1318 of the operation controller 1314 of the dock controller 116 corresponding to a particular dock. In some such examples, such information can be drawn for display via the display screen 117 and / or local status indicator 306.

[0082]

[0091] Except for the live productivity summary block 1502 in the exemplary productivity GUI 1500 in Figure 15, which contains data on a cargo in progress, all information in the GUIs in Figures 15-19 is generated based on historical data archived in memory. In some examples, the GUI generator 1420 on the main server 122 can also generate the GUI based on live data that provides additional details on a cargo in progress in virtually real time. For example, Figure 20 is a live dock GUI 2000 that includes a display of the status and / or progress of trailers in a dock in virtually real time. In some examples, trailer icons 2002 are represented adjacent to each dock icon 1604 corresponding to the dock 102 of the facility 100 where the trailer is parked. In some examples, a timing indicator 2004 is included within the trailer icon to show how long the trailer has been in each dock. In some examples, the timing indicator 2004 provides the same timing information as the timing indicator 308 provided to the local status indicator 306. In other words, the timing indicator 2004 in Figure 20 can count up or count down and change its appearance when the time approaches and / or exceeds the target threshold. In addition or by alternative means, the trailer indicator 2002 can change its appearance (e.g., change color, flash, etc.) when the time approaches and / or exceeds the target threshold.

[0083]

[0092] In some examples, moving and / or selecting a specific dock icon 1604 and / or trailer icon 2002 brings up a detailed analysis option 2006, allowing the user to choose to delve deeper and access further details regarding the substantially real-time status and / or progress of the corresponding trailer. Figure 21 shows a dock-specific live status GUI 2100 that can be presented to the user in response to the user selecting the detailed analysis option. The dock-specific live status GUI 2100 contains similar information to that presented in a similar manner to the method described above with respect to the dock-specific efficiency GUI 1900, except that the data represented in Figure 21 corresponds to a cargo in progress and can be updated substantially in real time, as shown in the example described. Therefore, as shown in the example described, none of the icons associated with the departure stage are shown on the timeline because they are not yet completed. In some examples, some or all of the information represented in the dock-specific live status GUI 2100 can be generated independently of the main server 122 by the GUI generator 1318 of the operation controller 1314 of the dock controller 116 corresponding to a specific dock. In some such examples, such information can be drawn for display via the display screen 117 and / or the local status indicator 306.

[0084]

[0093] Figure 22 shows an exemplary driver logbook GUI 2200 that can be generated by the GUI generator 1420. The exemplary driver logbook GUI 2200 provides aggregated cargo information and / or timing information for trailer cargo completed within any preferred period. In some examples, the information represented in the driver logbook GUI 2200 can be classified and / or filtered based on any type of information (e.g., carrier, time, shift, day of the week, inbound or outbound) to focus on trailer cargo having specific characteristics.

[0085]

[0094] Figure 23 shows an exemplary delay reporting GUI 2300 that can be generated by the GUI generator 1420. The exemplary delay reporting GUI 2300 provides aggregated cargo information and / or timing information for trailer cargoes that experienced delays before completion (for example, cargoes that took longer than a target threshold to complete). By organizing such data specifically for overdue cargoes in this way, users can classify and / or filter such cargoes to identify trends and / or patterns that may suggest specific aspects of such delayed cargoes and identify areas to focus on in order to improve efficiency and reduce future delays.

[0086]

[0095] Flowcharts representing exemplary hardware logic, machine-readable instructions, hardware-implemented state machines, and / or any combination thereof for implementing the main server 122 of Figure 1 and / or Figure 14 are shown in Figures 24 to 27. The machine-readable instructions may be one or more executable programs or parts(s) of executable programs for execution by a processor such as the computer processor 2812 shown in the exemplary processor platform 2800 discussed below with respect to Figure 28. The program may be implemented as software stored on a non-temporary computer-readable storage medium such as a CD-ROM, floppy disk, hard drive, DVD, Blu-ray disk, or memory associated with the processor 2812. Alternatively, the entire program and / or parts of the program may be executed by a device other than the processor 2812, and / or by firmware or dedicated hardware. Furthermore, while the exemplary program will be described with reference to the flowcharts shown in Figures 24 to 27, a number of other methods for implementing the exemplary main server 122 may also be used. For example, the execution order of these blocks can be changed, and / or some of the described blocks can be modified, removed, or combined. In addition or alternatively, any or all of the blocks can be implemented by one or more hardware circuits (e.g., discrete and / or integrated analog and / or digital circuits, FPGAs, ASICs, comparators, operational amplifiers (op-amps), logic circuits, etc.) configured to perform the corresponding operations without running software or firmware.

[0087]

[0096] The machine-readable instructions described herein may be stored in one or more of the following formats: compressed format, encrypted format, fragmented format, compiled format, executable format, packaged format, etc. The machine-readable instructions described herein may be stored as data (e.g., parts of instructions, code, coded representation, etc.) that can be used to create, manufacture, and / or form machine-executable instructions. For example, machine-readable instructions may be fragmented and stored in one or more storage devices and / or computing devices (e.g., servers). Machine-readable instructions may require one or more of the following processes to be made directly readable, interpretable, and / or executable by computing devices and / or other machines: installation, modification, adaptation, updating, combining, supplementing, setting up, decryption, restoration, unpacking, distribution, reallocation, compilation, etc. For example, machine-readable instructions may be stored in multiple parts individually compressed, encrypted, and stored in separate computing devices, and these parts, when decrypted, restored, and combined, form a set of executable instructions that implement a program such as those described herein.

[0088]

[0097] In another example, machine-readable instructions can be stored in a state that can be read by a computer, but require additional libraries (e.g., dynamic link libraries (DLLs)), software development kits (SDKs), application programming interfaces (APIs), etc., to execute the instructions on a particular computing device or other device. In yet another example, machine-readable instructions may need to be set up before the machine-readable instructions and / or corresponding program(s) can be executed in whole or in part (e.g., storing settings, entering data, recording network addresses, etc.). Thus, the disclosed machine-readable instructions and / or corresponding program(s) are intended to encompass such machine-readable instructions and / or programs(s) regardless of the specific format or state of the machine-readable instructions and / or programs(s) at the time of storage or otherwise while stationary or in transition.

[0089]

[0098] The machine-readable instructions described herein may be expressed in any past, present, or future instruction language, scripting language, programming language, etc. For example, machine-readable instructions may be expressed using any of the following languages: C, C++, Java®, C#, Perl, Python, JavaScript®, HyperText Markup Language (HTML), Structured Query Language (SQL), Swift, etc.

[0090]

[0099] As described above, the exemplary processes in Figures 24 to 27 can be implemented using executable instructions (e.g., computer and / or machine-readable instructions) stored in non-temporary computer and / or machine-readable media such as hard disk drives, flash memory, read-only memory, compact disks, digital multipurpose disks, caches, random-access memory, and / or any other storage devices or storage disks, where the information is stored for any duration (e.g., over a long period, permanently, in short instances, temporarily for buffering, and / or for caching information). In this specification, the term non-temporary computer-readable media is explicitly defined to include any type of computer-readable storage device and / or storage disk, and to exclude propagating signal and transmission media.

[0091]

[0100] In this specification, “includes” and “equips” (and all their forms and tenses) are used as unrestricted terms. Therefore, whenever a claim uses any form of “includes” or “equips” (e.g., equips, includes, possesses, contains, has, etc.) as a preamble or in the description of any type of claim, it should be understood that additional elements, terms, etc., may exist without exceeding the scope of the corresponding claim or description. In this specification, when the phrase “at least” is used, for example, as a transitional clause in the preamble of a claim, it is unrestricted in the same way that the terms “equips” and “includes” are unrestricted. The term “and / or” when used, for example, in the form of A, B, and / or C, refers to any combination or subset of A, B, and C, such as (1) A alone, (2) B alone, (3) C alone, (4) A and B, (5) A and C, (6) B and C, and (7) A, B and C. In this specification, in the context of describing a structure, component, article, object, and / or thing, the phrase “at least one of A and B” is intended to mean an implementation comprising (1) at least one A, (2) at least one B, and (3) either at least one A and at least one B. Similarly, in this specification, in the context of describing a component, article, object, and / or thing, the phrase “at least one of A or B” is intended to mean an implementation comprising (1) at least one A, (2) at least one B, and (3) either at least one A and at least one B. In this specification, in the context of describing the implementation or execution of a process, instruction, action, activity, and / or step, the phrase “at least one of A and B” is intended to mean an implementation comprising (1) at least one A, (2) at least one B, and (3) either at least one A and at least one B.Similarly, in the context of describing the implementation or execution of a process, instruction, action, activity, and / or step, the phrase “at least one of A or B” is intended to mean (1) at least one A, (2) at least one B, and (3) an implementation comprising either at least one A or at least one B.

[0092]

[0101] In this specification, singular references (e.g., "a," "an," "first," "second," etc.) do not exclude plurals. In this specification, entities with the term "a" or "an" refer to one or more of those entities. In this specification, the terms "a" (or "an"), "one or more," and "at least one" can be used interchangeably. Furthermore, multiple means, elements, or method actions, although listed individually, can be implemented, for example, by a single unit or processor. In addition, individual features can be included in different examples or claims, but these can be combined as appropriate, and inclusion in different examples or claims does not imply that the combination of features is not viable and / or advantageous.

[0093]

[0102] The program in Figure 24 starts in block 2402, where an exemplary target threshold determination unit 1412 sets a target threshold period for a task associated with the completion of the trailer loading or unloading process. In block 2404, an exemplary dock controller interface 1404 receives feedback from a sensor associated with the dock 102. In block 2406, an exemplary sensor feedback analyzer 1410 determines whether the sensor feedback indicates the completion of a task and / or the start of a new task to be completed. If so, control proceeds to block 2408, where an exemplary GUI generator 1420 determines whether the timing indicator 308 should be reset for the new task. If it should be reset, control proceeds to block 2410, where the exemplary GUI generator 1420 restarts the time represented by the timing indicator 308 for the new task. Control then proceeds to block 2410. Returning to block 2406, if the exemplary sensor feedback analyzer 1410 determines that a task is not complete and no new task has been started, control proceeds directly to block 2412. In block 2408, if the exemplary GUI generator 1420 determines not to reset the timing indicator 308 for a new task, control also proceeds directly to block 2412 in this case as well.

[0094]

[0103] In block 2412, the exemplary GUI generator 1420 determines whether to change the appearance of the timing indicator 308 to indicate a change in state relative to the target threshold period associated with the task. In some examples, the change in state may be based on the time represented by the timing indicator 308 approaching the target threshold and / or exceeding the target threshold period. If a change in state should be indicated, control proceeds to block 2414, in which block 2414, the exemplary GUI generator 1420 adjusts the appearance of the timing indicator to indicate the change in state. Control then proceeds to block 2416. If in block 2412 the GUI generator 1420 decides not to change the appearance of the timing indicator, control proceeds to block 2416. In block 2416, the exemplary main server 122 determines whether to continue the process. If the process is to continue, control returns to block 2402. Otherwise, the exemplary process in Figure 24 terminates. Although the program in Figure 24 is described as being implemented by the main server 122, in some examples, the exemplary program may also be implemented by the dock controller 116, either additionally or alternatively.

[0095]

[0104] The exemplary program in Figure 25 begins in block 2502, where an exemplary dock controller interface 1404 receives feedback from a sensor associated with the dock. In block 2504, an exemplary data logger 1406 archives the sensor feedback along with a timestamp (for example, provided by an exemplary time stamper 1406). In block 2506, an exemplary sensor feedback analyzer 1410 calculates the duration to complete the task based on the timestamp associated with the sensor feedback. In block 2508, an exemplary target threshold determination unit 1412 determines whether the target threshold should be updated and / or calculated. If the target threshold should be updated and / or calculated, control proceeds to block 2510, where the exemplary target threshold determination unit 1412 calculates the target threshold for the task based on a statistical analysis of the duration of completed tasks. Control then proceeds to block 2512. If, in block 2508, the exemplary target threshold determination unit 1412 decides not to update and / or calculate the target threshold, control proceeds directly to block 2512. In block 2512, the exemplary main server 122 decides whether to continue the process. If the process continues, control returns to block 2502. Otherwise, the exemplary process in Figure 25 terminates.

[0096]

[0105] The exemplary program in Figure 26 begins in block 2602, where an exemplary dock controller interface 1404 receives feedback from sensors associated with the dock. In block 2604, an exemplary data logger 1406 archives the sensor feedback along with a timestamp (e.g., provided by an exemplary timestamper 1406). In block 2606, an exemplary sensor feedback analyzer 1410 calculates the duration to complete a task based on the timestamp associated with the sensor feedback. In block 2608, an exemplary efficiency analyzer 1414 calculates an efficiency metric associated with the dock. In block 2610, an exemplary utilization analyzer 1416 calculates a utilization metric associated with the dock. In block 2614, an exemplary GUI generator 1420 draws a graphical user interface including summary statistics.

[0097]

[0106] In block 2616, the exemplary web server 128 and / or exemplary network communication interface 1402 determine whether a user request has been received for information associated with a specific date range, a specific sequence of operations, and / or a specific dock(s). If a user request has been received, control proceeds to block 2618, where the efficiency analyzer 1414 and / or utilization analyzer 1416 calculate the relevant statistics based on the requested information. In block 2620, the exemplary GUI generator 1420 draws a graphical user interface containing the relevant statistics. Control then proceeds to block 2628. If no user request has been received in block 2616, control proceeds directly to block 2628. In block 2628, the exemplary main server 122 determines whether to continue the process. If the process continues, control returns to block 2602. Otherwise, the exemplary process in Figure 26 terminates.

[0098]

[0107] The exemplary program in Figure 27 begins in block 2702, where an exemplary dock controller interface 1404 receives feedback from sensors associated with the dock. In block 2704, an exemplary data logger 1406 archives the sensor feedback along with a timestamp (for example, provided by an exemplary time stamper 1406). In block 2706, an exemplary sensor feedback analyzer 1410 calculates the duration to complete a task based on the timestamp associated with the sensor feedback. In block 2708, an exemplary efficiency analyzer 1414 calculates an efficiency metric associated with the dock. In block 2710, an exemplary utilization analyzer 1416 calculates a utilization metric associated with the dock.

[0099]

[0108] In block 2714, the exemplary dock allocation analyzer 1418 determines whether there is a trailer to be allocated. If there is a trailer, control proceeds to block 2716, where the exemplary dock allocation analyzer 1418 determines the recommended dock(s) for the trailer based on the calculated efficiency and / or utilization associated with the dock. In block 2718, the exemplary GUI generator 1420 provides the user with the recommended dock(s) for selection. In some examples, the dock allocation analyzer 1418 can automatically allocate the trailer to a specific dock based on the efficiency and / or utilization calculations. Control then proceeds to block 2720. If there is no trailer to be allocated to a dock in block 2714, control proceeds directly to block 2720. In block 2720, the exemplary main server 122 determines whether to continue the process. If the process continues, control returns to block 2702. Otherwise, the exemplary process in Figure 27 terminates.

[0100]

[0109] Figure 28 is a block diagram of an exemplary processor platform 2800 configured to implement the main server 122 of Figure 1 and / or Figure 14 by executing the instructions of Figures 24 to 27. The processor platform 2800 can be, for example, a server, a personal computer, a workstation, a self-learning machine (e.g., a neural network), a mobile device (e.g., a mobile phone, a smartphone, a tablet such as an iPad®), a personal digital assistant (PDA), an internet device, or any other type of computing device.

[0101]

[0110] The processor platform 2800 described in the example includes a processor 2812. The processor 2812 described in the example is hardware. For example, the processor 2812 can be implemented by one or more integrated circuits, logic circuits, microprocessors, GPUs, DSPs, or controllers from any desired family or manufacturer. The hardware processor can be a semiconductor-based (e.g., silicon-based) device. In this example, the processor implements an exemplary web server 128, an exemplary network communication interface 1402, an exemplary dock controller interface 1404, an exemplary time stamper 1406, an exemplary data logger 1406, an exemplary sensor feedback analyzer 1410, an exemplary target threshold determination unit 1412, an exemplary efficiency analyzer 1414, an exemplary utilization analyzer 1416, an exemplary dock allocation analyzer 1418, and an exemplary GUI generator 1420.

[0102]

[0111] The processor 2812 in the described example includes local memory 2813 (e.g., cache). The processor 2812 in the described example communicates with main memory, which includes volatile memory 2814 and non-volatile memory 2816, via bus 2818. The volatile memory 2814 can be implemented by synchronous dynamic random access memory (SDRAM), dynamic random access memory (DRAM), RAMBUS®, dynamic random access memory (RDRAM®), and / or any other type of random access memory device. The non-volatile memory 2816 can be implemented by flash memory and / or any other desired type of memory device. Access to main memory 2814, 2816 is controlled by a memory controller.

[0103]

[0112] The processor platform 2800 described in the example also includes an interface circuit 2820. The interface circuit 2820 can be implemented by any type of interface standard, such as an Ethernet® interface, Universal Serial Bus (USB), Bluetooth® interface, Near Field Communication (NFC) interface, and / or PCI Express interface.

[0104]

[0113] In the described example, one or more input devices 2822 are connected to the interface circuit 2820. The input device(s) 2822 allows the user to input data and / or commands to the processor 2812. The input device(s) can be implemented by, for example, a voice sensor, microphone, camera (still image or video), keyboard, buttons, mouse, touchscreen, trackpad, trackball, IsoPoint, and / or voice recognition system.

[0105]

[0114] One or more output devices 2824 are also connected to the interface circuit 2820 of the example described. The output devices 2824 can be implemented by, for example, display devices (e.g., light-emitting diodes (LEDs), organic light-emitting diodes (OLEDs), liquid crystal displays (LCDs), cathode ray tube displays (CRTs), in-place switching (IPS) displays, touchscreens, etc.), haptic output devices, printers, and / or speakers. Thus, the interface circuit 2820 of the example described typically includes a graphics driver card, a graphics driver chip, and / or a graphics driver processor.

[0106]

[0115] The interface circuit 2820 in the described example also includes communication devices such as transmitters, receivers, transceivers, modems, residential gateways, wireless access points, and / or network interfaces to facilitate data exchange with external machines (e.g., any type of computing device) via the network 2826. Communication can be carried out via, for example, Ethernet connections, digital subscriber line (DSL) connections, telephone line connections, coaxial cable systems, satellite systems, line-of-sight wireless systems, mobile phone systems, etc.

[0107]

[0116] The processor platform 2800 described in the example also includes one or more mass storage devices 2828 for storing software and / or data. Examples of such mass storage devices 2828 include floppy disk drives, hard drive disks, compact disk drives, Blu-ray disk drives, independent disk redundant array (RAID) systems, and digital versatile disk (DVD) drives. In this example, the mass storage devices include exemplary memory 1422.

[0108]

[0117] The machine-executable instructions 2832 shown in Figures 24 to 27 can be stored in a mass storage device 2828, volatile memory 2814, non-volatile memory 2816, and / or a removable non-temporary computer-readable storage medium such as a CD or DVD.

[0109]

[0118] From the above, it will be understood that exemplary methods, apparatus, and products are disclosed that enable tracking the progress of operational sequences associated with loading and / or unloading trailers parked at one or more docks within a material handling facility by collecting and analyzing data representing tasks associated with such docks. Furthermore, such data can be archived and analyzed to identify or develop target thresholds that can be used as levels for comparing the progress of operational sequences associated with future trailer loads. Furthermore, the archived data can be analyzed to identify factors and / or circumstances that enable increased efficiency of operational sequences for a particular dock. Furthermore, the analysis of the archived data can be used to determine the utilization rates of different docks and to facilitate the allocation of trailers to a particular dock in order to manage (e.g., reduce or concentrate) the wear of equipment associated with any particular dock or group of docks.

[0110]

[0119] Exemplary methods, apparatus, systems, and products for monitoring and controlling loading dock operations are disclosed herein. Further examples and combinations thereof include:

[0111]

[0120] Example 1 includes a sensor feedback analyzer for analyzing feedback from sensors associated with a dock of material handling equipment and determining the duration for completing tasks in an action sequence associated with loading or unloading trailers at the dock based on the feedback; an efficiency analyzer for comparing this duration with a target threshold associated with these tasks; and a user interface generator for generating a user interface that indicates at least one of the duration or the target threshold.

[0112]

[0121] Example 2 includes the apparatus of Example 1, where the user interface generator is for generating a timeline that shows when consecutive tasks in a task were completed relative to previous tasks in the task.

[0113]

[0122] Example 3 includes the apparatus of Example 2, wherein the loading or unloading of the trailer includes an arrival phase, a material handling phase, and a departure phase, and the timeline extends in a first direction during the arrival phase, in a second direction during the material handling phase, and in a third direction during the departure phase, the first direction being different from the second direction, and the second direction being different from the third direction.

[0114]

[0123] Example 4 includes the apparatus of Example 2, where the timeline is a first timeline and the user interface generator is for generating a second timeline based on a target threshold for the task.

[0115]

[0124] Example 5 includes the apparatus of Example 1, and further includes a memory for storing the duration for task completion, and a target threshold determination unit for updating the target threshold based on the stored duration.

[0116]

[0125] Example 6 includes the apparatus of Example 1 and further includes a utilization analyzer for determining utilization metrics for different docks of material handling equipment, and a dock allocation analyzer for assigning a new trailer to one of the different docks based on the utilization metrics.

[0117]

[0126] Example 7 includes the apparatus from Example 6, where the user interface generator is used to generate utilization heatmaps for different docks based on utilization metrics.

[0118]

[0127] Example 8 includes the apparatus of Example 1, where a user interface generator generates a timing indicator to provide a display of time relative to a first target threshold among target thresholds while a first task of the tasks is being completed.

[0119]

[0128] Example 9 includes the apparatus of Example 8, wherein a timing indicator counts up to show the amount of time elapsed since the start of the first task or the completion of at least one of the tasks preceding the first task.

[0120]

[0129] Example 10 includes the apparatus of Example 8, where a timing indicator counts down from a time corresponding to a first target threshold to show the amount of time remaining to complete the first task within the first target threshold.

[0121]

[0130] Example 11 includes a non-temporary computer-readable medium containing instructions, which, when executed, cause a machine to analyze feedback from sensors associated with a dock of material handling equipment, determine, based on the feedback, the duration for completion of tasks in an action sequence associated with loading or unloading trailers at the dock, compare this duration to a target threshold associated with these tasks, and generate a user interface indicating at least one of the duration or the target threshold.

[0122]

[0131] Example 12 includes the non-temporary computer-readable medium of Example 11, where the instruction further causes the machine to generate a timeline showing when consecutive tasks in a task were completed relative to previous tasks in the task.

[0123]

[0132] Example 13 includes the non-temporary computer-readable medium of Example 12, wherein the loading or unloading of the trailer includes an arrival phase, a material handling phase, and a departure phase, and the timeline extends in a first direction during the arrival phase, in a second direction during the material handling phase, and in a third direction during the departure phase, wherein the first direction is different from the second direction, and the second direction is different from the third direction.

[0124]

[0133] Example 14 includes the non-temporary computer-readable medium of Example 12, where the timeline is a first timeline, and the instruction further generates a second timeline for the machine based on a target threshold for the task.

[0125]

[0134] Example 15 includes the non-temporary computer-readable medium of Example 11, where the instruction further causes the machine to store the duration for task completion and update the target threshold based on the stored duration.

[0126]

[0135] Example 16 includes the non-temporary computer-readable medium of Example 11, where the instruction further causes the machine to determine a utilization metric for different docks of material handling equipment, and to assign a new trailer to one of the different docks based on the utilization metric.

[0127]

[0136] Example 17 includes the non-temporary computer-readable medium of Example 16, where the instruction further causes the machine to generate utilization heatmaps for different docks based on utilization metrics.

[0128]

[0137] Example 18 includes the non-temporary computer-readable medium of Example 11, where the instruction further causes the machine to generate a timing indicator while a first task of the tasks is being completed, providing a display of time relative to a first target threshold of the target thresholds.

[0129]

[0138] Example 19 includes the non-temporary computer-readable medium of Example 18, wherein a timing indicator counts up to show the amount of time elapsed since the start of the first task or the completion of at least one of the tasks preceding the first task.

[0130]

[0139] Example 20 includes the non-temporary computer-readable medium of Example 18, where a timing indicator counts down from a time corresponding to a first target threshold to show the amount of time remaining to complete a first task within the first target threshold.

[0131]

[0140] Example 21 includes a method comprising: analyzing feedback from sensors associated with a dock of material handling equipment; determining, based on the feedback, the duration for completion of tasks in an action sequence associated with loading or unloading trailers at the dock; comparing this duration with a target threshold associated with these tasks; and generating a user interface that indicates at least one of the duration or the target threshold.

[0132]

[0141] Example 22 includes the method of Example 21, and further includes the step of generating a timeline showing when consecutive tasks in a task were completed relative to earlier tasks in the task.

[0133]

[0142] Example 23 includes the method of Example 22, wherein the loading or unloading of the trailer includes an arrival phase, a material handling phase, and a departure phase, and the timeline extends in a first direction during the arrival phase, in a second direction during the material handling phase, and in a third direction during the departure phase, the first direction being different from the second direction, and the second direction being different from the third direction.

[0134]

[0143] Example 24 includes the method of Example 22, where the timeline is a first timeline, and the method further includes the step of generating a second timeline based on a target threshold for the task.

[0135]

[0144] Example 25 includes the method of Example 21, further comprising the steps of storing the duration for task completion and updating the target threshold based on the stored duration.

[0136]

[0145] Example 26 includes the method of Example 21, further comprising the steps of determining a utilization metric for different docks of material handling equipment, and assigning a new trailer to one of the different docks based on the utilization metric.

[0137]

[0146] Example 27 includes the method of Example 26, and further includes the step of generating utilization heatmaps for different docks based on utilization metrics.

[0138]

[0147] Example 28 includes the method of Example 21, further comprising the step of generating a timing indicator to provide a time indication of the first target threshold among the target thresholds while the first task of the tasks is being completed.

[0139]

[0148] Example 29 includes the method of Example 28, wherein the timing indicator counts up to show the amount of time elapsed since the start of the first task or the completion of at least one of the tasks preceding the first task.

[0140]

[0149] Example 30 includes the method of Example 28, where a timing indicator counts down from a time corresponding to a first target threshold to show the amount of time remaining to complete the first task within the first target threshold.

[0141]

[0150] While specific exemplary methods, apparatuses, and products are disclosed herein, the scope of this patent is not limited thereto. Conversely, this patent encompasses all methods, apparatuses, and products that appropriately fall within the scope of the claims herein.

[0142]

[0151] The following claims are incorporated herein by reference into this detailed description, and each claim constitutes a separate embodiment of the present disclosure.

Claims

1. A sensor feedback analyzer for analyzing feedback from sensors associated with a dock of material handling equipment and determining multiple durations for the completion of multiple corresponding tasks in an operation sequence associated with loading or unloading a trailer in the dock, wherein the tasks in the operation sequence include (i) positioning the trailer in the dock, (ii) activating a vehicle restraint device to secure the trailer in the dock, (iii) opening the dock door, and (iv) activating a dock leveler to straddle the gap between the trailer and the dock platform. An efficiency analyzer for comparing the duration with a target threshold associated with the task, A user interface generator for generating a user interface that shows at least one of the duration, the target threshold, or the difference between the duration and the target threshold. A device equipped with the following features.

2. A sensor feedback analyzer for analyzing feedback from sensors associated with a dock of material handling equipment, and for determining, based on the feedback, multiple durations for the completion of multiple corresponding tasks in an operation sequence associated with loading or unloading a trailer in the dock, An efficiency analyzer for comparing the duration with a target threshold associated with the task, A user interface generator for generating a user interface that shows at least one of the duration, the target threshold, or the difference between the duration and the target threshold. Equipped with, A device wherein the user interface generator generates a timeline indicating when consecutive tasks among the tasks were completed relative to previous tasks among the tasks.

3. The apparatus according to claim 2, wherein the loading or unloading of the trailer includes an arrival stage, a material handling stage, and a departure stage, and the timeline extends in a first direction during the arrival stage, extends in a second direction during the material handling stage, and extends in a third direction during the departure stage, wherein the first direction is different from the second direction, and the second direction is different from the third direction.

4. The apparatus according to claim 2, wherein the timeline is a first timeline, the user interface generator is for generating a second timeline different from the first timeline, and the second timeline indicates the time when consecutive tasks among the tasks are targeted to be completed based on the target threshold for the tasks.

5. A sensor feedback analyzer for analyzing feedback from sensors associated with a dock of material handling equipment, and for determining, based on the feedback, a plurality of durations for the completion of a plurality of corresponding tasks in an operation sequence associated with loading or unloading a trailer in the dock, An efficiency analyzer for comparing the duration with a target threshold associated with the task, A user interface generator for generating a user interface that shows at least one of the duration, the target threshold, or the difference between the duration and the target threshold, A memory for storing the duration for the completion of the aforementioned task, Based on the stored duration, a target threshold determination unit for updating the target threshold and A device including a device.

6. A sensor feedback analyzer for analyzing feedback from sensors associated with a dock of material handling equipment, and for determining, based on the feedback, a plurality of durations for the completion of a plurality of corresponding tasks in an operation sequence associated with loading or unloading a trailer in the dock, An efficiency analyzer for comparing the duration with a target threshold associated with the task, A user interface generator for generating a user interface that shows at least one of the duration, the target threshold, or the difference between the duration and the target threshold, A utilization analyzer for determining the utilization metric for different docks of the aforementioned material handling equipment, Based on the utilization metric, a dock allocation analyzer is used to assign a new trailer to one of the different docks. A device including a device.

7. The apparatus according to claim 6, wherein the user interface generator is for generating utilization heatmaps for the different docks based on the utilization metric.

8. A sensor feedback analyzer for analyzing feedback from sensors associated with a dock of material handling equipment, and for determining, based on the feedback, a plurality of durations for the completion of a plurality of corresponding tasks in an operation sequence associated with loading or unloading a trailer in the dock, An efficiency analyzer for comparing the duration with a target threshold associated with the task, A user interface generator for generating a user interface that shows at least one of the duration, the target threshold, or the difference between the duration and the target threshold. Equipped with, An apparatus wherein the user interface generator generates a timing indicator while a first task of the tasks is being completed, to provide a display of time relative to a first target threshold of the target thresholds.

9. The apparatus according to claim 8, wherein the timing indicator counts up to indicate the amount of time elapsed since the start of the first task or the completion of a task preceding the first task.

10. The apparatus according to claim 8, wherein the timing indicator counts down from a time corresponding to the first target threshold to indicate the amount of time remaining to complete the first task within the first target threshold.

11. A computer-readable medium containing instructions, wherein when the instructions are executed, the machine has at least: The system analyzes feedback from sensors associated with a dock of a material handling facility, and based on the feedback, determines multiple durations for the completion of multiple corresponding tasks in an operation sequence associated with loading or unloading a trailer in the dock, wherein the tasks in the operation sequence include (i) moving the dock leveler to a storage position spaced apart from the trailer, (ii) closing the dock door, (iii) deactivating the vehicle restraint device to release the trailer, and (iv) moving the trailer away from the dock. The duration is compared with the target threshold associated with the task. A computer-readable medium that generates a user interface indicating at least one of the duration, the target threshold, or the difference between the duration and the target threshold.

12. A computer-readable medium containing instructions, wherein when the instructions are executed, the machine has at least: The system analyzes feedback from sensors associated with the dock of the material handling equipment, and based on the feedback, determines multiple durations for the completion of multiple corresponding tasks within an operation sequence associated with loading or unloading trailers at the dock. The duration is compared with the target threshold associated with the task. To generate a user interface that shows at least one of the duration, the target threshold, or the difference between the duration and the target threshold, A computer-readable medium that generates a timeline showing when consecutive tasks among the aforementioned tasks were completed relative to previous tasks among the aforementioned tasks.

13. The computer-readable medium according to claim 12, wherein the loading or unloading of the trailer includes an arrival stage, a material handling stage, and a departure stage, and the timeline extends in a first direction during the arrival stage, extends in a second direction during the material handling stage, extends in a third direction during the departure stage, the first direction being different from the second direction, and the second direction being different from the third direction.

14. The computer-readable medium according to claim 12, wherein the timeline is a first timeline, and the instruction further causes the machine to generate a second timeline based on the target threshold for the task.

15. A computer-readable medium containing instructions, wherein when the instructions are executed, the machine has at least: The system analyzes feedback from sensors associated with the dock of the material handling equipment, and based on the feedback, determines multiple durations for the completion of multiple corresponding tasks within an operation sequence associated with loading or unloading trailers at the dock. The duration is compared with the target threshold associated with the task. To generate a user interface that shows at least one of the duration, the target threshold, or the difference between the duration and the target threshold, The duration for completing the aforementioned task is stored, A computer-readable medium that updates the target threshold based on the stored duration.

16. A computer-readable medium containing an instruction, wherein when the instruction is executed, the machine has at least: The system analyzes feedback from sensors associated with the dock of the material handling equipment, and based on the feedback, determines multiple durations for the completion of multiple corresponding tasks within an operation sequence associated with loading or unloading trailers at the dock. The duration is compared with the target threshold associated with the task. To generate a user interface that shows at least one of the duration, the target threshold, or the difference between the duration and the target threshold, Determine the utilization rate metric for the different docks of the aforementioned material handling equipment. A computer-readable medium that, based on the utilization metric, assigns a new trailer to one of the different docks.

17. The computer-readable medium according to claim 16, wherein the instruction further causes the machine to generate utilization heatmaps for the different docks based on the utilization metric.

18. A computer-readable medium containing instructions, wherein when the instructions are executed, the machine has at least: The system analyzes feedback from sensors associated with the dock of the material handling equipment, and based on the feedback, determines multiple durations for the completion of multiple corresponding tasks within an operation sequence associated with loading or unloading trailers at the dock. The duration is compared with the target threshold associated with the task. To generate a user interface that shows at least one of the duration, the target threshold, or the difference between the duration and the target threshold, A computer-readable medium that generates a timing indicator and provides a display of time relative to the first target threshold among the target thresholds while the first of the aforementioned tasks is being completed.

19. The computer-readable medium according to claim 18, wherein the timing indicator counts up to indicate the amount of time elapsed since the start of the first task or the completion of a task preceding the first task.

20. The computer-readable medium according to claim 18, wherein the timing indicator counts down from a time corresponding to the first target threshold to indicate the amount of time remaining to complete the first task within the first target threshold.

21. Steps include analyzing feedback from sensors associated with a dock of material handling equipment, and determining, based on the feedback, multiple durations for the completion of multiple corresponding tasks in an operation sequence associated with loading or unloading a trailer in the dock, wherein the tasks in the operation sequence include (i) positioning the trailer in the dock, (ii) activating a vehicle restraint device to secure the trailer in the dock, (iii) opening the dock door, and (iv) activating a dock leveler to straddle the gap between the trailer and the dock platform. The steps include comparing the duration with a target threshold associated with the task, A step of generating a user interface that shows at least one of the duration, the target threshold, or the difference between the duration and the target threshold. A method that includes this.

22. A step of analyzing feedback from a sensor associated with a dock of material handling equipment, and determining, based on the feedback, a plurality of durations for the completion of a plurality of corresponding tasks in an operation sequence associated with loading or unloading a trailer in the dock, The steps include comparing the duration with a target threshold associated with the task, A step of generating a user interface that shows at least one of the duration, the target threshold, or the difference between the duration and the target threshold, A step of generating a timeline showing when consecutive tasks among the aforementioned tasks were completed for previous tasks among the aforementioned tasks. Methods that include...

23. The method according to claim 22, wherein the loading or unloading of the trailer includes an arrival stage, a material handling stage, and a departure stage, and the timeline extends in a first direction during the arrival stage, extends in a second direction during the material handling stage, and extends in a third direction during the departure stage, wherein the first direction is different from the second direction, and the second direction is different from the third direction.

24. The method according to claim 22, wherein the timeline is a first timeline, and the method further comprises the step of generating a second timeline based on the target threshold for the task.

25. A step of analyzing feedback from a sensor associated with a dock of material handling equipment, and determining, based on the feedback, a plurality of durations for the completion of a plurality of corresponding tasks in an operation sequence associated with loading or unloading a trailer in the dock, The steps include comparing the duration with a target threshold associated with the task, A step of generating a user interface that shows at least one of the duration, the target threshold, or the difference between the duration and the target threshold, A step of storing the duration for the completion of the task, The steps include updating the target threshold based on the stored duration and Methods that include...

26. A step of analyzing feedback from a sensor associated with a dock of material handling equipment, and determining, based on the feedback, a plurality of durations for the completion of a plurality of corresponding tasks in an operation sequence associated with loading or unloading a trailer in the dock, The steps include comparing the duration with a target threshold associated with the task, A step of generating a user interface that shows at least one of the duration, the target threshold, or the difference between the duration and the target threshold, The steps include determining the utilization rate metric for different docks of the material handling equipment, The steps include: assigning a new trailer to one of the different docks based on the utilization rate metric; Methods that include...

27. The method according to claim 26, further comprising the step of generating utilization heatmaps for the different docks based on the utilization metric.

28. A step of analyzing feedback from a sensor associated with a dock of material handling equipment, and determining, based on the feedback, a plurality of durations for the completion of a plurality of corresponding tasks in an operation sequence associated with loading or unloading a trailer in the dock, The steps include comparing the duration with a target threshold associated with the task, A step of generating a user interface that shows at least one of the duration, the target threshold, or the difference between the duration and the target threshold, While the first of the aforementioned tasks is being completed, the steps include: generating a timing indicator to provide a time representation of the first target threshold among the target thresholds; Methods that include...

29. The method according to claim 28, wherein the timing indicator counts up to indicate the amount of time elapsed since the start of the first task or the completion of a task preceding the first task.

30. The method according to claim 28, wherein the timing indicator counts down from a time corresponding to the first target threshold to indicate the amount of time remaining to complete the first task within the first target threshold.

Images