Method for constructing a computer system and a control program

Abstract

Reduce the cost of building logistics control systems. [Solution] A computer system characterized by generating display data for arranging a plurality of the aforementioned icons on a screen according to user operations, determining the input and output of data for the program corresponding to each of the connected icons by connecting a plurality of the aforementioned higher-level icons on the screen according to user operations corresponding to the processes of logistics operations, arranging one or more material handling icons corresponding to material handling equipment installed in a warehouse on the screen according to user operations, connecting at least one of the connected higher-level icons on the screen with the arranged material handling icons, and constructing a control program to control the material handling equipment by linking the programs corresponding to the icons through the connection of the icons.

Description

[Technical Field]

[0001] The present invention relates to a computer system for building a control program. [Background Art]

[0002] To automate operations in warehouses (picking work, conveying work, sorting work, etc.), there exist automation systems that combine various material handling equipment such as automated warehouses, automated guided vehicles (conveying devices), and vertical conveyors (inter-area conveyors). For example, there is the technology described in Patent Document 1. [Prior Art Literature] [Patent Literature]

[0003] [Patent Document 1] Japanese Unexamined Patent Application Publication No. 2024-171865 [Summary of the Invention] [Problems to be Solved by the Invention]

[0004] When automating warehouse operations using material handling equipment, the content of operations to be automated, the handled articles (type, quantity, etc.), order details (delivery date, quantity, variability, etc.), warehouse environment (size, temperature, etc.), budget, and other conditions (e.g., hygiene management) vary among customers. Therefore, the type and quantity of material handling equipment introduced for automation also vary, and control software for realizing an automation system by combining these material handling devices also needs to be built for each customer (and / or each automation system), making the costs (time, expense, personnel) for building a problem. Furthermore, even after the automation system is built and put into operation, changes to the control software are required for changes in the content of operations to be automated and operational improvements, and the costs (time, expense, personnel) for these changes also become a problem. Hereinafter, the cost for such building or change may be referred to as building cost.

[0005] Therefore, the present invention provides a computer system and method that can reduce the construction cost of a logistics control system. [Means for solving the problem]

[0006] A representative example of the invention disclosed in this application is as follows: A computer system for constructing a control program for controlling a material handling device installed in a warehouse, comprising a processing unit that executes predetermined processing and a storage unit connected to the processing unit, wherein the storage unit executes predetermined processing using input data and stores icons associated with a program that outputs the results of the processing to other icons or the material handling device, the icons include a material handling icon corresponding to a material handling device and a higher-level icon connected to the material handling icon and corresponding to a program that outputs data to the material handling icon or other icons, and the higher-level icon corresponds to a program that executes processing related to the logistics operations process, regardless of the type of material handling device. The processing unit includes process icons, and the processing unit generates display data for arranging a plurality of the icons on a screen according to user operations, determines the input and output of data for the program corresponding to each connected icon as the plurality of higher-level icons are connected on the screen according to user operations corresponding to logistics operations, places one or more material handling icons corresponding to material handling equipment installed in a warehouse on the screen according to user operations, connects at least one of the higher-level icons connected on the screen to the placed material handling icons, and constructs a control program to control the material handling equipment by linking the programs corresponding to the icons through the connection of the icons. [Effects of the Invention]

[0007] According to one aspect of the present invention, the construction cost of a logistics control system can be reduced. Other problems, configurations, and effects not mentioned above will be clarified by the following description of the embodiments. [Brief explanation of the drawing]

[0008] [Figure 1] This figure shows the logical configuration of the computer system in this embodiment. [Figure 2] This figure shows the physical configuration of the computer system in this embodiment. [Figure 3] This figure shows an overview of the functions of the computer system in this embodiment. [Figure 4] This figure shows an example of the integrated WCS creation screen in this embodiment. [Figure 5A] This figure shows an example of the integrated WCS creation screen in this embodiment. [Figure 5B] This figure shows an example of the integrated WCS creation screen in this embodiment. [Figure 6] This figure shows an example of the higher-level parts management information in this embodiment. [Figure 7] This figure shows an example of material handling parts management information in this embodiment. [Figure 8] This figure shows an example of property item information in this embodiment. [Figure 9A] This figure shows an example of how parts are connected. [Figure 9B] This figure shows a specific example of higher-level parts management information in the connection relationship shown in Figure 9A. [Figure 9C] Figure 9A shows a specific example of property item information in the connection relationship. [Figure 10] This figure shows an example of an object connection information file in this embodiment. [Figure 11] This figure shows an example of an object list file in this embodiment. [Figure 12] This figure shows an example of object properties in this embodiment. [Figure 13] This figure shows an example of the object's operational state in this embodiment. [Figure 14A] This is a flowchart of the process for creating construction information in this embodiment. [Figure 14B] This is a flowchart of the process for creating construction information in this embodiment. [Figure 14C] This is a flowchart of the process for creating construction information in this embodiment. [Figure 15]It is a flowchart of a process executed in the execution environment of the present embodiment. [Figure 16A] It is a diagram showing configuration information of a process executed by the overdue exclusion icon of the present embodiment. [Figure 16B] It is a flowchart of a process executed by the overdue exclusion icon of the present embodiment. [Figure 17] It is a diagram showing an example of interface conversion according to the present embodiment. [Figure 18A] It is a diagram showing an example of a visualization screen for material handling data according to the present embodiment. [Figure 18B] It is a diagram showing an example of a visualization screen for material handling data according to the present embodiment. Mode for Carrying Out the Invention

[0009] Hereinafter, embodiments of the present invention will be described with reference to the drawings. The examples are exemplifications for explaining the present invention, and are appropriately omitted and simplified for clarifying the description. The present invention can also be implemented in various other forms. Unless particularly limited, each component may be either singular or plural.

[0010] The positions, sizes, shapes, ranges, and the like of each component shown in the drawings may not represent the actual positions, sizes, shapes, ranges, and the like, in order to facilitate understanding of the invention. Therefore, the present invention is not necessarily limited to the positions, sizes, shapes, ranges, and the like disclosed in the drawings.

[0011] Examples of various types of information may be described using expressions such as "table," "list," and "queue," but these types of information may also be represented by data structures other than these. These types of information can be data of any structure (for example, structured data or unstructured data), or they can be learning models such as neural networks, genetic algorithms, or random forests that generate output for input. For example, various types of information such as "XX table," "XX list," and "XX queue" may also be referred to as "XX information." Furthermore, in the following explanation, the structure of each table is just an example, and one table may be divided into two or more tables, or all or part of two or more tables may be one table.

[0012] Any information (for example, at least one of "ID," "name," and "number") may be used as information to identify an element (identification information, identifier). When describing identification information, expressions such as "identification information," "identifier," "name," "ID," and "number" are used, but these are interchangeable.

[0013] When there are multiple components with the same or similar function, they may be described using the same symbol but with different subscripts. Furthermore, when it is not necessary to distinguish between these multiple components, the subscripts may be omitted in the description.

[0014] In the following explanation, we may describe processes that are performed with the "program" as the subject, but these processes are those performed by executing the "program". Here, a computer executes a program using a processor (e.g., CPU, GPU) and performs the processing defined by the program using memory resources (e.g., memory) and interface devices (e.g., communication ports). Therefore, the main entity performing the processing by executing the program may be the processor. Similarly, the main entity performing the processing by executing the program may be a controller, device, system, computer, or node that has a processor. The main entity performing the processing by executing the program may be an arithmetic unit, and may include dedicated circuits that perform specific processing. Here, dedicated circuits include, for example, FPGAs (Field Programmable Gate Arrays), ASICs (Application Specific Integrated Circuits), CPLDs (Complex Programmable Logic Devices), etc.

[0015] The program may be installed on the computer from the program source. The program source may be, for example, a program distribution server or a computer-readable storage medium (e.g., a non-temporary recording medium). If the program source is a program distribution server, the program distribution server includes a processor and storage resources for storing the program to be distributed, and the processor of the program distribution server may distribute the program to other computers. In addition, in the embodiment, two or more programs may be implemented as a single program, or one program may be implemented as two or more programs.

[0016] A "processor" may be one or more processor devices. At least one processor device may typically be a microprocessor device such as a CPU (Central Processing Unit), but may also be other types of processor devices such as a GPU (Graphics Processing Unit). At least one processor device may be single-core or multi-core. At least one processor device may be a processor core. At least one processor device may be a broad processor device such as a circuit that is a collection of gate arrays defined by a hardware description language that performs some or all of the processing (e.g., FPGA (Field-Programmable Gate Array), CPLD (Complex Programmable Logic Device), or ASIC (Application Specific Integrated Circuit)).

[0017] "Memory" refers to one or more memory devices that are examples of one or more "storage devices," and is typically a main memory device. At least one memory device in memory may be a volatile memory device or a non-volatile memory device.

[0018] "Persistent storage device" may be one or more persistent storage devices that are examples of one or more "storage devices". Persistent storage devices are typically non-volatile storage devices (e.g., auxiliary storage devices), and specifically may be, for example, HDDs (Hard Disk Drives), SSDs (Solid State Drives), NVMe (Non-Volatile Memory Express) drives, or SCMs (Storage Class Memory).

[0019] An "interface device" may consist of one or more interface devices. These one or more interface devices may consist of at least one of the following: • One or more I / O (Input / Output) interface devices: An I / O interface device is an interface device to at least one of the following: an I / O device and a display computer. The I / O device may be either a user interface device, such as an input device like a keyboard and a pointing device, or an output device like a display device. The I / O interface device to the display computer may be a communication interface device. • One or more communication interface devices: One or more communication interface devices may be one or more identical communication interface devices (for example, one or more NICs (Network Interface Cards)) or two or more different communication interface devices (for example, a NIC and an HBA (Host Bus Adapter)).

[0020] The unit for "date and time" can be either coarser or finer than the year, month, day, hour, and minute unit.

[0021] When automating warehouse operations using material handling equipment, the tasks to be automated, the items handled (types, quantities, etc.), order details (delivery dates, quantities, variability, etc.), warehouse environment (size, temperature, etc.), budget, and other conditions (e.g., hygiene management) vary greatly from customer to customer. Therefore, the type and quantity of material handling equipment to be introduced for automation also vary, and the control software to realize the automation system by combining these material handling devices must be built for each customer (and / or each automation system), making the cost (time, expense, personnel) of construction a challenge. Furthermore, even after the automation system is built and put into operation, changes to the control software may be required due to changes in the tasks to be automated or to improve operations, and the cost (time, expense, personnel) of such changes also becomes a challenge.

[0022] Here, the control software used to realize an automated system using multiple material handling devices (material handling equipment) is called an integrated WCS (Warehouse Control System). The integrated WCS may also be called an integrated warehouse control system, warehouse control system (WCS), warehouse operation management system, or warehouse execution system (WES).

[0023] The logistics control system may be an integrated WCS, or it may be an automated system including material handling equipment and a computer system 10. The automated system automates at least a portion of the logistics operations, and may include some tasks performed by workers.

[0024] Material handling equipment refers to devices (machines, facilities) related to operations within a warehouse (such as picking, transporting, sorting, etc.), and may include automated warehouses, automated guided vehicles (transportation devices), vertical conveyors (inter-area conveyors), work terminals used by workers (such as handheld terminals), picking robots, picking systems (such as digital picking systems), inspection devices, packaging devices, etc. Material handling equipment may also be called material handling machinery or material handling facilities.

[0025] The computer system 10 in this embodiment is a system capable of constructing an integrated WCS, and can reduce the construction costs of the integrated WCS and the logistics control system. Furthermore, the computer system 10 is a system capable of modifying the integrated WCS, and can reduce the costs of modifying the integrated WCS. Note that the costs of modifying the integrated WCS are also sometimes referred to as construction costs. The computer system 10 may include the integrated WCS, or it may be separate software from the integrated WCS.

[0026] Figure 1 shows the logical configuration of the computer system 10 in this embodiment.

[0027] The computer system 10 of this embodiment includes a construction environment 100, an execution environment 120, a parts pool 140, a construction pool 150, and an object operating state 160.

[0028] The construction environment 100 is a functional block that executes processes for constructing an integrated WCS, and includes a construction management application 101 and a construction information temporary storage unit 107.

[0029] The construction management application 101 executes processes for constructing an integrated WCS and includes a construction unit 102, a parts pool reading unit 103, a user parts writing unit 104, a construction pool reading unit 105, and a construction pool writing unit 106.

[0030] The construction unit 102 creates an integrated WCS creation screen 400 (see Figure 5A) and constructs the integrated WCS by combining pre-prepared parts according to user input. The parts are programs that execute processing and interfaces that convert data formats, and are stored in the parts pool 140, which will be described later.

[0031] The parts pool reading unit 103 reads parts from the parts pool 140 according to user input. The user parts writing unit 104 writes the parts to be added to the parts pool 140. The parts to be added may be created by the user or by the vendor of the computer system 10.

[0032] The build pool read unit 105 retrieves the desired data (build information) from the build pool 150. The build pool write unit 106 writes the data (build information) to the build pool 150.

[0033] The temporary storage unit 107 for construction information temporarily stores the construction information.

[0034] The execution environment 120 is a functional block that executes the construction information (including the integrated WCS) constructed by the construction environment 100, and includes a platform controller 121, a task management unit 122, a task scheduler 123, a communication management unit 124, an object management unit 126, a parts pool reading unit 127, a construction pool reading unit 128, and execution environment setting information 129.

[0035] The platform controller 121 manages the execution of the task management unit 122, the task scheduler 123, the communication management unit 124, the object management unit 126, the parts pool reading unit 127, the construction pool reading unit 128, and the execution environment setting information 129. The task management unit 122 manages and monitors the tasks of each functional block. The task scheduler 123 controls the execution timing of the construction information. For example, the task scheduler 123 may execute an object repeatedly at predetermined intervals (e.g., every minute) according to the schedule set for the object, or execute the object at a predetermined time. The communication management unit 124 manages the communications that the execution environment 120 sends and receives. The object management unit 126 manages objects based on the construction information and switches between starting or stopping objects. The parts pool reading unit 127 reads parts from the parts pool 140 according to instructions from icons. The construction pool reading unit 128 acquires data from the construction pool 150 according to instructions from icons. The execution environment configuration information 129 records various settings related to the connection between the computer system 10 (and integrated WCS) and external devices, the schedule, and the execution environment.

[0036] The parts pool 140 contains data on parts used in the build environment 100 and the execution environment 120, and includes higher-level parts information 141, material handling parts information 142, user parts 143, and property item information 144.

[0037] The higher-level part information 141 records the higher-level part and higher-level part management information (see Figure 6). The material handling part information 142 records the material handling part and material handling part management information (see Figure 7). The user part 143 records information about parts created by the user. Note that the user part 143 may be classified as either a higher-level part or a material handling part depending on its attributes, and in the following explanation, it will be described as part of a higher-level part or a material handling part. The property item information 144 records information about the setting items of the property (see Figure 8).

[0038] The build pool 150 is data of build information built by the build environment 100, and includes an object connection information file 151, an object list file 152, and object properties 153.

[0039] Construction information includes information about an integrated WCS that has been constructed (including modifications) or is currently under construction, as well as information for constructing the integrated WCS (including management information such as screen information for the integrated WCS creation screen). Here, integrated WCS information includes object information and object connection information.

[0040] Here, an object is a part that is part of an integrated WCS that has been built or is being built, and information for operating that part (including information about the part's property settings, the data the part references, and the data the part passes). Each object may have its default properties (registered in part pool 140) for the part in question, or it may have properties set (by the user or automatically).

[0041] The object connection information file 151 corresponds to each object and records the connection information of that object included in the construction information constructed by the construction environment 100 (see Figure 10). The object list file 152 records the data of the objects that make up the construction information constructed by the construction environment 100 (see Figure 11). The object properties file 153 records the data of the properties set for the objects that make up the construction information constructed by the construction environment 100 (see Figure 12).

[0042] Object Operation Status 160 records the operation status of the object (see Figure 13).

[0043] The computer system 10 in this embodiment has a construction environment 100 and an execution environment 120, but the construction environment 100 and the execution environment 120 may be implemented on separate computers.

[0044] Figure 2 shows the physical configuration of the computer system 10 in this embodiment.

[0045] The computer system 10 of this embodiment is composed of a computer having a processor (CPU) 1, memory 2, auxiliary storage device 3, and communication interface 4. The computer system 10 may also have an input interface 5 and an output interface 8.

[0046] Processor 1 is an arithmetic unit that executes programs stored in memory 2. By executing various programs, Processor 1 realizes the functions of each functional unit of the computer system 10 (for example, each functional unit of the construction environment 100 and the execution environment 120). Note that some of the processing performed by Processor 1 when executing programs may be performed by other arithmetic units (for example, hardware such as ASICs and FPGAs).

[0047] Memory 2 includes ROM, a non-volatile memory element, and RAM, a volatile memory element. ROM stores immutable programs (e.g., BIOS). RAM is a high-speed, volatile memory element such as DRAM (Dynamic Random Access Memory), and temporarily stores programs executed by processor 1 and data used during program execution.

[0048] The auxiliary storage device 3 is, for example, a high-capacity, non-volatile storage device such as a magnetic storage device (HDD) or flash memory (SSD). The auxiliary storage device 3 also stores data used by the processor 1 when executing a program (for example, execution environment setting information 129, parts pool 140, build pool 150, object operating status 160), and the program that the processor 1 executes. In other words, the program is read from the auxiliary storage device 3, loaded into memory 2, and executed by the processor 1, thereby realizing the various functions of the computer system 10.

[0049] Communication interface 4 is a network interface device that controls communication with other devices (including external devices) according to a predetermined protocol.

[0050] Input interface 5 is an interface to which input devices such as a keyboard 6 and a mouse 7 are connected and to receive input from the user. Output interface 8 is an interface to which output devices such as a display device 9 and a printer (not shown) are connected and to output the program execution results in a format that the user can see. In addition, a user terminal connected to the computer system 10 via a network may provide the input and output devices. In this case, the computer system 10 may have the functionality of a web server, and the user terminal may access the computer system 10 using a predetermined protocol (e.g., http).

[0051] The program executed by processor 1 is provided to computer system 10 via removable media (such as CD-ROM or flash memory) or a network, and stored in non-volatile auxiliary storage device 3, which is a non-temporary storage medium. For this reason, computer system 10 should have an interface for reading data from removable media.

[0052] The computer system 10 is a computer system that is configured on a single physical computer, or on multiple logically or physically configured computers, and may operate on a virtual computer built on multiple physical computer resources. For example, multiple programs that implement the functions of the computer system 10 may each operate on separate physical or logical computers, or multiple programs may be combined and operate on a single physical or logical computer.

[0053] Figure 3 is a diagram showing an overview of the functions of the computer system 10 in this embodiment.

[0054] The functions provided by an integrated WCS include, for example, inbound / outbound planning, inventory management, transportation optimization, visualization, work management, and conversion. In the logistics field, the communication interfaces of material handling equipment from different companies are not standardized, and each function involves multiple methods. However, even if customer specifications differ, the processes of warehouse logistics operations are common. Therefore, by modularizing the programs that execute the processing of each process, it is possible to build logistics operation control software that is tailored to the customer's specifications.

[0055] For example, programs and interfaces that are common to multiple customers can be registered as parts in the parts pool 140, and can be used in common when building an integrated WCS for each customer. Any parts that differ for each customer (and / or each automation system) can be individually configured in the properties of that part (object). This reduces the cost of building an integrated WCS.

[0056] Figures 4, 5A, and 5B are diagrams showing examples of the integrated WCS creation screen 400 in this embodiment. Figure 4 shows the initial screen of the integrated WCS creation screen 400, Figure 5A shows the screen during the creation of construction information on the integrated WCS creation screen 400, and Figure 5B shows the display contents of the canvas 440.

[0057] The integrated WCS creation screen 400 includes an operation selection area 410, a part selection area 420, a property setting area 430, a canvas 440, and a configuration display area 450.

[0058] The operation selection area 410 includes the operation areas for "Project Selection," "Build," "Save / Load," and "Update." When "Project Selection" is operated, the user can select the build information to operate on. When "Build" is operated, new build information (integrated WCS) can be created. When "Save / Load" is operated, the created build information can be saved to the build pool 150. Saved build information can also be loaded from the build pool 150. When "Update" is operated, the build information can be updated.

[0059] The parts selection area 420 is the area where selectable parts are displayed during the construction information configuration. The parts displayed in the parts selection area 420 may be categorized and made selectable, such as receiving management, shipping management, inventory management, work terminals, automated warehouses, AGVs, sorters, and maintenance. The user creates construction information (objects) by moving the parts displayed in the parts selection area 420 from the parts selection area 420 to the canvas 440.

[0060] The property setting area 430 is where you set properties for objects that will become part of the integrated WCS being built (for example, parts moved to canvas 440). For example, the properties can be changed for each customer.

[0061] Canvas 440 is the area where users place parts to create construction information (integrated WCS). On the initial screen of the integrated WCS creation screen 400, Canvas 440 is blank. Parts (objects) are displayed as icons on Canvas 440.

[0062] Parts are divided into material handling parts and parts other than material handling parts (called higher-level parts). Similarly, objects are divided into material handling objects that correspond to material handling parts and higher-level objects that correspond to higher-level parts. Higher-level objects may be objects other than material handling objects. Similarly, icons are divided into material handling icons that correspond to material handling parts (material handling objects) and higher-level icons that correspond to higher-level parts (material handling objects).

[0063] A material handling part (material handling object) corresponds to a material handling device and performs input / output processing (including instructions and responses) to the material handling device (which may include the software (WCS: Warehouse Control System) that controls the material handling device). The material handling part (material handling object) converts the data processed by the material handling device into a format that can be input / output to programs corresponding to other parts (e.g., higher-level parts (higher-level objects)). Similarly, the material handling part (material handling object) converts data into a format that can be input / output to programs corresponding to other parts (e.g., higher-level parts (higher-level objects)) into data processed by the material handling device. In this way, the material handling part (material handling object) is associated with a data conversion interface that performs data conversion processing between the data format that each part (each object) of the integrated WCS can process and the data format of the material handling device.

[0064] Material handling parts (material handling objects) are parts (objects) prepared for each type (category) of material handling equipment. Here, each type of material handling equipment may, for example, be each product with a different interface. Each type of material handling equipment may, for example, be each product model (from the same manufacturer or vendor), each product group, or each product category. Material handling parts (material handling objects) may be prepared for each customer, but it is not mandatory to prepare them for each customer.

[0065] The higher-level part (higher-level object) is located upstream of the material handling part (material handling object) (with the closer to the material handling device being considered downstream), and corresponds to a program that outputs data to the material handling part (material handling object) or other parts (material handling objects).

[0066] In the logistics sector, the lack of standardized communication interfaces for material handling equipment across different companies is one factor contributing to increased costs in building integrated WCS (Warehouse Control Systems). However, by configuring material handling parts (material handling objects) with associated data conversion interfaces, and connecting these parts (material handling objects) to higher-level parts (higher-level objects), material handling equipment can be easily added to the logistics system (automation system).

[0067] There are process parts and higher-level connection parts as higher-level components. Similarly, there are process objects corresponding to process parts as higher-level objects. Process parts (process objects) correspond to programs that execute processes related to logistics operations. Process parts (process objects) are parts (objects) prepared for each process related to logistics operations.

[0068] Logistics warehouse operations involve processes specific to logistics, such as receiving, inventory allocation, picking, sorting, inspection, and shipping. Even if customer specifications differ, the processes of warehouse operations are common, and unlike manufacturing processes, the valuation of each process is limited. Therefore, by preparing multiple process parts (process objects) related to logistics operations in advance, and selecting, arranging, and connecting process parts (process objects) according to customer specifications, an integrated WCS (Warehouse Control System) tailored to customer specifications can be built.

[0069] Higher-level connection parts (higher-level connection objects) correspond to higher-level devices (e.g., Warehouse Management System (WMS)) and perform input / output processing (including instructions and responses) to those higher-level devices. The higher-level connection parts (higher-level connection objects) convert data processed by the higher-level device into a format that can be input / output to programs corresponding to other parts (e.g., higher-level parts (higher-level objects)). Similarly, the higher-level connection parts (higher-level connection objects) convert data into a format that can be input / output to programs corresponding to other parts (e.g., higher-level parts (higher-level objects)) into data processed by the higher-level device. In this way, higher-level connection parts (higher-level connection objects) are associated with data conversion interfaces that perform data conversion processing between the data formats that each part (each object) of the integrated WCS can process and the data formats of the higher-level devices.

[0070] Upstream connection parts (upstream connection objects) are parts (objects) provided for each type (category) of upstream equipment. Here, each type of upstream equipment may, for example, be for each product with a different interface. Each type of upstream equipment may, for example, be for each product model of the upstream equipment (from the same manufacturer or vendor), for each group of products of the upstream equipment, or for each category of products of the upstream equipment. Upstream connection parts (upstream connection objects) may be provided for each customer, but it is not mandatory to provide them for each customer.

[0071] There are simulator parts as components. Similarly, there are simulator objects that correspond to simulator parts as objects. Simulator parts (simulator objects) correspond to programs that simulate the operation of material handling equipment. Until actual material handling equipment (e.g., an automated warehouse) is actually installed, it is not possible to input or output actual data. Therefore, by using simulator parts to operate a virtual simulator (e.g., simulating an automated warehouse) within the simulator part (e.g., simulating an automated warehouse) and inputting and outputting data, the logistics control system can be verified.

[0072] At the higher level, there are maintenance parts. Similarly, at the higher level, there are maintenance objects corresponding to the maintenance parts. The maintenance parts (maintenance objects) correspond to maintenance programs that collect data from material handling equipment. Traditionally, customers have built their own logistics control systems, making it difficult to standardize maintenance procedures. Therefore, by performing maintenance with maintenance programs corresponding to maintenance parts (maintenance objects), the reliance on individual expertise can be reduced, thereby lowering maintenance costs, the time required for maintenance, and maintenance man-hours.

[0073] As a component (object), there is a component (object) that, for example, when the communication management unit 124 receives data from an external device or external software (e.g., WMS), outputs that data to another object.

[0074] Regarding icons, icons corresponding to material handling parts (material handling objects) are called material handling icons. Icons corresponding to higher-level parts (higher-level objects) are called higher-level icons. Icons corresponding to process parts (process objects) are called process icons. Icons corresponding to simulator parts (simulator objects) are called simulator icons. Icons corresponding to maintenance parts (maintenance objects) are called maintenance icons.

[0075] In Figure 5B, for example, the icons for "α Company Automated Warehouse" and "β Company Conveyor" are examples of material handling icons. In Figure 5B, for example, the icons for "Outbound Instruction Reception (File Reception)" and "Outbound Management" are examples of process icons. In Figure 5B, for example, the icon for "Material Handling Maintenance" is an example of a maintenance icon.

[0076] The configuration display area 450 is an area where information about the build created by the user by placing parts is displayed.

[0077] Figure 6 shows an example of upper-level parts management information recorded in the upper-level parts information 141 of the parts pool 140 in this embodiment.

[0078] The higher-level parts management information records information about higher-level parts, including data on logistics process, operations / processes, components, property items, IN, OUT, and requests. Additionally, the higher-level parts management information may include information on the corresponding higher-level icons for each higher-level part.

[0079] Logistics operations processes are broad classifications of logistics operations, such as receiving management, transportation, shipping, and maintenance. Operations / processes are the operations or processes performed within the logistics operations. Components are the names (or identification information) of the parts that perform the operations or processes.

[0080] A property item is identification information for the property set for that part. For example, different parts, such as Inbound Schedule Receipt Process A and Inbound Schedule Receipt Process B, may have the same property item or they may have different property items. Property items will be described later with reference to Figure 8. By setting properties for each part, the function of the program corresponding to the part can be changed, thus reducing the number of parts.

[0081] IN is the identification information of the received command input to the part, and OUT is the identification information of the transmitted command output from the part. For example, the OUT of receiving management process A is y1, and the IN of transport management is y1, and since they match, it is possible to connect receiving management process A to transport management.

[0082] A request is a request identifier (request ID) for the processing (processing for sending) related to the transmission command defined in OUT. For example, even if the same or different transmission commands are sent in different processing steps as part of the processing of a single part (object), each command can be distinguished by the request ID. Furthermore, the transmission commands defined in OUT may have an output order defined. The output order can be set arbitrarily and may be changeable by setting a property.

[0083] Figure 7 shows an example of material handling parts management information recorded in the material handling parts information 142 of the parts pool 140 in this embodiment.

[0084] Material handling parts management information records information about material handling parts, including vendor, equipment type, category, product, component, property items, IN, and OUT data. In addition, material handling parts management information may include material handling icons and information about material handling equipment corresponding to each material handling part.

[0085] The Vendor field is the name (or identification information) of the supplier of the material handling equipment to which the material handling parts correspond. The Equipment Type field is the functional classification of the material handling equipment. The Classification field is the classification of the material handling equipment, indicating whether the equipment is an actual machine or a simulator that mimics an actual machine. The Product field records the product name (or part number) of the material handling equipment. It is preferable that the Product field can record one or more product names.

[0086] A component is the name (or identification information) of the material handling part that performs the relevant task or process. Property items are the identification information of the properties set for the material handling part, and should be represented in the same system as the components in the higher-level parts management information (Figure 6). Property items will be described later with reference to Figure 8. IN is the identification information of the received command input to the material handling part, and OUT is the identification information of the transmitted command output from the material handling part. IN and OUT should be represented in the same system as IN and OUT in the higher-level parts management information (Figure 6). Note that IN should be defined for each type of material handling part (and material handling device).

[0087] Figure 8 shows an example of property item information 144 of the parts pool 140 in this embodiment.

[0088] Property item information 144 records property information, which is the setting content of parts handled by the computer system 10, and is referenced from higher-level parts management information (Figure 6) and material handling parts management information (Figure 7). Property item information 144 includes data for property items and setting items.

[0089] A property item is the identification information for a property. A setting item is the name (or identification information) of the setting item for that property item.

[0090] Next, with reference to Figures 9A, 9B, and 9C, we will explain the higher-level part management information and property item information 144 in specific examples of part connection relationships.

[0091] Figure 9A shows an example of the connection relationship between parts and material handling equipment in this example.

[0092] The transport management component 200, the work management component 201, and the outbound work screen component 202 are connected to the material handling parts of the automated warehouse 210 and the conveyor 211. Each material handling part is connected to a material handling device corresponding to that part.

[0093] When the transport management component 200 receives a dispatch start command, it writes the dispatch slip information received in the dispatch start command to the transport information table, refers to the transport route confirmation table to set the transport route (transportation by conveyor after dispatch from the automated warehouse), outputs a dispatch instruction command to the material handling parts of "α Company Automated Warehouse" 210, outputs a transport instruction command to the material handling parts of "β Company Conveyor" 211, and outputs a dispatch work instruction command to the work management component 201, in that order.

[0094] When a material handling part of the "α Company Automated Warehouse" 210 receives a dispatch command, it performs data conversion to match the corresponding material handling device (α Company Automated Warehouse) and then sends the dispatch command to that device. The corresponding material handling device (α Company Automated Warehouse) then, in accordance with the dispatch command, dispatches, for example, the specified items from the automated warehouse.

[0095] When a material handling part of the "β Company Conveyor" 211 receives a transport instruction command, it performs data conversion to match the corresponding material handling device (β Company Conveyor) and then transmits the transport instruction command to that material handling device. The corresponding material handling device (β Company Conveyor) then transports, for example, items retrieved from an automated warehouse to a designated location, according to the transport instruction command.

[0096] When the work management component 201 receives a dispatch work instruction command, it outputs a screen display command to the dispatch work screen component 202. When the dispatch work screen component 202 receives the screen display command, it displays the dispatch work screen on the station terminal.

[0097] In the connection relationship shown in Figure 9A, the following information is recorded for managing the higher-level parts, as shown in Figure 9B.

[0098] For the transport management component 200, the logistics process is "transport," the task / process is "transport management," the component is "transport management," the property item is "proplistX," IN is "start of outbound shipment," OUT is "outbound shipment instruction," "transport instruction," "outbound work instruction," and the requests are "req10," "req11," and "req12."

[0099] For the work management component 201, the logistics process is "transportation", the task / process is "transportation management", the component is "work management", the property item is "proplistY", the IN is "outbound work instruction", the OUT is "outbound work screen", and the request is "req13".

[0100] For the outbound work screen component 202, the logistics process is "transportation", the task / process is "transportation management", the component is "outbound work screen", the property item is "proplistZ", and IN is "screen display".

[0101] Similarly, for the automated warehouse 210 and conveyor 211, data on logistics operations, tasks / processes, components, property items, and IN are recorded in the higher-level parts management information.

[0102] In the connection relationship shown in Figure 9A, property item information 144 records the setting items that constitute each of the property items recorded in the higher-level parts management information, as shown in Figure 9C. For example, the transport management component 200 writes the outbound slip information to the transport information table and sets the transport route by referring to the transport route confirmation table. In the property item "proplistX" referenced by the transport management component 200, the transport information table and the transport route confirmation table are recorded as setting items.

[0103] Figure 10 shows an example of the object connection information file 151 of the build pool 150 in this embodiment.

[0104] The object connection information file 151 corresponds to an icon and records the connection information of parts included in the build information built by the build environment 100, recording the source object, source icon, request, destination object, destination icon, and command.

[0105] The source object is the name (or identification information) of the source object (for example, the one connected to a higher level). The source icon is the name (or identification information) of the icon corresponding to the source object. The request is the request identifier (request ID) for the processing (processing for sending) related to the transmission command sent from the source icon. The destination object is the name (or identification information) of the destination object (for example, the one connected to a lower level). The destination icon is the name (or identification information) of the icon corresponding to the destination object. The command is the transmission command sent to the destination icon (the command received by the destination icon). Note that the source object may be the source of the transmission command, and the destination object may be the destination of the transmission command.

[0106] Figure 11 shows an example of the object list file 152 of the build pool 150 in this embodiment.

[0107] The object list file 152 records data on objects that make up the build information created by the build environment 100, and includes the objects, icons, and properties.

[0108] The object is the name (or identifier) ​​of the object used to construct the integrated WCS. The icon is the name (or identifier) ​​of the icon corresponding to that object. The property is the identifier of the property set for that object.

[0109] Figure 12 shows an example of object properties 153 of the build pool 150 in this embodiment.

[0110] Object property 153 records data of properties set on objects that constitute the construction information constructed by the construction environment 100, and records the property, key, and value. Object property 153 may also include information about the icon corresponding to the object. The property is the identification information of the property set on the object. The key is the name of the item to which the property is set. The value is the value set for the key.

[0111] Figure 13 shows an example of object operating state 160 in this embodiment.

[0112] Object Status 160 records the operational status of an object, recording both the object and its startup status. The object is the name (or identification information) of the object used in the integrated WCS being constructed. The startup status indicates whether the object is running or stopped.

[0113] Figures 14A, 14B, and 14C are flowcharts of the construction information creation process in this embodiment. This flowchart is an example and is not limited to this example. For example, the processes may be processed in a different order than that shown in the flowchart, and some processes may be repeatable. For example, the property setting process (Figure 14C) may be performed before the connection process (Figure 14B). Also, for example, when a user places icons consecutively on canvas 440, the process in Figure 14A may be repeated.

[0114] The process of creating construction information is broadly divided into icon placement (Figure 14A), connection processing (Figure 14B), and property setting processing (Figure 14C).

[0115] As shown in Figure 14A, the icon placement process starts after the initial screen display (1001).

[0116] The construction unit 102 displays the initial screen (1001). As shown in Figure 4, the initial screen displays the operation selection area 410, the part selection area 420, and the configuration display area 450, while the canvas 440 is blank.

[0117] After displaying the initial screen in step 1001, the construction unit 102 starts the icon placement process (Figure 14A).

[0118] The construction unit 102 accepts a user operation (operation 1) to select a part from the part selection area 420 (part selection operation). For example, it accepts an operation to drag and drop a part (part name or icon) displayed in the part selection area 420 onto the canvas 440 (1002).

[0119] In process 1, the construction unit 102 draws an icon corresponding to the target part (object) on the canvas 440 according to the part selection operation, and the construction pool writing unit 106 writes the data of the target part (object) to the object list file 152 of the construction pool 150, and writes the initial property values ​​of the part to the object properties 153 (1003).

[0120] When the user completes the icon placement process or starts the icon connection process, the construction unit 102 terminates the icon placement process and starts the connection process (Figure 14B).

[0121] In the connection process (Figure 14B), as a user operation (operation 2), the construction unit 102 accepts an operation to connect icons (objects) (connection operation), and the construction pool reading unit 105 obtains object data related to the accepted connection operation from the object list file 152 (1011).

[0122] The construction unit 102 determines whether the source object corresponding to the source icon and the destination object corresponding to the destination icon are different objects (1012). If the source object and the destination object are the same object, the construction unit 102 displays a warning in process 3 indicating that the source object and the destination object are the same (1015).

[0123] On the other hand, if the source object and the destination object are different objects, the construction unit 102 checks the consistency of the interfaces connecting the source object and the destination object (1013). For example, by referring to the information of the higher-level part or material handling part read by the parts pool reading unit 103 (higher-level part management information in Figure 6, or material handling part management information in Figure 7), it can determine that there is consistency if the OUT of the source object (part) and the IN of the destination object (part) match. If the interfaces of the source object and the destination object do not match, the construction unit 102 displays a warning in process 3 indicating that the interfaces of the source object (source icon) and the destination object (destination icon) do not match (1015). On the other hand, if the interfaces of the source object and the destination object are compatible, the construction unit 102, in process 2, draws an arrow (or line) connecting the source icon and the destination icon on the canvas 440 and writes the information connecting the source object and the destination object to the object connection information file 151 (1014).

[0124] When the user performs an operation to terminate the connection process or starts a property setting operation, the construction unit 102 terminates the connection process and starts the property setting process (Figure 14C).

[0125] In the property setting process (Figure 14C), the construction unit 102 accepts the user's selection from the object list file 152 as operation 3, and displays a property setting screen including the selected object (1021).

[0126] In processing 4, the construction unit 102 obtains the current property setting information from the object property 153 and displays the obtained property information on the property setting screen (1022).

[0127] The construction unit 102 accepts the editing of the setting value as operation 4 (1023), and in processing 5, writes the edited setting value to the object property 153 (1024).

[0128] When the user completes the property setting process, the construction unit 102 saves the construction information as operation 5 (1025).

[0129] The integrated WCS is constructed by performing the above-described construction information creation process in response to user operations. For example, under predetermined conditions, such as when a user performs a predetermined operation or when predetermined processing such as saving construction information is performed, the constructed integrated WCS is processed to be in an executable state in the execution environment, or to become executable.

[0130] Figure 15 is a flowchart of the processes executed in the execution environment 120 of this embodiment.

[0131] There are three possible triggers for a task to be executed in execution environment 120: (1) Detect the start of a task according to the schedule. (2) Receiving data from external devices (3) An object that is currently executing calls another object

[0132] When the task scheduler 123 detects the start of a task according to the schedule, or when the communication management unit 124 receives data from an external device (1031), the object management unit 126 checks the start object command from the settings (1032) and proceeds to step 1035.

[0133] When the object management unit 126 detects that an object currently in execution has called another object (1033), it refers to the object connection information file 151, obtains the requested object ID (1034), and proceeds to step 1035.

[0134] In step 1035, the object management unit 126 requests the activation of the object (S1).

[0135] Then, the object management unit 126 refers to the object operation status 160 and determines whether the object is operational (1036).

[0136] If the object is in an operational state, the build pool reading unit 128 retrieves property information from the object properties 153 (S2, 1037), and the object management unit 126 starts the object according to the retrieved properties (S3, 1038).

[0137] On the other hand, if the object's state is not operational, the object management unit 126 waits for the object to start up (S4, 1039).

[0138] Figure 16A is a diagram showing the structure information of the process executed by the overdue exclusion icon 1062 in this embodiment, and Figure 16B is a flowchart of the process executed by the overdue exclusion icon 1062 based on the structure information shown in Figure 16A. Using Figures 16A and 16B, the process of determining the order of processing (including data output) of the object corresponding to the icon will be explained.

[0139] In automated logistics systems, it is necessary to determine the next process based on various responses (for example, determining the next process based on the result of query S1044), and therefore a process is required to determine the order of these processes.

[0140] In the example in Figure 16A, the destination icons for the transmission command from the expired deadline exclusion icon 1062 are the product master management icon 1063 and the allocation decision icon 1065. The order of processing (including data output) is determined by the program or settings of the object corresponding to the expired deadline exclusion icon 1062, and a flowchart like the one in Figure 16B is executed.

[0141] When the object corresponding to the expired item exclusion icon 1062 receives the "filter" command 1061 (1041), it retrieves the product code from the received data (1042).

[0142] The object corresponding to the expired item exclusion icon 1062 sends the "Product Master Inquiry" command 1064 to the object corresponding to the product master management icon 1063 (1043).

[0143] Then, for the object corresponding to the overdue exclusion icon 1062, it is determined from the query results whether or not deadline management is in place (1044).

[0144] The object corresponding to the expired item exclusion icon 1062 retrieves the expiration date of the product with the relevant product code (1046) if the product with that product code is an expiration-controlled item (YES in 1045), and excludes candidates whose expiration date is within a specified number of days from today (1047).

[0145] Then, if the product code in question is not subject to expiration date management (NO in 1045), or after step 1047 is executed, the object corresponding to the expiration date exclusion icon 1062 sends the "Allocation Decision" command 1066 to the object corresponding to the allocation decision icon 1065 (1048).

[0146] Figure 17 shows an example of interface conversion in a material handling object in this embodiment. It illustrates an example where a material handling object receives a transport instruction from a higher-level object, specifying the transport ID (rack_id), the source location (from_x,y,z), and the destination location (to_x,y,z) of the transported object during inter-process transport by an automated guided vehicle (AGV), which is a material handling device.

[0147] In the example in Figure 17, the transport instruction received by the material handling object is as shown in IN, with the transport item ID (rack_id) being "rack01". The source location is (02, 03, 01) in three-dimensional coordinates (x, y, z), where (from x, from y, from z) is expressed. The destination location is (05, 06, 01) in three-dimensional coordinates (x, y, z), where (to x, to y, to z) is expressed. Here, the three-dimensional coordinates (x, y, z) are explained as representing the positions on the x, y, and z axes in a three-dimensional Cartesian coordinate system (the z axis being the height direction of the warehouse).

[0148] Case 1 assumes that, for example, in a warehouse, an automated guided vehicle (AGV) that transports goods in a single-floor warehouse without vertical movement requires transport instructions in the form of two-dimensional coordinate data (x, y) with x and y axes. Therefore, the material handling object corresponding to the AGV converts the received transport instructions (the IN data in Figure 17) into transport instructions that match the data format of the AGV, removing the values ​​of the z-coordinate (height) parameters (from_z, to_z), and then sends the transport instructions to the AGV. The transport instructions sent by the material handling object are as shown in "OUT (case 1)" in Figure 17, with the transport item ID (rack_id) being "rack01", the source location being (02, 03), and the destination location being (05, 06).

[0149] Case 2 assumes that, for example, in a warehouse, an automated guided vehicle (AGV) that transports goods across multiple floors with vertical movement requires transport instructions in the data format of three-dimensional coordinates (x, y, z) of the x, y, and z axes. In this case, the material handling object corresponding to the AGV converts the received transport instructions (data IN in Figure 17) into transport instructions that match the data format of the AGV, without removing the values ​​of the z-coordinate (height) parameters (from_z, to_z), and then sends the transport instructions to the AGV. The transport instructions sent by the material handling object are as shown in "OUT (case 2)" in Figure 17, where the ID of the transported item (rack_id) is "rack01", the source location is (02, 03, 01), and the destination location is (05, 06, 01).

[0150] Case 3 assumes that, for example, in a warehouse, an automated guided vehicle (AGV) that transports goods across multiple floors with vertical movement requires transport instructions in the form of node ID data corresponding to the three-dimensional coordinates (x, y, z) of the x, y, and z axes, such as an AGV that transports goods in a warehouse spanning multiple floors. In this case, the material handling object corresponding to the AGV converts the received transport instructions (the IN data in Figure 17) into transport instructions that represent the three-dimensional coordinates (x, y, z) of the source and destination locations as node IDs, in accordance with the data format of the AGV, and then sends the transport instructions to the AGV. As shown in "OUT (case 3)" in Figure 17, the transport item ID (rack_id) is "rack01", the node ID of the source location is "020301", and the node ID of the destination location is "050601".

[0151] In addition to the cases mentioned above, the following cases may also exist. If the coordinate information of the integrated WCS (for example, the information shown as IN in Figure 17) and the coordinate information managed by the material handling device have different coordinate axes, for example, the material handling object may output a command to the material handling device that converts the coordinate information related to the specified position (the position of the transport source or transport destination) into data. The material handling object outputs a command to the material handling device specifying some information regarding the IN position (e.g., z-axis coordinates, floor number, area, etc.). The material handling device may then determine the specific destination for transport based on the specified information. The material handling object may output a command to the material handling device specifying the source or destination ID (for example, the ID of the work station). The material handling device then transports the object based on the specified source or destination ID.

[0152] Furthermore, while the data conversion process when issuing commands to material handling equipment has been described above, material handling objects may also undergo similar data conversion when receiving data from material handling equipment.

[0153] In the example described above, there is one automated guided vehicle (AGV). However, if there are multiple AGVs, the material handling object may add the AGV ID to the OUT parameter. The material handling object may then determine which AGV to assign the transport task to and send transport instructions for the assigned task to the AGV.

[0154] As shown in the example in Figure 17, even if the material handling equipment (e.g., automated guided vehicles) is of a different type and, for example, the data format is different, the material handling object corresponding to the material handling equipment eliminates the need to change the processing of the higher-level object (including transport instructions from the higher-level object), thereby reducing the construction cost of the integrated WCS.

[0155] Figures 18A and 18B show examples of data visualization screens in this embodiment. As explained using Figure 3, the integrated WCS can provide, for example, visualization functions.

[0156] The integrated WCS can receive (collect) data from each material handling device through the corresponding material handling parts. In particular, the existence of material handling parts means that even if the types of material handling devices handled differ from customer to customer (and / or from automation system to automation system), and even if the data formats differ, for example, the processing of higher-level objects (including transport instructions from higher-level objects) does not need to be changed by using material handling objects corresponding to the material handling device, thereby reducing the construction cost of the integrated WCS.

[0157] The integrated WCS may analyze the collected data (which may include other data related to logistics operations in addition to data collected from material handling equipment) and notify users (workers and managers) via screen (data visualization screen) or audio. This notification (screen or audio) can be output from output interface 8 and displayed on output devices such as display device 9. Furthermore, the integrated WCS may feed back the data analysis results to the control of the automated system, including material handling equipment, for operational management purposes such as optimization and maintenance.

[0158] The integrated WCS (Warehouse Control System) that has been constructed allows for the output of various screens related to logistics operations for data visualization. For example, Figures 5A, 5B, and 9A show examples of outputting the outbound work screen and maintenance screen, but the system is not limited to these examples, and other screens may be output. As an example of a data visualization screen, Figure 18A describes an example of a device efficiency screen 54 that visualizes the efficiency of material handling equipment. For example, a user can refer to this device efficiency screen 54 to check whether the equipment is operating efficiently and use this information to take measures to improve warehouse throughput. Figure 18B describes an example of a device maintenance screen 57 that visualizes the status of material handling equipment. For example, a user can refer to this device maintenance screen 57 to determine the priority and necessity of maintenance and which parts should be maintained. In addition to these examples, there may also be screens that visualize the work status and efficiency at each work station and each worker (employee), screens that visualize the status and efficiency of the charging equipment for material handling equipment, and screens that visualize the progress rate of shipping operations (overall and per batch).

[0159] The device efficiency screen 54 shown in Figure 18A accepts user input of a specified time period in field 54a. In the illustrated example, the length of the specified time period is "1 hour = 60 minutes". Note that the specified time period may be automatically set to a default value (for example, a predetermined period based on the current time).

[0160] The device efficiency screen 54 displays data regarding the device efficiency of each material handling device (e.g., automated warehouse, conveyor, transport vehicle, etc.), specifically the time and percentage for task processing, charging, standby, etc., for each device ID of the material handling device. The items displayed may be changed for each type of device. Figure 18A shows an example where the material handling device is a transport vehicle, and each item on the device efficiency screen 54 is explained below.

[0161] • Utilization rate: The ratio of the total of allocated work time and unallocated work time to the total length of the specified time period. • Working hours: Total of allocated working hours and unallocated working hours within the specified time period. • Pickup time: The cumulative time from the start time to the end time of the "pickup" within the designated time period (Pickup time is included in the allocated work time). • Allocation work time: The cumulative value of the time from the start time to the end time of the "allocation work" within the specified time period. • Unallocated work time: The cumulative value of the time from the start time to the end time of “unallocated work” within the specified time period. • Waiting time: The cumulative value of the time from the start time to the end time of the "waiting" period within the specified time frame. • Charging time: The cumulative time from the start time to the end time of "charging" within the specified time period. • Offline time: From the start time to the end time of “offline” within the specified time period. Cumulative value of time

[0162] Here, “allocation work” refers to “work aimed at transporting,” and may include, for example, the state in which a transport vehicle is transporting goods, or the “receiving” state in which the transport vehicle is driving toward the location of the goods to be transported. “Non-allocation work” refers to “work not aimed at transporting,” and may include, for example, the state in which a transport vehicle is driving toward a charging location for charging. Furthermore, “offline” means that the material handling device with the device ID is unable to communicate with the material handling device’s WCS or integrated WCS, and is in a state that is neither “allocation work,” “non-allocation work,” “standby,” nor “charging.”

[0163] Furthermore, the device efficiency screen 54 displays the ratio of "allocated work time," "non-allocated work time," "standby time," "offline time," and "charging time" to the length of the specified time period as "device operation distribution" using pie charts, bar graphs, etc.

[0164] The device maintenance screen 57 shown in Figure 18B displays information regarding the status of each material handling device (e.g., automated warehouse, conveyor, transport vehicle, etc.), particularly data related to deterioration, abnormalities (failures, errors), and maintenance of the material handling device, for each device ID. The items displayed may be changed for each type of device. Figure 18B shows an example where the material handling device is a transport vehicle, and an example of the items on the device maintenance screen 57 is described below. The evaluation index for each of the following items is an evaluation value (numerical value) for the period from the reference point (e.g., the time of the last maintenance) to the present time, and may be set by the user or automatically.

[0165] • Operating time: Total of allocated working time and unallocated working time • Mileage: Mileage • Number of charging cycles: Number of charging cycles • Number of communication interruptions: The number of "communication interruptions". • Number of anomalies: The number of times an anomaly was detected.

[0166] The integrated WCS compares the numerical value of each evaluation metric with a predetermined threshold set for each evaluation metric. The integrated WCS may output a screen in which the evaluation metric that deviates the most from the threshold among those that are above the threshold is highlighted in the first mode, and the other evaluation metrics are highlighted in the second mode. In the example in Figure 18B, the first mode is double diagonal hatching, and the second mode is single diagonal hatching.

[0167] The integrated WCS may output a screen displaying "C", "B", or "A" in the "Overall Judgment" column, according to the following rules. <Rule 1> A material handling device having at least one emphasis mark of the first aspect shall be marked with "C". <Rule 2> For transport vehicles that do not have a highlighting of the first aspect but have at least one highlighting of the second aspect, “B” shall be displayed. <Rule 3> For transport vehicles that do not have emphasis on the first aspect and do not have emphasis on the second aspect, “A” shall be displayed.

[0168] In the example in Figure 18B, for example, the following can be observed: The material handling equipment (transport vehicles) that require the most urgent maintenance are those with an "Overall Assessment" of "C". In the example in Figure 18, these are the material handling equipment with equipment IDs "A002", "A008", "A015", and "A016". • For the material handling equipment with device ID "A008," the evaluation metric "number of communication interruptions" exceeds the threshold and is significantly higher than that of other transport vehicles. Therefore, maintenance should be prioritized on communication systems, such as antennas used for communication.

[0169] Furthermore, the storage devices (memory 2, auxiliary storage device 3) store information on material handling objects, which are objects for each type of material handling equipment, and information on process objects, which are objects for each process related to the logistics operations. The input device (input interface 5) receives input regarding the selection of objects or the connection between objects, and the processing device (processor 1) constructs control software to automate logistics operations using material handling equipment based on the input, and the output device (output interface 8) outputs information on objects including material handling objects and process objects. Processor 1 constructs control software such that the material handling object selected in the input is connected to at least some of the selected process objects, and that the material handling object selected in the input performs input / output processing with the connected process objects and input / output processing to the material handling equipment corresponding to the material handling object. Furthermore, Processor 1 constructs control software to connect multiple selected process objects to correspond to the flow of each process in the logistics operations.

[0170] Although specifications may differ for each customer (and / or each automation system), the basic flow of logistics operations (e.g., inventory allocation, picking, etc.) is common, and the valuation of each process is also selective. In the computer system 10, a logistics control system (integrated WCS) that automates logistics operations can be built by selecting objects (parts) on the screen. In the computer system 10, regarding the valuation of each process, multiple process objects (or higher-level objects) are available, allowing selection according to specifications, and it can accommodate the logistics workflow of each customer (and / or each automation system). Furthermore, in the computer system 10, individual handling for each type of material handling equipment (data collection from material handling equipment, control of material handling equipment, and data conversion for such collection and control) is performed using the corresponding material handling object, so the higher-level object (e.g., process object) is independent of the type of material handling equipment, making system construction (including modification) easier. This reduces the construction costs for building (including modifying) logistics control systems (automation systems) for each customer (and / or each automation system).

[0171] Similarly, for higher-level devices (e.g., WMS) above the integrated WCS, the computer system 10 performs data conversion using higher-level connection objects corresponding to the higher-level devices. This allows the higher-level object portion (e.g., process object) to be independent of the higher-level device, facilitating system construction (including modifications). This reduces the construction costs for building (including modifications) logistics control systems (automation systems) for each customer (and / or each automation system).

[0172] The storage devices (memory 2, auxiliary storage device 3) store information on higher-level connection objects, which are objects for each type of higher-level device, and information on process objects, which are objects for each process related to the logistics operations. The input device (input interface 5) receives input regarding the selection of objects or the connection between objects, the processing device (processor 1) constructs control software to automate logistics operations based on the input, and the output device (output interface 8) outputs information on objects, including higher-level connection objects and process objects. Processor 1 constructs control software such that the higher-level connection objects selected in the input connect at least some of the selected process objects, and that for the higher-level connection objects selected in the input, it performs input / output processing with the connected process objects and input / output processing to the higher-level device corresponding to the said higher-level connection objects. Furthermore, Processor 1 constructs control software to connect multiple selected process objects to correspond to the flow of each process in the logistics operations.

[0173] It should be noted that the present invention is not limited to the embodiments described above, but includes various modifications and equivalent configurations within the spirit of the attached claims. For example, the embodiments described above are described in detail for the purpose of clearly illustrating the present invention, and the present invention is not necessarily limited to having all the described configurations. Furthermore, some of the configurations of one embodiment may be replaced with those of another embodiment. Furthermore, configurations of other embodiments may be added to the configuration of one embodiment. Furthermore, some of the configurations of each embodiment may be added, deleted, or replaced with those of other embodiments.

[0174] Furthermore, each of the aforementioned configurations, functions, processing units, and processing means may be implemented in hardware, for example, by designing them as integrated circuits, or they may be implemented in software by having a processor interpret and execute programs that realize each function.

[0175] Information such as programs, tables, and files that implement each function can be stored in memory, hard disks, SSDs (Solid State Drives), or other storage media such as IC cards, SD cards, and DVDs.

[0176] Furthermore, the control lines and information lines shown are those deemed necessary for explanatory purposes and do not necessarily represent all control lines and information lines required for implementation. In reality, it can be assumed that almost all components are interconnected. [Explanation of Symbols]

[0177] 1 processor 2 memory 3 Auxiliary storage 4. Communication Interface 5 Input Interfaces 6 Keyboard 7 Mouse 8 output interfaces 9 Display device 10 Computer Systems 54. Device Efficiency Screen 57. Device Maintenance Screen 100 Built Environment 101 Construction Management Application 102 Construction Department 103 Parts pool reading unit 104 User Parts Programming Section 105 Construction Pool Reading Unit 106 Construction Pool Writing Section 107 Temporary Storage Unit for Construction Information 120 Execution Environment 121 Platform Controller 122 Task Management Department 123 Task Scheduler 124 Communications Management Department 126 Object Management Department 127 Parts pool reading unit 128 Construction Pool Reading Unit 129 Execution Environment Configuration Information 140 parts pool 141 Top Parts Information 142 Material Handling Parts Information 143 User Parts 144 Property Item Information 150 Construction Pool 151 Object Connection Information File 152 Object List File 153 Object Properties 160 Object Operating Status 200 Transport Management Components 201 Work Management Components 202 Outbound Operation Screen Component 210 Automated Warehouse 211 Conveyor 400 Integrated WCS creation screen 410 Operation Selection Area 420 Part Selection Area 430 Property Selection Area 440 canvas 450 Configuration display area

Claims

1. A computer system for constructing control programs for controlling material handling equipment installed in a warehouse, It comprises a processing unit that performs a predetermined process and a storage unit connected to the processing unit, The storage unit stores icons associated with a program that performs predetermined processing using the input data and outputs the results of the processing to other icons or the material handling device. The aforementioned icons include a material handling icon corresponding to a program that inputs and outputs to the material handling device, and a higher-level icon connected above the material handling icon and corresponding to a program that outputs data to other programs. The aforementioned higher-level icon includes a process icon corresponding to a program that executes processing related to the logistics operations process, regardless of the type of material handling equipment. The aforementioned processing unit, In accordance with the user's actions, display data is generated for arranging multiple of the aforementioned icons on the screen. In accordance with the logistics process, multiple of the aforementioned higher-level icons are connected on the screen. In accordance with the user's operation, one or more material handling icons corresponding to material handling equipment installed in the warehouse are placed on the screen, and at least one of the connected higher-level icons on the screen is connected to the placed material handling icons. A computer system characterized by defining the input and output of data for programs corresponding to each of the connected icons, and constructing a control program to control the material handling device by linking the programs corresponding to the connected icons.

2. A computer system according to claim 1, The computer system is characterized in that the processing unit enables the connection of the first icon and the second icon when the output format of the program corresponding to the first icon and the input format of the program corresponding to the second icon are compatible.

3. A computer system according to claim 1, The aforementioned icon connects with other icons, The program corresponding to that icon has multiple interfaces for sending and receiving data with programs corresponding to other icons. A computer system characterized in that a program having multiple interfaces has a data output order determined such that data is output from the first interface first, and then from the second interface.

4. A computer system according to claim 1, The computer system is characterized in that the aforementioned icons include maintenance icons corresponding to a program for collecting data from the material handling device.

5. A computer system according to claim 1, The computer system is characterized in that the aforementioned icons include simulator icons corresponding to a program that simulates the operation of the material handling device.

6. A computer system according to claim 1, A computer system characterized in that the program corresponding to the material handling icon includes an interface that converts the format of data input to and output from the material handling device corresponding to the material handling icon to the format of data input to and output from the program corresponding to the higher-level icon.

7. A computer system according to claim 1, The computer system is characterized in that each of the aforementioned icons can be configured to set information relating to the processing to be performed by the program corresponding to that icon.

8. A computer system according to claim 1, The storage unit includes a program created by the user. A computer system characterized in that the icons stored in the memory unit include icons corresponding to programs created by the user.

9. A storage device that stores information on material handling objects, which are objects for each type of material handling equipment, and information on process objects, which are objects for each process related to the logistics operations. An input / output device that outputs information about objects including the material handling object and the process object, and can accept input regarding the selection of the object or the connection between objects, The system comprises a processing unit that constructs control software for automating logistics operations using a material handling device based on the aforementioned input, The selected material handling object is connected to at least a portion of the selected process object, The aforementioned processing apparatus is The control software is constructed to perform input / output processing with the connected process object and input / output processing with the material handling device corresponding to the selected material handling object. A computer system characterized by connecting a plurality of selected process objects and constructing the control software to correspond to the flow of each process in logistics operations.

10. A storage device that stores information on higher-level connection objects, which are objects for each type of higher-level device, and information on process objects, which are objects for each process related to the logistics operations process, An input / output device that outputs information about the object including the aforementioned higher-level connection object and the aforementioned process object, and can accept input regarding the selection of the object or the connection between the objects, The system comprises a processing unit that constructs control software for automating logistics operations based on the aforementioned input, The selected higher-level connection object is connected to at least a portion of the selected process object, The aforementioned processing apparatus is The control software is constructed to perform input / output processing with the connected process object and input / output processing with the corresponding higher-level device for the selected higher-level connection object. A computer system characterized by connecting a plurality of selected process objects and constructing the control software to correspond to the flow of each process in logistics operations.

Images