Schedule management system and program
The schedule management system addresses inefficiencies in guiding vehicles at construction site gates by using a server and terminals to predict arrival times and manage reservations, enhancing vehicle guidance efficiency.
Patent Information
- Application Number
- JP2023075028
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-04-28
- Publication Date
- 2024-11-08
AI Technical Summary
Existing technologies struggle to smoothly guide multiple loading/unloading vehicles at construction site gates due to changes in scheduled arrival times, leading to inefficiencies in managing vehicle entry and exit.
A schedule management system and program that utilizes a schedule management server and terminals for drivers and gate managers to transmit and display location information, predict arrival times, and manage reservations, allowing for efficient guidance of vehicles at construction site gates.
The system enables smooth guidance of loading/unloading vehicles by displaying predicted arrival times and reservation statuses, improving efficiency at construction site gates.
Smart Images

Figure 2024159189000001_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to a schedule management system and a program. [Background technology]
[0002] Conventionally, a transportation system is known in which information regarding the location of a transportation means, travel time of a transportation route, and a destination is collected and centrally managed, and this information is shared among the departure point, the transportation means, and the destination (for example, Patent Document 1).
[0003] Also, a train operation schedule linking method that facilitates the modification of a train operation schedule and the action associated with the result of the modification is known (for example, Patent Document 2).
[0004] There is also known a schedule management system that determines whether a departure time is near or far from the current time, and notifies any destination of changes in the scheduled departure time or predicted arrival time that accompany changes in traffic conditions (eg, Patent Document 3).
[0005] Also, a schedule management device is known that realizes schedule management and appropriate schedule modification without requiring communication via a network (for example, Patent Document 4). [Prior art documents] [Patent documents]
[0006] [Patent Document 1] JP 2002-324295 A [Patent Document 2] Japanese Patent Application Publication No. 10-63728 [Patent Document 3] JP 2005-11196 A [Patent Document 4] JP 2010-257358 A Summary of the Invention [Problem to be solved by the invention]
[0007] Incidentally, the loading / unloading gates of construction sites generally have a high traffic of loading / unloading vehicles. In this specification, the term "loading / unloading gate" includes a gate that only loads materials and equipment to the construction site, a gate that only loads the materials and equipment, and a gate that loads and unloads the materials and equipment. In addition, in this specification, the term "loading / unloading vehicle" includes a vehicle that only loads materials and equipment to the construction site, a vehicle that only loads the materials and equipment, and a vehicle that loads and unloads the materials and equipment. Furthermore, in this specification, the term "scheduled loading / unloading time" as described later includes only the scheduled time of loading materials and equipment to the construction site by the loading / unloading vehicle, only the scheduled time of unloading materials and equipment from the construction site by the loading / unloading vehicle, and a combination of both the scheduled loading time and the scheduled unloading time.
[0008] For this reason, if the scheduled time for a loading / unloading vehicle to enter the loading / unloading gate is changed, the person in charge of the loading / unloading gate must take that change into account when guiding other loading / unloading vehicles.
[0009] In this regard, the techniques disclosed in the above Patent Documents 1 to 4 are techniques for notifying any destination of changes in the predicted arrival time of a vehicle, but simply notifying the gate manager at the construction site of the change makes it difficult to smoothly guide multiple vehicles. For example, even if the gate manager is notified of a change in the scheduled arrival time of a certain vehicle, the gate manager must also understand the schedules of the vehicles before and after that vehicle and guide the multiple vehicles.
[0010] The present invention has been made in consideration of the above circumstances, and has an object to provide a schedule management system and program that can smoothly guide vehicles entering and leaving a construction site at its loading and unloading gates. [Means for solving the problem]
[0011] The schedule management system of the present invention described in claim 1 is a schedule management system comprising a terminal held by each of the drivers of a plurality of loading / unloading vehicles and a schedule management server, wherein each of the plurality of terminals transmits location information of the loading / unloading vehicle to the schedule management server, and the schedule management server calculates at least one of the predicted arrival times of the plurality of loading / unloading vehicles at the loading / unloading gate for equipment and materials at a construction site and the required time for the plurality of loading / unloading vehicles to arrive at the loading / unloading gate based on the location information of the loading / unloading vehicle transmitted from each of the plurality of terminals, and displays a list of at least one of the predicted arrival times and the required time of the plurality of loading / unloading vehicles and the original scheduled loading / unloading times of the plurality of loading / unloading vehicles.
[0012] According to the schedule management system of the present invention as described in claim 1, at least one of the predicted arrival times of multiple loading / unloading vehicles at the equipment / materials loading / unloading gate at the construction site and the time required for the multiple loading / unloading vehicles to arrive at the loading / unloading gate is calculated based on the location information of the loading / unloading vehicles transmitted from each of the multiple terminals, and at least one of the predicted arrival times and the required time for the multiple loading / unloading vehicles to arrive at the loading / unloading gate is displayed in a list, thereby making it possible to smoothly guide the loading / unloading vehicles at the loading / unloading gate at the construction site.
[0013] The schedule management system of the present invention as described in claim 2 is the schedule management system as described in claim 1, wherein the schedule management server displays a list of scheduled loading and unloading times, which are the reservation status of loading and unloading gates at multiple construction sites, on each of the terminals held by each of the drivers of the multiple loading and unloading vehicles.
[0014] According to the schedule management system of the present invention as described in claim 2, the schedule management server displays a list of scheduled loading / unloading times, which are the reservation status of the loading / unloading gates of multiple construction sites, on each of the terminals held by the drivers of multiple loading / unloading vehicles, thereby allowing the drivers of multiple loading / unloading vehicles to understand the reservation status of the loading / unloading vehicles they drive.
[0015] The schedule management system of the present invention as described in claim 3 is a schedule management system as described in claim 1 or claim 2, wherein the schedule management server, in response to instruction information from the terminal, causes the terminal to display a map image including location information of the loading / unloading gate at the construction site.
[0016] According to the schedule management system of the present invention as described in claim 3, the schedule management server responds to instruction information from the terminal by displaying a map image including location information of the loading / unloading gates at the construction site on the terminal, thereby enabling multiple loading / unloading vehicles to move more smoothly to the loading / unloading gates at the construction site.
[0017] The schedule management system of the present invention as described in claim 4 is the schedule management system as described in claim 1 or claim 2, wherein the schedule management server identifies the current status of each of the multiple loading / unloading vehicles based on information input by a user or location information of the loading / unloading vehicles, and when displaying a list of the predicted arrival time and the scheduled loading / unloading time of each of the multiple loading / unloading vehicles, displays the current status of each of the multiple loading / unloading vehicles, and the current status of the loading / unloading vehicles is at least one of departing for the construction site, waiting in the vicinity of the construction site, entering the construction site, working at the construction site, and leaving the construction site.
[0018] According to the schedule management system of the present invention as described in claim 4, the current status of each of the multiple loading / unloading vehicles is identified based on information input by the user or the location information of the loading / unloading vehicles, and when displaying a list of the predicted arrival time and scheduled loading / unloading time of each of the multiple loading / unloading vehicles, the current status of each of the multiple loading / unloading vehicles is displayed, while the current status of the loading / unloading vehicle is set to at least one of departing for the construction site, waiting in the vicinity of the construction site, entering the construction site, working at the construction site, and leaving the construction site, so that a person viewing the predicted arrival time and scheduled loading / unloading time can understand the applied status of the multiple loading / unloading vehicles.
[0019] The schedule management system of the present invention as described in claim 5 is a schedule management system as described in claim 1 or claim 2, wherein, when the loading / unloading vehicle is able to enter the loading / unloading gate, the schedule management server notifies the terminal held by the driver of the loading / unloading vehicle that entry is now possible.
[0020] According to the schedule management system of the present invention as described in claim 5, when a loading / unloading vehicle is able to enter the loading / unloading gate, the schedule management server notifies the terminal held by the driver of the loading / unloading vehicle that entry is now possible, thereby enabling the drivers of multiple loading / unloading vehicles to drive efficiently depending on the ability to enter the loading / unloading gate.
[0021] The schedule management system of the present invention as described in claim 6 is a schedule management system as described in claim 1 or claim 2, wherein the schedule management server notifies the terminal held by the driver of the loading / unloading vehicle of the entry time, which is the time when the loading / unloading vehicle will be able to enter the loading / unloading gate.
[0022] According to the schedule management system of the present invention as described in claim 6, the schedule management server notifies the terminal held by the driver of the loading / unloading vehicle of the entry time, which is the time when the loading / unloading vehicle is able to enter the loading / unloading gate, thereby enabling the drivers of multiple loading / unloading vehicles to drive efficiently according to the entry time at the loading / unloading gate.
[0023] The program of the present invention as set forth in claim 7 causes a computer to execute a process of calculating at least one of the predicted arrival times of a plurality of loading / unloading vehicles at a material / equipment loading / unloading gate at a construction site and the amount of time required for the plurality of loading / unloading vehicles to arrive at the loading / unloading gate, based on position information of the loading / unloading vehicles transmitted from each of a plurality of terminals, and displaying a list of at least one of the predicted arrival times and the amount of time required for the plurality of loading / unloading vehicles and the original scheduled loading / unloading times of the plurality of loading / unloading vehicles.
[0024] According to the program of the present invention as set forth in claim 7, at least one of the predicted arrival times of multiple loading / unloading vehicles at the equipment / materials loading / unloading gate at the construction site and the time required for the multiple loading / unloading vehicles to arrive at the loading / unloading gate is calculated based on the location information of the loading / unloading vehicles transmitted from each of the multiple terminals, and at least one of the predicted arrival times and the required time for the multiple loading / unloading vehicles to arrive at the loading / unloading gate is displayed in a list, thereby making it possible to smoothly guide the loading / unloading vehicles at the loading / unloading gate at the construction site. Effect of the Invention
[0025] As described above, according to the present invention, it is possible to smoothly guide vehicles entering and leaving a construction site at a loading / unloading gate. [Brief description of the drawings]
[0026] [Figure 1] 1 is a block diagram showing an example of a hardware configuration of a schedule management system according to an embodiment. [Diagram 2] 1 is a block diagram showing an example of a functional configuration of a schedule management system according to an embodiment. [Diagram 3] 1 is a diagram illustrating an example of a list display of predicted arrival times and original scheduled delivery times of a plurality of delivery and unloading vehicles in a schedule management system according to an embodiment, and is used to explain the effects of the example. FIG. [Figure 4] FIG. 2 is a schematic diagram illustrating an example of a configuration of a schedule management database according to the embodiment. [Diagram 5] FIG. 2 is a schematic diagram showing an example of a configuration of a construction site information database according to the embodiment. [Figure 6] 10 is a flowchart illustrating an example of a schedule management process according to the embodiment. [Figure 7] 10 is a flowchart illustrating an example of a gate terminal process according to the embodiment. [Figure 8] 11 is a front view showing an example of a configuration of a schedule management list screen according to the embodiment; FIG. [Figure 9] 11 is a front view showing an example of a configuration of a first state designation screen according to the embodiment. FIG. [Figure 10] 10 is a flowchart illustrating an example of a driver terminal process according to the embodiment. [Figure 11] FIG. 13 is a front view showing an example of a configuration of a carry-in / carry-out list screen according to the embodiment. [Figure 12] 11 is a front view showing an example of a configuration of a second state designation screen according to the embodiment. FIG. [Figure 13] FIG. 13 is a front view showing an example of the configuration of a carry-in route display screen according to the embodiment. [Figure 14] FIG. 1 is a schematic diagram for explaining the effect of a schedule management system according to an embodiment. [Figure 15] FIG. 13 is a front view showing another example of the configuration of the carry-in / out list screen according to the embodiment. [Figure 16] FIG. 13 is a front view showing another example of the configuration of the carry-in / out list screen according to the embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0027] Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings. In this embodiment, the present invention will be described as being applied to a schedule management system including a schedule management server that manages the schedule for delivery of materials and equipment to a construction site, a driver terminal held by each driver of a plurality of delivery vehicles that deliver materials and equipment to and from the construction site, and a gate manager terminal held by a plurality of managers that manage the entry and exit of delivery vehicles at a delivery gate of the construction site.
[0028] First, the configuration of a schedule management system 90 according to this embodiment will be described with reference to Fig. 1. Fig. 1 is a block diagram showing an example of the hardware configuration of the schedule management system 90 according to this embodiment.
[0029] 1, a schedule management system 90 according to this embodiment includes a schedule management server 10, multiple driver terminals 30, and multiple gate administrator terminals 50, each of which is accessible to a network 80. Examples of the schedule management server 10 include information processing devices such as personal computers and server computers. Examples of the driver terminal 30 and the gate administrator terminal 50 include portable terminals such as smartphones, tablet terminals, and PDAs (Personal Digital Assistants, portable information terminals).
[0030] The driver's terminal 30 according to this embodiment includes a CPU (Central Processing Unit) 31 as a processor, a memory 32 as a temporary storage area, a non-volatile storage unit 33, an input unit 34 such as a touch panel, a display unit 35 such as a liquid crystal display, and a medium reading and writing device (R / W) 36. The driver's terminal 30 also includes a wireless communication unit 38 and a position detection unit 39. The CPU 31, the memory 32, the storage unit 33, the input unit 34, the display unit 35, the medium reading and writing device 36, the wireless communication unit 38, and the position detection unit 39 are connected to each other via a bus B1. The medium reading and writing device 36 reads information written in a recording medium 37 and writes information to the recording medium 37.
[0031] The storage unit 33 is realized by an HDD (Hard Disk Drive), an SSD (Solid State Drive), a flash memory, or the like. A driver terminal processing program 33A is stored in the storage unit 33 as a storage medium. The driver terminal processing program 33A is stored (installed) in the storage unit 33 by setting a recording medium 37, on which the program 33A is written, in the medium reading and writing device 36, and the medium reading and writing device 36 reading the program 33A from the recording medium 37. The CPU 31 appropriately reads the driver terminal processing program 33A from the storage unit 33, expands it in the memory 32, and sequentially executes the processes of the driver terminal processing program 33A.
[0032] The position detection unit 39 detects its own position and transmits position information indicating the position. In this embodiment, a system using a GPS (Global Positioning System) is applied as a system for detecting the position by the position detection unit 39, but the present invention is not limited to this. For example, a system using a beacon, a two-dimensional code, or air pressure may be applied as a system for detecting the position by the position detection unit 39.
[0033] Meanwhile, the gate administrator terminal 50 according to this embodiment includes a CPU 51 as a processor, a memory 52 as a temporary storage area, a non-volatile storage unit 53, an input unit 54 such as a touch panel, a display unit 55 such as a liquid crystal display, a medium reading and writing device (R / W) 56, and a wireless communication unit 58. The CPU 51, memory 52, storage unit 53, input unit 54, display unit 55, medium reading and writing device 56, and wireless communication unit 58 are connected to each other via a bus B2. The medium reading and writing device 56 reads information written in a recording medium 57 and writes information to the recording medium 57.
[0034] The storage unit 53 is realized by an HDD, an SSD, a flash memory, or the like. A gate terminal processing program 53A is stored in the storage unit 53 as a storage medium. The gate terminal processing program 53A is stored (installed) in the storage unit 53 by setting a recording medium 57, on which the program 53A is written, in the medium reading and writing device 56, and the medium reading and writing device 56 reading the above program 53A from the recording medium 57. The CPU 51 appropriately reads the gate terminal processing program 53A from the storage unit 53, expands it in the memory 52, and sequentially executes processes contained in the gate terminal processing program 53A.
[0035] Meanwhile, the schedule management server 10 according to this embodiment includes a CPU 11 as a processor, a memory 12 as a temporary storage area, a non-volatile storage unit 13, an input unit 14 such as a keyboard and mouse, a display unit 15 such as a liquid crystal display, a medium reading and writing device 16, and a communication interface (I / F) unit 18. The CPU 11, memory 12, storage unit 13, input unit 14, display unit 15, medium reading and writing device 16, and communication interface (I / F) unit 18 are connected to each other via a bus B3. The medium reading and writing device 16 reads information written in a recording medium 17 and writes information to the recording medium 17.
[0036] The storage unit 13 is realized by an HDD, an SSD, a flash memory, or the like. A schedule management program 13A is stored in the storage unit 13 as a storage medium. The schedule management program 13A is stored (installed) in the storage unit 13 by setting a recording medium 17, on which the program 13A is written, in the medium reading and writing device 16, and the medium reading and writing device 16 reading the program 13A from the recording medium 17. The CPU 11 appropriately reads the schedule management program 13A from the storage unit 13, expands it in the memory 12, and sequentially executes the processes of the schedule management program 13A.
[0037] Furthermore, a schedule management database 13B and a construction site information database 13C are stored in the storage unit 13. The schedule management database 13B and the construction site information database 13C will be described in detail later.
[0038] Next, a functional configuration of the schedule management system 90 according to this embodiment will be described with reference to Fig. 2. Fig. 2 is a block diagram showing an example of the functional configuration of the schedule management system 90 according to this embodiment.
[0039] As shown in FIG. 2, the schedule management server 10 according to the present embodiment includes a calculation unit 11A, a display control unit 11B, and an identification unit 11C. The CPU 11 of the schedule management server 10 executes the schedule management program 13A, thereby functioning as the calculation unit 11A, the display control unit 11B, and the identification unit 11C. The driver terminal 30 according to the present embodiment includes a transmission / reception unit 31A and a display control unit 31B. The CPU 31 of the driver terminal 30 executes the driver terminal processing program 33A, thereby functioning as the transmission / reception unit 31A and the display control unit 31B. The gate administrator terminal 50 according to the present embodiment includes a transmission / reception unit 51A and a display control unit 51B. The CPU 51 of the gate administrator terminal 50 executes the gate terminal processing program 53A, thereby functioning as the transmission / reception unit 51A and the display control unit 51B.
[0040] The transmitting / receiving unit 31A of the driver's terminal 30 according to this embodiment transmits position information of the carrying-in / out vehicle driven by the driver who holds the transmitting / receiving unit 31A to the schedule management server 10. The position information at this time can be obtained by the position detection unit 39.
[0041] On the other hand, the calculation unit 11A of the schedule management server 10 in this embodiment calculates the predicted arrival time of the multiple loading / unloading vehicles at the equipment loading / unloading gate at the construction site based on the location information of the loading / unloading vehicles transmitted from each of the multiple driver terminals 30.
[0042] The display control unit 11B of the schedule management server 10 according to this embodiment controls the display of a list of the predicted arrival times of the multiple loading / unloading vehicles obtained by calculation and the initial scheduled loading / unloading times of the multiple loading / unloading vehicles. Note that in the schedule management system 90 according to this embodiment, the gate manager terminal 50 is used as the device that is the target of control of the list display by the display control unit 11B of the schedule management server 10, but this is not limited to this. For example, the schedule management server 10 itself or the driver's terminal 30 may be used as the device that is the target of the list display.
[0043] The transmitting / receiving unit 51A of the gate administrator terminal 50 according to this embodiment receives information transmitted in association with the control of the above-mentioned list display by the display control unit 11B of the schedule management server 10. Then, the display control unit 51B of the gate administrator terminal 50 controls its own display unit 55 to perform the list display using the information received by the transmitting / receiving unit 51A.
[0044] FIG. 3 is a diagram for explaining an example of a list display of predicted arrival times and original scheduled carry-in times of a plurality of carry-in / out vehicles in the schedule management system 90 according to this embodiment, and the effects thereof.
[0045] As an example, as shown in Fig. 3, in the schedule management system 90 according to this embodiment, for each loading / unloading vehicle (in this embodiment, a vehicle of a contracting company (hereinafter simply referred to as "company")), the original scheduled loading time S, the original loading end time E, and the predicted arrival time P (such as "8:05" in the example shown in Fig. 3) are displayed in chronological order and graphically in a list. Here, the predicted arrival time P is updated successively according to the position information transmitted from the corresponding loading / unloading vehicle.
[0046] For example, as shown in the upper diagram of Figure 3, Company B's original scheduled delivery time S was 8:30 a.m. ("8:30"), and Company C's original scheduled delivery time S was 9:30 a.m. ("9:30")
[0047] However, if the predicted arrival time P of Company B's loading / unloading vehicle is 9:30 ("9:30") and the predicted arrival time P of Company C's loading / unloading vehicle is 9:00 ("9:00") as shown in the upper diagram of Figure 3, the gate manager in charge of the loading / unloading gate will adjust the timing so that Company C's loading / unloading vehicle enters first from 9:00, and Company B's loading / unloading vehicle enters from 9:30, as shown in the lower diagram of Figure 3. Note that the lower diagram of Figure 3 is an image and will not actually be displayed like this.
[0048] In this way, by referring to the list screen shown in the upper part of Figure 3 as an example, the gate manager can smoothly guide vehicles entering and exiting the construction site's loading and unloading gates.
[0049] Meanwhile, the display control unit 11B of the schedule management server 10 controls each of the multiple driver terminals 30 to display a list of scheduled loading times, which are the reservation statuses of the loading / unloading gates of multiple construction sites. Furthermore, in response to instruction information from the driver terminal 30, the display control unit 11B of the schedule management server 10 controls the driver terminal 30 to display a map image including position information of the loading / unloading gates at the construction sites.
[0050] In response to this, the transmitting / receiving unit 31A of the driver's terminal 30 according to this embodiment receives the information transmitted in association with the control of displaying the scheduled delivery time and the map image by the display control unit 11B of the schedule management server 10. Then, the display control unit 31B of the driver's terminal 30 controls its own display unit 35 to display the scheduled delivery time and the map image using the information received by the transmitting / receiving unit 31A.
[0051] In addition, the identification unit 11C of the schedule management server 10 according to this embodiment identifies the current status of each of the multiple vehicles based on the information input by the user and the location information of the vehicles. The display control unit 11B of the schedule management server 10 controls the display of the current status of each of the multiple vehicles when displaying a list of the predicted arrival time and the scheduled loading time of each of the multiple vehicles. In the schedule management system 90 according to this embodiment, the driver's terminal 30 and the gate manager's terminal 50 are used as devices to be displayed by the display control unit 11B of the schedule management server 10, but this is not limited to this. For example, the schedule management server 10 itself may be used as a device to be displayed by the display control unit 11B of the schedule management server 10.
[0052] Therefore, the transmitting / receiving unit 31A of the driver's terminal 30 according to this embodiment receives the information transmitted in association with the control by the display control unit 11B of the schedule management server 10 to display the current status. Then, the display control unit 31B of the driver's terminal 30 controls its own display unit 35 to display the current status using the information received by the transmitting / receiving unit 31A. Also, the transmitting / receiving unit 51A of the gate administrator terminal 50 according to this embodiment receives the information transmitted in association with the control by the display control unit 11B of the schedule management server 10 to display the current status. Then, the display control unit 51B of the gate administrator terminal 50 controls its own display unit 55 to display the current status using the information received by the transmitting / receiving unit 51A.
[0053] In the schedule management system 90 according to the present embodiment, all of the following states are applied as the current state: departure to the construction site, waiting around the construction site, entering the construction site, working at the construction site, and leaving the construction site, but this is not limiting. For example, any one of these states may be applied as the current state, or a combination of multiple states excluding all of these states may be applied as the current state.
[0054] Next, the schedule management database 13B according to this embodiment will be described with reference to Fig. 4. Fig. 4 is a schematic diagram showing an example of the configuration of the schedule management database 13B according to this embodiment.
[0055] As shown in FIG. 4, the schedule management database 13B according to this embodiment stores information on the company, schedule, vehicle ID (identification), construction site, loading / unloading gate, scheduled loading time, loading end time, predicted arrival time, and status.
[0056] The company is information indicating the name of a company that undertakes the transportation of materials and equipment targeted by the schedule management system 90, and the schedule is information indicating the date on which the corresponding company will transport materials and equipment to a construction site. The vehicle ID is information for individually identifying each of the transportation vehicles belonging to the corresponding company, and is information that is assigned in advance as being different for each of the transportation vehicles. The construction site is information indicating the name of a construction site at a corresponding company to which the corresponding transportation vehicle transports materials and equipment, and the transportation gate is information indicating the name of a transportation gate used by the corresponding transportation vehicle when entering the corresponding construction site.
[0057] In addition, the scheduled delivery time, delivery end time, and predicted arrival time are information corresponding to the scheduled delivery time S, delivery end time E, and predicted arrival time P mentioned above, respectively, and the status is information indicating the current status mentioned above.
[0058] In the example shown in Figure 4, a loading / unloading vehicle belonging to Company A and assigned the vehicle ID "A001" is registered to be transporting materials and equipment through the north gate of the construction site of Factory A on February 27, 2023, with the planned delivery time being 10:00 and delivery completion time being 11:00. Also, in the example shown in Figure 4, it is registered that the loading / unloading vehicle is predicted to arrive at the north gate at 10:05, and the current status of the loading / unloading vehicle is "waiting."
[0059] Therefore, the company, schedule, vehicle ID, construction site, loading / unloading gate, scheduled loading time, and end time in the schedule management database 13B are information that is registered in advance, and the predicted arrival time and status are information that is updated sequentially according to the position of the corresponding loading / unloading vehicle.
[0060] In the schedule management system 90 according to the present embodiment, the information on the company, schedule, vehicle ID, construction site, and loading / unloading gate is registered by the person in charge of the corresponding company, and the information on the scheduled loading time and the end time of loading is registered by the driver of the corresponding loading / unloading vehicle, but the present invention is not limited to this. For example, some or all of this information may be registered by the administrator of the schedule management server 10.
[0061] Next, the construction site information database 13C according to this embodiment will be described with reference to Fig. 5. Fig. 5 is a schematic diagram showing an example of the configuration of the construction site information database 13C according to this embodiment.
[0062] As shown in FIG. 5, the construction site information database 13C according to this embodiment stores information on the construction site, the work content, the loading / unloading gate, and the position information.
[0063] The above construction site and the above loading / unloading gate are the same information as the construction site and the loading / unloading gate in the schedule management database 13B. The above construction content is information indicating the content of the construction to be carried out at the corresponding construction site, and the above position information is information indicating the position of the corresponding loading / unloading gate at the corresponding construction site. In this embodiment, the same coordinate system information (information indicating latitude and longitude in this embodiment) as the position information obtained by the position detection unit 39 provided in the driver terminal 30 is applied as the position information, but this is not limited to this. For example, a form may be used in which coordinate values in a predetermined coordinate system with a predetermined point in the area to be managed in the schedule management system 90 (Kanto region in this embodiment) as the origin are applied as the position information indicating the position of the loading / unloading gate.
[0064] In the schedule management system 90 according to this embodiment, a case will be described in which the manager of the schedule management server 10 registers each piece of information in the construction site information database 13C, but it goes without saying that the present invention is not limited to this.
[0065] Next, the operation of the schedule management system 90 according to this embodiment will be described with reference to FIGS.
[0066] First, the operation of the schedule management server 10 when executing the schedule management process according to this embodiment will be described with reference to Fig. 6. Fig. 6 is a flowchart showing an example of the schedule management process according to this embodiment.
[0067] The CPU 11 of the schedule management server 10 executes the schedule management program 13A to execute the schedule management process shown in Fig. 6. The schedule management process shown in Fig. 6 is executed when the start time of a time period (in this embodiment, a time period from 5:00 to 24:00 on weekdays) that is predetermined as the time period during which the schedule management system 90 operates is reached. Note that, in order to avoid confusion, a case will be described here in which the schedule management database 13B and the construction site information database 13C have already been constructed.
[0068] In the schedule management system 90 according to this embodiment, when a loading / unloading vehicle is moving, the driver terminal 30 held by the driver of the loading / unloading vehicle transmits the above-mentioned location information to the schedule management server 10 at regular intervals (every 10 seconds in this embodiment). At this time, the driver terminal 30 transmits information that can identify the driver terminal 30 (vehicle ID in this embodiment) to the schedule management server 10 together with the location information.
[0069] Furthermore, in the schedule management system 90 according to this embodiment, first display instruction information instructing the schedule management server 10 to display the schedule management list screen shown in FIG. 8 as an example is sent from the gate manager terminal 50 to the schedule management server 10, together with information indicating the loading / unloading gate managed by the gate manager who holds the gate manager terminal 50 (hereinafter referred to as "target gate information").
[0070] In addition, in the schedule management system 90 of this embodiment, second display instruction information instructing the schedule management server 10 to display the loading / unloading list screen shown in FIG. 11 as an example is sent from the driver's terminal 30 to the schedule management server 10, together with information indicating the loading / unloading vehicle being driven by the driver holding the driver's terminal 30 (in this embodiment, the vehicle ID).
[0071] Furthermore, in the schedule management system 90 of this embodiment, third display instruction information instructing the display of a transport route display screen as shown in FIG. 13 as an example is transmitted from the driver's terminal 30 to the schedule management server 10, together with position information indicating the position detected by the position detection unit 39 of the driver's terminal 30, and information indicating the loading / unloading gate designated by the driver holding the driver's terminal 30 (hereinafter referred to as "designated gate information").
[0072] Therefore, in step 100 of FIG. 6, the CPU 11 determines whether or not position information has been received from any of the driver terminals 30 at the periodic timing described above. If the determination is affirmative, the process proceeds to step .
[0073] In step 102, the CPU 11 uses the received location information to calculate the predicted arrival time of the transport vehicle that transmitted the location information (hereinafter referred to as the "target vehicle") at the target transport gate as follows: Note that, needless to say, the calculation of the predicted arrival time is only performed until the target vehicle arrives at the target transport gate.
[0074] First, the CPU 11 reads out from the schedule management database 13B information indicating the loading / unloading gate (hereinafter referred to as the "target gate") that corresponds to the vehicle ID received together with the location information and that corresponds to the nearest loading scheduled time after this time.
[0075] Next, the CPU 11 reads out the position information corresponding to the target gate indicated by the read information from the construction site information database 13C. The position indicated by the read position information indicates the position of the target gate (hereinafter referred to as the "gate position").
[0076] Then, the CPU 11 uses the position indicated by the received position information (hereinafter referred to as "vehicle position") and the gate position to derive the time required for the target vehicle to arrive at the target gate, and calculates the predicted arrival time by adding the required time to the current time (postponing the current time by the required time). Note that the above-mentioned required time can be derived by using general-purpose application software such as Google Maps API made by Google, or by creating and using dedicated software that can take into account the situation at that time, such as the degree of congestion on the route from the vehicle position to the gate position and the actual driving speed of the target vehicle.
[0077] In this way, in the schedule management system 90 according to this embodiment, when calculating the predicted arrival time, the position of the target gate (the loading / unloading gate through which the loading / unloading vehicle is scheduled to enter) and the current position of the loading / unloading vehicle are used. The loading / unloading gate through which the loading / unloading vehicle must enter is determined in advance, so it is preferable to use the position of that gate in calculating the predicted arrival time. It is also possible to use the center position of the construction site in calculating the predicted arrival time, but this tends to result in lower accuracy when the construction site is large. For this reason, too, it is preferable to use the position of the target gate in calculating the predicted arrival time.
[0078] In step 104, the CPU 11 identifies the state of the target vehicle at this point in time as follows.
[0079] First, the CPU 11 identifies the vehicle as "departure" when the previous state has not been registered, the vehicle position is outside a construction site having a target gate (hereinafter referred to as the "target site"), and is a predetermined first distance (10 m in this embodiment) or more away from the gate position. The area of the target site can be obtained by reading the position information of all loading / unloading gates corresponding to the target site from the construction site information database 13C, and deriving the area surrounded by the positions indicated by this position information. However, this is not limited to this form, and information indicating the area of each construction site may be registered in advance in the construction site information database 13C, and the area of the target site may be obtained by referring to this information.
[0080] In addition, the CPU 11 identifies the vehicle as "waiting" when the previous state was "departure," the vehicle position is outside the target site, and is closer than a first distance from the gate position, and identifies the vehicle as "entry" when the previous state was "waiting" and the vehicle position is within a predetermined error range of the gate position (within ±1 m in this embodiment).
[0081] Furthermore, the CPU 11 identifies the vehicle as "working" if the previous state was "entering", the vehicle position is inside the target site, and is away from the gate position beyond the above-mentioned error range, and identifies the vehicle as "exiting" if the previous state was "working" and the vehicle position is away from the center position of the target site by a predetermined second distance (500 m in this embodiment).
[0082] The center position of the target site can be obtained by reading the position information of all the loading / unloading gates corresponding to the target site from the construction site information database 13C and deriving the center of gravity of the area surrounded by the positions indicated by this position information. However, this is not limited to this form, and it is also possible to register information indicating the center position of each construction site in advance in the construction site information database 13C and obtain the center position of the target site by referring to this information.
[0083] In this way, in the schedule management system 90 according to this embodiment, the center position of the target site is used to determine whether the target vehicle has left the target site. This is because the loading / unloading gate through which the target vehicle leaves the site is not predetermined, and the entrance gate and the exit gate may be different. Also, whether the target vehicle has left the site does not require high accuracy. For this reason, too, the center position of the target site is used to determine whether the target vehicle has left the site.
[0084] In step 106, the CPU 11 registers (updates) the calculated predicted arrival time and information indicating the state of the identified target vehicle in the corresponding storage area of the schedule management database 13B, and then proceeds to step 120.
[0085] On the other hand, if the determination in step 100 is negative, the process proceeds to step 108. In step 108, the CPU 11 determines whether or not the above-mentioned first display instruction information has been received from any of the gate administrator terminals 50. If the determination is positive, the process proceeds to step 110.
[0086] In step 110, the CPU 11 executes a predetermined schedule management list screen display process as follows.
[0087] First, the CPU 11 reads out all information related to this day and corresponding to the loading / unloading gate indicated by the target gate information received together with the first display instruction information from the schedule management database 13B. The information read out here is hereinafter referred to as the "first schedule management information."
[0088] Next, the CPU 11 uses the read first schedule management information to create information for displaying a schedule management list screen of a predetermined configuration (hereinafter referred to as "schedule management list display information"), transmits the information to the gate manager terminal 50 from which the access originates, and then proceeds to step 120.
[0089] Upon receiving the schedule management list display information, the accessing gate administrator terminal 50 uses the schedule management list display information to display a schedule management list screen, as shown in FIG. 8 as an example, as will be described later.
[0090] On the other hand, if the determination in step 108 is negative, the process proceeds to step 112. In step 112, the CPU 11 determines whether or not the above-mentioned second display instruction information has been received from any of the driver terminals 30. If the determination is positive, the process proceeds to step 114.
[0091] In step 114, the CPU 11 executes a predetermined processing for displaying a list of carry-in and carry-out data as follows.
[0092] First, the CPU 11 reads out all information related to this day and corresponding to the incoming / outgoing vehicles indicated by the vehicle IDs received together with the second display instruction information from the schedule management database 13B. The information read out here is hereinafter referred to as the "second schedule management information."
[0093] Next, the CPU 11 uses the read second scheduled management information to create information for displaying a predetermined configuration of an entry / exit list screen (hereinafter referred to as "entry / exit list display information"), transmits it to the driver's terminal 30 from which the access originated, and then proceeds to step 120.
[0094] When receiving the delivery / unloading list display information, the accessing driver's terminal 30 uses the delivery / unloading list display information to display a delivery / unloading list screen as shown in FIG. 11 as an example, as described below.
[0095] On the other hand, if the determination in step 112 is negative, the process proceeds to step 116. In step 116, the CPU 11 determines whether or not the above-mentioned third display instruction information has been received from any of the driver terminals 30. If the determination is negative, the process proceeds to step 120, whereas if the determination is positive, the process proceeds to step 118.
[0096] In step 118, the CPU 11 executes a predetermined transport path display screen display process as follows.
[0097] First, the CPU 11 creates information (hereinafter referred to as "transport route display information") for displaying a transport route display screen including a map image showing a map from the position of the loading / unloading vehicle indicated by the position information received together with the third display instruction information to the position of the loading / unloading gate indicated by the received designated gate information.
[0098] Next, the CPU 11 transmits the created transportation route display information to the driver's terminal 30 from which the access originates, and then proceeds to step 120.
[0099] The map image can be created using general-purpose application software such as the Google Maps API from Google Inc., as well as by creating and applying dedicated software.
[0100] When receiving the transportation route display information, the accessing driver's terminal 30 uses the transportation route display information to display a transportation route display screen as shown in FIG. 13 as an example, as described later.
[0101] In step 120, the CPU 11 judges whether or not a predetermined end timing has arrived, and if the judgment is negative, the process returns to step 100, whereas when the judgment is positive, the schedule management process ends. Note that in this embodiment, the timing at which the end time of the above-mentioned predetermined time period is reached is applied as the end timing, but it goes without saying that the present invention is not limited to this.
[0102] Next, the operation of the gate administrator terminal 50 when executing the gate terminal process according to this embodiment will be described with reference to Figures 7 to 9. Figure 7 is a flow chart showing an example of the gate terminal process according to this embodiment.
[0103] The gate terminal processing shown in Fig. 7 is performed by the CPU 51 of the gate administrator terminal 50 executing the gate terminal processing program 53A. The gate terminal processing shown in Fig. 7 is performed when an execution instruction is input by any gate administrator (hereinafter referred to as the "target gate administrator") via the input unit 54 of the gate administrator terminal 50 held by that gate administrator. Note that, again, in order to avoid confusion, a case will be described in which the schedule management database 13B and the construction site information database 13C have already been constructed.
[0104] 7, the CPU 51 transmits the above-mentioned first display instruction information together with the above-mentioned target gate information to the schedule management server 10. Upon receiving this first display instruction information, the schedule management server 10 creates and transmits schedule management list display information as described above.
[0105] Therefore, in step 202, the CPU 51 waits until it receives schedule management list display information from the schedule management server 10. In step 204, the CPU 51 controls the display unit 55 to display a schedule management list screen using the received schedule management list display information, and in step 206, the CPU 51 waits until predetermined information is input. An example of the schedule management list screen according to this embodiment is shown in Figure 8.
[0106] As shown in Fig. 8, the schedule management list screen according to this embodiment displays an image displaying a list of the predicted arrival time P, the original scheduled delivery time S, and the original delivery end time E, as explained with reference to Fig. 3. By referring to this image, the gate manager can smoothly guide vehicles entering and leaving the construction site delivery gate, as described above.
[0107] 8, on the schedule management list screen according to this embodiment, status information 55B indicating the status of each loading / unloading vehicle is displayed in the corresponding individual display area 55A. At this time, if the status is "in operation" or later, the loading / unloading vehicle has already arrived at the loading / unloading gate, so the predicted arrival time P is not displayed.
[0108] When the schedule management list screen shown in Figure 8 is displayed on display unit 55, if a loading / unloading vehicle displayed on the schedule management list screen is waiting in front of a loading / unloading gate that the target gate manager manages (hereinafter referred to as the "managed gate"), the target gate manager will ensure that the vehicle passes through the loading / unloading gate appropriately, depending on the status of the loading / unloading vehicle displayed on the schedule management list screen, as described above.
[0109] On the other hand, when the target gate manager wishes to register the status of an incoming or outgoing vehicle that he or she knows, he or she designates the individual display area 55A displayed on the schedule management list screen and corresponding to the incoming or outgoing vehicle via the input unit 54. The above-mentioned cases where the manager wishes to register the status of an incoming or outgoing vehicle that he or she knows means cases where the incoming or outgoing vehicle exists before or after the gate to be managed, or cases where the manager remembers that the vehicle has already passed through the gate to be managed, and the manager is able to reliably understand the status of the incoming or outgoing vehicle. When the target gate manager wishes to end the display of the schedule management list screen, he or she designates the end button 55D via the input unit 54. When the target gate manager designates the individual display area 55A or the end button 55D, the determination in step 206 is affirmative, and the process proceeds to step 208.
[0110] In step 208, the CPU 31 determines whether or not the target gate manager has specified a state registration by determining whether or not any of the individual display areas 55A has been specified by the target gate manager. If the determination is negative, the CPU 51 proceeds to step 212, whereas if the determination is positive, the CPU 51 proceeds to step 210.
[0111] In step 210, the CPU 51 executes a predetermined status registration process as follows.
[0112] First, the CPU 51 controls the display unit 55 to display, as an example, a first state designation screen shown in Fig. 9. Fig. 9 is a front view showing an example of the configuration of the first state designation screen according to the present embodiment.
[0113] 9, the first status designation screen according to this embodiment displays information about the loading / unloading vehicle corresponding to the individual display area 55A designated by the target gate manager. Also, the first status designation screen according to this embodiment displays status selection buttons 55C indicating the statuses that the target gate manager can designate for the displayed loading / unloading vehicle.
[0114] When the first status designation screen shown in FIG. 9 is displayed on the display unit 55, the target gate manager designates, via the input unit 54, the status selection button 55C that corresponds to the displayed status of the loading / unloading vehicle.
[0115] When any of the status selection buttons 55C is designated by the target gate manager, the CPU 51 transmits instruction information to the schedule management server 10 to register the status corresponding to the designated button. Upon receiving the instruction information, the schedule management server 10 stores (updates) the status corresponding to the designated button in the corresponding storage area of the schedule management database 13B.
[0116] In step 212, the CPU 51 judges whether a predetermined end timing has arrived, and if the judgment is negative, the process returns to step 200, whereas if the judgment is positive, the gate terminal process ends. Note that in this embodiment, the above-mentioned end timing is the timing at which the target gate manager inputs an instruction to stop the execution of the gate terminal process, but it goes without saying that the present invention is not limited to this.
[0117] Next, the operation of the driver terminal 30 when executing the driver terminal process according to this embodiment will be described with reference to Figures 10 to 13. Figure 10 is a flowchart showing an example of the driver terminal process according to this embodiment.
[0118] The CPU 31 of the driver terminal 30 executes the driver terminal processing program 33A, thereby executing the driver terminal processing shown in Fig. 10. The driver terminal processing shown in Fig. 10 is executed when an execution instruction is input by any driver (hereinafter referred to as the "target driver") via the input unit 34 of the driver terminal 30 held by that driver. Note that, again, in order to avoid confusion, a case will be described where the schedule management database 13B and the construction site information database 13C have already been constructed.
[0119] 10, the CPU 31 transmits the second display instruction information to the schedule management server 10 together with the vehicle ID indicating the delivery / unloading vehicle driven by the target driver. Upon receiving this second display instruction information, the schedule management server 10 creates and transmits the delivery / unloading list display information as described above.
[0120] Therefore, in step 302, the CPU 51 waits until it receives the carry-in / out list display information from the schedule management server 10. In step 304, the CPU 51 controls the display unit 35 to display the carry-in / out list screen using the received carry-in / out list display information, and in step 306, the CPU 31 waits until predetermined information is input. An example of the carry-in / out list screen according to this embodiment is shown in Figure 11.
[0121] As shown in Fig. 11, the loading / unloading list screen according to this embodiment displays in a table format the names of prime contractors by time period on the day, the construction site (shown as "workshop" in the example shown in Fig. 11), the details of the work, and the names and statuses of the corresponding gates (shown as "status" in the example shown in Fig. 11). Therefore, by referring to the loading / unloading list screen, the driver can easily grasp the schedule for loading and unloading the materials and equipment that he will be carrying out on the day.
[0122] When the carry-in / out list screen shown in Fig. 11 is displayed on the display unit 35, if the target driver wishes to change his / her own status at that time, he / she designates the change button 35A displayed to the right of the corresponding status via the input unit 34. If the target driver wishes to display the transport route to any of the gates displayed on the carry-in / out list screen, he / she designates the display area of the corresponding gate name via the input unit 34. Furthermore, if the target driver wishes to stop displaying the carry-in / out list screen, he / she designates the end button 35B via the input unit 34. If the target driver designates any of the change buttons 35A, any of the gate name display areas, or the end button 35B, step 306 is judged as positive, and the process proceeds to step 308.
[0123] In step 308, the CPU 31 determines whether or not a change in state has been specified by the target driver by determining whether or not any of the change buttons 35A has been specified by the target driver, and if the determination is affirmative, proceeds to step 310.
[0124] In step 310, the CPU 31 executes a predetermined state change process as follows.
[0125] First, the CPU 31 controls the display unit 35 to display, as an example, a second state designation screen shown in Fig. 12. Fig. 12 is a front view showing an example of the configuration of the second state designation screen according to the present embodiment.
[0126] As shown in FIG. 12, the second state designation screen according to this embodiment displays state designation buttons 35C indicating the states that the target driver can designate.
[0127] When the second status designation screen shown in Figure 12 is displayed on the display unit 35, the target driver designates the status designation button 35C corresponding to the current status of the loading / unloading vehicle that he or she is driving, and then designates the registration button 35D.
[0128] When the target driver designates the register button 35D, the CPU 31 transmits instruction information to the schedule management server 10 to register the state corresponding to the designated state designation button 35C. Upon receiving the instruction information, the schedule management server 10 stores (updates) the state corresponding to the designated state designation button 35C in the corresponding storage area of the schedule management database 13B.
[0129] On the other hand, if the determination in step 308 is negative, the process proceeds to step 312. In step 312, CPU 31 determines whether the target driver has specified a display area for any gate name, thereby determining whether the target driver has instructed to display the transport route to the loading / unloading gate indicated by the gate name. If the determination is negative, it is assumed that the target driver has specified the end button 35B, and the process proceeds to step 316, whereas if the determination is positive, the process proceeds to step 314.
[0130] In step 314, the CPU 31 executes a predetermined carry-in route display process as follows.
[0131] First, the CPU 31 transmits the third display instruction information together with the position information indicating the position detected by its own position detection unit 39 and the designated gate information indicating the loading / unloading gate designated by the target driver. Upon receiving this third display instruction information, the schedule management server 10 creates and transmits the transport route display information as described above.
[0132] Therefore, the CPU 31 waits until the transport route display information is received from the schedule management server 10, and then controls the display unit 35 to display a carry-in route display screen using the received transport route display information. An example of the configuration of the carry-in route display screen according to this embodiment is shown in Fig. 13. Note that the example shown in Fig. 13 shows an example of the display state of the carry-in route display screen when the target carry-in / out vehicle is moving to the vicinity of the target carry-in / out gate.
[0133] 13, the carry-in route display screen according to this embodiment displays a map image 35E showing the route from the current position of the carry-in / out vehicle to the specified carry-in / out gate. Therefore, by referring to the carry-in route display screen, the target driver can easily understand the route from his / her own position at this time to the specified carry-in / out gate.
[0134] 13, the carry-in route display screen according to this embodiment displays a marker 35F indicating the location of the carry-in / out gate through which the carry-in / out vehicle will enter. Therefore, by referring to the carry-in route display screen, the target driver can easily ascertain the carry-in / out gate through which he or she will enter.
[0135] In step 316, CPU 31 determines whether a predetermined end timing has arrived, and if the determination is negative, the process returns to step 300, whereas if the determination is positive, the driver terminal processing ends. Note that in this embodiment, the end timing is the timing at which the target driver inputs an instruction to stop the execution of the driver terminal processing, but it goes without saying that the end timing is not limited to this.
[0136] As a result of the above various processes, as an example, as shown diagrammatically in Fig. 14, the gate manager can check the predicted arrival time of loading / unloading vehicles that use the loading / unloading gate that he is in charge of for loading / unloading vehicles in states ranging from "departure" to "entry" by referring to the schedule management list screen. In addition, by referring to the schedule management list screen, the gate manager can also check whether the loading / unloading vehicles under his management are in a state ranging from "waiting" to "exiting", and as a result, he can efficiently adjust the entry and exit of the loading / unloading vehicles.
[0137] On the other hand, the driver of the loading / unloading vehicle can understand his / her own schedule and transportation route by referring to the loading / unloading list screen and the loading route display screen. In addition, the driver of the loading / unloading vehicle does not necessarily need to register his / her own status when in a status such as "exit", which is highly convenient.
[0138] As described above, according to this embodiment, the predicted arrival times of multiple vehicles at the gate for carrying in and out of the construction site are calculated based on the position information of the vehicles transmitted from each of the multiple terminals, and the predicted arrival times of the multiple vehicles and the initial scheduled delivery times of the multiple vehicles are displayed in a list. This makes it possible to smoothly guide the vehicles at the gate for carrying in and out of the construction site.
[0139] Furthermore, according to this embodiment, the schedule management server displays a list of scheduled loading times, which are the reservation statuses of the loading / unloading gates of multiple construction sites, on each of the terminals held by the drivers of multiple loading / unloading vehicles. This allows the drivers of multiple loading / unloading vehicles to understand the reservation statuses of the loading / unloading vehicles they drive.
[0140] According to the present embodiment, in response to instruction information from the terminal, a map image including the position information of the loading / unloading gate at the construction site is displayed on the terminal, so that multiple loading / unloading vehicles can move more smoothly to the loading / unloading gate at the construction site.
[0141] Furthermore, according to this embodiment, the current status of each of the multiple vehicles is identified based on the information input by the user or the location information of the vehicles, and when the predicted arrival time and scheduled delivery time of each of the multiple vehicles are displayed in a list, the current status of each of the multiple vehicles is set to at least one of departing for the construction site, waiting around the construction site, entering the construction site, working at the construction site, and leaving the construction site. Therefore, a person referring to the predicted arrival time and scheduled delivery time can understand the applied status of the multiple vehicles.
[0142] In the above embodiment, the schedule management server 10 controls the display of various images displayed on the driver terminal 30 and the gate administrator terminal 50, but the present invention is not limited to this. For example, the driver terminal 30 and the gate administrator terminal 50 may control the display of various screens that they display themselves. In this case, the process for displaying various images in the schedule management process is not required.
[0143] In the above embodiment, the schedule management process is executed by the schedule management server 10, but the present invention is not limited to this. For example, the schedule management process may be executed by either the driver terminal 30 or the gate manager terminal 50, or the schedule management server 10, the driver terminal 30, and the gate manager terminal 50 may cooperate with each other to share and execute each process in the schedule management process.
[0144] In the above embodiment, the status of the vehicles being carried in and out is registered in each of the schedule management server 10, the driver terminal 30, and the gate manager terminal 50, but this is not limiting. For example, the status of the vehicles being carried in and out may be registered only by the schedule management server 10, or the status of the vehicles being carried in and out may be registered only by the driver terminal 30 and the gate manager terminal 50.
[0145] In the above embodiment, the case where vehicles belonging to different companies are also included as vehicles to be managed has been described, but the present invention is not limited to this. For example, only vehicles belonging to a single company may be managed as vehicles to be managed.
[0146] Although not mentioned in the above embodiment, when it becomes possible for a loading / unloading vehicle to load materials and equipment into any of the loading / unloading gates, this fact may be displayed on the driver terminal 30 held by the driver of the loading / unloading vehicle.
[0147] In this embodiment, when a loading / unloading vehicle is permitted to enter the loading / unloading gate, the schedule management server 10 notifies the driver terminal 30 held by the driver of the loading / unloading vehicle that the vehicle is permitted to enter. In this embodiment, the gate manager who manages the loading / unloading gate may designate that materials and equipment are permitted to enter the loading / unloading gate. In addition, the schedule management server 10 may automatically notify the user when the loading / unloading vehicle enters the construction site through the loading / unloading gate earlier than scheduled. FIG. 15 shows an example of the configuration of the loading / unloading list screen in this embodiment.
[0148] As shown in Fig. 15, on this loading / unloading list screen, a display indicating that entry is possible (in the example shown in Fig. 15, "Entry permitted") is displayed in the status display area of the corresponding loading / unloading gate. Therefore, by referring to this loading / unloading list screen, the driver can know that the loading / unloading vehicle he or she is driving can enter through the corresponding loading / unloading gate.
[0149] In this embodiment, the time when entry is possible may be further displayed. In this embodiment, the schedule management server 10 notifies the driver terminal 30 held by the driver of the loading / unloading vehicle of the entry possible time, which is the time when the loading / unloading vehicle is allowed to enter the loading / unloading gate. An example of the configuration of the loading / unloading list screen in this embodiment is shown in Figure 16.
[0150] 16, on this loading / unloading list screen, the display area for the status of the corresponding loading / unloading gate displays the above-mentioned indication that entry is possible, as well as the time at which entry will be possible. Therefore, by referring to this loading / unloading list screen, the driver can know the time at which the loading / unloading vehicle he or she is driving will be able to enter through the corresponding loading / unloading gate.
[0151] Needless to say, both push notification and pull notification can be used as the notification method.
[0152] In addition, in the above embodiment, a case has been described in which a list is displayed showing the predicted arrival times of multiple loading / unloading vehicles at the loading / unloading gate, and both the original scheduled loading times and unloading times (in the above embodiment, the original loading end time E) of the multiple loading / unloading vehicles, but this is not limited to the above.
[0153] For example, the predicted arrival time and either one of the scheduled carry-in time and the scheduled carry-out time may be displayed in a list. Also, the time required for a plurality of carrying-in / out vehicles to arrive at the carrying-in / out gate, which is derived when calculating the predicted arrival time, and at least one of the scheduled carry-in time and the scheduled carry-out time may be displayed in a list. Furthermore, both the predicted arrival time and the required time, and at least one of the scheduled carry-in time and the scheduled carry-out time may be displayed in a list.
[0154] As an example of a form for displaying the required times in a list, the schedule management list screen shown in FIG. 8 may display the corresponding required times instead of the predicted arrival time P, or may display the corresponding required times alongside the predicted arrival time P.
[0155] In the above embodiment, for example, the following various processors can be used as the hardware structure of the processing units that execute the processes of the calculation unit 11A, the display control unit 11B, the specification unit 11C, the transmission / reception unit 31A, the display control unit 31B, the transmission / reception unit 51A, and the display control unit 51B. As described above, the above various processors include a CPU, which is a general-purpose processor that executes software (programs) and functions as a processing unit, as well as a programmable logic device (PLD), which is a processor whose circuit configuration can be changed after manufacture such as an FPGA (Field-Programmable Gate Array), a dedicated electric circuit, which is a processor having a circuit configuration designed exclusively for executing specific processes such as an ASIC (Application Specific Integrated Circuit), etc.
[0156] The processing unit may be configured with one of these various processors, or may be configured with a combination of two or more processors of the same or different types (for example, a combination of multiple FPGAs, or a combination of a CPU and an FPGA).The processing unit may also be configured with a single processor.
[0157] As an example of configuring the processing unit with one processor, first, there is a form in which one processor is configured with a combination of one or more CPUs and software, as represented by computers such as client and server, and this processor functions as the processing unit. Second, there is a form in which a processor is used that realizes the functions of the entire system including the processing unit with one IC (Integrated Circuit) chip, as represented by System On Chip (SoC), etc. In this way, the processing unit is configured using one or more of the above various processors as a hardware structure.
[0158] Furthermore, more specifically, the hardware structure of these various processors can be an electric circuit that combines circuit elements such as semiconductor elements. [Explanation of symbols]
[0159] 10 Schedule Management Server 11 CPU 11A Calculation section 11B Display control unit 11C Specific part 12. Memory 13 Storage section 13A Schedule Management Program 13B Schedule Management Database 13C Construction site information database 14 Input section 15 Display 16 Media Read / Write Device 17 Recording media 18 Communication I / F section 30 Driver's terminal 31 CPU 31A Transmitter / Receiver 31B Display control unit 32 Memory 33 Storage section 33A Driver terminal processing program 34 Input section 35 Display section 35A Change button 35B Exit button 35C Status button 35D Registration button 35E Map Image 35F Marker 36 Media Read / Write Device 37 Recording media 38 Wireless Communication Division 39 Position detection unit 50 Gate Administrator Terminal 51 CPU 51A Transmitter / Receiver 51B Display control unit 52 Memory 53 Storage section 53A Gate Terminal Processing Program 54 Input section 55 Display section 55A Individual display area 55B Status Information 55C Status selection button 55D Exit button 56 Media Read / Write Device 57 Recording media 58 Wireless Communication Division 80 Network 90 Schedule Management System
Claims
1. A schedule management system including a terminal held by each of drivers of a plurality of loading / unloading vehicles and a schedule management server, Each of the plurality of terminals transmits position information of the carrying-in / out vehicle to the schedule management server, The schedule management server calculates at least one of a predicted arrival time of the plurality of loading / unloading vehicles at a loading / unloading gate for materials and equipment at a construction site and a required time for the plurality of loading / unloading vehicles to arrive at the loading / unloading gate based on the position information of the loading / unloading vehicles transmitted from each of the plurality of terminals, displaying a list of at least one of the predicted arrival times and the required times of the plurality of carrying-in / out vehicles and the initial scheduled carrying-in / out times of the plurality of carrying-in / out vehicles; Schedule management system.
2. The schedule management server displays a list of scheduled loading / unloading times, which are reservation statuses of loading / unloading gates of a plurality of construction sites, on each of the terminals held by each of the drivers of the plurality of loading / unloading vehicles. The schedule management system according to claim 1 .
3. the schedule management server, in response to instruction information from the terminal, causes the terminal to display a map image including position information of the loading / unloading gate at the construction site; The schedule management system according to claim 1 or 2.
4. The schedule management server includes: Identifying a current state of each of the plurality of loading / unloading vehicles based on information input by a user or position information of the loading / unloading vehicles; When displaying the list of the predicted arrival time and the scheduled loading / unloading time of each of the plurality of loading / unloading vehicles, a current status of each of the plurality of loading / unloading vehicles is displayed; The current state of the loading / unloading vehicle is at least one of: departing for the construction site, waiting around the construction site, entering the construction site, working at the construction site, and leaving the construction site. The schedule management system according to claim 1 or 2.
5. When the loading / unloading vehicle is permitted to enter the loading / unloading gate, the schedule management server notifies the terminal held by the driver of the loading / unloading vehicle that the vehicle is permitted to enter the loading / unloading gate. The schedule management system according to claim 1 or 2.
6. The schedule management server notifies the terminal held by the driver of the loading / unloading vehicle of an entry possible time, which is a time when the loading / unloading vehicle is allowed to enter the loading / unloading gate. The schedule management system according to claim 1 or 2.
7. Calculating at least one of a predicted arrival time of the plurality of vehicles at a material / equipment loading / unloading gate at the construction site and a required time for the plurality of vehicles to arrive at the material / equipment loading / unloading gate based on the position information of the vehicles transmitted from each of the plurality of terminals; displaying a list of at least one of the predicted arrival times and the required times of the plurality of carrying-in / out vehicles and the initial scheduled carrying-in / out times of the plurality of carrying-in / out vehicles; A program that causes a computer to carry out processing.
Citation Information
Patent Citations
Method and device for linking up with operation schedule by portable information terminal
JP1998063728A
Carriage system, carrying method and carrying device
JP2002324295A
Schedule management system
JP2005011196A
Schedule management device and schedule management program
JP2010257358A
Cited By
Substrate processing apparatus and substrate processing method
CN121680003A
