JP2006276961A - Vehicle dispatch management device - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a vehicle dispatch management device capable of reducing labor for carrying out vehicle dispatch conforming to requests regarding vehicles and crew. <P>SOLUTION: A crew database storing part 31 stores a crew database including crew identification data and crew attribute data. An operation control table storing part 37 stores an operation control table recording the crew identification data of the crew on each vehicle, along with vehicle identification data and vehicle attribute data. When a crew identification code is received from an on-vehicle terminal, the crew identification data is registered in the operation control table in association with the vehicle. When dispatch request data including a vehicle attribute and a crew attribute is inputted, the operation control table and the crew database are referred to retrieve a conforming vehicle corresponding to the dispatch request data. An allocation instruction is sent to an on-vehicle terminal mounted on the retrieved conforming vehicle. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a vehicle allocation management device that manages the allocation of taxis, and more particularly, to a vehicle allocation management device that can appropriately respond to customer requests.

Traditionally, taxi dispatch has been done exclusively by hand using radio devices. On the other hand, in recent years, a technique called an AVM (Automatic Vehicle Monitor) dispatch system has been put into practical use. In the GPS-AVM dispatch system, the in-vehicle terminal (mobile station) detects the current position using GPS, and transmits the detected current position to the dispatch management device. The vehicle allocation management device can display the position of each vehicle on a map. Further, the vehicle allocation management device can automatically detect a vehicle close to a customer who desires vehicle allocation. An AVM vehicle allocation system is disclosed in, for example, Patent Document 1.
JP 2002-150491 A (Page 6-9, FIG. 1)

  However, in the conventional vehicle allocation management device, it is necessary to rely on the manual operation of the operator in order to meet the customer's request for the type of vehicle and the attributes of the crew, and there is a problem that this operation is complicated.

  To further explain the above problem, there are taxi vehicles such as wagons, and the customer may specify the type of vehicle. The customer may also specify attributes such as a qualified caregiver for a crew member. On the other hand, a single taxi vehicle may be used alternately by a plurality of crew members. In addition, one crew member may change a plurality of vehicles. For this reason, conventionally, which crew member is in which vehicle is manually managed by using a boarding schedule. Then, the operator is looking for a vehicle that is in line with the customer's request and on which the crew member desired by the customer is on board while manually viewing the boarding schedule. Alternatively, an appropriate vehicle has been found by issuing an inquiry to all the vehicles by voice communication. Thus, conventionally, since a vehicle that meets the customer's request has been searched manually, the vehicle allocation management work is complicated, which is disadvantageous in terms of quick service.

  The present invention has been made to solve the conventional problems, and an object of the present invention is to provide a vehicle allocation management device capable of reducing labor for vehicle allocation in accordance with requests for vehicles and crew members.

  A vehicle allocation management device according to the present invention includes a communication unit that communicates with an in-vehicle terminal mounted on each of a plurality of vehicles, a crew member database storage unit that stores a crew member database including crew member identification data and crew member attribute data for each crew member, and a vehicle. A vehicle management data storage unit that records vehicle management data and vehicle attribute data for each vehicle, and that stores a vehicle management table that records crew member identification data of crew members on each vehicle, and the communication unit from the in-vehicle terminal. Crew identification data receiving means for receiving the crew identification data received, and the crew identification data received by the crew identification data receiving means, related to the vehicle identification data corresponding to the in-vehicle terminal that has sent the crew identification data Table registration means for registering in the operation management table, A vehicle allocation request input means for inputting vehicle allocation request data including the vehicle attribute and the crew attribute, and the operation management table and the crew database, with reference to the vehicle attribute of the vehicle allocation request data and the compatible vehicle corresponding to the crew attribute. A suitable vehicle search means for searching from a management table, and a vehicle allocation instruction transmission processing means for transmitting a vehicle allocation instruction to the in-vehicle terminal mounted on the compatible vehicle searched by the compatible vehicle search means via the communication unit.

  With this configuration, a crew member database and an operation management table are provided, crew attributes are registered in the crew database, vehicle attributes are registered in the operation management table, and vehicles and crew members are linked on the operation management table. Then, when the vehicle allocation request data is input, the operation management table and the crew database are referred to search for the vehicle attribute of the vehicle allocation request data and the compatible vehicle corresponding to the crew attribute, and a vehicle allocation instruction is issued to the searched compatible vehicle. Since it is transmitted, it is possible to reduce the time and labor for dispatching in line with the customer's request.

  Further, in the vehicle allocation management device of the present invention, the suitable vehicle search means corresponds to a vehicle attribute and a crew attribute based on vehicle position data received from an in-vehicle terminal of each vehicle and a customer position included in the vehicle allocation request data. Among the conforming vehicles to be used, the vehicle closest to the customer position is obtained. With this configuration, when there are a plurality of vehicles that meet the requirements of the vehicle attribute and the crew attribute, the optimal vehicle can be selected from the viewpoint of distance.

  Another aspect of the present invention is a vehicle allocation system including an in-vehicle terminal mounted on each of a plurality of vehicles and a allocation management device having a communication unit that communicates with the plurality of in-vehicle terminals. In this vehicle allocation system, the vehicle allocation management device stores a communication unit that communicates with a vehicle-mounted terminal mounted on each of a plurality of vehicles, and a crew member database storage that stores a crew member database including crew member identification data and crew member attribute data for each crew member An operation management table storage means for storing an operation management table that records vehicle identification data and vehicle attribute data for each vehicle, and records crew identification data of crew members on each vehicle, and the communication unit A vehicle corresponding to the in-vehicle terminal that has sent the crew member identification data to the crew member identification data receiving unit that receives the crew member identification data received from the in-vehicle terminal, and the crew member identification data received by the crew member identification data receiving unit. The text to be registered in the operation management table so as to be associated with the identification data. Refer to the vehicle registration and the crew attribute of the vehicle allocation request data with reference to the vehicle registration request, the vehicle allocation request input means for inputting the vehicle allocation request data including the vehicle attribute and the crew attribute, the operation management table and the crew database. Applicable vehicle search means for searching for a corresponding compatible vehicle from the operation management table, and vehicle allocation instruction transmission processing means for transmitting a vehicle allocation instruction to the in-vehicle terminal mounted on the compatible vehicle searched by the compatible vehicle search means via the communication unit And. This configuration also provides the above-described advantages of the present invention.

  The present invention registers crew attributes in the crew database, registers vehicle attributes in the operation management table, links vehicles and crew members on the operation management table, and requests dispatch by referring to these operation management table and crew database. By searching for a suitable vehicle corresponding to the vehicle attribute and the crew attribute of the data, it is possible to provide a vehicle allocation management device having an effect that it is possible to reduce labor for vehicle allocation according to a customer's request.

  Hereinafter, a vehicle allocation management apparatus according to an embodiment of the present invention will be described with reference to the drawings. In the present embodiment, the present invention is applied to an AVM taxi dispatch system. The AVM management device of the AVM taxi dispatch system corresponds to the dispatch management device of the present invention.

  FIG. 1 shows an AVM taxi dispatch system 1 according to an embodiment of the present invention. In FIG. 1, an AVM taxi dispatch system 1 includes an AVM management device 3 and an AVM mobile station device 5. The AVM management device 3 is installed in a taxi company. The AVM mobile station device 5 is an in-vehicle terminal mounted on each vehicle and communicates with the AVM management device 3. The AVM management device 3 includes a vehicle allocation terminal 7, a telephone reception terminal 9, and a customer database device 11.

  The dispatch terminal 7 is a computer including input / output devices such as a keyboard, a display, a microphone, and a speaker, and is operated by an operator. In the dispatch terminal 7, the control unit 21 controls the entire dispatch terminal 7. The screen processing unit 23 performs processing for displaying a map, a vehicle position mark, and the like on the display. The screen processing unit 23 also displays a screen for searching for dispatch. The transmission / reception device 25 is a communication unit of the present invention, and performs wireless communication with the AVM mobile station device 5. The communication processing unit 27 communicates data with the telephone reception terminal 9.

  Further, the crew member code processing unit 29 performs processing such as update and search on the crew member database stored in the crew member database storage unit 31. In addition, the dispatch processing unit 33 performs processing related to dispatch. For example, the vehicle allocation processing unit 33 performs a process of displaying the vehicle position received from the AVM mobile station device 5 on a map stored in the map database storage unit 35. Further, in the present embodiment, the vehicle allocation processing unit 33 performs processing such as reading and writing and searching for the operation management table stored in the operation management table storage unit 37, and performs the vehicle allocation process using the operation management table. Configured to do.

  Next, the telephone reception terminal 9 is a computer provided with input / output devices such as a keyboard, a display, a microphone, and a speaker, as with the vehicle allocation terminal 7. The telephone reception terminal 9 may be operated by a separate operator from the dispatch terminal 7 or may be operated by the same operator as the dispatch terminal 7. It is also possible to integrate the telephone reception terminal 9 and the dispatch terminal 7.

  In the telephone reception terminal 9, the control unit 41 controls the entire telephone reception terminal 9, and the screen processing unit 43 performs processing for displaying a vehicle allocation request (request) input screen and a customer information screen on the display. . The telephone reception processing device 45 has a telephone function, is connected to a customer's telephone, and is used for receiving a request for dispatch. The communication processing unit 47 communicates data with the communication processing unit 27 of the dispatch terminal 7. Further, the customer database processing unit 49 performs processing for searching customer data in the customer database 51 of the customer database device 11.

  In the customer database device 11, the customer database 51 stores data such as the name, address, telephone number, and usage history of the customer who has received a request in the past. The customer database processing device 53 performs processing such as updating of the customer database 51.

  Next, the AVM mobile station apparatus 5 will be described. The AVM mobile station device 5 is a computer device mounted on a vehicle and includes input / output devices such as a switch, a display, a microphone, and a speaker, and is operated by a crew member.

  In the AVM mobile station apparatus 5, the control unit 61 controls the entire AVM mobile station apparatus 5, and the screen processing unit 63 displays necessary information on the display (for example, a customer address for pick-up after dispatch). Perform the process. In addition, the transmission / reception device 65 performs wireless communication with the transmission / reception device 25 of the vehicle allocation terminal 7. The position detection unit 67 is composed of a GPS device and detects the current position of the vehicle. Of course, the position detection unit 67 may have a configuration using both GPS and autonomous navigation. The position detection unit 67 supplies the current position sequentially detected to the control unit 61, and the control unit 61 periodically transmits the current position data to the vehicle allocation terminal 7 via the transmission / reception device 65.

  The crew member code input / output unit 69 is realized by the input / output device described above, and inputs the crew member code and displays the entered crew member code. The crew member code transmission processing unit 71 performs processing for causing the transmission / reception device 65 to transmit the input crew member code to the dispatch terminal 7.

  In the above configuration, in the present embodiment, in particular, the crew terminal database storage unit 31 and the operation management table storage unit 37 are provided in the vehicle allocation terminal 7, and suitable vehicle allocation is performed by information processing using these.

  FIG. 2 shows the crew database. The crew database is a table of crew names, crew codes, and crew attributes of each crew. The crew name and crew code correspond to crew identification data of the present invention. The crew attributes have the gender and qualification of the crew. The qualification is, for example, a qualification related to care. However, the crew attributes are not limited to these, and may include other information.

  FIG. 3 shows an operation management table. The operation management table is a table of the vehicle number, vehicle attribute, vehicle allocation target setting, and vehicle state of each vehicle. The vehicle number corresponds to the vehicle identification data of the present invention. The vehicle attribute is the type of vehicle, such as large, small, or wagon. The vehicle allocation target setting is information indicating whether or not the vehicle allocation target is set. When the vehicle allocation target is set in the process described later, the vehicle allocation target setting column is changed from non-target to target. Further, the vehicle state is a state of a vehicle such as an empty vehicle, a real vehicle, an incoming vehicle, and forwarding, and vehicle state data received from the AVM mobile station device 5 is written. Note that the operation management table may be divided into a plurality of parts and may be associated with each other (the same applies to other tables).

  As shown in FIG. 3, in the operation management table, a crew member code and a crew name of a crew member riding in each vehicle are further registered. The crew member code and the crew member name are received from the AVM mobile station apparatus 5 and written in the operation management table in the process described later.

  FIG. 4 shows the customer database 51. As illustrated, the customer database 51 stores data such as the name, address, telephone number, and usage history of a customer who has received a request in the past.

  Next, the operation of the AVM taxi dispatch system 1 according to the present embodiment will be described. 5 and 6 are flowcharts showing operations of the AVM mobile station device 5 and the dispatch terminal 7 when the vehicle starts operation.

  In FIG. 5, in the AVM mobile station apparatus 5, when the engine is started (S1), the crew member code is input from the crew member input / output unit 69 and received by the control unit 61 (S3). The control unit 61 determines whether or not the inputted crew member code is a dummy code (S5). If the crew member code is a predetermined dummy code (for example, a number such as 999), the opening process is performed in the non-allocation target mode. (S7). As a result, the sink business is carried out without being set as a vehicle allocation target at the vehicle allocation terminal 7.

  If the inputted crew member code is not a dummy code, the control unit 61 causes the transmission / reception device 65 to transmit the crew member code to the dispatch terminal 7 (S9). The crew member code is transmitted to the dispatch terminal 7 together with the vehicle number that is the vehicle identification data. Then, it is determined whether or not the wireless transmission of the crew member code is successful (S11). If the wireless transmission is not successful, a station opening process is performed as a vehicle not to be dispatched (S13), and the transmission of the crew member code is continued by returning to step S9. . Until the crew member code is successfully transmitted, the crew member code is continued to be transmitted and the sink business is carried out. When the crew member code is successfully transmitted, the opening process as a vehicle allocation target is performed (S15). The station opening process is a process of starting a predetermined operation as a mobile station such as causing the AVM mobile station device 5 to function as a mobile station and raising the current position to the dispatching terminal 7 at an appropriate interval.

  As shown in FIG. 6, in the dispatch terminal 7, the transmission / reception device 25 receives the crew member code and supplies it to the control unit 21 (S31). Then, the vehicle allocation processing unit 33 changes the vehicle allocation target setting of the corresponding vehicle in the operation management table from the non-target to the target, thereby setting the vehicle as a vehicle allocation target (a candidate for a vehicle to be allocated) (S33). Furthermore, the crew member code processing unit 29 searches for a crew member name corresponding to the crew member code from the crew member database in the crew member database storage unit 31 (S35). If there is a corresponding crew member name (S37, Yes), the crew member code and the crew member name are associated with the vehicle number (S39). Here, the dispatch processing unit 33 writes the received crew member code and the searched crew member name in the corresponding vehicle column of the operation management table. Then, the control unit 21 causes the communication processing unit 27 to transmit the searched crew name to the AVM mobile station device 5 (S41). When the crew name corresponding to the crew code does not exist in the crew database (No in S37), the control unit 21 causes the communication processing unit 27 to transmit an error message (S43).

  In the above-described processing of the dispatch terminal 7, the control unit 21, the crew member code processing unit 29, and the dispatch unit 33 receive the crew member identification data and register it in the operation management table so as to be associated with the corresponding vehicle. Functions as a crew member identification data receiving means and a table registration means.

  Returning to FIG. 5, the AVM mobile station apparatus 5 receives and displays a crew member name or an error message from the dispatch terminal 7 (S17), and the control unit 61 determines whether or not a confirmation operation is performed (S19). The crew name is displayed, and if the crew name is correct, the crew member confirms the input device. When the confirmation operation is received, the control unit 61 causes the transmission / reception device 65 to transmit a confirmation signal to the vehicle allocation terminal 7 (S21). In this way, in the present embodiment, the validity of the entered crew member code can be confirmed by the system.

  It is assumed that the crew member has entered an incorrect crew member code in step S3. In this case, the wrong crew member code is sent from the AVM mobile station apparatus 5 to the dispatching terminal 7, and the dispatching terminal 7 searches the crew member database for the crew member name using the wrong crew member code. In this case, the wrong crew member name is retrieved and returned to the AVM mobile station apparatus 5. Alternatively, an error message is returned because the corresponding crew member name does not exist in the database. In this case, the confirmation operation is not accepted (S19, No), the crew member code is re-input (S23), the crew member code is re-transmitted (S25), and it is determined again whether the signal transmission is successful (S27). ). If the signal transmission is successful, the process proceeds to step S17 and subsequent steps. In addition, when the crew terminal code is received, the dispatching terminal 7 side performs the process shown in FIG. 6 once again.

  The operation at the time of opening the station has been described above. Next, the operation at the time of dispatch will be described. FIGS. 7 and 8 show the operations of the vehicle allocation terminal 7 and the AVM mobile station device 5 at the time of vehicle allocation, respectively.

  At the time of dispatch, the telephone reception terminal 9 accepts a request for dispatch (a request for dispatch) from the customer before the processing of FIG. In the telephone reception terminal 9, the telephone reception processing device 45 receives a telephone call from a customer. The operator and the customer have a conversation, and the operator inputs a dispatch request to the telephone reception terminal 9. In the case of a new customer, the operator inputs a customer name, a telephone number, a customer location (address), and a request (request) from the customer. Customer requests are vehicle attributes and crew attributes. The vehicle attribute is a type of vehicle such as a wagon car. The crew attributes are gender and qualification. The vehicle allocation request is input to a predetermined input screen and accepted by the control unit 41, and the control unit 41 causes the communication processing unit 47 to transmit the vehicle allocation request data to the vehicle allocation terminal 7.

  If the customer is not new, customer information registered in the customer database 51 is used. For example, the operator searches for customer information by inputting a telephone number heard from a customer. Customer information such as name, telephone number, and address is displayed on the screen. This customer information may be added to the dispatch request data.

  As described above, the vehicle allocation request data is transmitted from the telephone reception terminal 9 to the vehicle allocation terminal 7, received by the communication processing unit 27 of the vehicle allocation terminal 7, and supplied to the control unit 21. At this time, the communication processing unit 27 functions as a dispatch request input unit that inputs dispatch request data. When the vehicle allocation request data is input, the process of FIG. 7 starts.

  In FIG. 7, the control unit 21 receives the vehicle allocation request data and passes it to the vehicle allocation processing unit 33 (S51). The vehicle allocation processing unit 33 generates a vehicle allocation call signal and performs a process of transmitting the generated vehicle allocation call signal to all the vehicles (S53). The vehicle allocation call signal includes the customer position (address) in the vehicle allocation request. The vehicle allocation call signal is transmitted from the transmission / reception device 27 of the vehicle allocation terminal 7 to each AVM mobile station device 5 by wireless communication.

  Then, as shown in FIG. 8, in each AVM mobile station device 5, the transmitting / receiving device 65 receives the dispatch call signal and supplies it to the control unit 61 (S81). Does the control unit 61 transmit a response signal? It is determined whether or not (S83). In this step, the control unit 61 acquires the customer position included in the dispatch call signal, and compares the customer position with the current position detected by the current position detection unit 67. And the control part 61 calculates the distance of a customer position and a present position, and determines whether this distance is below a predetermined threshold value. It is preferable to calculate the distance by a navigation technique using an in-vehicle map database. If the distance between the customer position and the current position is less than or equal to the threshold value, the determination in step S83 is Yes. The threshold value is a distance of 500 m, for example. In addition, the control unit 61 calculates an arrival time (also referred to as travel time or travel time) from the current position to the customer position by using navigation technology using an in-vehicle map database, and compares it with a predetermined threshold value (time). May be. In this case, if the arrival time is less than or equal to the threshold value, the determination in step S83 is Yes. If determination of step S83 is No, the control part 61 will perform the process which ignores a dispatch call signal, and will not respond to the dispatch terminal 7 (S91). If determination of step S83 is Yes, the control part 61 will make the transmission / reception apparatus 65 transmit a response signal to the allocation terminal 7 (S85). At this time, the control unit 61 generates and transmits a response signal including the latest current position data detected by the position detection unit 67. The response signal includes the vehicle number of the corresponding vehicle.

  As described above, when the AVM management device 3 receives a vehicle allocation request, it first transmits a vehicle allocation call signal and receives a response signal including the current position from a vehicle relatively close to the customer. Note that the AVM management device 3 receives the current position from each vehicle at an appropriate interval even if no dispatch request is input. However, the current position is acquired every time the vehicle travels a predetermined distance or every predetermined time, and is not the latest position information. On the other hand, when the vehicle allocation call signal is received, the AVM mobile station device 5 transmits the latest current position to the AVM vehicle allocation management device 3, so that the AVM vehicle allocation management device 3 indicates the latest vehicle position of each vehicle. Use it to handle dispatch.

  As shown in FIG. 7, in the AVM allocation management device 3, the transmission / reception device 27 receives a response signal including the current position and supplies the response signal to the allocation processing unit 33 (S55). Further, the vehicle allocation processing unit 33 analyzes the vehicle allocation request data to determine whether or not there is a vehicle condition (whether or not the vehicle attribute is included in the vehicle allocation request data) (S57). The vehicle condition (vehicle attribute) is set as a search key (S59). Further, the vehicle allocation processing unit 33 determines whether or not there is a crew member condition in the vehicle dispatch request data (whether or not the crew member attribute is included in the vehicle dispatch request data) (S61). If there is a crew member condition, the crew member condition is determined. (Crew attribute) is set as a search key (S63).

  Then, the vehicle allocation processing unit 33 functions together with the crew member code processing unit 29 to search for a suitable vehicle corresponding to the vehicle attribute and the crew member attribute of the set search condition (S65). A suitable vehicle is searched from vehicles set as a dispatch target (candidate) (set in step S33 in FIG. 6). Further, the suitable vehicle is selected from the vehicles for which the response signal has been received in step S53, and the vehicle closest to the customer position is selected as will be described later.

  The processing in step S65 will be described in detail. The vehicle allocation processing unit 33 searches the operation management table in the operation management table storage unit 37 for a compatible vehicle. At this time, the crew member database in the crew member database storage unit 31 is used. Then, the vehicle allocation processing unit 33 determines that “(1) a vehicle corresponding to the vehicle attribute of the vehicle allocation request on the operation management table and (2) a crew member corresponding to the crew attribute of the vehicle allocation request on the crew database. The vehicle “associated with the identification data and the operation management table” is searched.

  For example, it is assumed that the vehicle attribute of the dispatch request is “Large”, and the crew attribute is “Care for two types of caregiver”. The vehicle allocation processing unit 33 extracts the vehicle number of the large-sized vehicle from the operation management table, and further obtains a crew member code associated with the extracted vehicle number in the operation management table. Then, the crew member code processing unit 29 searches the crew member database for the crew member code that corresponds to the “2nd class qualified person” among the extracted crew member codes. The vehicle number associated with the searched crew member code in the operation management table is obtained as a compatible vehicle.

  The allocation processing unit 33 selects a vehicle that is equipped with the AVM mobile station device 5 that has sent the response signal in step S53 among the compatible vehicles searched as described above, and that is closest to the customer position. Ask.

  Here, the vehicle allocation processing unit 33 refers to the vehicle number and the current position in the response signal received from each AVM mobile station device 5. Then, the vehicle allocation processing unit 33 extracts the vehicle number included in the response signal from the vehicle numbers of the compatible vehicles. Furthermore, the dispatch processing unit 33 calculates the distance between the current position of each vehicle and the customer position. The customer position is included in the dispatch request data. And the dispatch processing part 33 calculates | requires the vehicle with the shortest distance. Instead of the distance, time (arrival time from the current position to the customer position) is calculated, and the vehicle with the shortest time may be obtained. The distance or time is calculated using the map database in the map database storage unit 35. Distance or time may be calculated using navigation techniques.

  As described above, in the present embodiment, a compatible vehicle is obtained in step S65. At this time, the vehicle allocation processing unit 33 and the crew member code processing unit 29 function as a suitable vehicle search means, and refer to the operation management table and the crew database to find a suitable vehicle corresponding to the vehicle attribute and the crew attribute of the vehicle allocation request data. Searching and seeking the closest vehicle to the customer among the compatible vehicles.

  And the dispatch processing part 33 produces | generates a dispatch message, and transmits a dispatch message to the suitable vehicle nearest to the customer calculated | required by step S63 (S67). At this time, the vehicle allocation processing unit 33 functions as a vehicle allocation instruction transmission processing means. The dispatch message corresponds to the dispatch instruction of the present invention, and is data including the customer's name, telephone number, and location. The dispatch message is transmitted from the transmitting / receiving device 25 to the transmitting / receiving device 65 of the AVM mobile station device 5. Therefore, among the vehicles that sent the response signal in the previous stage, the vehicle that received the dispatch message has been dispatched. In the AVM mobile station apparatus 5, as shown in FIG. 8, it is determined whether or not a dispatch message is received (S87). When the dispatch message is received (S87, Yes), the dispatch message is displayed. (S89).

  In the above processing, the customer may specify one of the vehicle attribute and the crew attribute. In this case, one attribute is included in the vehicle allocation request data, which is set as a search condition in one of steps S59 and 63, and the search is performed based on this search condition. In addition, the customer may not specify the vehicle attribute or the crew attribute. In this case, in step S65 of FIG. 7, a suitable vehicle may be searched based only on the distance (or time).

  The AVM taxi dispatch system 1 and the dispatch management apparatus according to the embodiment of the present invention have been described above. According to the present embodiment, the crew database and the operation management table as described above are provided, the crew attributes are registered in the crew database, the vehicle attributes are registered in the operation management table, and the vehicle and the crew are registered on the operation management table. It is tied. Then, when the vehicle allocation request data is input, the operation management table and the crew database are referred to search for the vehicle attribute of the vehicle allocation request data and the compatible vehicle corresponding to the crew attribute, and a vehicle allocation instruction is issued to the searched compatible vehicle. Sent. Therefore, it is possible to reduce the time and labor for vehicle allocation in accordance with the customer's request for the vehicle attribute and the crew attribute.

  In addition, this embodiment is based on the vehicle position data received from the in-vehicle terminal of each vehicle and the customer position included in the dispatch request data. It is configured to obtain the closest vehicle, and therefore, when there are a plurality of vehicles that meet the requirements of the vehicle attribute and the crew attribute, the optimal vehicle can be selected from the viewpoint of distance.

  The preferred embodiments of the present invention have been described above. However, the present invention is not limited to the above-described embodiments, and it goes without saying that those skilled in the art can modify the above-described embodiments within the scope of the present invention.

  As described above, the vehicle allocation management device according to the present invention has an effect of reducing labor for vehicle allocation in accordance with the demands for vehicles and crews, and is useful as a taxi vehicle allocation system.

The block diagram of the AVM taxi dispatch system in embodiment of this invention Diagram showing the crew database Diagram showing the operation management table Diagram showing customer database Flow chart showing the operation of the AVM mobile station apparatus when the station is opened Flow chart showing the operation of the dispatch terminal when the station is opened Flow chart showing operation of dispatch terminal during dispatch Flowchart showing the operation of the AVM mobile station apparatus during dispatch

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 AVM taxi allocation system 3 AVM management apparatus 5 AVM mobile station apparatus 7 Distribution terminal 9 Telephone reception terminal 11 Customer database apparatus 21 Control part 23 Screen processing part 25 Transmission / reception apparatus 27 Communication processing part 29 Crew member code processing part 31 Crew member database storage part 33 Dispatch processing unit 35 Map database storage unit 37 Operation management table storage unit

Claims (3)

A communication unit that communicates with an in-vehicle terminal mounted on each of a plurality of vehicles;
A crew member database storage unit storing a crew member database including crew member identification data and crew member attribute data for each crew member;
An operation management table storage unit that stores an operation management table that records vehicle identification data and vehicle attribute data for each vehicle, and records crew identification data of crew members on each vehicle,
Crew identification data receiving means for receiving crew identification data received from the in-vehicle terminal by the communication unit;
Table registration means for registering the crew identification data received by the crew identification data receiving means in the operation management table so as to be associated with the vehicle identification data corresponding to the in-vehicle terminal that has sent the crew identification data;
Vehicle allocation request input means for inputting vehicle allocation request data including vehicle attributes and crew attributes;
With reference to the operation management table and the crew database, compatible vehicle search means for searching for a compatible vehicle corresponding to the vehicle attribute and the crew attribute of the dispatch request data from the operation management table;
A vehicle allocation instruction transmission processing unit that transmits a vehicle allocation instruction to the in-vehicle terminal mounted on the compatible vehicle searched by the compatible vehicle search unit via the communication unit;
A vehicle allocation management device characterized by comprising:   The conforming vehicle search means is configured to determine the customer position among the conforming vehicles corresponding to the vehicle attribute and the crew attribute based on the vehicle position data received from the in-vehicle terminal of each vehicle and the customer position included in the dispatch request data. The vehicle allocation management device according to claim 1, wherein the nearest vehicle is obtained. An in-vehicle terminal mounted on each of the plurality of vehicles, and a vehicle allocation management device having a communication unit that communicates with the plurality of in-vehicle terminals,
The vehicle allocation management device
A communication unit that communicates with an in-vehicle terminal mounted on each of a plurality of vehicles;
A crew member database storage unit storing a crew member database including crew member identification data and crew member attribute data for each crew member;
An operation management table storage unit that stores an operation management table that records vehicle identification data and vehicle attribute data for each vehicle, and records crew identification data of crew members on each vehicle,
Crew identification data receiving means for receiving crew identification data received from the in-vehicle terminal by the communication unit;
Table registration means for registering the crew identification data received by the crew identification data receiving means in the operation management table so as to be associated with the vehicle identification data corresponding to the in-vehicle terminal that has sent the crew identification data;
Vehicle allocation request input means for inputting vehicle allocation request data including vehicle attributes and crew attributes;
With reference to the operation management table and the crew database, compatible vehicle search means for searching for a compatible vehicle corresponding to the vehicle attribute and the crew attribute of the dispatch request data from the operation management table;
A vehicle allocation instruction transmission processing unit that transmits a vehicle allocation instruction to the in-vehicle terminal mounted on the compatible vehicle searched by the compatible vehicle search unit via the communication unit;
A vehicle allocation system characterized by comprising: