JP7628661B2 - Program and matching support system - Google Patents

Description

The present invention relates to a program and a matching support system.

Patent Document 1 discloses a program that enables two-way information exchange between a mobile food and beverage vendor that uses a vehicle to sell food and beverages, and a non-mobile food and beverage vendor at a store (a non-mobile store), regarding the sales of food and beverages that each vendor handles. This program enables a food and beverage vendor at a store to request the mobile food and beverage vendor to sell food and beverages on their behalf.

Patent No. 7104384

In the program of Patent Document 1, the user who uses the program must be a store-based food and beverage retailer or a mobile salesperson. Furthermore, the program of Patent Document 1 is premised on the fact that the food and beverages handled by the food and beverage retailer are sold by the mobile salesperson's staff using a vehicle owned by the mobile salesperson. In other words, Patent Document 1 is premised on the existence of a mobile salesperson that has the resources to operate a mobile sales business (for example, a kitchen car business).

However, there are cases where the owner of a vehicle (e.g., a food truck) is unable to cook the food themselves, or the schedule does not match the day the sale takes place (when there are no staff available, i.e., there is no labor). There are also cases where the owner is able to act as staff to cook and drive the vehicle (having the labor), but does not own the vehicle or restaurant. There are also people who wish to develop a mobile food sales business but do not have the resources of a vehicle, staff, or restaurant, and event organizers who wish to invite a food truck to an event but do not have any of the above resources.

In other words, there are people who wish to operate a mobile sales business but are unable to do so because they do not have some or all of the resources required to operate a mobile sales business. As such, there is a demand for a program and matching support system that supports matching between people who wish to plan a mobile sales business (hereinafter referred to as "planners") and resource owners who possess at least one of the resources necessary for a mobile food and beverage sales business.

This disclosure has been made to solve the above-mentioned problems, and aims to provide a program and matching support system for supporting matching between planners and resource owners who own at least one of the resources required for a mobile food and beverage sales business.

In order to achieve the above object, the program according to the first aspect of the present disclosure, which will be disclosed below, is a program for causing a processor of a system capable of communicating with a planner terminal used by a planner who plans a mobile food and beverage sales business, and a resource owner terminal used by a resource owner who owns at least one of the resources necessary for the mobile food and beverage sales business to execute processing, the resources including a vehicle for providing food and beverages, a labor force for performing at least one of the tasks of driving the vehicle and providing food and beverages in the vehicle, and cargo to be loaded on the vehicle, the cargo including at least one of the food and beverages and ingredients for the food and beverages to be provided in the vehicle, and the program associates information about the vehicle for providing food and beverages with the availability conditions of the vehicle and the resource owner who owns the vehicle, and The processor executes a vehicle registration process to register information of the resource owner who provides the labor force in the source database, a labor registration process to register information of the resource owner who provides the labor force in the resource database by associating the information with the labor supply conditions, a cargo registration process to register information of the cargo in the resource database by associating the information with the cargo supply conditions and a resource owner who owns or can prepare the cargo, a use conditions reception process to acquire from the planner terminal desired use conditions input or selected at the planner terminal, and an extraction process to extract at least one of the information of the vehicle, the information of the resource owner who provides the labor force, and the information of the cargo from the resource database based on the supply conditions that satisfy the desired use conditions acquired in the use conditions reception process.

Furthermore, the matching support system according to the second aspect of the present disclosure is a matching support system capable of communicating with a planner terminal used by a planner who plans a mobile food and beverage sales business, and a resource owner terminal used by a resource owner who owns at least one of the resources necessary for the mobile food and beverage sales business, the resources including a vehicle for providing food and beverages, a labor force for performing at least one of the tasks of driving the vehicle and providing food and beverages in the vehicle, and cargo to be loaded on the vehicle, the cargo including at least one of the food and beverages provided in the vehicle and ingredients for the food and beverages, and the matching support system associates information about the vehicle for providing food and beverages with the availability conditions of the vehicle and the resource owner who owns the vehicle, and stores the information in a resource database. a vehicle registration processing unit that registers information of the resource owner who provides the labor force in the resource database, a labor registration processing unit that registers information of the resource owner who provides the labor force in the resource database in association with the labor supply conditions, a cargo registration processing unit that registers information of the cargo in the resource database in association with the cargo supply conditions and the resource owner who owns or can prepare the cargo, a usage conditions reception processing unit that acquires desired usage conditions input or selected at the planner terminal from the planner terminal, and an extraction processing unit that extracts at least one of the vehicle information, the information of the resource owner who provides the labor force, and the cargo information from the resource database based on the supply conditions that satisfy the desired usage conditions acquired at the usage conditions reception processing unit.

According to the above configuration, the planner can procure the resources he or she needs from the resource owner based on the extracted information. The resource owner can allow the planner to use resources that the planner owns but is not using. In other words, it is possible to support matching between planners and resource owners. This allows the planner to operate a mobile food and drink sales business even if he or she does not own all of the resources, and allows the resource owner to utilize his or her own resources.

FIG. 1 is a block diagram showing the configuration of a matching support system 100 according to one embodiment. FIG. 2 is a block diagram of the information terminal 20. FIG. 3 is a block diagram of the server device 10. FIG. 4 is a diagram (1) for explaining the configuration of the database 13a. FIG. 5 is a diagram (2) for explaining the configuration of the database 13a. FIG. 6 is a diagram (3) for explaining the configuration of the database 13a. FIG. 7 is a diagram (4) for explaining the configuration of the database 13a. FIG. 8 is a diagram (5) for explaining the configuration of the database 13a. FIG. 9 is a diagram (6) for explaining the configuration of the database 13a. FIG. 10 is a diagram (1) showing an example of a screen displayed on the touch panel 22. FIG. 11 is a diagram (2) showing an example of a screen displayed on the touch panel 22. In FIG. FIG. 12 is a diagram (3) showing an example of a screen displayed on the touch panel 22. FIG. 13 is a diagram (4) showing an example of a screen displayed on the touch panel 22. FIG. 14 is a diagram (5) of an example of a screen displayed on the touch panel 22. FIG. 15 is a diagram (6) of an example of a screen displayed on the touch panel 22. FIG. 16 is a diagram (7) of an example of a screen displayed on the touch panel 22. FIG. 17 is a diagram (8) of an example of a screen displayed on the touch panel 22. FIG. 18 is a diagram (9) of an example of a screen displayed on the touch panel 22. FIG. 19 is a diagram (10) of an example screen displayed on the touch panel 22. FIG. 20 is a diagram (11) of an example of a screen displayed on the touch panel 22. FIG. 21 is a diagram (12) of an example of a screen displayed on the touch panel 22. FIG. 22 is a diagram (13) of an example of a screen displayed on the touch panel 22. FIG. 23 is a diagram (14) of an example of a screen displayed on the touch panel 22. FIG. 24 is a diagram (15) of an example of a screen displayed on the touch panel 22. FIG. 25 is a diagram (16) of an example of a screen displayed on the touch panel 22. FIG. 26 is a diagram (17) of an example of a screen displayed on the touch panel 22. FIG. 27 is a diagram (18) of an example of a screen displayed on the touch panel 22. FIG. 28 is a diagram (19) of an example of a screen displayed on the touch panel 22. FIG. 29 is a diagram (20) of an example screen displayed on the touch panel 22. FIG. 30 is a diagram (21) of an example of a screen displayed on the touch panel 22. FIG. 31 is a diagram (22) of an example screen displayed on the touch panel 22. FIG. 32 is a diagram (23) of an example of a screen displayed on the touch panel 22. FIG. 33 is a diagram (24) of an example of a screen displayed on the touch panel 22.

An embodiment of the present disclosure will be described below with reference to the drawings. Note that the present disclosure is not limited to the following embodiment, and appropriate design changes can be made within the scope of the configuration of the present disclosure. In the following description, the same reference numerals are used in common between different drawings for the same parts or parts having similar functions, and repeated description will be omitted. The configurations described in the embodiment and modified examples may be combined or modified as appropriate. In order to make the description easier to understand, the configurations are shown simplified or schematic in the drawings referenced below.

[Overall configuration of the matching support system]
FIG. 1 is a block diagram showing the configuration of a matching support system 100 (hereinafter, referred to as "system 100") in this embodiment.

As shown in FIG. 1, the system 100 is a system that matches planners and resource owners by communicating with a planner terminal 20a used by the planner and a resource owner terminal 20b used by the resource owner via a network N. Note that the network N is, for example, the Internet and a Local Area Network (LAN), but other networks (for example, a Wide Area Network (WAN)) may also be used.

In the system 100, the resource owner registers the resources he owns in the database 13a (see FIG. 3). The resource owner also determines which resources to put up for sale from the registered resources. When the planner inputs or selects the desired conditions of use, the system 100 extracts resource information from the database 13a. The system 100 allows the planner to select any of the extracted information and make a reservation for the resource. When the resource owner approves the reservation from the planner, the system 100 notifies the planner that the reservation has been approved. In this way, the system 100 enables reservations so that the planner can procure the necessary resources from the resource owner when he or she is about to start a mobile food and beverage sales business. The system 100 also enables the resource owner to allow the planner to use resources that the resource owner owns but has not used. In other words, the system 100 of this embodiment can match planners and resource owners. This allows the planner to start a mobile food and beverage sales business even if he or she does not own all of the resources, and allows the resource owner to utilize his or her own resources.

"Resources" are the resources necessary for a mobile food and beverage sales business. "Resources" include a vehicle for serving food and beverages, labor to drive the vehicle and/or serve food and beverages in the vehicle, cargo to be loaded onto the vehicle including at least one of the food and beverages and ingredients for said food and beverages served in the vehicle, the location where the food and beverages are served (the location where the food and beverages are set up), and the location where the food and beverages or ingredients for said food and beverages (cargo) are loaded onto the vehicle (the preparation location). "Food and beverages" includes at least one of beverages and food.

A "resource owner" is a person who owns at least one of the resources described above. In other words, "resource owners" include resource owners who own vehicles for providing food and drink, resource owners who own or can prepare cargo, resource owners who own a stall where food and drink are provided, resource owners who own a place to load food and drink or ingredients for said food and drink into a vehicle, and resource owners who have the labor to drive a vehicle and/or serve food and drink in the vehicle. An example of a "vehicle" is a food truck with a kitchen inside the vehicle, but this example is not limited to this. For example, "vehicle" also includes vehicles that do not have a kitchen. "Cargo" includes not only food and drink provided in the vehicle, but also ingredients (ingredients) that are cooked to become food and drink, containers and packaging for storing food and drink, and cooking utensils.

A "planner" is a person who plans a mobile food and beverage sales business. When a planner provides his or her own resources to another planner, he or she becomes a resource owner. In other words, a user who uses this system 100 becomes a "resource owner" when providing resources, and becomes a "planner" when using resources.

"Matching" means that a planner makes an offer (reservation) to the resource owner who owns the resource that he/she wishes to use the resource, and the resource owner approves the use (loan) to the planner. In this case, when the planner uses the resource owner's resource, the planner pays the resource owner a usage fee (rental fee). Note that this is not limited to this example, and the resource owner may allow the planner to use the resource free of charge.

[Configuration of each part of the matching support system]
As shown in Figure 1, the system 100 communicates with a planner terminal 20a, a resource owner terminal 20b, and a consumer terminal 20c via a network N. For the sake of explanation, the planner terminal 20a, the resource owner terminal 20b, and the consumer terminal 20c have been given different names and symbols to distinguish them according to the user, but they are all information terminals 20 (see Figure 2). That is, the planner terminal 20a is an information terminal 20 used by the planner. The resource owner terminal 20b is an information terminal 20 used by the resource owner. The consumer terminal 20g is an information terminal 20 used by a consumer who purchases food and drink from the mobile sales. The system 100 includes a server device 10.

2 is a block diagram of the information terminal 20. The information terminal 20 is configured as, for example, a smartphone, a smart watch, a personal computer, or a tablet terminal. The information terminal 20 includes a control unit 21, a touch panel 22, a communication unit 23, and a storage unit 24. The control unit 21 includes a processor that executes control processing by executing a program 24a. The control unit 21 executes each control processing of the information terminal 20. The touch panel 22 also includes a display that displays images and accepts touch operations from the user. The communication unit 23 is a communication interface and is connected to the network N. The storage unit 24 includes at least one of a ROM and a RAM that can store data. The storage unit 24 stores a program 24a. The program 24a is an application program that executes the control processing of the information terminal 20. Note that it is not limited to using dedicated application software, and browser software (e.g., a web browser) that connects to the server device 10 may be installed in the information terminal 20. The program 24a is an application program common to the planner and the resource owner. For example, if a planner owns resources, he or she will use the system 100 as the resource owner when the planner is not running a mobile sales business.

FIG. 3 is a block diagram of the server device 10. The server device 10 includes a control unit 11, a communication unit 12, and a storage unit 13. The control unit 11 includes a processor that executes each control process of the server device 10. The communication unit 12 is a communication interface, and is connected to the network N. The storage unit 13 includes at least one of a ROM and a RAM capable of storing data. The storage unit 13 stores a database 13a and a program 13b. The program 13b causes the control unit 11 to execute the processes shown in FIGS. 10 to 33, which will be described later. The server device 10 may be an on-premise (fixed) server device, or may be a server device configured on the cloud.

[Database configuration]
The database 13a will be described with reference to Figures 4 to 9. The database 13a stores information on resources registered by resource owners, information on matching between planners and resource owners, and information on settlement between planners and resource owners.

(Resource information)
<Vehicle Information>
As shown in FIG. 4, vehicle information is registered in the database 13a. The "vehicle information" includes a vehicle ID, a vehicle name, a vehicle storage location, equipment, size, and rental fee. The "vehicle ID" is identification information that can identify a registered vehicle. The identification information includes at least one of a number, a letter, and a symbol. In the example of FIG. 4, the "vehicle ID" is "0001". The "vehicle name" is a name of the vehicle arbitrarily set by the resource owner. In the example of FIG. 4, the "vehicle name" is "Kitchen car A". The "vehicle storage location" is a location where the vehicle is stored. The "vehicle storage location" may be, for example, the address of the resource owner who owns the vehicle. The "equipment" is equipment necessary for preparing or cooking food and drink loaded on the vehicle. In the example of FIG. 4, the "equipment" is a "rice cooker" and "100 L of water". The "size" is, for example, the total vehicle weight, or information indicating whether the vehicle is a "light truck", a "small truck", a "medium truck", or a "large truck". The "rental fee" is the amount charged to the planner when using the vehicle. Although not shown, image data of the vehicle may be registered in the database 13a.

In addition, in database 13a, vehicle information is registered in association with availability conditions, which are conditions under which the vehicle can be provided, and the resource owner who owns the vehicle. As shown in FIG. 4, an "owner ID," which is identification information indicating the resource owner, is registered in association with "vehicle information." In addition, as shown in FIG. 5, a vehicle ID (e.g., "0001") is registered in database 13a in association with the vehicle availability period (e.g., the desired start date and time and end date and time). Note that the availability conditions may include at least one of the rental fee, the vehicle storage location, the facilities, and the size of the vehicle, in addition to (or instead of) the desired time of provision (available period) shown in FIG. 5, as shown in FIG. 4.

<Store location information>
As shown in FIG. 6, the database 13a registers information about the location of the store. The "information about the location of the store" includes the location ID, the location name, the address, the details, and the rental fee. The "location ID" is identification information that can identify the registered location of the store. In the example of FIG. 6, the "location ID" is "0011". The "location name" is the name of the location of the store. In the example of FIG. 6, the "location name" is "XX University XX Campus". The "address" is the address of the location of the store. The "details" are the purpose of opening a store at the location of the store and any contact information for the planner. The "rental fee" is the amount to be charged to the planner when the location of the store is used. Although not shown, image data of the location of the store may be registered in the database 13a.

In addition, in database 13a, store location information is registered in association with availability conditions, which are conditions under which the store location can be provided, and the resource owner who owns the store location. As shown in FIG. 6, an "owner ID," which is identification information indicating the resource owner, is registered in association with "store location information." Also, as shown in FIG. 5, a store location ID (e.g., "0011") is registered in database 13a in association with the availability period of the store location (e.g., the start date and time and the end date and time of the desired date and time). Note that the availability conditions may include at least one of the rental fee, address, and content in addition to (or instead of) the desired period of provision (available period) shown in FIG. 5, as shown in FIG. 6.

<Information about preparation area>
As shown in FIG. 7, information on preparation locations is registered in the database 13a. The "preparation location" is a location where cargo is prepared and loaded onto a vehicle. The "information on preparation location" includes a preparation location ID, a name, an address, equipment, and a rental fee. The "preparation location ID" is identification information that can identify a registered preparation location. In the example of FIG. 7, the "preparation location ID" is "0021". The "name" is the name of the preparation location. In the example of FIG. 7, the "name" is "Restaurant A". The "address" is the address of the preparation location. The "equipment" is equipment that can be used for cooking at the preparation location. The "rental fee" is an amount charged to the planner when using the preparation location. Although not shown, image data of the preparation location may be registered in the database 13a.

In addition, in database 13a, information on preparation locations is registered in association with availability conditions, which are conditions under which the preparation location can be provided, and the resource owner who owns the preparation location. As shown in FIG. 7, an "owner ID," which is identification information indicating the resource owner, is registered in association with "preparation location information." In addition, as shown in FIG. 5, a preparation location ID (e.g., "0021") is registered in database 13a in association with the availability period of the store location. Note that the availability conditions may include at least one of the rental fee, address, and equipment, in addition to (or instead of) the desired time of provision (available period) shown in FIG. 5, as shown in FIG. 7.

<Cargo information>
As shown in FIG. 8, information on the cargo is registered in the database 13a. In this embodiment, the "information on the cargo" is associated with information on the restaurant that prepares the cargo. The "information on the restaurant" includes the restaurant ID, name, and address. The "information on the cargo" includes the name of the cargo and the rental fee. The "restaurant ID" is identification information that can identify the registered restaurant. In the example of FIG. 8, the "restaurant ID" is "0031". The "name" is the name of the restaurant. In the example of FIG. 8, the "name" is "Restaurant A". The "address" is the address of the restaurant. The "name of the cargo" is the name of the food or drink or the name of the ingredients. The "rental fee" is the amount charged to the planner when the cargo is used. Although not shown, image data of the cargo may be registered in the database 13a.

In addition, in database 13a, information on the cargo is registered in association with availability conditions, which are conditions under which the cargo can be provided or prepared, and with the resource owner who owns or can prepare the cargo. As shown in FIG. 8, an "owner ID," which is identification information indicating the resource owner, is registered in association with "shipment information." As shown in FIG. 5, a restaurant ID (e.g., "0031") is registered in database 13a in association with the availability period (e.g., the start date and time and the end date and time of the desired date and time). Note that the availability conditions may include at least one of the rental fee, address, and name of the cargo in addition to (or instead of) the desired time of provision (available period) shown in FIG. 5, as shown in FIG. 8.

Labor force information
As shown in FIG. 9, the database 13a registers information on labor. The "labor information" includes gender and rental fee. "Gender" refers to the gender of the person performing the labor work. "Rental fee" refers to the amount charged to the planner when the person performing the labor work is used. In addition, the database 13a stores information on the resource owner who provides the labor force in association with the availability conditions under which the labor force can be provided. The information on the resource owner who provides the labor force includes an "owner ID" and "labor information." As shown in FIG. 5, the database 13a registers an owner ID (e.g., "1041") in association with the availability time (e.g., the start date and time and the end date and time of the desired date and time). Although not shown, image data of the person performing the labor work may be registered in the database 13a. In addition to (or instead of) the desired time of provision (available time) shown in FIG. 5, the availability conditions may include at least one of the rental fee and gender, as shown in FIG. 9.

(Matching Information)
As shown in Fig. 5, the database 13a stores information regarding matching between a planner and a resource owner. When a planner reserves the use of a resource and the resource owner accepts, the database 13a associates information indicating that matching has been completed with the identification information of the planner who made the reservation ("reservation ID" in the example of Fig. 5) and the identification information of the reserved resource or the resource owner ("ID" in the example of Fig. 5).

(Payment Information)
As shown in Fig. 5, the database 13a stores information regarding the settlement between the planner and the resource owner. When the monetary transaction (settlement) between the planner and the resource owner is completed, the database 13a associates information indicating that the settlement has been completed with the identification information of the planner who made the reservation ("reservation ID" in the example of Fig. 5) and the identification information of the reserved resource or the resource owner ("ID" in the example of Fig. 5).

[Control process by control unit]
Next, a description will be given of the control process of the system 100. The control process of the system 100 is realized by the control unit 11 of the server device 10 executing the program 13b. Moreover, the control process in the information terminal 20 is realized by the control unit 21 executing the program 24a.

(Registration process)
The resource registration process by the system 100 will be described with reference to FIG. 10 to FIG. 19. The screens in FIG. 10 to FIG. 19 are examples of screens displayed on the touch panel 22 of the resource owner terminal 20b. As shown in FIG. 10, the control unit 11 displays a calendar on the touch panel 22. The screen shown in FIG. 10 is hereinafter referred to as a "calendar display screen." The calendar includes a current day, a selected day, and information indicating a matched schedule. In the example of FIG. 10, the "current day" is "June 18, 2022," and a circle is added to the date. In addition, in the example of FIG. 10, the "selected day" is "June 22, 2022," and hatching is applied to the date column. In the example of FIG. 10, the "information indicating a matched schedule" is displayed in the "June 23, 2022" column, and for example, an object of "Schedule B" is displayed.

Here, when a user (e.g., the resource owner) operates the "My Page" object on the calendar display screen shown in FIG. 10, the system 100 transitions the screen displayed on the touch panel 22 from the calendar display screen to the My Page screen shown in FIG. 11.

When the "Cargo Setting" object is selected on the My Page screen shown in FIG. 11, the system 100 transitions the screen displayed on the touch panel 22 from the My Page screen to the cargo setting screen shown in FIG. 15. When the "Kitchen Car Setting" object is selected on the My Page screen, the system 100 transitions the screen displayed on the touch panel 22 from the My Page screen to the kitchen car information editing screen shown in FIG. 12. When the "Store Location Setting" object is selected on the My Page screen, the system 100 transitions the screen displayed on the touch panel 22 from the My Page screen to the store location setting screen shown in FIG. 13. When the "Preparation Location Setting" object is selected on the My Page screen, the system 100 transitions the screen displayed on the touch panel 22 from the My Page screen to the store location setting screen shown in FIG. 14. When the "Personnel Setting" object is selected on the My Page screen, the system 100 transitions the screen displayed on the touch panel 22 from the My Page screen to the staff setting screen shown in FIG. 16.

In the kitchen car information editing screen shown in FIG. 12, the resource owner inputs information on "name", "size", "equipment", and "rental fee". The information may be input by inputting text or numbers, or may be selected by the resource owner from options prepared in advance. The input method is similar in the examples of FIG. 13 to FIG. 16. For example, options such as "light truck", "2 ton truck", and "4 ton truck" may be prepared in advance for the input of "size". Then, when the "Edit" object is selected on the kitchen car information editing screen, the system 100 registers the input information in the database 13a shown in FIG. 4 in association with the resource owner's identification information "owner ID". That is, the input information and the owner ID are transmitted from the resource owner terminal 20b to the system 100. The "vehicle ID" is automatically assigned by the system 100. Also, without being limited to this, the resource owner may input the "vehicle ID" on the kitchen car information editing screen, although not shown.

In the store location setting screen shown in FIG. 13, the resource owner inputs information on "location name," "address," "contents," and "rental fee." Then, when the "Edit" object is selected on the store location setting screen, the system 100 associates the input information with the resource owner's identification information "owner ID," and registers it in the database 13a shown in FIG. 6. The "store location ID" is automatically assigned by the system 100. Also, without being limited to this, the resource owner may input the "store location ID" on the store location setting screen, although this is not shown.

In the preparation location setting screen shown in FIG. 14, the resource owner inputs the information "Name," "Address," "Equipment," and "Rental Fee." Then, when the "Edit" object is selected on the preparation location setting screen, the system 100 associates the input information with the resource owner's identification information "Owner ID," and registers it in the database 13a shown in FIG. 7. The "Preparation location ID" is automatically assigned by the system 100. Also, without being limited to this, the resource owner may input the "Preparation location ID" on the store location setting screen, although this is not shown.

In the cargo setting screen shown in FIG. 15, the resource owner inputs the information "Name" (restaurant name), "Address", "Cargo name", and "Rental fee". Then, when the "Edit" object is selected on the cargo setting screen, the system 100 associates the input information with the resource owner's identification information "Owner ID", and registers it in the database 13a shown in FIG. 8. The "Restaurant ID" is automatically assigned by the system 100. Also, without being limited to this, the resource owner may input the "Restaurant ID" in the cargo setting screen, although this is not shown.

In the personnel setting screen shown in FIG. 16, the resource owner inputs information on "gender" and "rental fee." Then, when the "Edit" object on the personnel setting screen is selected, the system 100 associates the input information with the resource owner's identification information "owner ID" and registers it in the database 13a shown in FIG. 9.

As shown in FIG. 17, when a "+" object is selected on the calendar display screen, the system 100 displays a list on the touch panel 22 from which the resource owner can select the resource to list. When "List a Kitchen Car" on this list is selected, the system 100 transitions the screen displayed on the touch panel 22 from the calendar display screen to a Kitchen Car Listing screen.

As shown in FIG. 18, the resource owner inputs the available period on the kitchen car listing screen. The "available period" is the period during which the resource owner can provide the resources he owns to the planner. In other words, it is the period during which the resource owner wishes the planner to use the resources he owns. In the example of FIG. 18, the start of the "available period" is entered in the "desired matching date and time start" field, and the end of the "available period" is entered in the "desired matching date and time end" field.

When "Matching Kitchen Car" is selected on the kitchen car listing screen shown in FIG. 18, the system 100 transitions the screen displayed on the touch panel 22 from the kitchen car listing screen to the kitchen car list screen shown in FIG. 19. If the resource owner has registered multiple vehicles in the database 13a, the resource owner selects one of the registered vehicles. When a vehicle is selected, the system 100 displays the name of the vehicle on the kitchen car listing screen.

In addition, the start time and end time entered in the "Available Period" are repeatedly entered in the "Repeat" column shown in FIG. 18 every day, every day of the week, every week, or every month. Then, when the "Add" object is selected, the resource ID (vehicle ID) and the available period (desired start date and time and desired end date and time) are registered in the database 13a as shown in FIG. 5. As a result, as shown in FIG. 4 and FIG. 5, the owner ID, the resource ID (e.g., "vehicle ID"), the available period, the owner ID, and the rental fee (fee information) are associated with each other in the database 13a. For example, if the available period is June 22, 2022, as shown in FIG. 17, the system 100 displays the "Plan A" object on the calendar. When "Plan A" is selected, the system 100 transitions the screen displayed on the touch panel 22 from the calendar display screen to the "Self-reservation screen" shown in FIG. 26. Please note that the "Store location exhibit," "Preparation location exhibit," "Cargo exhibit," and "Personnel exhibit" are the same as the "Kitchen car exhibit" above, so explanations will be omitted.

(Reservation processing)
Next, the resource reservation process by the system 100 will be described with reference to Figures 20 to 25. The screens in Figures 20 to 25 are examples of screens displayed on the touch panel 22 of the planner terminal 20a.

<Terms of Use Acceptance Processing>
As shown in FIG. 20, a calendar screen is displayed on the touch panel 22 of the planner terminal 20a. The system 100 acquires the date on the calendar selected by the planner as the desired use time, which is the time when the planner desires to make a reservation. Then, as shown in FIG. 21, the system 100 transitions the screen displayed on the touch panel 22 from the calendar screen to a search keyword input screen. The search keyword input screen displays the desired use time, an input field for the search keyword, an input field for the desired rental fee, and an object for "Execute search." In other words, the search keyword input screen is a screen for the planner to input the desired conditions of use. The system 100 acquires the desired use time, the keyword input in the input field for the search keyword, and the information input in the input field for the desired rental fee. The input fields may be used to input characters, or may be provided with multiple options prepared in advance.

Extraction Process
When the "Search" object is selected on the search keyword input screen shown in FIG. 21, the system 100 extracts from the database 13a information on resources whose available time matches the desired use time, contain the search keyword, and meet the conditions for which the rental fee has been input. That is, the system 100 extracts from the database 13a information on resources associated with available conditions that meet the desired use conditions. In other words, filtering is performed from the database 13a based on the desired use conditions, the search keyword, and the rental fee. "Available time matches the desired use time" means that at least a part of the period from the start to the end of the matching desired date and time of the available time registered in the database 13a is included in the desired use time. The system 100 extracts from the database 13a all information on resources whose available time matches the desired use time, contain the search keyword, and meet the conditions for which the rental fee has been input, and displays the extracted information in a list on the touch panel 22 as shown in FIG. 22. Note that Figure 22 shows an example in which only the kitchen car (vehicle) is extracted, but if the available time coincides with the desired usage time and the resources containing the search keyword are labor (personnel) other than the vehicle, the store location, the preparation location, and the cargo, the system 100 extracts this information.

Selection Processing
When the planner selects one of the extracted information shown in FIG. 22 on the planner terminal 20a, the system 100 displays a detailed display screen on the touch panel 22 as shown in FIG. 23. The system 100 displays the information extracted from the database 13a on the detailed display screen. In the example of FIG. 23, "Name", "Address", "Facilities", "Rental Fee", and a "Message Column" (comment column) are displayed. Since the "Rental Fee" is displayed on this screen, the planner can select a resource after checking the fee for using the resource. In addition, since the "Message Column" is displayed, the planner can check the message exchange between the planner and the resource owner on this screen. When the "Message Column" is selected, the system 100 transitions the screen displayed on the touch panel 22 from the detailed display screen to a comment screen as shown in FIG. 24.

As shown in FIG. 24, the system 100 displays on the comment screen a message from the planner sent from the planner terminal 20a and a message from the resource owner sent from the resource owner terminal 20b. When the message input field is entered into the message input field by the planner terminal 20a or the resource owner terminal 20b while the comment screen is displayed (in the example of FIG. 24, "Thank you") and the "Send" object is selected, the message is posted (the message is added to the comment screen). The system 100 stores the message from the planner sent from the planner terminal 20a and the message from the resource owner sent from the resource owner terminal 20b in the database 13a in association with the resource information (vehicle ID "0001" in the example of FIG. 23). The system 100 may be configured so that messages cannot be posted on the comment screen after matching is established (approved by the resource owner), as described below.

When the "reservation" object is selected by the planner on the detailed display screen shown in FIG. 23, the system 100 acquires the ID of the planner from the planner terminal 20a. Then, as shown in FIG. 5, the system 100 associates the ID of the planner with the ID of the resource as a reserving user ID. The state in which the reserving user ID is associated with the ID of the resource is called a "reserved state." Here, when "matching" is selected on the calendar display screen shown in FIG. 20, the system 100 transitions the screen displayed on the touch panel 22 from the calendar display screen to the matching display screen shown in FIG. 25. Then, when "reservation by me" is selected on the matching display screen, the system 100 transitions the screen displayed on the touch panel 22 from the matching display screen to the "reservation by me" confirmation screen shown in FIG. 26. The "reservation by me" confirmation screen displays whether the resource owner (other party) has been approved or is waiting for approval.

(Matching process)
When the ID of the resource is associated with the reserving user ID and the resource is in a reserved state, for example, as shown in FIG. 17, the system 100 displays information indicating that the resource has been reserved by the planner (in the example of FIG. 17, an object of "Plan A") on the calendar display screen of the touch panel 22 of the resource owner terminal 20b of the resource owner who owns the reserved resource. The information indicating that the resource has been reserved by the planner may be displayed as a pop-up display, a badge display, or a banner display on the calendar display screen. When the resource owner selects the "Plan A" object or selects the "Reservation by Other Party" object on the matching display screen (see FIG. 25), the system 100 transitions the screen displayed on the touch panel 22 to a "Reservation by Other Party" confirmation screen shown in FIG. 27. The system 100 displays the desired use time (desired matching date and time), a message, and an object of "matching approval" on the "Reservation by Other Party" confirmation screen. When the "Matching approval" object is selected, information of "matching completed" is added to the reserving user ID as shown in FIG. 5. When the "matched" information is added to the reservation ID, the "Reservation by You" confirmation screen displayed on the touch panel 22 of the planner terminal 20a changes from "Waiting for approval" to "Approved."

According to this configuration, a planner can make a reservation so that the necessary resources can be procured from a resource owner at the time when the planner wishes to operate a mobile food and beverage sales business. The resource owner can allow the planner to use resources that the planner owns but will not be using during the above-mentioned available period. In other words, planners and resource owners can be matched. This allows the planner to operate a mobile food and beverage sales business even if he or she does not own all of the resources, and allows the resource owner to utilize his or her own resources.

(Payment Processing)
When the resource owner selects the "Matching Approval" object, the system 100 causes the planner terminal 20a to display the payment screen shown in FIG. 28. The system 100 causes the payment screen to display the amount to be charged to the planner and the "Pay" object. When the "Pay" object is selected, the system 100 executes a payment process. The payment process may, for example, store the planner's credit card information, bank account information, or electronic money account in the database 13a in advance, and execute a process of depositing money from the planner's account to the resource owner's account. Additionally, the system 100 may cooperate with an external payment system separate from the system 100, and the payment from the planner to the resource owner may be made via the external payment system.

When the payment process is completed, the system 100 displays a screen on the touch panel 22 of the planner terminal 20a notifying the completion of the payment as shown in FIG. 29. Then, as shown in FIG. 30, the system 100 displays a screen on the planner terminal 20a inquiring whether the receipt of the resource (service) is completed. When the planner selects "Yes" on the screen shown in FIG. 30, the system 100 transitions the screen displayed on the touch panel 22 from the inquiry screen to a calendar display screen. When the planner selects "No" on the screen shown in FIG. 30, the system 100 displays an evaluation screen shown in FIG. 31 on the touch panel 22 of the resource owner terminal 20b. On the evaluation screen, for example, a message "The other party has requested that the service has not been provided. If the service has not been provided, please provide the service," a "cancel" object, and a "provision completed" object are displayed. When the "cancel" object is selected, the system 100 cancels the payment process and deletes the "matched" information in the database 13a shown in FIG. 5. In other words, the system 100 returns to the state before matching. When the "Provision Completed" object is selected, the system 100 transitions the screen displayed on the touch panel 22 from the evaluation screen to the calendar display screen.

(Food and drink purchase processing)
The system 100 causes the touch panel 22 of the consumer terminal 20c to display the product name ("Mapo Rice Bowl" in the example of FIG. 32) and the price ("500 yen" in the example of FIG. 32) shown in FIG. 32 on a calendar display screen. When the "Order" object is selected by the consumer on the calendar display screen, a payment process is carried out and the consumer pays the price to the planner. The system 100 then causes the touch panel 22 of the consumer terminal 20c to display an indication indicating completion of payment, the order number, and an object "Pickup Completed" shown in FIG. 33. When the object "Pickup Completed" is selected by the consumer, the system 100 transitions the screen displayed on the touch panel 22 from the screen shown in FIG. 33 to the calendar display screen. This allows the system 100 to execute processes related to the purchase procedures not only by the planner and resource owner but also by the consumer.

[Modification]
As described above, the above-described embodiments are merely examples for implementing the present disclosure. Therefore, the present disclosure is not limited to the above-described embodiments, and can be implemented by appropriately modifying the above-described embodiments without departing from the spirit of the present disclosure.

(1) In the above embodiment, an example was shown in which the availability time or the desired use time was selected on a calendar, but the present disclosure is not limited to this. In other words, the availability time or the desired use time may be input or selected without the calendar being displayed.

(2) In the above embodiment, an example was shown in which the desired conditions of use included a desired time of use, a keyword, and a rental fee, but the present disclosure is not limited to this. In other words, resource information may be extracted from the database with only the desired time of use as the desired conditions of use, regardless of keywords or rental fee, or resource information may be extracted from the database with only keywords as the desired conditions of use, regardless of time or rental fee, or resource information may be extracted from the database with only the rental fee as the desired conditions of use, regardless of time or keyword.

(3) In the above embodiment, an example was shown in which a message (comment) was displayed on a details display screen, but the present disclosure is not limited to this. For example, a message may be displayed on a calendar display screen, or a message may be displayed on a pop-up screen.

(4) In the above embodiment, vehicles, labor (personnel), cargo, store locations, and preparation locations are given as examples of resources, but the present disclosure is not limited to this. For example, resources may be only vehicles, labor (personnel), and cargo, or the system 100 may provide matching support for resources other than vehicles, labor (personnel), cargo, store locations, and preparation locations.

(5) In the above embodiment, an example was shown in which the system executes the selection process, matching process, payment process, and food and beverage purchase process, but the present disclosure is not limited to this. A system may be configured that does not execute the selection process, matching process, payment process, or food and beverage purchase process. In this case, for example, the planner can check the resource information by accessing the information extracted by the extraction process, and make a reservation by contacting the resource owner himself.

The above configuration can be explained as follows:

The program according to the first configuration is a program that causes a processor of a system capable of communicating with a planner terminal used by a planner who plans a mobile food and beverage sales business, and a resource owner terminal used by a resource owner who owns at least one of the resources necessary for the mobile food and beverage sales business to execute processing, the resources including a vehicle for providing food and beverages, a labor force for performing at least one of the tasks of driving the vehicle and providing food and beverages in the vehicle, and cargo to be loaded on the vehicle, the cargo including at least one of the food and beverages and ingredients for the food and beverages to be provided in the vehicle, and the program associates information about the vehicle for providing food and beverages with the availability conditions of the vehicle and the resource owner who owns the vehicle, and generates resource data. The processor executes a vehicle registration process to register information of a resource owner who provides labor in a resource database, a labor registration process to register information of a resource owner who provides labor in a resource database by associating the information with the labor availability conditions, a cargo registration process to register information of a load in a resource database by associating the information with the cargo availability conditions and a resource owner who owns or can prepare the load, a usage conditions reception process to acquire from the planner terminal desired usage conditions input or selected in the planner terminal, and an extraction process to extract at least one of vehicle information, information of a resource owner who provides labor, and cargo information from the resource database based on availability conditions that satisfy the desired usage conditions acquired in the usage conditions reception process (first configuration).

According to the first configuration, the planner can procure the resources he or she needs from the resource owner based on the extracted information. The resource owner can allow the planner to use resources that the planner owns but is not using. In other words, it is possible to support matching between planners and resource owners. This allows the planner to operate a mobile food and drink sales business even if he or she does not own all of the resources, and allows the resource owner to utilize his or her own resources.

In the first configuration, the desired use conditions may include a desired use time, which is the time when the planner desires to use one of the resources. The availability conditions may include an available time, which is the time when the resource owner can provide the resource. The extraction process may include a process of extracting at least one of vehicle information, information on the resource owner providing the labor, and cargo information from the resource database based on the available time that matches the desired use time acquired in the use conditions acceptance process (second configuration).

The second configuration allows the planner to extract the necessary resources when he or she is planning to launch a mobile food and beverage sales business.

In the second configuration, the use conditions acceptance process may include a process of displaying a calendar on the display of the planner terminal and acquiring a date selected on the calendar as the desired use time. The program may be further configured to cause the processor to execute an on-screen selection process of displaying the information extracted by the extraction process on the display of the planner terminal and allowing the planner to select information extracted by the extraction process on the planner terminal, and a reservation display process of displaying a reservation from the planner on the calendar on the display of the resource owner terminal used by the resource owner associated with the information selected by the on-screen selection process (third configuration).

According to the third configuration, the planner can easily select the desired time of use by selecting a date on the calendar displayed on the display, and can easily select the resource he or she wants to use from the information (resources) extracted by the extraction process displayed on the display. The resource owner can then check the reservation from the planner on the calendar.

In any one of the first to third configurations, the program may be further configured to cause the processor to execute a selection process in which the planner selects, via the planner terminal, any of the information extracted by the extraction process, and a transmission process in which reservation information from the planner is transmitted to a resource owner terminal used by the resource owner associated with the information selected in the selection process (fourth configuration).

According to the fourth configuration, a planner can make a reservation so that the necessary resources can be procured from a resource owner at the time when the planner plans to start a mobile food and beverage sales business. The resource owner can allow the planner to use resources that the planner owns but is not using. In other words, planners and resource owners can be matched.

In the fourth configuration, the use conditions reception process may include a process of further acquiring from the planner terminal the keywords input or selected at the planner terminal. The extraction process may include a process of extracting at least one of the following information from the resource database: vehicle information including the keywords, resource owner information providing the labor, and cargo information, and further extracting information based on available conditions that satisfy the desired use conditions input or selected in the use conditions reception process from the at least one information including the keywords (fifth configuration).

According to the fifth configuration, resource information that includes the keyword input or selected by the planner is extracted from the resource database. This allows efficient extraction of information on resources that the planner wishes to use.

In any one of the first to fifth configurations, the program may be further configured to cause the processor to execute a message acquisition process for acquiring a message from each of the planner terminal and the resource owner terminal, and a display process for displaying an image including the information extracted by the extraction process and the message on the display of the planner terminal and the display of the resource owner terminal (sixth configuration).

According to the sixth configuration, messages can be exchanged between the planner and the resource owner.

In any one of the first to sixth configurations, the program may be further configured to cause the processor to execute a store location registration process that registers the store location, which is information about the location where food and beverages are provided, in the resource database by associating the store location with the availability conditions of the store location and the resource owner who owns the store location. The extraction process may include a process of extracting at least one of vehicle information, information about the resource owner providing labor, and information about the cargo, and store location information from the resource database based on the availability conditions that satisfy the desired use conditions acquired in the use conditions reception process (seventh configuration).

The seventh configuration above makes it possible to match planners who do not have a place to provide food and beverages with resource owners who have a place to set up shop.

In any one of the first to seventh configurations, the program may be configured to cause the processor to execute a loading location registration process that registers information about a location where food and beverages or ingredients for the food and beverages are loaded onto a vehicle in a resource database, in association with the availability conditions of the loading location and the resource owner who owns the loading location. The extraction process may include a process of extracting at least one of information about the vehicle, information about the resource owner who provides the labor, and information about the cargo from the resource database based on the availability conditions that satisfy the desired use conditions acquired in the use conditions reception process (eighth configuration).

According to the eighth configuration, it is possible to match a planner who does not have a place to load food and drink or ingredients for said food and drink onto a vehicle with a resource owner who has a place to load food and drink or ingredients for said food and drink onto a vehicle.

In any one of the first to eighth configurations, the vehicle registration process may include a process of registering vehicle information in the resource database, further associating the information on the vehicle with information on the fee for using the vehicle. The labor registration process may include a process of registering information on the resource owner providing the labor in the resource database, further associating the information on the fee for using the labor. The cargo registration process may include a process of registering information on the cargo in the resource database, further associating the information on the fee for using the cargo. The program may be further configured to cause the processor to execute a fee information transmission process that further transmits fee information associated with the information extracted by the extraction process to the planner terminal (ninth configuration).

According to the ninth configuration, the planner can select a resource after checking the fee for using the resource.

The matching support system according to the tenth configuration is a matching support system capable of communicating with a planner terminal used by a planner who plans a mobile food and beverage sales business, and a resource owner terminal used by a resource owner who owns at least one of the resources necessary for the mobile food and beverage sales business, the resources including a vehicle for providing food and beverages, a labor force for performing at least one of the tasks of driving the vehicle and providing food and beverages in the vehicle, and cargo to be loaded on the vehicle, the cargo including at least one of the food and beverages and ingredients for the food and beverages to be provided in the vehicle, and the matching support system associates information about the vehicle for providing food and beverages with the availability conditions of the vehicle and the resource owner who owns the vehicle, and generates resource data. The tenth configuration includes a vehicle registration processing unit that registers information on the resource owner who provides the labor force in the resource database, a labor registration processing unit that registers information on the resource owner who provides the labor force in the resource database in association with the labor provision conditions, a cargo registration processing unit that registers information on the cargo in the resource database in association with the cargo provision conditions and the resource owner who owns or can prepare the cargo, a usage conditions reception processing unit that acquires from the planner terminal the desired usage conditions that are input or selected in the planner terminal, and an extraction processing unit that extracts at least one of the vehicle information, the information on the resource owner who provides the labor force, and the cargo information from the resource database based on the provision conditions that satisfy the desired usage conditions acquired in the usage conditions reception processing unit (tenth configuration).

According to the tenth configuration, it is possible to provide a matching support system that can support matching between a planner and a resource owner who owns at least one of the resources required for a mobile food and beverage sales business.

13a...database, 13b...program, 20...information terminal, 20a...planner terminal, 20b...resource owner terminal, 20c...consumer terminal, 22...touch panel, 24a...program, 100...matching support system

Claims (10)

A program for causing a processor of a system capable of communicating with a planner terminal used by a planner who plans a mobile food and beverage sales business and a resource owner terminal used by a resource owner who owns at least one of the resources required for the mobile food and beverage sales business, comprising:
The resources include a vehicle for providing food and beverages, a labor force for performing at least one of driving the vehicle and providing food and beverages in the vehicle, and a load to be loaded on the vehicle, the load including at least one of food and beverages provided in the vehicle and ingredients for the food and beverages;
The program is
a vehicle registration process for registering information on a vehicle for providing food and beverages in a resource database in association with the availability conditions of the vehicle and a resource owner who owns the vehicle;
a labor force registration process for registering information of a resource owner who provides the labor force in the resource database in association with the labor force availability conditions;
a cargo registration process for registering information on the cargo in the resource database in association with a condition under which the cargo can be provided and a resource owner who owns or can prepare the cargo;
a use conditions receiving process for receiving from the planner terminal the desired use conditions input or selected at the planner terminal;
and an extraction process of extracting at least one of information on the vehicle, information on the resource owner providing the labor, and information on the cargo from the resource database based on available conditions that satisfy the desired conditions of use obtained in the conditions of use acceptance process. The desired conditions of use include a desired time when the planner desires to use any of the resources;
The provision availability condition includes a provision availability time, which is a time when the resource owner is able to provide the resource;
The program according to claim 1, wherein the extraction process includes a process of extracting at least one of information on the vehicle, information on the resource owner providing the labor, and information on the cargo from the resource database based on a supply period that matches the desired use period obtained in the use conditions acceptance process. the use conditions reception process includes a process of displaying a calendar on a display of the planner terminal and acquiring a date selected on the calendar as the desired use time,
the program includes an on-screen selection process for displaying the information extracted by the extraction process on a display of the planner terminal and allowing the planner to select the information extracted by the extraction process using the planner terminal;
3. The program according to claim 2, further causing the processor to execute a reservation display process for displaying reservations from the planner on a calendar on a display of a resource owner terminal used by the resource owner associated with the information selected by the on-screen selection process. A selection process in which a planner selects, via the planner terminal, any of the information extracted by the extraction process;
The program according to claim 1, further causing the processor to execute a transmission process of transmitting reservation information from the planner to a resource owner terminal used by the resource owner associated with the information selected in the selection process. The use conditions reception process further acquires, from the planner terminal, a keyword that has been input or selected at the planner terminal;
The program according to claim 4 , wherein the extraction process extracts at least one of information on the vehicle including the keyword, information on a resource owner providing the labor force, and information on the cargo from the resource database. A message acquisition process for acquiring messages from the planner terminal and the resource owner terminal, respectively;
A program described in any one of claims 1 to 5, further causing the processor to execute a display process of displaying an image including the information extracted by the extraction process and the message on the display of the organizer terminal and the display of the resource owner terminal. and further causing the processor to execute a store location registration process for registering information on a store location, which is a location where food and beverages are provided, in the resource database by associating the store location with a provision condition of the store location and a resource owner who owns the store location;
The program described in any one of claims 1 to 5, wherein the extraction process extracts at least one of information on the vehicle, information on the resource owner providing the labor, and information on the cargo, and information on the store location, from the resource database based on available conditions that satisfy the desired conditions of use obtained in the conditions of use acceptance process. and further causing the processor to execute a loading place registration process for registering information on a place where food and drink or ingredients for the food and drink are loaded onto a vehicle in the resource database in association with a provision condition of the loading place and a resource owner who owns the loading place;
The program according to any one of claims 1 to 5, wherein the extraction process extracts at least one of information on the vehicle, information on the resource owner providing the labor, and information on the cargo, and information on the loading location, from the resource database based on available conditions that satisfy the desired usage conditions obtained in the usage conditions acceptance process. The vehicle registration process further associates the vehicle information with information on a fee for using the vehicle, and registers the information in the resource database;
The labor force registration process further associates information of a resource owner who provides the labor force with information on a fee for using the labor force, and registers the information in the resource database;
The cargo registration process further associates the cargo information with information on a fee for using the cargo, and registers the information in the resource database;
A program described in any one of claims 1 to 5, further causing the processor to execute a fee information transmission process that further transmits fee information associated with the information extracted by the extraction process to the planner terminal. A matching support system capable of communicating with a planner terminal used by a planner who plans a mobile food and drink sales business, and a resource owner terminal used by a resource owner who owns at least one of the resources required for the mobile food and drink sales business, comprising:
The resources include a vehicle for providing food and beverages, a labor force for performing at least one of driving the vehicle and providing food and beverages in the vehicle, and a load to be loaded on the vehicle, the load including at least one of food and beverages provided in the vehicle and ingredients for the food and beverages;
The matching support system includes:
a vehicle registration processing unit that registers information about a vehicle for providing food and beverages in a resource database in association with a provision condition of the vehicle and a resource owner who owns the vehicle;
a labor registration processing unit that registers information of a resource owner who provides labor in the resource database in association with a labor supply condition of the resource owner;
a cargo registration processing unit that registers information about the cargo in the resource database in association with a condition under which the cargo can be provided and a resource owner who owns or can prepare the cargo;
a usage conditions reception processing unit that receives from the planner terminal the desired usage conditions input or selected at the planner terminal;
and an extraction processing unit that extracts at least one of information on the vehicle, information on the resource owner providing the labor, and information on the cargo from the resource database based on available conditions that satisfy the desired usage conditions acquired by the usage conditions reception processing unit.

Images