State confirmation system

Abstract

A state confirmation system comprises a collection device, a storage device, and a display terminal. The collection device collects operation data including position data pertaining to a traveling vehicle that travels in a logistic facility. The storage device stores a tag information database in which tag information that indicates the state of that traveling vehicle and is designated from a user, and identification information pertaining to the traveling vehicle, are associated with each other. The display terminal receives the operation data, causes a model of the traveling vehicle to travel on a virtual plane or in a virtual space on the basis of the operation data, and displays operation video in which the tag information associated with the traveling vehicle is displayed so as to be attached to the model of the traveling vehicle.

Description

Status Check System

[0001] The present invention primarily relates to a system for checking the status of logistics facilities (including automated material handling systems that transport semiconductors).

[0002] The management system of Patent Document 1 manages parking facilities using a monitoring equipment terminal. The monitoring equipment terminal is capable of communicating with a control device installed in the parking facilities. The monitoring equipment terminal can display a message on the display unit of the control device of the parking facilities by sending a command to the control device of the parking facilities. The message to be displayed can be created and registered in advance. Patent Document 1 describes, as specific examples of messages, the details of abnormal conditions in the parking facilities and the maintenance status of the parking facilities.

[0003] Japanese Patent Application Laid-Open No. 2004-169506

[0004] The management system of Patent Document 1 allows operators of managed parking facilities to easily understand the status of the parking facilities. However, Patent Document 1 does not describe a process for allowing a manager to understand the status of multiple parking facilities. Furthermore, Patent Document 1 describes that the management system can be applied to automated warehouses, but does not describe its specific configuration. Therefore, Patent Document 1 does not describe a process for allowing a manager to understand the status of devices (traveling vehicles) located in the automated warehouse. This issue is not limited to automated warehouses that manage packages for delivery, but is a common issue in logistics facilities in general, including automated transport systems that transport semiconductors.

[0005] The present invention has been made in consideration of the above circumstances, and its main purpose is to provide a status confirmation system that allows managers to easily understand the status of vehicles traveling through logistics facilities. Means to solve the problem and effects

[0006] The problem to be solved by the present invention is as described above. Next, the means for solving this problem and the effects thereof will be explained.

[0007] According to an aspect of the present invention, there is provided a status confirmation system having the following configuration. That is, the status confirmation system includes a collection device, a storage device, and a display terminal. The collection device collects operation data including position data of traveling vehicles traveling within a logistics facility. The storage device stores a tag information database in which tag information, which indicates the status of the traveling vehicles and is information specified by a user, is associated with identification information of the traveling vehicles. The display terminal receives the operation data, causes a model of the traveling vehicle to travel on a virtual plane or virtual space based on the operation data, and displays an operation video in which the tag information associated with the traveling vehicle is attached to the traveling vehicle model.

[0008] This allows the facility manager (system user) to view operational footage with tag information, enabling him or her to see conditions close to the actual situation at the facility. Therefore, the manager can grasp the detailed status of vehicles simply by viewing the operational footage.

[0009] In the above-described status confirmation system, it is preferable that the tag information database registers the tag information common to a plurality of the traveling vehicles.

[0010] This allows for unified management by registering common tag information for vehicles in the same condition.

[0011] In the above-described status confirmation system, it is preferable that only one piece of tag information is registered for one traveling vehicle in the tag information database.

[0012] This makes it easier to manage the state of the traveling vehicle.

[0013] The status confirmation system is preferably configured as follows: The display terminal displays a vehicle list that lists a plurality of the vehicles. The display terminal displays an indicator in the vehicle list that indicates whether the tag information is registered in the vehicle, but does not display the contents of the tag information in the vehicle list.

[0014] This makes it possible to increase the number of traveling vehicles that can be displayed in the traveling vehicle list on one screen by hiding the contents of the tag information.

[0015] The status confirmation system preferably has the following configuration: The status confirmation system includes a notification unit that notifies of an abnormality in the traveling vehicle. Even if an abnormality occurs in the traveling vehicle for which the tag information is registered, the notification unit does not notify of the abnormality in the traveling vehicle.

[0016] This means that when a process (e.g., maintenance) that may result in an abnormality being notified is scheduled to be performed on a traveling vehicle, unnecessary notifications can be prevented by registering tag information in the traveling vehicle in advance.

[0017] In the above-described status confirmation system, it is preferable that the display terminal displays the operating video in which a three-dimensional model of the traveling vehicle is traveling in a virtual space based on the operating data, and in which a three-dimensional display body containing the tag information is attached to the three-dimensional model of the traveling vehicle.

[0018] This allows managers to see conditions at logistics facilities that are closer to the actual situation on-site.

[0019] In the above-described status confirmation system, it is preferable to store a registration start time when the tag information is registered to the traveling vehicle and a registration deregistration time when the tag information is deregistered from the traveling vehicle.

[0020] This allows the state of a traveling vehicle according to time to be included in the management target.

[0021] In the above-described status checking system, it is preferable that the display terminal uses a time axis to illustrate whether or not the tag information has been registered for each traveling vehicle, based on the registration start time and the registration cancellation time for each traveling vehicle.

[0022] This allows the administrator to easily understand changes in the status of traveling vehicles over time.

[0023] FIG. 1 is a block diagram of a status checking system according to an embodiment of the present invention. FIG. 2 is a diagram showing the contents of a database related to operational data. FIG. 3 is a sequence diagram showing the exchange of various types of data. FIG. 4 is a diagram showing a display terminal on which an operational video is displayed. FIG. 5 is a sequence diagram showing the process of registering and canceling tag information for a traveling vehicle. FIG. 6 is a diagram showing an example of a screen for registering tag information for a traveling vehicle. FIG. 7 is a diagram showing the contents of a tag information database. FIG. 8 is a diagram showing an example of a screen on which a display indicating tag information is added to an operational video. FIG. 9 is a diagram showing an example of a screen on which an icon indicating tag information is added to a traveling vehicle list. A flowchart showing the process of omitting notification of an abnormality when tag information is registered. FIG. 10 is a time chart of the status of a traveling vehicle.

[0024] Next, an embodiment of the present invention will be described with reference to the drawings. First, the configuration of a status checking system 1 will be described with reference to Figs.

[0025] The status confirmation system 1 is installed in a logistics facility. A logistics facility is a facility that handles goods and clearly includes automated material handling systems that transport semiconductors. For example, at a logistics facility, a warehousing operation is performed in which goods are transported and stored in a storage location, and a shipping operation is performed in which goods stored in the storage location are removed and transported to a specified location.

[0026] A plurality of traveling vehicles 10 are provided in the logistics facility. The traveling vehicles 10 are vehicles that travel autonomously within the logistics facility. The traveling vehicles 10 are, for example, transport vehicles that perform warehousing and retrieval operations. Specifically, the transport vehicles are stacker cranes, AGVs, shuttle trolleys, overhead transport vehicles, etc. Furthermore, the traveling vehicles are not limited to vehicles that transport cargo. The traveling vehicles 10 may be, for example, vehicles that monitor the conditions within the logistics facility or vehicles that clean the logistics facility.

[0027] As shown in Fig. 1, the traveling vehicle 10 includes a drive unit 11 and a control unit 12. The drive unit 11 is an electric motor or an engine, and generates power for driving the traveling vehicle 10. The control unit 12 is a computer having a CPU, memory, storage, etc. The control unit 12 controls the drive unit 11 and a steering device (not shown) using a program to cause the traveling vehicle 10 to drive autonomously.

[0028] The traveling vehicle 10 is provided with a module 20. The module 20 modularizes a camera 21, a sensor 22, and a communication device 23. The camera 21 captures images of the surroundings of the traveling vehicle 10. If the traveling vehicle 10 is a stacker crane, the camera 21 may be mounted on a carriage that moves back and forth along rails installed on the ground or on a platform that moves up and down along a mast that extends up and down. Hereinafter, the image data captured and generated by the camera 21 will be referred to as "camera image data." The sensor 22 detects information about the traveling vehicle 10 or its surroundings and generates sensor data indicating the detection results. The sensor 22 detects, for example, temperature, vibration, sound volume, and radio wave conditions. The module 20 may be provided with multiple types of sensors 22, or multiple sensors of the same type. The communication device 23 is a wireless communication module capable of transmitting data via wireless communication. A UWB (Ultra-Wide Band) wireless chipset may be used as the wireless module of the communication device 23. In this case, even if the traveling vehicle 10 is an AGV that travels without a track on a two-dimensional plane, the position of the traveling vehicle 10 can be determined with high accuracy inside the building.

[0029] The data transmitted by the communication device 23 includes not only the camera image data and sensor data described above but also operation data. As shown in FIG. 2 , operation data is data indicating the operation status of the traveling vehicle 10, and includes at least position data of the traveling vehicle 10. The position data of the traveling vehicle 10 included in the operation data is, for example, information specifying one section when a facility is divided according to specific criteria. Alternatively, when the traveling vehicle 10 moves along rails or the like, the position data of the traveling vehicle 10 may be information specifying the position on the rail path. When the traveling vehicle 10 moves on a specific plane, the height position may be omitted. Because the traveling vehicle 10 travels autonomously under the control of the control device 12, the position of the traveling vehicle 10 can be specified based on the control content of the control device 12.

[0030] The operation data may include data other than the position data of the traveling vehicle 10. For example, if the traveling vehicle 10 is capable of changing its orientation (front direction), the operation data may include information on the orientation of the traveling vehicle 10. The operation data may include information indicating whether the traveling vehicle 10 is transporting cargo. If the traveling vehicle 10 has a tool (e.g., a transfer tool), the operation data may include information indicating the status of the tool. For example, if the traveling vehicle 10 is a stacker crane, the operation data may include information indicating the height position of a lifting platform serving as a transfer tool provided on the stacker crane.

[0031] The operation data, camera image data, and sensor data are all time-series data. That is, the operation data is data that indicates the operation status, such as the position of the traveling vehicle 10, at each time. The camera image data is data that indicates images at each time. The sensor data is data that indicates the detection values ​​of the sensor 22 at each time. In the following description, the operation data, camera image data, and sensor data may be collectively referred to as "collected data."

[0032] The status checking system 1 includes a collection server 2, a central server 3, and a display terminal 4.

[0033] The collection server 2 is installed within the logistics facility. The collection server 2 can communicate with the general server 3, the display terminal 4, and the traveling vehicles 10 via a network within the logistics facility. The collection server 2 is a server device equipped with a CPU, memory, storage, communication equipment, etc. The collection server 2 realizes various functions by the CPU executing programs.

[0034] The collection server 2 functions as a collection device. The collection device is a device that receives and stores collected data transmitted by the traveling vehicles 10, as shown in Fig. 3. The collection server 2 may receive the collected data directly from the traveling vehicles 10, or may receive the data via a relay device. The collection server 2 associates the collected data received from the traveling vehicles 10 with a unique device ID (identification information) for identifying the traveling vehicles 10, and stores the data in a database.

[0035] The collecting server 2 determines whether an abnormality has occurred in the traveling vehicle 10 based on the collected data received from the traveling vehicle 10. For example, it determines whether a predetermined abnormality condition is met. The abnormality condition may be, for example, the traveling vehicle 10 being continuously stationary for more than a predetermined time, the position of the traveling vehicle 10 being outside a predetermined range, the position of the luggage being detected to be outside an allowable range based on the analysis results of camera video data, or the detected value of a sensor being above a threshold. The traveling vehicle 10 may determine whether an abnormality has occurred and notify the collecting server 2 of the determination result. As shown in FIG. 3 , if the collecting server 2 determines that an abnormality has occurred, it notifies the central server 3 of the detected abnormality.

[0036] The timing at which the collection server 2 receives the collected data from the traveling vehicle 10 is arbitrary. For example, the collection server 2 may receive the collected data from the traveling vehicle 10 in real time. Alternatively, the traveling vehicle 10 may store collected data for a predetermined length of time (for example, several hours), and the collection server 2 may then receive the collected data for the predetermined length of time all at once.

[0037] 1, the status confirmation system 1 includes a plurality of collection servers 2. Each collection server 2 has the same functions. However, each collection server 2 acquires collected data from a different traveling vehicle 10. For example, each collection server 2 stores a list of device IDs of traveling vehicles 10 from which it should acquire collected data, and stores only collected data for device IDs listed on the list in a database.

[0038] The general server 3 may be installed within the logistics facility, or may be installed in a monitoring facility located away from the logistics facility. The general server 3 can communicate with the collection server 2 and the display terminal 4 via a network within the logistics facility. The general server 3 may also be installed on a cloud. In this case, the general server 3 can communicate with the collection server 2 and the display terminal 4 via the Internet.

[0039] The general server 3 is a server device equipped with a CPU, memory, storage, communication equipment, etc. The CPU executes programs to enable the general server 3 to realize various functions, including a web server function, a model management function, and a state management function.

[0040] The web server function is a function that transmits data such as HTML data, CSS, and images required to display a specific web page to the display terminal 4 when the display terminal 4 accesses it using a browser. The browser on the display terminal 4 displays the web page based on the received data. Furthermore, when a button or link displayed on the web page is selected, the central server 3 transmits new data such as HTML data, CSS, and images corresponding to the selected button or link to the display terminal 4. Note that the web server function is not essential, and the display terminal 4 may store information regarding the screen layout, etc.

[0041] Next, the model management function will be described. In this embodiment, an image in which a three-dimensional model (three-dimensional CAD data) is arranged in a virtual space is generated. The three-dimensional model includes a three-dimensional model showing the environment of the logistics facility and a three-dimensional model showing the traveling vehicle 10. The three-dimensional model of the environment is data in which three-dimensional models of structures such as floors, shelves, ceilings, and stationary machines are arranged according to the actual positions of the logistics facility. The central server 3 stores the above-mentioned three-dimensional models and transmits a specified three-dimensional model in response to a request from the display terminal 4. Note that the model management function is not essential; for example, the display terminal 4 may store the three-dimensional models in advance.

[0042] The status management function is a function for managing the status of the traveling vehicle 10. For example, the status management function is a function for storing information that an abnormality has occurred in the traveling vehicle 10 in association with the device ID. Furthermore, the status management function is a function for notifying the display terminal 4 that an abnormality has occurred, and for notifying the mobile terminal of the administrator that an abnormality has occurred. The status management function allows the central server 3 to operate as a notification unit. Note that the status management function is not essential and can be omitted. The status management function also includes a function for storing a tag information database, which will be described later. This allows the central server 3 to also operate as a storage device.

[0043] By using the above-described functions, the central server 3 transmits browser display data, three-dimensional models of the environment and the traveling vehicle, and abnormality information to the display terminal 4, as shown in FIG.

[0044] The status checking system 1 of this embodiment is provided with two types of server devices: a collection server 2 and a general server 3. Alternatively, the functions of the collection server 2 and the general server 3 may be integrated into a single server device. Alternatively, a separate server device may be provided for each of the multiple functions possessed by the general server 3.

[0045] The display terminal 4 is a terminal that allows the manager to check the status of the logistics facility. The display terminal 4 is capable of communicating with the collection server 2 and the general server 3 via a network within the logistics facility. The display terminal 4 is, for example, a tablet device, a smartphone, a PC, or a dedicated terminal. The display terminal 4 is equipped with a CPU, memory, storage, a communication device, a display, and an input device. The CPU executes programs to enable the display terminal 4 to realize various functions. The display shows images and the like that allow the manager to check the status of the logistics facility. The input device is a hardware key or a touch panel, and accepts operations from the manager.

[0046] The display terminal 4 displays operation video on the display, for example, by generating and playing operation video data. The operation video is a video in which a 3D model of the environment of the logistics facility described above is placed in a virtual space and the 3D model of the traveling vehicle 10 is traveling based on the operation data. Since the operation data includes position data, the display terminal 4 can generate operation video data by changing the display position of the 3D model in response to changes in the position data.

[0047] For example, when an administrator gives an instruction to display an operation video of a specified area, the display terminal 4 requests and acquires collected data of the traveling vehicles 10 located in that area from the collection server 2. Next, the display terminal 4 requests and acquires a 3D model of the environment and traveling vehicles 10 located in that area from the central server 3. Next, the display terminal 4 generates and plays back operation video data based on the acquired collected data (particularly operation data) and 3D model, thereby displaying the operation video on the display as shown in FIG.

[0048] The central server 3 may generate the operation video data instead of the display terminal 4. In this case, the display terminal 4 plays the operation video data received from the central server 3. Since the operation video is a three-dimensional video, the viewpoint can be changed. Also, some three-dimensional models can be hidden. By checking the three-dimensional operation video, the manager can intuitively and in detail grasp the state of the logistics facility (especially the state of the traveling vehicles 10).

[0049] In this embodiment, the display terminal 4 displays three-dimensional operation images on the display. Alternatively, the display terminal 4 may display two-dimensional operation images on the display. The two-dimensional operation images are, for example, images in which a two-dimensional model of the environment (image data or two-dimensional drawing data) and a two-dimensional model of the traveling vehicle 10 are arranged on a virtual plane, and the two-dimensional model of the traveling vehicle 10 is caused to travel based on the operation data. For example, when the traveling vehicle 10 barely moves in the vertical direction, an operation image can be generated that shows the positional relationship between the environment and the traveling vehicle 10 in a planar view.

[0050] Next, the function of registering tag information in the traveling vehicle 10 and displaying it in the operating video will be described in detail with reference to FIGS. 5 to 9. FIG.

[0051] In an actual logistics facility, when a traveling vehicle 10 is undergoing maintenance, a tag (display board, sign) stating "under maintenance" may be attached to the traveling vehicle 10. An operator of the logistics facility can understand the status of the traveling vehicle 10 by looking at this tag. In addition to when the traveling vehicle 10 is undergoing maintenance, tags stating "installation in progress" or "requires inspection" may also be attached.

[0052] On the other hand, tags are not displayed in conventional operation images. Therefore, even if the traveling vehicle 10 is undergoing maintenance, the manager cannot know from the operation image that the maintenance is being performed. In contrast, the status confirmation system 1 of this embodiment displays an indicator equivalent to a tag in the operation image, thereby displaying operation image that is closer to the actual site of the logistics facility. Detailed processing will be described below.

[0053] In this embodiment, tag information can be registered for the traveling vehicle 10. The tag information is information that indicates the status of the traveling vehicle 10, and for example, information equivalent to the tag described above can be registered. The administrator, who is the user of this system, can enter any character string to register the tag information. Note that multiple registration candidates may be prepared in advance on the system side, and the administrator may select the most appropriate registration candidate from the multiple registration candidates. In actual operation, tag information is expected to include, for example, as described above, "under maintenance," "under installation work," and "requires inspection."

[0054] As shown in the sequence diagram of Fig. 5, the display terminal 4 can accept registration of tag information for a traveling vehicle. Specifically, as shown in Fig. 6, the display terminal 4 displays a registration screen 30 for registering tag information on the display. The registration screen 30 includes an ID field 31, a display content field 32, a traveling vehicle field 33, and a remarks field 34.

[0055] The ID of the tag information is automatically entered in the ID field 31. The ID of the tag information is used by the status confirmation system 1 to identify the tag information, but the administrator does not need to be aware of the ID. The administrator can enter the content of the tag information in the display content field 32. As described above, the administrator may freely enter text, or may select one from registration candidates. The content entered in the display content field 32 is displayed on the operating video, as described below. The name of the traveling vehicle 10 for which tag information is to be registered is entered in the traveling vehicle field 33. Specifically, by selecting the link labeled "Select traveling vehicle" to the right of the display content field 32, a list of traveling vehicles 10 is displayed on the display. The administrator selects one or more traveling vehicles 10 for which tag information is to be registered from the list of traveling vehicles 10. As a result, the name of the traveling vehicle 10 is entered in the traveling vehicle field 33. An explanation of the tag information, etc., can be entered in the remarks field 34, as necessary.

[0056] In this embodiment, tag information in which the same character string is entered in the display content field 32 is treated as common tag information. For example, if, at a certain timing, a first traveling vehicle 10 is registered as being under maintenance, and thereafter a second traveling vehicle 10 is also registered as being under maintenance, the two traveling vehicles 10 are treated as having common tag information registered therein. This makes it possible to display a list of traveling vehicles 10 undergoing maintenance, as will be described later.

[0057] In this embodiment, multiple traveling vehicles 10 can be entered in the traveling vehicle field 33, so it is possible to collectively register tag information common to multiple traveling vehicles 10. However, this function is an example, and only one traveling vehicle 10 may be entered in the traveling vehicle field 33.

[0058] In this embodiment, for the purpose of facilitating management, only one piece of tag information can be registered to one traveling vehicle 10. Alternatively, multiple pieces of tag information may be registered to one traveling vehicle 10.

[0059] 6 is an example, and tag information may be registered from another screen. For example, tag information may be registered in the traveling vehicle 10 by operating a menu button on a list or property screen of the traveling vehicle 10 and operating "Add tag information" or the like.

[0060] After completing the input, the administrator operates the registration button. As a result, the display terminal 4 transmits the correspondence between the traveling vehicle 10 (more specifically, the device ID of the traveling vehicle 10) and the tag information to the general server 3 based on the input content on the registration screen 30 ( FIG. 5 ). The general server 3 associates the traveling vehicle 10, tag information, and registration start time and registers them in the database based on the correspondence received from the display terminal 4 ( FIG. 5 ). The registration start time may be the time when the general server 3 registers the tag information, the time when the correspondence information is received from the display terminal 4, or the time when the registration start time is received from the display terminal 4. This completes the registration of the tag information.

[0061] As a result, a tag information database such as that shown in Fig. 7 is created. The tag information database is a database in which the device ID of the traveling vehicle 10, tag information (content entered in the display content field 32), registration start time, and registration deregistration time (details will be described later) are associated with each other. The general server 3 can transmit information extracted in response to a request received from the display terminal 4 to the display terminal 4. For example, when a device ID is specified from the display terminal 4, the general server 3 extracts tag information, registration start time, and registration deregistration time associated with the specified device ID and transmits them to the display terminal 4. Furthermore, when tag information is specified from the display terminal 4, the general server 3 extracts one or more device IDs associated with the specified tag information, their respective registration start times, and registration deregistration times, and transmits them to the display terminal 4.

[0062] 8 shows an example of a screen in which a display 41 showing tag information is attached to an operation video. The display 41 is plate-shaped and displays the name of the traveling vehicle 10, an icon showing the tag information, and the content of the tag information. The content of the tag information is the same as the content entered in the display content field 32. Because the display 41 is displayed attached to the corresponding traveling vehicle 10, when the traveling vehicle 10 moves, the display 41 also moves together with the traveling vehicle 10. Furthermore, it is possible to select whether the display 41 is displayed in an orientation that allows the content of the display 41 to be seen even when the viewpoint of the operation video is changed, or whether it is displayed so that it can be seen from a fixed direction when viewed from a bird's eye view, depending on the settings.

[0063] This allows the above-mentioned tag to be reproduced on the operational video, allowing the manager to easily grasp the state of the traveling vehicle 10.

[0064] 9 shows an example screen in which an icon representing tag information is added to the traveling vehicle list. The traveling vehicle list is an item that displays a list of all traveling vehicles 10 installed in a logistics facility, or a list of traveling vehicles 10 extracted based on predetermined conditions. As shown in FIG. 9, if tag information is registered for a traveling vehicle 10 listed in the traveling vehicle list, an icon representing the tag information is added near the name of the traveling vehicle 10. This allows the administrator to know at a glance whether tag information is registered for a traveling vehicle 10 listed in the traveling vehicle list.

[0065] As shown in the example screen at the top of Fig. 9, when the list of traveling vehicles is simply displayed, the contents of the tag information are not displayed. When the administrator selects one of the traveling vehicles 10, the display field for the traveling vehicle 10 expands, as shown in the example screen at the bottom of Fig. 9, and the contents of the tag information and the registration start time are further displayed. This allows the administrator to check the contents of the tag information registered in the traveling vehicle 10 as needed.

[0066] In this way, by reducing the amount of information displayed for each item in the traveling vehicle list before the administrator makes a selection, the traveling vehicles 10 can be displayed densely in the traveling vehicle list, improving the visibility. Then, by simply selecting a traveling vehicle 10, the administrator can check the contents of the tag information, etc.

[0067] It is preferable that the additional information displayed when a traveling vehicle 10 is selected from the traveling vehicle list includes at least the contents of the tag information. However, displaying the registration start time and the registration cancellation time is not essential and can be omitted.

[0068] Display examples of tag information are not limited to the examples shown in Fig. 8 and Fig. 9. For example, the display terminal 4 can also collectively display traveling vehicles 10 for which common tag information is registered. For example, it can display a list of traveling vehicles 10 for which tag information is registered that are undergoing maintenance.

[0069] Next, the release of tag information will be described. As shown in the sequence diagram of Fig. 5, the display terminal 4 can accept the release of tag information registered in the traveling vehicle 10. For example, the administrator operates a menu button on the property screen of the traveling vehicle 10 and selects to release tag information, which causes the display terminal 4 to accept the release of tag information. As a result, the display terminal 4 transmits to the general server 3 the traveling vehicle 10 whose tag information is to be released (Fig. 5). Based on the information received from the display terminal 4, the general server 3 additionally registers the registration release time in the tag information database (Fig. 5).

[0070] When the deregistration time is registered, the corresponding tag information becomes inactive, and the display 41 is not displayed in the operating video. However, in this embodiment, the tag information is not deleted from the tag information database in order to record the time period in which the tag information was registered.

[0071] Next, the relationship between abnormality notification and tag information will be described with reference to Fig. 10. Each process in the flowchart of Fig. 10 includes a process performed by the collection server 2 and a process performed by the central server 3.

[0072] First, the collection server 2 determines whether or not an abnormality has occurred in the traveling vehicle 10 (S101). The criteria for determining whether or not an abnormality has occurred are as described above. If the collection server 2 determines that an abnormality has occurred in the traveling vehicle 10, it notifies the general server 3 to that effect (S102). The content of the notification includes, for example, the device ID of the traveling vehicle 10, the time when the abnormality occurred, and the content of the abnormality.

[0073] The central server 3, upon receiving this notification, determines whether tag information is registered for the traveling vehicle 10 in which the abnormality was detected. The central server 3 also functions as a storage device for the tag information database, and is therefore able to make this determination based on the contents of its own storage.

[0074] Here, when performing maintenance on the traveling vehicle 10, abnormal conditions may be met because the traveling of the traveling vehicle 10 is stopped or vibrations are generated due to part replacement, etc. Furthermore, even during installation work or when an inspection is required, the situation of the traveling vehicle 10 is different from that during normal work, so abnormal conditions may be met. If an abnormality is notified to the administrator in such a situation, it will increase the administrator's workload.

[0075] In this regard, the general server 3 of this embodiment omits the notification of an abnormality for traveling vehicles 10 for which tag information is registered. Specifically, when the general server 3 receives a notification of an abnormality from the collection server 2, it determines whether tag information is registered for the target traveling vehicle 10 (S103). If tag information is not registered for the target traveling vehicle 10, the general server 3 notifies the abnormality (S104). As described above, the method of notifying the abnormality may be to notify the display terminal 4 or the administrator's mobile terminal. On the other hand, if tag information is registered for the target traveling vehicle 10, the general server 3 omits the notification of the abnormality (S105). This makes it possible to reduce unnecessary notifications.

[0076] In this embodiment, in step S103, it is determined whether or not any tag information is registered in the traveling vehicle 10, but it may also be determined whether or not specific tag information is registered in the traveling vehicle 10. As a result, for example, it is possible to set up so that notification of an abnormality is omitted when tag information of "under maintenance" is registered in the traveling vehicle 10, and so that notification of an abnormality is notified when tag information of "just after repair" is registered in the traveling vehicle 10.

[0077] Next, a state time chart of the traveling vehicle 10 will be described with reference to FIG.

[0078] The status time chart for the traveling vehicle 10 is a diagram showing the status of a specified traveling vehicle 10 at each time. The horizontal axis in FIG. 11 corresponds to the time axis. Based on instructions given by the administrator operating the display terminal 4, the central server 3 or the display terminal 4 generates a status time chart and displays it on the display of the display terminal 4. The statuses shown in the status time chart include the tag information registration status, abnormal status, warning status, unconnected status, and normal status. Statuses other than the tag information registration status are not required and can be omitted.

[0079] As described above, the registration start time and registration cancellation time of tag information are registered in the central server 3 for each traveling vehicle 10. Therefore, a status time chart of tag information can be generated based on the registration start time and registration cancellation time. In the example of Figure 11, the content of the tag information is "under maintenance," so "under maintenance" is also written in the status time chart.

[0080] Abnormalities are as described above. Warnings are states that do not meet the abnormal conditions but are close to them. Unconnected states mean that collected data cannot be acquired from the traveling vehicle 10. Normal states are states that do not fall into any of the above states. In this embodiment, logs are created for abnormalities, warnings, and unconnected states, each associated with a time, and a state time chart can be generated based on the logs.

[0081] As described above, the status confirmation system 1 of this embodiment includes the collection server 2, the central server 3, and the display terminal 4. The collection server 2 collects operation data including position data of the traveling vehicles 10 traveling in the logistics facility. The central server 3 stores a tag information database in which tag information, which indicates the status of the traveling vehicles 10 and is information specified by a user, is associated with identification information of the traveling vehicles 10. The display terminal 4 receives the operation data, causes a model of the traveling vehicle 10 to travel on a virtual plane or virtual space based on the operation data, and displays an operation video in which the tag information associated with the traveling vehicle 10 is attached to the model of the traveling vehicle 10. This is Feature 1.

[0082] This allows the facility manager (system user) to view operational footage with tag information, enabling him or her to see conditions close to the actual situation at the facility. Therefore, the manager can grasp the detailed status of vehicles simply by viewing the operational footage.

[0083] In the state confirmation system 1 of this embodiment, common tag information is registered in the tag information database for a plurality of traveling vehicles 10. This is the second feature.

[0084] This allows for unified management by registering common tag information for traveling vehicles 10 in the same state.

[0085] In the state confirmation system 1 of this embodiment, only one piece of tag information is registered in the tag information database for one traveling vehicle 10. This is characteristic 3.

[0086] This makes it easier to manage the state of the traveling vehicle 10.

[0087] In the status checking system 1 of this embodiment, the display terminal 4 displays a vehicle list that lists a plurality of vehicles 10. The display terminal 4 displays an icon indicating whether tag information is registered in the vehicle 10, but does not display the contents of the tag information in the vehicle list. This is feature 4.

[0088] This makes it possible to increase the number of traveling vehicles 10 that can be displayed in the traveling vehicle list on one screen by hiding the contents of the tag information.

[0089] The status checking system 1 of this embodiment includes a central server 3 that notifies of abnormalities in the traveling vehicles 10. Even if an abnormality occurs in a traveling vehicle 10 whose tag information is registered, the central server 3 does not notify of the abnormality in the traveling vehicle 10. This is the fifth feature.

[0090] This means that when a process (e.g., maintenance) that may result in an abnormality being notified is scheduled to be performed on the vehicle, unnecessary notifications can be prevented by registering tag information in the vehicle 10 in advance.

[0091] In the condition monitoring system 1 of this embodiment, the display terminal 4 displays an operation video in which a three-dimensional model of the traveling vehicle 10 is driven in a virtual space based on operation data, and a three-dimensional display body 41 carrying tag information is attached to the three-dimensional model of the traveling vehicle 10. This is Feature 6.

[0092] This allows managers to see conditions at logistics facilities that are closer to the actual situation on-site.

[0093] The status checking system 1 of this embodiment stores the registration start time when tag information is registered in the traveling vehicle 10 and the registration deregistration time when tag information is deregistered from the traveling vehicle 10. This is feature 7.

[0094] This allows the state of the traveling vehicle 10 according to time to be included in the management target.

[0095] In the status checking system 1 of this embodiment, the display terminal 4 uses a time axis to display whether or not tag information has been registered for each traveling vehicle 10, based on the registration start time and the registration cancellation time for each traveling vehicle 10. This is Feature 8.

[0096] This allows the administrator to easily grasp the changes in the state of the traveling vehicle 10 over time.

[0097] The above-described features 1 to 8 can be combined, for example, as follows, to realize status confirmation systems with the following aspects: [Aspect 1] A status confirmation system having feature 1. [Aspect 2] A status confirmation system that, in addition to aspect 1, further has feature 2. [Aspect 3] A status confirmation system that, in addition to aspect 1 or 2, further has feature 3. [Aspect 4] A status confirmation system that, in addition to any one of aspects 1 to 3, further has feature 4. [Aspect 5] A status confirmation system that, in addition to any one of aspects 1 to 4, further has feature 5. [Aspect 6] A status confirmation system that, in addition to any one of aspects 1 to 5, further has feature 6. [Aspect 7] A status confirmation system that, in addition to any one of aspects 1 to 6, further has feature 7. [Aspect 8] A status confirmation system that, in addition to aspect 7, further has feature 8.

Claims

1. A status confirmation system comprising: a collection device that collects operational data including position data of vehicles traveling within a logistics facility; a storage device that stores a tag information database that associates tag information, which is information that indicates the status of the vehicles and is specified by a user, with identification information of the vehicles; and a display terminal that receives the operational data, runs a model of the vehicle on a virtual plane or virtual space based on the operational data, and displays an operational video in which the tag information associated with the vehicle is attached to the model.

2. A status confirmation system according to claim 1, characterized in that the tag information database registers the tag information common to a plurality of the traveling vehicles.

3. A status confirmation system according to claim 1, characterized in that only one piece of tag information is registered for one traveling vehicle in the tag information database.

4. A status confirmation system as described in claim 1, wherein the display terminal displays a list of a plurality of said traveling vehicles, and the display terminal displays an indicator in the traveling vehicle list indicating whether or not said tag information is registered in said traveling vehicle, but does not display the contents of said tag information in said traveling vehicle list.

5. A status confirmation system as described in claim 1, further comprising a notification unit that notifies of an abnormality in the traveling vehicle, wherein even if an abnormality occurs in the traveling vehicle for which the tag information is registered, the notification unit does not notify of the abnormality in the traveling vehicle.

6. A status confirmation system as described in claim 1, characterized in that the display terminal displays the operating video in which a three-dimensional model of the traveling vehicle is traveling in a virtual space based on the operating data, and a three-dimensional display body containing the tag information is attached to the three-dimensional model of the traveling vehicle.

7. A status confirmation system as claimed in claim 1, characterized in that it stores the registration start time when the tag information is registered to the traveling vehicle and the registration cancellation time when the tag information is cancelled from the traveling vehicle.

8. A status confirmation system as described in claim 7, characterized in that the display terminal uses a time axis to illustrate whether or not the tag information for each traveling vehicle has been registered, based on the registration start time and the registration cancellation time for each traveling vehicle.

Images