Method of managing work orders performed in warehouse and electronic device thereof
Patent Information
- Application Number
- TW112150834
- Authority / Receiving Office
- TW · TW
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2022-12-27
- Filing Date
- 2023-12-26
- Publication Date
- 2026-11-11
- Estimated Expiration
- 2043-12-25
Smart Images

Figure TWG2TB001920236_001 
Figure TWG2TB001920236_002 
Figure TWG2TB001920236_003
Abstract
Description
Technical Field
[0001] The present invention relates to a technology for managing work orders implemented in a sorting warehouse. Prior Art
[0002] Within a sorting warehouse, users (or workers) execute various work orders. Using their own terminals, users receive work orders from the server and execute them. The operations performed within a sorting warehouse can be broadly categorized into the ordering phase, the unloading phase, the inbound (or receiving) process, the display process, the picking process, and the outbound process. For example, a user must perform a series of actions to receive a specific item into the warehouse.
[0003] When a user performs a specific action on a terminal device, the user's (or their terminal device's) progress status changes accordingly. The progress status refers to the current status of the work the user is currently performing on a job order. In other words, the user's progress status changes when the user's terminal device performs an action. However, if a problem or error occurs on the server or terminal device for various reasons, the progress status will not change regardless of how many times the user performs the specific action. Summary of the Invention
[0004] [Problems to be solved by the invention]
[0005] According to various embodiments of the present invention, the technical problem to be solved is: receiving at least one abnormal request from multiple terminal devices owned by multiple users, analyzing the received at least one abnormal request, and determining whether a problem has occurred. On the user's terminal device, due to a code problem, the progress status may not change (the current page may not switch to the next page). Furthermore, if an unknown error occurs on the server, the progress status may not change even if the user performs a specific activity. Furthermore, even if no error has occurred on the server, if data is missing in the response, the progress status may not change. In these situations, if the specific activity occurs multiple times consecutively on the user's terminal device, the electronic device may determine that an error related to the specific activity has occurred.
[0006] According to various embodiments of the present invention, the technical problem to be solved is to quickly determine whether a problem has occurred and quickly implement appropriate responses to the problem. [Technical means to solve the problem]
[0007] According to various embodiments of the present invention, an electronic device for managing work orders executed in a sorting warehouse may include: a communication circuit connected to a plurality of terminal devices owned by a plurality of users; a memory; and a processor. The work order includes a plurality of progress states and a plurality of activities that can be executed in the plurality of progress states. The processor in various embodiments may be configured as follows: receiving at least one abnormal request related to the plurality of activities from the plurality of terminal devices; recording the at least one abnormal request based on the time at which the at least one abnormal request was generated and the activity that generated the at least one abnormal request; generating a first table of the number of abnormal request occurrences corresponding to the time based on the recorded at least one abnormal request; determining whether there is a specific time period in the first table in which the number of abnormal request occurrences exceeds a preset first threshold; and in response to the presence of a specific time period in which the number of abnormal request occurrences exceeds the first threshold, determining that a problem has occurred in the specific time period.
[0008] The processor of various embodiments can be configured as follows: in response to a specific time period in which the number of abnormal requests exceeding the first critical value does not exist, it is determined that no problem has occurred.
[0009] The processor of various embodiments may be configured in the following manner: in response to determining that a problem situation occurs within the specific time period, a notification regarding the problem situation is transmitted to a terminal device of an administrator.
[0010] The processor of various embodiments can be configured as follows: transmitting a guideline for resolving the problem to at least one terminal device, the at least one terminal device being one of the plurality of terminal devices that transmits an abnormal request generated during the specific time period.
[0011] The above-mentioned processor of various embodiments can be constructed in the following manner: for each of the above-mentioned multiple activities, a plurality of second graphs are generated, which show the number of abnormal requests generated corresponding to time, and it is determined whether there is a specific time period in each of the above-mentioned multiple second graphs in which the number of abnormal requests generated exceeds a preset second critical value. In response to the existence of a specific time period in a specific graph among the above-mentioned multiple second graphs in which the number of abnormal requests generated exceeds the above-mentioned second critical value, the specific activity corresponding to the above-mentioned specific graph is determined to have a problem in the above-mentioned specific time period.
[0012] The processor of various embodiments can be configured as follows: in response to the absence of a specific time period in each of the plurality of second graphs in which the number of abnormal requests generated exceeds the second critical value, it is determined that no problem has occurred.
[0013] The processor of various embodiments can be configured as follows: in response to determining that the specific activity is a problem occurring during the specific time period, a notification regarding the specific activity and the problem occurring during the specific time period is transmitted to the administrator's terminal device.
[0014] The processor of various embodiments can be configured as follows: when a request to complete the execution of a specific activity among the multiple activities is received continuously from a specific terminal device more than a predetermined number of times, it is determined that an abnormal request related to the specific activity is received from the specific terminal device.
[0015] The processor of various embodiments can be configured as follows: when a predetermined abnormal activity among the plurality of activities is continuously received from the specific terminal device for more than a predetermined number of times, it is determined that a normal request related to the abnormal activity is received from the specific terminal device.
[0016] The first threshold value in various embodiments may be determined based on the average number of abnormal requests generated per unit time.
[0017] Various embodiments of the present invention include methods for managing work orders executed in a sorting warehouse by means of electronic devices, which may include the following actions: receiving at least one abnormal request related to a plurality of activities from a plurality of terminal devices; recording the at least one abnormal request based on the time of generation of the at least one abnormal request and the activity that generated the at least one abnormal request; generating a first chart of the number of times the abnormal request was generated corresponding to the time based on the recorded at least one abnormal request; determining whether there is a specific time period in the first chart in which the number of times abnormal requests were generated exceeds a preset first critical value; and in response to the existence of a specific time period in which the number of times abnormal requests were generated exceeds the first critical value, determining that a problem occurred in the specific time period; the work order includes a plurality of ongoing states and a plurality of activities that can be executed in the plurality of ongoing states. [Effects of the Invention]
[0018] According to various embodiments of the present invention, at least one abnormal request can be received from a plurality of terminal devices owned by each of a plurality of users, and the at least one abnormal request received can be analyzed to determine whether a problem has occurred.
[0019] According to various embodiments of the present invention, it is possible to quickly determine whether a problem has occurred and to quickly implement appropriate responses to the problem. Simple diagram description
[0020] FIG1 is a diagram showing a system according to various embodiments of the present invention. FIG2 is a block diagram showing an electronic device and a terminal device according to various embodiments of the present invention. FIG3 is a flowchart of the operation of the electronic device according to various embodiments of the present invention. FIG. 4 a is a diagram showing a first table of abnormal requests generated in a plurality of terminal devices when no problem occurs according to various embodiments of the present invention. FIG. 4 b is a diagram showing a first graph of the number of times abnormal requests are generated in a plurality of terminal devices corresponding to time when a problem occurs according to various embodiments of the present invention. FIG5 is a flowchart illustrating the operation of the electronic device according to various embodiments of the present invention. FIG6 is a flowchart illustrating the operation of the electronic device according to various embodiments of the present invention. FIG. 7 a shows a plurality of second graphs related to abnormal requests for each of a plurality of activities generated in a plurality of terminal devices when no problem occurs according to various embodiments of the present invention. FIG. 7 b is a diagram showing a plurality of second graphs showing the number of times abnormal requests are generated in a plurality of terminal devices corresponding to the time of each of a plurality of activities when a problem occurs according to various embodiments of the present invention. Implementation Method
[0021] The embodiments of the present invention are provided for the purpose of illustrating the technical concept of the present invention. The scope of the patent application of the present invention is not limited to the following embodiments or the detailed description of these embodiments.
[0022] Unless otherwise defined, all technical and scientific terms used in this disclosure have the meanings commonly understood by those skilled in the art to which this disclosure relates. All terms used in this disclosure are selected to more clearly describe the present invention and are not intended to limit the scope of the present invention.
[0023] Expressions such as “including,” “having,” and “having” used in the present invention should be understood as open-ended terms that may include other embodiments, unless otherwise stated in the sentence or text containing the corresponding expression.
[0024] Singular expressions described in the present invention may include plural expressions unless otherwise mentioned, and the same applies to singular expressions recorded in the scope of patent applications.
[0025] The expressions "first" and "second" used in the present invention are used to distinguish multiple components from each other and do not limit the order or importance of these components.
[0026] As used herein, the term "component" refers to software or hardware components such as FPGAs (field-programmable gate arrays) and ASICs (application-specific integrated circuits). However, "component" is not limited to hardware and software. A "component" can be implemented as a memory device located on an addressable storage medium or as a representation of one or more processors. Thus, for example, a "component" includes components such as software components, object-oriented software components, class components, and task components, processes, functions, properties, procedures, routines, code snippets, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The components and the functions provided within them can be combined into a smaller number of components and "components," or further separated into additional components and "components."
[0027] The expression "based on ~" used in the present invention is used to describe one or more factors described in the sentence or article containing the expression that affect the behavior or action of determination or judgment. The expression does not exclude other factors that affect the behavior or action of determination or judgment.
[0028] In the present invention, when it is mentioned that a certain component is "connected" or "linked" to another component, it should be understood that the above-mentioned component can be directly connected or linked to the above-mentioned other component, or can be connected or linked to the above-mentioned other component through a new other component as a medium.
[0029] The following describes embodiments of the present invention with reference to the accompanying drawings. In the accompanying drawings, identical or corresponding components are denoted by the same reference numerals. In the following descriptions of the embodiments, repeated descriptions of identical or corresponding components may be omitted. However, even if the description of a component is omitted, it does not mean that such component is not included in a particular embodiment.
[0030] FIG1 is a diagram illustrating a system 10 according to various embodiments of the present invention. The system 10 may include an electronic device 110 and a plurality of terminal devices 120. The electronic device 110 may be a server device for operating a sorting warehouse management system (WMS). The plurality of terminal devices 120 may refer to terminal devices owned by a plurality of users (or a plurality of workers) who execute various work orders in a sorting warehouse. The terminal device 120 may be a device capable of connecting to the Internet, for example, a personal digital assistant (PDA), a mobile phone, a smartphone, a notebook computer, a wearable device, or an HMD (head mounted display).
[0031] The plurality of terminal devices 120 in various embodiments can connect to the electronic device 110 via a network and exchange various data. The electronic device 110 can provide various job orders to the plurality of terminal devices 120. For example, a first user can request the electronic device 110 to assign a job order via the first terminal device 120a. In this case, the electronic device 110 can assign a specific job order to the first user and transmit the specific job order assigned to the first terminal device 120a. The first user can confirm and execute the specific job order assigned by the first terminal device 120a. In this figure, the plurality of terminal devices 120 are shown to include the first terminal device 120a, the second terminal device 120b, and the third terminal device 120c. However, it is apparent that the number of the plurality of terminal devices 120 may be greater than that shown.
[0032] Work orders in various embodiments may include multiple progress states and multiple activities that can be performed within each of these progress states. A progress state refers to the progress state of a work order assigned to a user (or a user's terminal device), and the work order may display the current tasks to be performed. When at least one activity is performed within a specific progress state, the work order may be changed (transitioned) to the next progress state.
[0033] For example, the progress status of a picking process can include "job allocation required," "container allocation required," "location movement," "picking status," and "destination movement." When the progress status is "job allocation required," actions such as "allocation action" and "movement to another process" can be performed. When the progress status is "container allocation required," actions such as "container barcode scanning action" and "accepting the assigned job release action" can be performed. When the progress status is "location movement," actions such as "location barcode scanning action," "accepting the assigned job release action," "location problem reporting action," and "container completion action" can be performed. When the progress status is "picking status," actions such as "product placement action," "problem reporting action," "accepting the assigned job release action," and "container completion action" can be performed. When the progress status is "destination movement," actions such as "next job allocation action" and "job completion action" can be performed. The tote disclosed in this specification is a basket for placing merchandise, and may be a plastic basket. The above content is an example. In addition to the content described above, the work order may also include various progress statuses and activities.
[0034] The first user, using the first terminal device 120a, accepts a specific work order assigned to them, assuming that this specific work order is an order to pick and ship X items. The current progress status of the first user (or the first terminal device 120a) who receives this specific work order may be "Shipping box allocation required." While the first user (or the first terminal device 120a owned by the first user) is in the "Shipping box allocation required" progress status, the first user can perform an action called "Shipping box barcode scanning" to allocate a shipping box, and the first user's progress status may be changed to "Location movement status." In a similar manner to the above, the first user can perform multiple actions included in the work order.
[0035] The electronic device 110 of various embodiments can receive at least one abnormal request related to multiple activities from multiple terminal devices 120. Specifically, if a specific terminal device receives a predetermined number of consecutive requests to complete a specific activity from a specific terminal device, the electronic device 110 can determine that an abnormal request related to the specific activity has been received from the specific terminal device. If a problem occurs in the electronic device 110 or the terminal device 120, the progress status will not change even if the designated activity is executed. If an unexplained error occurs in the electronic device 110 acting as a server, the progress status will not change even if the specific activity is executed (completed) on the terminal device 120.
[0036] Even if the terminal device 120 normally transmits a request for a specific activity to the electronic device 110, if a problem occurs in the electronic device 110 or the terminal device 120, the request cannot be properly processed in the electronic device 110. In the above situation, the terminal device 120 may repeatedly transmit the request for the specific activity to the electronic device 110. For example, if a user repeatedly presses a button to complete the execution of the specific activity through the terminal device 120, the terminal device 120 may repeatedly transmit the request to complete the execution of the specific activity to the electronic device 110. In other words, the electronic device 110 may determine that the repeated request received from the terminal device 120 is an abnormal request. The term "receiving an abnormal request" disclosed in this specification may refer to: the electronic device 110 continuously receiving a request for the specific activity from the terminal device 120 more than a predetermined number of times. That is, even if the terminal device 120 transmits the request for a specific activity to the electronic device 110 normally, if the above request is continuously transmitted to the electronic device 110 more than a predetermined number of times, the electronic device 110 may also determine that an abnormal request related to the specific activity is received from the terminal device 120.
[0037] For example, if a first user is in the "box allocation required state" and can perform an action called "box barcode scanning" using first terminal device 120a, but an error occurs in electronic device 110, even if the first user performs the "box barcode scanning" action multiple times, the box cannot be allocated, and the progress state cannot be changed to "location movement state." In this case, electronic device 110 may receive a predetermined number of consecutive requests for completion of the "box scanning action" from first terminal device 120a. In this case, electronic device 110 may determine that an abnormal request (i.e., an abnormal request) related to the "box scanning action" has been received from first terminal device 120a. In other words, electronic device 110 may determine that an abnormal request related to the "box scanning action" has been generated by first terminal device 120a.
[0038] In various embodiments, the electronic device 110 can receive at least one abnormal request related to a plurality of activities from a plurality of terminal devices 120 and record the at least one abnormal request based on the time at which the at least one abnormal request was generated and the activity that generated the at least one abnormal request. Based on the recorded at least one abnormal request, the electronic device 110 can determine whether a problem has occurred. The specific determination method is described below.
[0039] FIG. 2 is a block diagram showing an electronic device 110 and a terminal device 120 according to various embodiments of the present invention.
[0040] 2 , electronic device 110 in various embodiments may include a processor 111, a memory 113, and a communication circuit 115. At least one of the components included in electronic device 110 may be omitted, or other components may be added to electronic device 110. Some components may be integrated additionally or alternatively to implement the electronic device 110, or implemented as a single or multiple components. At least some of the components within electronic device 110 may be connected to each other via a bus, general purpose input / output (GPIO), SPI (serial peripheral interface), or MIPI (mobile industry processor interface), etc., to transmit and receive data and / or signals.
[0041] According to various embodiments, the processor 111 of the electronic device 110 may be configured to control various components of the electronic device 110 (e.g., the memory 113) and / or perform communication-related calculations or data processing. For example, the processor 111 may be operatively connected to the components of the electronic device 110. The processor 111 may load commands or data received from other components of the electronic device 110 into the memory 113, process the commands or data stored in the memory 113, and store the resulting data. The processor 111 disclosed herein may also refer to a collection of more than one processor 111.
[0042] According to various embodiments, the memory 113 of the electronic device 110 may store instructions for executing the processor 111. The memory 113 may also store various information about the online store. The memory 113 may include information about each of the multiple products sold in the online store. For example, the information about each of the multiple products may include detailed product information, the product's price, and the product's scheduled delivery date.
[0043] According to various embodiments, the communication circuit 115 of the electronic device 110 can establish a wired or wireless communication channel with an external device (e.g., the terminal device 120) to transmit and receive various data with the external device. According to one embodiment, to enable wired communication with the external device, the communication circuit 115 may include at least one port for connecting to the external device via a wired cable. In this case, the communication circuit 115 can communicate with the wired external device via the at least one port. According to one embodiment, the communication circuit 115 can be configured as follows: including a cellular communication module to connect to a cellular network (e.g., 3G (3rd Generation Mobile Communication Technology), LTE (Long-Term Evolution), 5G (5th Generation Mobile Communication Technology), Wibro (Wireless Broadband), or Wimax (Worldwide Interoperability for Microwave Access)). According to various embodiments, the communication circuit 115 may include a short-range communication module and utilize short-range communication (e.g., Wi-Fi (Wireless Fidelity), Bluetooth, Bluetooth Low Energy (BLE), or UWB (Ultra Wide Band)) to transmit and receive data with an external device, but the present invention is not limited thereto. According to one embodiment, the communication circuit 115 may include a contactless communication module for contactless communication. Contactless communication may include, for example, at least one contactless short-range communication technology such as NFC (near field communication), RFID (radio frequency identification), or MST (magnetic secure transmission).
[0044] The terminal device 120 of various embodiments may include a controller 121, a memory 123, a display 125, and a communication circuit 127. Even if a portion of the components shown in FIG2 is omitted or replaced, it will not hinder the implementation of the various embodiments disclosed herein.
[0045] The controller 121 of the terminal device 120 in various embodiments is configured to control the various components of the terminal device 120 and / or perform communication-related calculations or data processing. For example, the controller 121 may be operatively connected to the components of the terminal device 120. The controller 121 may load commands or data received from other components of the terminal device 120 into the memory 123 of the terminal device 120, process the commands or data stored in the memory 123, and store the resulting data.
[0046] The memory 123 of various embodiments can store instructions for the operation of the controller 121 .
[0047] The display 125 of the terminal device 120 in various embodiments can display various screens under the control of the controller 121. The display 125 can be implemented in the form of a touch sensor panel (TSP) that detects the contact or proximity of various external objects (e.g., a finger). Touch sensor panels can have various structures and types, and the present invention is applicable to all touch sensor panels regardless of their structure and type. The display 125 can include an electrostatic capacitive sensor to detect the contact or proximity of various external objects. The electrostatic capacitive sensor can include a plurality of capacitors, and the electrostatic capacitive sensor can apply an electrical signal to the capacitors. The capacitors can charge and discharge in response to the application of the electrical signal. When an electrical signal is applied to the capacitors, the capacitors are charged according to the voltage of the electrical signal. The display 125 can receive touch input based on the signal collected from the electrostatic capacitive sensor. For example, the display 125 can receive a tap touch, a double tap touch, a sliding touch, a drag & drop touch, and a long touch from the user.
[0048] The controller 121 of various embodiments may provide (display) various screens for executing job orders via the display 125 .
[0049] FIG3 is a flowchart of the operation of the electronic device 110 according to various embodiments.
[0050] Referring to action flow chart 300, in action 310, the processor 111 of the electronic device 110 of various embodiments may receive at least one abnormal request related to a plurality of activities from a plurality of terminal devices 120. A plurality of users may execute a work order to be executed in a sorting warehouse via the plurality of terminal devices 120. The work order may include a plurality of progress states and a plurality of activities that can be executed in the plurality of progress states. A user may transmit an abnormal request related to a plurality of activities included in the work order to the electronic device 110 via the terminal device 120. For example, an abnormal request related to activity X may be received from the first terminal device 120a of the first user, an abnormal request related to activity Y may be received from the second terminal device 120b of the second user, and no abnormal request may be received from the third terminal device 120c of the third user. At least one abnormal request related to a plurality of activities may be received from the plurality of terminal devices 120 using a method similar to the above method.
[0051] When a specific terminal device receives a predetermined number of consecutive requests to complete a specific activity, the processor 111 may determine that an abnormal request related to the specific activity has been received from the specific terminal device. For example, when a first terminal device 120a receives five or more consecutive requests to complete an activity X, the processor 111 may determine that an abnormal request related to activity X has been received from the first terminal device 120a. Specifically, when the first terminal device 120a receives five or more consecutive requests to complete an activity X, the processor 111 determines that an error has occurred in the first terminal device 120a that prevents the progress state from being changed, and thus determines that an abnormal request related to activity X has been received from the first terminal device 120a.
[0052] According to one embodiment, when processor 111 receives a predetermined number of consecutive requests to complete a predetermined abnormal activity among a plurality of activities, processor 111 may determine the abnormal activity request as a normal request rather than an abnormal request. For example, since refresh activities are typically executed multiple times in succession, processor 111 may not determine the refresh activity as an abnormal request.
[0053] In action 320, the processor 111 of various embodiments may record the at least one abnormal request based on the time at which the at least one abnormal request was generated and the activity that generated the at least one abnormal request. The processor 111 may record the at least one abnormal request received from the plurality of terminal devices 120 as an error.
[0054] For example, the processor 111 may record the following data: an abnormal request related to activity X was generated at 12:10 PM on the first terminal device 120a; and an abnormal request related to activity Y was generated at 10:00 AM on the second terminal device 120b. The time and activity of each of the at least one abnormal request can be recorded using the same method as described above.
[0055] In action 330, the processor 111 of various embodiments may generate a first table showing the number of times abnormal requests were generated, based on the recorded at least one abnormal request. Specifically, the processor 111 may aggregate the abnormal requests generated by the plurality of terminal devices 120 to generate the first table showing the number of times abnormal requests were generated, based on the recorded at least one abnormal request. The first table will be described below with reference to Figures 4a and 4b.
[0056] In action 340, the processor 111 of various embodiments may determine whether a specific time period exists in the first chart during which the number of abnormal requests exceeds a predetermined first threshold. In action 350, the processor 111 of various embodiments may determine that a problem has occurred during the specific time period in response to the presence of a specific time period during which the number of abnormal requests exceeds the first threshold. The specific determination method is described below with reference to Figures 4a and 4b.
[0057] FIG4a is a first graph 410 showing abnormal requests generated by a plurality of terminal devices 120 when no problem occurs (normal situation). Specifically, FIG4a is a first graph 410 showing the number of abnormal requests generated by a plurality of terminal devices 120 versus time when no problem occurs.
[0058] For example, if the processor 111 receives a predetermined number (e.g., five) or more consecutive requests for completing a specific activity from the first terminal device, the processor 111 may determine that an abnormal request related to the specific activity has been received from the first terminal device 120a. The processor 111 may count the number of abnormal request occurrences as 1 at the time the abnormal request was generated. Similarly, abnormal requests generated by all of the plurality of terminal devices 120 within a day may be received, and a first chart 410 may be generated showing the number of abnormal request occurrences corresponding to the time.
[0059] Figure 4a shows a scenario where no problems have occurred. Therefore, it can be confirmed that a relatively constant level of abnormal requests has been generated throughout the entire time period of first graph 410. Processor 111 can determine whether there is a specific time period in first graph 410 of Figure 4a where the number of abnormal requests generated exceeds a preset first threshold. If the first threshold (not shown) is set at 50, processor 111 can determine that there is no specific time period where the number of abnormal requests generated exceeds the first threshold. In response to the absence of a specific time period where the number of abnormal requests generated exceeds the first threshold, processor 111 can determine that no problems have occurred. In other words, if first graph 410 is the same as Figure 4a, processor 111 can determine that no problems have occurred that require cause analysis and / or remedial measures, and that the recorded abnormal requests are at a level that is expected to occur in routine work orders.
[0060] On the other hand, FIG4b shows a first graph 420 showing the number of abnormal requests generated by the plurality of terminal devices 120 over time when a problem occurs. FIG4b receives at least one abnormal request generated by all of the plurality of terminal devices 120 within a day and generates the first graph 420 showing the number of abnormal requests generated by the plurality of terminal devices 120 over time.
[0061] The first graph 420 shown in FIG4b is a graph showing a problem situation. Therefore, it can be confirmed that the number of abnormal requests increases dramatically during the time period 423 between 13:00 and 14:00. Specifically, in the first graph 420 in FIG4b, the processor 111 can determine that the time period 423 between 13:00 and 14:00 is present. This time period 423 is a specific time period in which the number of abnormal requests exceeds a preset first threshold 421 (e.g., 50). In response to the presence of the specific time period 423, the processor 111 can determine that a problem situation has occurred during the specific time period 423. In other words, when the first graph 420 is the same as FIG4b, the processor 111 can determine that a problem situation has occurred that requires cause analysis and / or remedial measures. Specifically, it can be determined that a problem situation has occurred during the time period 423 between 13:00 and 14:00.
[0062] According to various embodiments, the first threshold 421 can be directly set by an administrator or determined based on statistical values. For example, the first threshold 421 can be determined based on the average number of abnormal requests generated per unit time.
[0063] FIG5 is a flowchart of the operation of the electronic device 110 according to various embodiments of the present invention. Detailed information that overlaps with that described in FIG3 will be omitted.
[0064] In act 501, the processor 111 of the electronic device 110 of various embodiments may receive at least one abnormal request related to a plurality of activities from a plurality of terminal devices 120. In act 503, the processor 111 of various embodiments may record the at least one abnormal request based on the time at which the at least one abnormal request was generated and the activity that generated the at least one abnormal request. In act 505, the processor 111 of various embodiments may generate a first table of the number of times the abnormal request was generated corresponding to a time period based on the recorded at least one abnormal request.
[0065] In action 507 , the processor 111 of various embodiments may determine whether there is a specific time period in the first chart in which the number of abnormal requests generated exceeds a preset first threshold.
[0066] If the number of abnormal requests generated in the first chart does not exceed the first threshold for a specific time period, the process branches to action 515 (507-No), and the processor 111 can determine that no problem has occurred. For example, as shown in FIG4a, if the number of abnormal requests generated in the first chart does not exceed the first threshold for a specific time period (e.g., 50 times), the processor 111 can determine that no problem has occurred during the entire time period.
[0067] If the number of abnormal requests generated during a specific time period in the first chart exceeds a preset first threshold, the process branches to action 509 (507-Yes), and the processor 111 may determine that a problem has occurred during the specific time period. For example, as shown in FIG4b, if the number of abnormal requests generated during a specific time period (between 13:00 and 14:00) exceeds a preset first threshold (e.g., 50 times), the processor 111 may determine that a problem has occurred during the specific time period.
[0068] In action 511, the processor 111 of various embodiments may, in response to determining that a problem occurred during a specific time period, transmit a notification regarding the problem to the administrator's terminal device. Specifically, as shown in FIG4b , if a problem occurs during a specific time period, the processor 111 may transmit a notification regarding the problem to the administrator's terminal device. The administrator may report the notification, analyze the cause of the problem that occurred during the specific time period, and develop a response plan.
[0069] In action 513, the processor 111 of various embodiments may transmit a guideline for resolving the problem to at least one terminal device among the plurality of terminal devices 120 that transmitted an abnormal request generated during a specific time period. Specifically, as shown in FIG4b , when a problem occurs during a specific time period, the processor 111 may transmit a guideline for resolving the problem to the at least one terminal device that transmitted the abnormal request during the specific time period. For example, if the problem occurs due to traffic exceeding the allowable amount on the electronic device 110, the processor 111 may transmit a guideline to the at least one electronic device 110 stating, "Please restart the terminal device or retry the connection after a few minutes."
[0070] FIG6 is a flowchart illustrating the operation of electronic device 110 according to various embodiments of the present invention. Specifically, FIG6 shows a plurality of second graphs showing the number of abnormal request occurrences over time for each of a plurality of activities. Any overlap with the descriptions in FIG3 and FIG5 will be omitted.
[0071] Referring to flowchart 600, in act 610, the processor 111 of the electronic device 110 according to various embodiments may receive at least one abnormal request related to the plurality of activities from the plurality of terminal devices 120. In act 620, the processor 111 according to various embodiments may record the at least one abnormal request based on the time at which the at least one abnormal request was generated and the activity that generated the at least one abnormal request.
[0072] In action 630, the processor 111 of various embodiments may generate a plurality of second graphs of the number of times abnormal requests are generated corresponding to time for each of the plurality of activities. The plurality of second graphs are described in detail in Figures 7a and 7b.
[0073] In action 640, the processor 111 of various embodiments may determine whether a specific time period exists in each of the plurality of second graphs during which the number of abnormal requests generated exceeds a predetermined second threshold. In action 650, in response to the presence of a specific time period in a specific graph among the plurality of second graphs during which the number of abnormal requests generated exceeds the second threshold, the processor 111 of various embodiments may determine that a problem occurred in the specific activity corresponding to the specific graph during the specific time period. The specific method for determining whether a problem has occurred is described in detail in Figures 7a and 7b.
[0074] Figure 7a is a diagram 710 showing a plurality of second graphs 715a, 715b, 715c, and 715d of abnormal requests for each of a plurality of activities generated in a plurality of terminal devices 120 when no problem occurs (normal situation). Specifically, Figure 7a presents a plurality of second graphs 715a, 715b, 715c, and 715d showing the number of abnormal requests generated versus the time of each of a plurality of activities in a plurality of terminal devices 120 when no problem occurs. For reference, 715a is the second graph corresponding to the first activity, 715b is the second graph corresponding to the second activity, 715c is the third graph corresponding to the third activity, and 715d is the fourth graph corresponding to the fourth activity. The second graph 715a corresponding to the first activity can be represented by a light solid line, the second graph 715b corresponding to the second activity can be represented by a dotted line, the third graph 715c corresponding to the third activity can be represented by a two-dot chain line, and the fourth graph 715d corresponding to the fourth activity can be represented by a thick solid line. In FIG7a , although four second graphs corresponding to four activities are shown for ease of explanation, the number of activities can naturally exceed four, and therefore the number of second graphs can also increase in proportion to the number of activities.
[0075] For example, if the processor 111 receives a predetermined number (e.g., five) or more consecutive requests for completing the execution of a first activity from the first terminal device 120a, the processor 111 may determine that an abnormal request related to the first activity has been received from the first terminal device 120a. For the first activity, the processor 111 may count the number of abnormal request occurrences as 1 at the time the abnormal request was generated. Similarly, the processor 111 may receive abnormal requests related to the first activity from all of the plurality of terminal devices 120 within a single day, generating a second graph 715a related to the first activity. Similarly, by generating a second graph for each of the plurality of activities, the processor 111 may generate a plurality of second graphs 715a, 715b, 715c, and 715d.
[0076] Figure 7a illustrates a scenario where no issues have occurred. Therefore, it can be confirmed that multiple activities have generated a relatively constant level of abnormal requests throughout the entire time period. Processor 111 can determine whether any of the multiple second graphs 715a, 715b, 715c, and 715d in Figure 7a contain a specific time period in which the number of abnormal requests generated exceeds a preset second threshold 711. If second threshold 711 is set to 10, processor 111 can determine that no specific graph among the multiple second graphs 715a, 715b, 715c, and 715d contains a specific time period in which the number of abnormal requests generated exceeds the second threshold.
[0077] In response to the absence of a specific time period in which the number of abnormal requests exceeding the second threshold in a specific chart among the plurality of second charts 715a, 715b, 715c, and 715d does not exist, the processor 111 may determine that no problems have occurred in all of the plurality of activities. Specifically, if the plurality of second charts 715a, 715b, 715c, and 715d are the same as those in FIG. 7a, the processor 111 may determine that no problems requiring cause analysis and / or remedial measures have occurred, and that the recorded abnormal requests are of a level that would be expected in a routine execution of work orders.
[0078] On the other hand, Figure 7b shows a diagram 720 that presents a plurality of second graphs 725a, 725b, 725c, and 725d showing the number of abnormal requests generated by a plurality of terminal devices 120 and the time corresponding to each of a plurality of activities when a problem occurs. Figure 7b receives at least one abnormal request generated by all of the plurality of terminal devices 120 within a day and generates a plurality of second graphs 725a, 725b, 725c, and 725d showing the number of abnormal requests generated by the plurality of terminal devices 120 and the time corresponding to each of the plurality of activities. In Figure 7b, the second graph 725a corresponding to the first activity is represented by a light solid line, the second graph 725b corresponding to the second activity is represented by a dotted line, the third graph 725c corresponding to the third activity is represented by a double-dashed line, and the fourth graph 725d corresponding to the fourth activity is represented by a thick solid line.
[0079] The plurality of second graphs 725a, 725b, 725c, and 725d shown in FIG7b are graphs when a problem situation occurs. Therefore, it can be confirmed that the first through fourth activities all experience a sharp increase in the number of abnormal requests generated during the time period 723 between 13:00 and 14:00. Specifically, in the plurality of second graphs 725a, 725b, 725c, and 725d in FIG7b, the processor 111 can determine that the time period 723 between 13:00 and 14:00 is a specific time period in which the number of abnormal requests generated exceeds a preset second threshold 721 (e.g., 10). In response to a specific time period in which the number of abnormal requests exceeds the second threshold 721, and the abnormal requests are generated in a specific chart among the plurality of second charts 725a, 725b, 725c, and 725d, the processor 111 may determine that a problem occurred in the specific activity corresponding to the specific chart during the specific time period. For example, if the number of abnormal requests generated in the time period 723 between 13:00 and 14:00 in the second chart 725a corresponding to the first activity exceeds the second threshold 721, the first activity may be determined to have a problem occurred in the time period 723 between 13:00 and 14:00. The same method can be used to determine the problem for the remaining second charts 725b, 725c, and 725d.
[0080] In response to determining that a specific activity is problematic during the specific time period, the processor 111 of various embodiments may transmit a notification regarding the specific activity and the problematic situation occurring during the specific time period to the administrator's terminal device.
[0081] In the flowcharts shown in the figures, process steps, method steps, algorithms, etc. are described sequentially. However, such processes, methods, and algorithms can be configured so that the steps are performed in any appropriate order. In other words, the steps of the processes, methods, and algorithms described in the various embodiments of the present invention do not need to be performed in the order described in the present invention. Furthermore, even if some steps are described as being performed asynchronously, in other embodiments, these steps may be performed simultaneously. Furthermore, the examples of processes described with the aid of the figures do not exclude other variations or modifications of the illustrated processes, nor do they imply that the illustrated processes or any of their steps are required for one or more of the various embodiments of the present invention, nor do they imply that the illustrated processes are preferred.
[0082] Although the above method is described using specific embodiments, it can also be implemented as computer-readable code on a computer-readable recording medium. Computer-readable recording media include all types of recording devices that store data readable by a computer system. Examples of computer-readable recording media include ROM (Read Only Memory), RAM (Random Access Memory), CD-ROM (Compact Disc Read-Only Memory), magnetic tapes, floppy disks, and optical data storage devices. Furthermore, computer-readable recording media can be distributed across computer systems connected via a network, storing and executing computer-readable code in a distributed manner. Furthermore, the functional programs, codes, and code segments used to implement the above embodiments can be easily derived by programmers skilled in the art to which the present invention relates.
[0083] 10: System 110: Electronic devices 111: Processor 113: Memory 115: Communication circuit 120: Terminal device 120a: First terminal device 120b: Second terminal device 120c: Third terminal device 121:Controller 123:Memory 125: Display 127: Communication circuit 300:Action Flowchart 310: Action 320: Action 330: Action 340: Action 350: Action 410: Chart 1 420: Chart 1 421: First critical value 423: Time period 501:Action 503:Action 505:Action 507: Action 509:Action 511: Action 513: Action 515: Action 600: Action Flowchart 610: Action 620: Action 630: Action 640:Action 650: Action 710: Picture 711: Second critical value 715a: Chart 2 715b: Chart 2 715c: Chart 2 715d: Chart 2 720: Picture 721: Second critical value 723: Time period 725a: Chart 2 725b: Chart 2 725c: Chart 2 725d: Chart 2
Claims
1. An electronic device for managing work orders executed in a sorting warehouse, comprising: communication A circuit, communicatively connected to a plurality of terminal devices owned by a plurality of users; a memory; and a processor; the work order includes a plurality of ongoing states and a plurality of activities that can be performed in the plurality of ongoing states, the processor being configured to: receive at least one abnormal request related to the plurality of activities from the plurality of terminal devices; record the at least one abnormal request based on the occurrence time of the at least one abnormal request and the activity that generated the at least one abnormal request; generate a plurality of graphs for each of the plurality of activities, corresponding to the number of times abnormal requests are generated; determine, within a whole time period associated with the plurality of graphs, whether there is a specific time period in each of the plurality of graphs in which the number of times abnormal requests are generated exceeds a predetermined threshold; in response to the existence of the specific time period in a specific graph of the plurality of graphs in which the number of times abnormal requests are generated exceeds the predetermined threshold, determine that a problem has occurred in the specific time period of the specific activity corresponding to the specific graph. Based on the aforementioned specific time period and the aforementioned specific activity, it is determined that at least one of the aforementioned terminal devices transmits an abnormal request for the aforementioned specific activity during the aforementioned specific time period; and a guideline for resolving the aforementioned problem situation of the aforementioned specific activity is transmitted to the aforementioned at least one terminal device.
2. The electronic device of claim 1, wherein the processor is configured to: determine that the problem has not occurred in the specific activity during the specific time period in which no abnormal requests are generated exceeding the predetermined threshold.
3. The electronic device of claim 1, wherein the processor is configured to: in response to determining that the aforementioned problem occurred during the aforementioned specific time period in the aforementioned specific activity, transmit a notification regarding the aforementioned problem in the aforementioned specific activity to the terminal device of the administrator.
4. The electronic device of claim 1, wherein the processor is configured such that, when a certain terminal device continuously receives a predetermined number or more requests for completion of a specific activity among the plurality of activities, it determines that an abnormal request related to the specific activity has been received from the specific terminal device.
5. The electronic device of claim 4, wherein the processor is configured such that, when a predetermined abnormal activity is received from the specific terminal device a predetermined number of times or more from the plurality of activities, it determines that a normal request related to the abnormal activity has been received from the specific terminal device.
6. The electronic device as requested in item 1, wherein the aforementioned predetermined threshold is determined based on the average number of abnormal requests generated per unit time.
7. A method for managing work orders, implemented in a sorting warehouse via electronic devices, comprising the following actions: receiving at least one abnormal request related to a plurality of activities from a plurality of terminal devices; recording the at least one abnormal request based on the occurrence time of the at least one abnormal request and the activity that generated the at least one abnormal request; generating a plurality of charts for each of the plurality of activities, corresponding to the number of times the abnormal request occurred; determining, within a whole time period associated with the plurality of charts, whether there is a specific time period in each of the plurality of charts in which the number of times the abnormal request occurred exceeds a predetermined threshold; and, in response to the existence of the specific time period in a specific chart in the plurality of charts in which the number of times the abnormal request occurred exceeds the predetermined threshold, determining that a problem occurred in the specific time period corresponding to the specific activity of the specific chart. Based on the aforementioned specific time period and the aforementioned specific activity, it is determined that at least one of the aforementioned plurality of terminal devices transmits an abnormal request for the aforementioned specific activity during the aforementioned specific time period; and a guideline for resolving the aforementioned problem situation of the aforementioned specific activity is transmitted to the aforementioned at least one terminal device; wherein the aforementioned work order includes a plurality of in progress states and a plurality of activities that can be performed in the aforementioned plurality of in progress states.
Citation Information
Patent Citations
Abnormal logistics order monitoring method and related device
CN115293682A
Monitor
JP2017004088A
Method for provinding integrated management platform for device failures
KR1020220121008A
Method and system for detection of tool performance degradation and mismatch and related computer program product and apparatus
TWI524189B
