Program, information processing device, method, and system

Abstract

Aim to improve the efficiency of event planning operations. [Solution] A program to be executed by a computer having a processor, which causes the processor to execute the following steps: acquiring project information including the planned content, desired period, and desired area of ​​the event, and the skills and number of staff required; facility information including the availability of assets and usage fees; and human resource information including the skills and schedules of staff who are potential participants in the event; searching for combinations of assets and potential participating staff that satisfy the constraints based on the facility information and human resource information, using at least a portion of the project information as constraints; and calculating, using a predetermined algorithm, evaluation indexes for one or more combinations obtained through the search, and setting the combination with the best evaluation index as the allocation plan from the one or more combinations.

Description

[Technical Field]

[0001] The present disclosure relates to a program, an information processing device, a method, and a system. [Background technology]

[0002] Traditionally, there has been work to plan and manage events (hereinafter referred to as "events") such as pop-up stores, promotional events, exhibitions, and sales events at various facilities such as commercial facilities and event venues. Event organizers planning such events had to search for assets within the facility, such as sections and entrances, that matched the planned content of the event, inquire with the facility manager about the availability of the assets, and make reservations.

[0003] Furthermore, in order to hold an event, it is essential not only to secure assets, but also to secure the necessary number of staff with the appropriate skills for the necessary period to carry out tasks such as customer service, setup, cash register operation, etc. For this reason, event organizers have responded by adjusting the schedules of their in-house staff or arranging for the necessary staff from external contractors or temporary staffing agencies while reserving assets, or after the asset reservation has been confirmed.

[0004] In this type of event planning work, asset availability and staff availability were often checked separately, resulting in extreme inefficiency. Even if the optimal asset was found, there were cases where staff with the necessary skills could not be secured for that date, or conversely, staff could be secured but the asset could not. This resulted in a suboptimal combination of assets and staff, potentially resulting in missed opportunities for the event.

[0005] Known technologies related to planning and running events include, for example, a technology in which resource information such as the venue and equipment required for an event is compiled into a database, and event supporters search for the resource information according to the user's wishes to create and run the event (for example, Patent Document 1). [Prior art documents] [Patent documents]

[0006] [Patent Document 1] Japanese Patent Application Laid-Open No. 2002-109129 Summary of the Invention [Problem to be solved by the invention]

[0007] However, while the technology disclosed in Patent Document 1 creates a database of resource information such as the venue and equipment required for an event, it does not fully consider the ability to automatically generate an optimal allocation plan (shift plan) by dynamically combining two different pieces of resource information: staff schedules essential for holding the event, and the availability of assets.

[0008] As mentioned above, information about assets and information about staff are managed separately. Therefore, in conventional event planning, event organizers have to check the status of both and find the optimal combination of assets and staff, which requires a lot of time and effort.

[0009] Furthermore, due to the issues mentioned above, it was even more difficult to compare multiple options (combinations of assets and staff) after taking into account costs such as asset usage fees and staff labor costs, as well as projected sales and profits from the event.As a result, the most profitable allocation plan was not necessarily selected, which could result in lost opportunities.

[0010] The purpose of this disclosure is to improve the efficiency of event planning by automating the matching process of matching the wishes of event organizers with the availability of assets installed in facilities. [Means for solving the problem]

[0011] In order to solve the above-mentioned problems, a program according to one aspect of the present disclosure is a program to be executed by a computer having a processor, and causes the processor to execute the following steps: acquiring project information including the planned content of the event, the desired period and area for holding the event, and the skills and number of staff required to carry out the event; facility information including the availability status and usage fees for each of multiple assets set up in the facility; and human resource information including the skills and schedules of each of multiple staff members who are candidates to participate in the event; searching for combinations of assets and staff members who are candidates to participate in the event that satisfy the constraint conditions by comparing the acquired facility information and human resource information with the constraint conditions, using at least a portion of the acquired project information as constraint conditions; and calculating an evaluation index for one or more combinations obtained by the search, using a predetermined algorithm to evaluate at least one of the predicted costs and profits if the event is held, and identifying the combination with the best calculated evaluation index from the one or more combinations obtained by the search, and creating an allocation plan. [Effects of the Invention]

[0012] According to the present disclosure, the matching process of matching the wishes of the event organizer with the availability of assets installed in the facility can be automated, thereby improving the efficiency of event planning operations. [Brief explanation of the drawings]

[0013] [Figure 1] FIG. 1 is a diagram illustrating an example of the overall configuration of an event support system. [Figure 2] FIG. 2 is a block diagram illustrating an example of a hardware configuration of a client terminal. [Figure 3] 3 is a block diagram showing functional units realized by a control unit of the client terminal; FIG. [Figure 4] FIG. 2 is a block diagram illustrating an example of a hardware configuration of a server. [Figure 5] 3 is a block diagram showing functional units realized by a control unit of the server. FIG. [Figure 6]FIG. 10 illustrates an example of the data structure of a case management table. [Figure 7] FIG. 10 is a diagram illustrating an example of the data structure of a facility management table. [Figure 8] FIG. 10 illustrates an example of the data structure of a human resource management table. [Figure 9] FIG. 10 illustrates an example of the data structure of an allocation plan management table. [Figure 10] FIG. 10 illustrates an example of the data structure of a performance management table; [Figure 11] FIG. 10 is a diagram illustrating an example of a case list screen. [Figure 12] FIG. 10 is a diagram illustrating an example of an allocation planning screen. [Figure 13] 10 is a flowchart illustrating an example of the operation of a server when executing an allocation plan specifying process. [Figure 14] 10 is a flowchart illustrating an example of the operation of a server when performing a temporary reservation process and a document generation process. [Figure 15] 10 is a flowchart illustrating an example of the operation of the server when executing a settlement process and a management process. DETAILED DESCRIPTION OF THE INVENTION

[0014] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. In all drawings describing the embodiments, common components are designated by the same reference numerals, and repeated explanations will be omitted. Note that the following embodiments do not unduly limit the content of the present disclosure described in the claims. Furthermore, not all components shown in the embodiments are necessarily essential components of the present disclosure. Furthermore, each drawing is a schematic diagram and is not necessarily a precise illustration.

[0015] In the following description, a "processor" refers to one or more processors. A processor may be expressed as, for example, processing circuitry. The at least one processor is typically a microprocessor such as a CPU (Central Processing Unit), but may also be another type of processor such as a GPU (Graphics Processing Unit). The at least one processor may be single-core or multi-core. The at least one processor may also be a general-purpose processor or a special-purpose processor.

[0016] Furthermore, the at least one processor may be a processor in the broad sense, such as a hardware circuit (for example, a field-programmable gate array (FPGA) or an application-specific integrated circuit (ASIC)) that performs part or all of the processing.

[0017] In the following explanation, information that produces an output for an input may be described using expressions such as "xxx table," but this information may be data of any structure, or may be a learning model such as a neural network that produces an output for an input. Therefore, an "xxx table" may be referred to as "xxx information."

[0018] Furthermore, in the following description, the configuration of each table is an example, and one table may be divided into two or more tables, or all or part of two or more tables may be one table.

[0019] The program may be pre-installed in the information processing device described below, or may be stored on a recording medium (e.g., non-transitory) that can be read by the information processing device and then installed in the information processing device. The program may also be transmitted from a program distribution server to the information processing device and installed. In the following description, two or more programs may be realized as one program, or one program may be realized as two or more programs.

[0020] In the following description, various types of identification information are used, but the identification information may be any information that indicates a specific object, and the specific data is not limited to those described in the embodiments. The identification information may be an identification number or an identifier including letters and symbols.

[0021] [Embodiment] <Summary> An event support system 1 (see FIG. 1) according to this embodiment provides a service that supports the event planning work carried out by an event organizer using a client terminal 10. Among the event planning work, the event support system 1 mainly supports the matching work. "Matching work" refers to the work of matching the wishes of the event organizer with the availability of assets provided in the facility. Specifically, the matching work is a series of management tasks that arranges the assets and staff required to plan and implement an event with the content desired by the event organizer, and adjusts the schedules of both parties to optimally allocate them. As a service that supports the matching work, the event support system 1 automatically generates an allocation plan that optimally combines assets and staff.

[0022] That is, the server 20 of the event support system 1 receives event project information from the event organizer. Project information can be considered information indicating the event organizer's desired content for the event. The server 20 acquires facility information, including asset availability and usage fees, from one or more facility management systems 30. The server 20 also acquires human resource information, including the skills and schedules of staff who are potential participants in the event, which is pre-stored in the server 20's database 270 (see FIG. 4 ) or acquired in conjunction with an external attendance management system. Based on this information, the server 20 then searches for combinations of assets and staff that meet the requirements of the project information (desired period, area, required skills, number of staff, etc.). Furthermore, the server 20 calculates predicted sales, costs (asset usage fees, labor costs, etc.), and profits for the searched combinations and identifies an allocation plan that will maximize the profit for the event organizer. The server 20 presents the identified allocation plan or multiple candidate allocation plans to the client terminal 10.

[0023] This will automate the matching process, which was previously performed inefficiently and manually, significantly improving the efficiency of event planning work and preventing opportunity loss.

[0024] <System configuration> FIG. 1 is a diagram illustrating an example of the overall configuration of an event support system 1. The event support system 1 is an example of a system according to one aspect of the present disclosure. As shown in FIG. 1, the event support system 1 includes one or more client terminals 10 operated by an event organizer, a server 20 that provides the main functions of the event support processing according to this embodiment, and one or more facility management systems 30 used by each facility. The client terminals 10, the server 20, and the facility management systems 30 are connected to each other so as to be able to communicate with each other via a network 40 such as the Internet or a LAN (Local Area Network).

[0025] The client terminal 10 provides a user interface (UI) for the event organizer to use the functions of the server 20. For example, the client terminal 10 is an information processing device such as a personal computer (PC), a tablet terminal, or a smartphone. The client terminal 10 accesses the server 20 via a web browser, dedicated application software, or the like, and performs operations such as registering project information (described later), checking progress (see FIG. 11), and viewing allocation plans (see FIG. 12).

[0026] The server 20 is an example of an information processing device according to an embodiment of the present disclosure, and functions as an event support device by executing an event support program 205 (see FIG. 4). The event support program 205 is application software for executing and managing services provided by the event support system 1.

[0027] The server 20 generates an allocation plan when it acquires project information from the client terminal 10, and presents it to the client terminal 10. Details of the project information and the allocation plan will be described later. The server 20 also executes a provisional reservation process based on the allocation plan, an automatic document data generation process, a progress management process, and a settlement process after the event is held. Note that it is not essential for the server 20 to execute these various processes after the allocation plan is determined.

[0028] The server 20 may be a single physical computer, or may be a cloud computing system in which multiple computers function in cooperation with one another.

[0029] The facility management system 30 is an existing system used by each facility to manage the reservation status, usage fees, etc. of its own assets. In response to a request from the server 20, the facility management system 30 provides the server 20 with facility information, which will be described later, via an API (Application Programming Interface).

[0030] It is not essential that the facility management system 30 owns and manages the facility information. Alternatively, for example, another external system (not shown) linked to the facility management system 30 may own the facility information. Alternatively, for example, the server 20 may own and manage the facility information in advance. In this case, the facility management system 30 is not necessary, and the event support system 1 is composed of the client terminal 10 and the server 20.

[0031] <Terminal Device> Fig. 2 is a block diagram showing an example of the hardware configuration of the client terminal 10. As shown in Fig. 2, the client terminal 10 includes a control unit 101 which is a processor such as a CPU or a GPU, a storage unit 102 which includes a ROM (Read Only Memory), a RAM (Random Access Memory), etc., a communication unit 103 for communicating with the network 40, an input unit 104 (e.g., a keyboard, a mouse, a touch panel) for accepting operations from the event organizer, and an output unit 105 (e.g., a liquid crystal display) for displaying information. The blocks included in the client terminal 10 are electrically connected, for example, by a bus or the like.

[0032] The control unit 101 comprehensively controls the operation of the client terminal 10 by executing a program (for example, a web browser or a dedicated application) not shown stored in the storage unit 102. Specifically, as shown in Fig. 3, the control unit 101 functions as an operation reception unit 111 that receives operations from the event organizer via the input unit 104, as a transmission / reception unit 112 that transmits and receives various information to and from the server 20 via the communication unit 103, and as a presentation control unit 113 that displays the information received from the server 20 on the output unit 105.

[0033] <server> Fig. 4 is a block diagram showing an example of the hardware configuration of server 20. As shown in Fig. 4, server 20 includes a control unit 201 which is a processor such as a CPU or a GPU, a storage unit 202 which includes a ROM, a RAM, etc., a communication unit 203 for communicating with network 40, and an input / output IF 204. The blocks included in server 20 are electrically connected by, for example, a bus or the like.

[0034] The control unit 201 is an example of a processor according to an embodiment of the present disclosure. The control unit 201 executes an event support program 205 stored in the storage unit 202 to operate as each functional block in FIG. 5 (described later) and comprehensively control the operation of the server 20. The storage unit 202 stores a database 270 in addition to the event support program 205. The database 270 is made up of a project management table 501, a facility management table 502, a human resource management table 503, an allocation plan management table 504, and a performance management table 505. Details of each of these tables will be described later.

[0035] 5 is a block diagram showing the functional units realized by the control unit 201. By executing the event support program 205, the control unit 201 mainly functions as a communication control unit 210, an information acquisition unit 220, a plan specification unit 230, an information presentation unit 240, an execution control unit 250, and a management unit 260.

[0036] The communication control unit 210 controls communication between the client terminal 10 and the facility management system 30 via the communication unit 203 .

[0037] The information acquisition unit 220 acquires various information necessary for generating an allocation plan. Specifically, the information acquisition unit 220 accepts and acquires the project information input by the event organizer from the client terminal 10, and stores the project information in the project management table 501.

[0038] "Project information" is information that defines the requirements for implementing an event. The project information includes at least the planned content of the event, the desired period and area for the event, and the skills and number of staff required to implement the event.

[0039] "Planning content" (synonymous with "event planning") is information that indicates the outline of the event, such as "promotion of new mobile product XX", the purpose, a text description of the event content, the target demographic, the products being handled, etc.

[0040] The "desired period for holding the event" is information indicating a specific date or a range of dates for which the event is desired to be held, such as "December 1, 2025 to December 7, 2025."

[0041] The "area where the event is desired to be held" is information indicating the geographical range in which the event is desired to be held, such as at the city, ward, town, or village level, such as "all of Chiba Prefecture" or "Shibuya Ward, Tokyo," or at the prefecture level, or at the floor level within a specific facility, such as "1st floor of △△ Mall."

[0042] "Necessary staff skills" refers to information that indicates the abilities, qualifications, experience, etc. of personnel required to carry out the event. Examples include "cash register operation," "apparel customer service," "foreign language support (English)," and "vehicle driving."

[0043] The "number of staff required" refers to the number of people required to carry out the event, and skills and numbers may be associated, for example, in the form of "two people with cash register operation skills" or "three people with apparel customer service skills."

[0044] Furthermore, the information acquisition unit 220, triggered by the receipt of case information or the like, requests facility information via the API from one or more facility management systems 30. Then, the information acquisition unit 220 acquires the facility information from the one or more facility management systems 30. The information acquisition unit 220 temporarily or permanently stores the acquired facility information in the facility management table 502.

[0045] "Facility information" is information that defines the physical, temporal, and financial conditions of the location where the event will be held. The facility information includes at least the availability status and usage fees for each of the multiple assets provided in the facility.

[0046] For example, commercial facilities are facilities that are the target of services provided by the event support system 1. Commercial facilities are facilities used for the purpose of selling various products or providing various services, and include, for example, shopping malls, department stores, retail stores, clinic malls, amusement facilities, etc.

[0047] However, the aforementioned facilities are not limited to commercial facilities, but include any facility where space can be rented out for temporary use.Specific examples include commercial facilities, transportation hubs (e.g., train stations, airport terminal buildings, expressway service or parking areas, roadside stations), public / cultural facilities (e.g., halls in government buildings such as city halls or ward offices, parks, library or museum entrances), accommodation / customer attraction facilities (e.g., hotel lobbies or banquet halls, event venues, exhibition halls or halls, stadium or arena concourses), and educational institutions (e.g., plazas or student halls on university campuses).

[0048] An "asset" refers to a specific space that can be used to hold an event. Examples of assets include sections, entrances, corridors, halls, and rest areas. Specifically, assets include "Event Space A on the first floor of △△ Mall" and "Event Hall on the first basement floor of □□ Department Store."

[0049] The "availability status" is information indicating whether a specific asset is available for reservation at a specific date and time. For example, it is obtained as real-time availability status in conjunction with calendar information or reservation ledger information of the facility management system 30.

[0050] "Usage fee" is the cost required to use an asset for a specific period of time, and is monetary information such as "50,000 yen per day" or "8,000 yen per hour."

[0051] The information acquisition unit 220 also acquires human resource information. The human resource information is read from, for example, a human resource management table 503 stored in the database 270 of the server 20. Alternatively, the information acquisition unit 220 may link with an existing attendance management system, a shift management system, or an external human resource management system provided by a staffing agency, etc., used by the event organizer via an API, and acquire human resource information (staff skills, schedules, etc.) from these external systems in real time or periodically.

[0052] "Human resource information" defines information about the capabilities and schedules of personnel (staff) who can participate in the implementation of the event. Human resource information includes at least the skills and schedules of each of multiple staff members who are candidates to participate in the event.

[0053] "Candidate staff" refers to personnel who may participate in the implementation of the event. "Skills" refers to information indicating the abilities, qualifications, experience, etc. possessed by each staff member, and corresponds to the "required staff skills" in the project information (e.g., "cash register operation" or "apparel customer service"). "Schedule" refers to calendar information or shift information that indicates the dates and times when each staff member is available to work, or the dates and times when they are already assigned to other tasks.

[0054] The plan specification unit 230 generates an allocation plan based on the acquired job information, facility information, and human resource information. Specifically, the plan specification unit 230 uses at least a portion of the acquired job information as a constraint condition and compares the acquired facility information and human resource information with the constraint condition. In this way, the plan specification unit 230 searches for combinations of assets that satisfy the constraint condition and staff who are candidates to participate in the event.

[0055] An "allocation plan" is an execution plan that specifically defines which assets will be used on which dates and which staff will be deployed on which dates for an event corresponding to specific project information.

[0056] "Constraint conditions" are conditions derived from the project information that are used to narrow down the candidate combinations to be searched. For example, if the "desired period to hold the event" and "desired area to hold the event" in the project information are used as constraint conditions, the plan specification unit 230 extracts only assets that are available (vacant) during that period and that are located in that area. In addition, the plan specification unit 230 extracts only staff who are available to work during that period. In this way, not all of the information included in the project information (e.g., project content) may be used as constraint conditions; only some of the information (e.g., period, area, skills) may be used as constraint conditions. "Matching" refers to the process of comparing the constraint conditions with facility information and human resource information to determine whether the conditions are met.

[0057] Furthermore, the plan specifying unit 230 calculates an evaluation index for each of the one or more combinations obtained by the search, by using a predetermined algorithm.

[0058] The "predetermined algorithm" refers to a calculation logic, formula, or model for quantifying the quality of a combination of assets and staff. In this embodiment, the algorithm evaluates at least one of the expected costs and benefits of holding an event.

[0059] "Cost" refers to the total amount of expenses required to carry out the event, and includes at least the usage fee for facility information and personnel costs based on human resource information.

[0060] "Profit" is the revenue predicted to be obtained by holding the event, and is calculated, for example, as the value obtained by subtracting costs from sales, which will be described later.

[0061] An "evaluation index" is an index that quantitatively indicates the quality of a combination of assets and staff. There are no particular limitations on the way in which the evaluation index is presented, and it may be a numerical value or a rank. In this embodiment, profit is used as the evaluation index and is presented as a numerical value. Note that sales itself, which is one of the indexes for evaluating costs or profits, may also be used as the evaluation index. In other words, the evaluation index may be any index that evaluates at least one of the costs and profits predicted when an event is held.

[0062] As an example, the predetermined algorithm may be an algorithm that calculates profit as an evaluation index based on at least one of usage fees, costs including labor costs, predicted sales, and past event performance at the asset. "Sales" refers to the sales amount predicted to be obtained when an event is held with a specific combination of assets and staff. "Event performance" refers to various performance data (e.g., sales, number of visitors) from events held at the asset in the past.

[0063] Furthermore, for example, sales may be calculated based on at least one of the number of visitors to past events similar to the current event and past people flow data for the asset. "Similar past events" refer to events in the same area, in the same industry, and on the same scale, for example. "People flow data" refers to statistical data such as the number of people passing by by time of day and day of the week in the vicinity of the asset or in the entire facility.

[0064] The plan specification unit 230 refers to this performance data and predicts sales using an AI algorithm (machine learning model, statistical model, etc.). Examples of applicable AI algorithms include regression models such as random forest, gradient boosting, and support vector machine (SVM), or neural network models using deep learning, and Bayesian statistical models. These AI models may be included in the server 20, or may be included in an AI system (not shown) (e.g., a server dedicated to AI processing, a cloud AI service, etc.) connected to the server 20 via the network 40, and the event support system 1 may be configured to include such an AI system.

[0065] Furthermore, the plan specifying unit 230 specifies the combination with the best calculated evaluation index from among the one or more combinations obtained by the search, and sets the combination as the allocation plan.

[0066] "The evaluation index is the best" means that the evaluation index set according to the purpose of the event organizer is optimized. One of the technical significances of this disclosure is that the definition of "best" (type of evaluation index and direction of optimization) can be flexibly set according to the business purpose of the event organizer.

[0067] Specifically, for example, if the event organizer places the highest priority on profitability, the plan specifying unit 230 uses "profit" (= sales - cost) as the evaluation index and identifies the combination with the highest "profit" as the combination with the "best evaluation index." Alternatively, for example, if the event organizer places the highest priority on strict budget adherence, the plan specifying unit 230 uses "cost" as the evaluation index and identifies the combination with the lowest "cost" (or a combination that satisfies a predetermined budget upper limit (constraint) included in the project information) as the combination with the "best evaluation index." Furthermore, if the event organizer places the highest priority on increasing brand awareness or exposure, the plan specifying unit 230 uses "sales" (or "number of visitors" or "predicted number of people who can be contacted based on people flow data") as the evaluation index and identifies the combination with the highest "sales" as the "best" combination.

[0068] In this way, by being able to select and set the evaluation index to be optimized and the direction of that evaluation index (maximization, minimization) according to the diverse business needs of event organizers, it becomes possible to automatically generate and present allocation plans that go beyond a simple combination of assets and staff and truly contribute to the achievement of business objectives. Specifically, for example, if "profit" is used as the evaluation index, this means maximizing profit, and if "cost" is used, this means minimizing cost.

[0069] The information presenting unit 240 transmits the identified allocation plan (the best combination of assets and staff) to the client terminal 10 for presentation. In addition to the identified allocation plan and its evaluation index, the information presenting unit 240 may also execute a step of presenting to the client terminal 10 other combinations (for example, combinations with the second highest or third highest profits) among the combinations obtained by the search, whose evaluation indexes satisfy a predetermined threshold, and their evaluation indexes. The "predetermined threshold" is, for example, a reference value such as "80% or more of the plan with the top profit."

[0070] The execution control unit 250 controls various processes that are executed after the allocation plan is specified. Specifically, when the execution control unit 250 receives an approval operation for the presented allocation plan from the client terminal 10, it requests provisional reservation of the assets and staff included in the allocation plan.

[0071] "Requesting provisional reservation" means requesting a process to temporarily secure (reserve) an asset or staff schedule for the allocation plan. A request for an asset is made, for example, by an API call to the facility management system 30. A request for a staff member is realized, for example, by (i) updating the schedule of the relevant staff member managed in the human resource management table 503 to a "provisionally reserved" status, (ii) registering the plan in an external schedule management system via an API, or (iii) sending a notification to the staff member or a manager.

[0072] In addition, the execution control unit 250 extracts specified information necessary for asset usage applications or staff allocation from at least one of the acquired case information, facility information, human resource information, or the identified allocation plan, and generates document data including the extracted specified information.

[0073] "Documents containing prescribed information" refers to various forms and contracts required in the matching business and event implementation process. Specific examples include (i) "facility use application forms," ​​"event proposals," "(asset) use applications," and "lease agreements" to be submitted to facility managers; (ii) "service outsourcing contracts," "purchase orders," "purchase acceptance forms," ​​and "non-disclosure agreements (NDAs)" to be exchanged with assigned staff; and (iii) "quotes" to be submitted to event clients. "Prescribed information" refers to items required for document creation, such as the event plan, asset usage fees, staff names, and schedules.

[0074] Specifically, the execution control unit 250 embeds information extracted from at least one of the acquired case information, facility information, human resource information, or identified allocation plan into the corresponding location in template data of a specified format document (e.g., PDF, Word format, XML data).

[0075] Furthermore, after the event is held based on the allocation plan, the execution control unit 250 executes a settlement process and generates billing data. The settlement process determines the final costs incurred in holding the event based on the usage fees included in the facility information and labor costs based on the human resource information. For example, the costs are recalculated to reflect actual results such as an extension of asset usage or changes in staff working hours. "Billing data" is electronic data (e.g., PDF invoice, data for linking with accounting systems) used to bill the determined costs to relevant parties such as the event organizer and facility manager.

[0076] The management unit 260 associates the identified allocation plan with the project information, facility information, and human resource information that are the basis of the plan, and stores them in the allocation plan management table 504 as a single management unit.

[0077] The "single management unit" means a data structure that allows multiple pieces of information that have conventionally been managed separately to be handled as a single unit linked to a specific allocation plan (or project). For example, this is realized by having references (IDs) to the project management table 501, facility management table 502, and human resource management table 503 in the records of the allocation plan management table 504.

[0078] The management unit 260 also accepts updates to the progress status of this management unit and presents the updated progress status. The "progress status" is a status that indicates at what stage in the business process from planning to settlement the management unit (allocation plan) is. Examples of statuses include "plan proposed," "tentatively reserved," "event in progress," and "awaiting settlement." The management unit 260 updates the progress status in response to operations from the client terminal 10 or the like, or in response to the processing results of the control unit 201. The information presentation unit 240 presents the latest progress status (for example, by displaying it on the case list screen 700).

[0079] <Data Structure> 6 to 10 are diagrams showing examples of the data structure of each table included in database 270. Note that Figures 6 to 10 are merely examples and do not exclude data that is not listed. Furthermore, even data listed in the same table may be stored in separate storage areas in storage unit 202.

[0080] The tables shown in Figures 6 to 10 refer to a relational database, which is used to manage and associate data sets called tables, which are structured according to rows and columns. In a database, a table is called a table, a column in a table is called a column, and a row in a table is called a record. In a relational database, relationships between tables can be set and associated.

[0081] Typically, each table has a column set as a primary key for uniquely identifying a record, but setting a primary key to a column is not essential. The control unit 201 can cause the processor to add, delete, or update records in a specific table stored in the storage unit 202 according to various programs.

[0082] The database 270 is stored in the storage unit 202 and includes a case management table 501 , a facility management table 502 , a human resources management table 503 , an allocation plan management table 504 , and a performance management table 505 .

[0083] 6, the case management table 501 is a table for managing case information, and includes columns for case ID, case name, client name, project content, desired period (start), desired period (end), desired area, required skills, and required number of people. These columns store the case information received by the information acquisition unit 220 from the client terminal 10.

[0084] The "Project ID" column is a primary key used to uniquely identify each project, and stores identification information such as "A0001" and "A0002." The "Project Name" column stores the specific name of each event (e.g., "X Mobile New Product Promotion"). The "Client Name" column stores the name of the client of each event (e.g., "X Co., Ltd."). The "Plan Details" column stores text information indicating the overview, purpose, target demographic, etc. of each event (e.g., "Touch and try event for new product X. Targeted at women in their 20s..."). The "Desired Period (Start)" and "Desired Period (End)" columns store the event organizer's desired start and end dates for each event in date format (e.g., "2025-12-01," "2025-12-07"). The "Desired Area" column stores the name of the desired location for each event (e.g., "Shibuya Ward, Tokyo," "All of Chiba Prefecture," "1st Floor of X Mall"). The "Required Skills" column stores the staff skills required to run the event (e.g., "Cash register operation," "Apparel customer service," "English support"), for example, in JSON format or as a comma-separated string (e.g., "Cash register operation, English support"). The "Number of people required" column stores the number of people required for each skill (e.g., "2 people," "5 people") in a format that corresponds to the "Required Skills" column (e.g., "{"Cash register operation": 2, "English support": 1}" in JSON format).

[0085] 7, the facility management table 502 is a table for managing facility information and includes columns for asset ID, facility name, asset name, area information, calendar information, usage fee, and linked API information. These columns store facility information acquired by the information acquisition unit 220 from the facility management system 30. Note that if the event support system 1 does not include the facility management system 30, the facility information is stored in the facility management table 502 in advance.

[0086] The "Asset ID" column is a primary key for uniquely identifying each asset, and stores identification information such as "S0010" or "S0011." The "Facility Name" column stores the name of the facility to which the asset belongs (e.g., "△△ Mall," "□□ Department Store"). The "Asset Name" column stores the specific name of the asset (e.g., "Event Space A on the 1st floor," "Event Hall on the 1st basement floor"). The "Area Information" column stores address information indicating the location of the asset (e.g., "Shibuya-ku, Tokyo...") and latitude and longitude information. The "Calendar Information" column stores the real-time reservation status of the asset obtained from the facility management system 30 (e.g., a list of reserved dates and times in JSON format "[{"start":"2025-11-20,""end":"2025-11-22"},...]"). The "Usage Fee" column stores the asset usage fee (e.g., "50,000") along with the unit price (e.g., "yen / day") or as a numeric value. The "Linked API Information" column stores information required for real-time linkage with the facility management system 30 (e.g., API endpoint URL, authentication key).

[0087] 8, the human resource management table 503 is a table for managing human resource information, and includes columns for staff ID, name, affiliation, possessed skills, schedule, and unit labor cost. These columns store information on staff who are candidates to participate in the event, which has been registered in advance or obtained from an external system.

[0088] The "Staff ID" column is a primary key that uniquely identifies each staff member and stores identification information such as "STF001" and "STF002." The "Name" column stores the staff member's name (e.g., "Yamada X-ro"). The "Affiliation" column stores the staff member's affiliation (e.g., "Head Office Sales Department," "Team A," "Outsourced"). The "Possessed Skills" column stores the staff member's skills (e.g., "Cashier Operation," "Apparel Customer Service," "Foreign Language Support (English)") in JSON format, comma-separated strings, etc. The "Schedule" column stores information indicating the staff member's available dates and times, or the dates and times when they are already scheduled (e.g., a list of available dates and times in JSON format, or a reference ID to an external attendance management system or calendar system). The "Labor Cost Unit Price" column stores the staff member's hourly rate or daily allowance (e.g., "2000") that serves as the basis for cost calculation, along with the unit price (e.g., "yen / hour"), or as a numeric value.

[0089] 9, the allocation plan management table 504 is a table for managing the generated allocation plans, and includes columns for plan ID, project ID, asset ID, staff ID list, allocation date and time, evaluation index, and progress status. These columns store the processing results of the plan specification unit 230, execution control unit 250, and management unit 260. The "project ID," "asset ID," and "staff ID list" are associated as a single management unit.

[0090] The "Plan ID" column is a primary key for uniquely identifying each generated allocation plan, and stores identification information such as "P001A" (Plan A of Project A0001) or "P001B" (Plan B of Project A0001). The "Project ID" column stores a foreign key (e.g., "A0001") to the Project Management Table 501, indicating which project information each allocation plan corresponds to. The "Asset ID" column stores a foreign key (e.g., "S0010") to the Facility Management Table 502, indicating the asset assigned in each allocation plan. The "Staff ID List" column stores a list of foreign keys (e.g., a JSON array "["STF001", "STF005"]" or a comma-separated string) to the Human Resource Management Table 503, indicating the multiple staff members assigned in each allocation plan. The "Allocation Date and Time" column stores the specific start and end dates and times when each allocation plan is implemented (e.g., from "2025-12-04 10:00:00" to "2025-12-06 18:00:00"). The "Evaluation Index" column stores the numerical values ​​of each evaluation index calculated by the plan identification unit 230 (e.g., cost "500,000", sales "1,200,000", profit "700,000"). The "Progress Status" column stores values ​​indicating the current status of each allocation plan (e.g., "Plan Proposal in Progress", "Tentatively Reserved", "In Progress", "Settled").

[0091] 10, the performance management table 505 is a table for managing various performance data related to past events used to calculate evaluation indexes, and includes columns for performance ID, asset ID, type of business of the past event, number of visitors, sales performance, and people flow data. These data are referenced by the plan specification unit 230.

[0092] The "Actual ID" column is a primary key for uniquely identifying the performance data of each past event, and stores identification information such as "R001" and "R002." The "Asset ID" column stores a foreign key (e.g., "S0010") to the facility management table 502, indicating which asset each past event occurred at. The "Past Event Industry" column stores the industry of each past event (e.g., "Apparel," "Food Sales," "Mobile Phone Promotion"), which the sales forecasting AI model uses to determine similarity. The "Number of Visitors" column stores the actual number of visitors to each past event (e.g., "3,000" (people / 3 days)). The "Sales Actual" column stores the actual sales amount of past events (e.g., "1,500,000" (yen)). The "People Flow Data" column stores statistical data such as foot traffic volume around the asset (e.g., average foot traffic volume by day of the week and time period in JSON format: {"weekday":{"10-12":500,"12-14":800,···},"holiday":{···}}").

[0093] <Screen example> FIG. 11 is a diagram showing an example of a project list screen 700 displayed on the client terminal 10. The project list screen 700 is a user interface that presents a list of registered projects related to events and their progress status. The project list screen 700 includes a project name display field 701, a client name display field 702, an area display field 703, a period display field 704, and a progress status display field 705. The project name display field 701 displays the specific name of each event. The client name display field 702 displays the name of the client who requested each event. The area display field 703 displays the name of the desired venue for each event or the name of the actual venue. The period display field 704 displays the desired start date and desired end date, or the actual start date and actual end date, of each event. The progress status display field 705 displays the progress status managed by the management unit 260, such as "matching," "tentatively reserved," "ongoing," and "settlement completed."

[0094] 12 is a diagram showing an example of an allocation plan screen 800 displayed on the client terminal 10. The allocation plan screen 800 is a user interface that presents the allocation plan identified by the plan identification unit 230 and candidate allocation plans. The allocation plan screen 800 includes an asset display area 801, a timeline display area 802, candidate plan tabs 803 and 804, and an evaluation index display area 805.

[0095] The asset display area 801 displays a floor map (or map data), and an asset area 8011 on the floor map is highlighted. The timeline display area 802 displays a timeline that visualizes the schedules of the assigned staff. The plan candidate tabs 803 (Plan A) and 804 (Plan B) are tabs that show multiple allocation plan candidates with good evaluation indicators (two candidates, Plan A and Plan B, in the example of FIG. 12). When the event organizer selects a tab, the displays of the asset display area 801, timeline display area 802, and evaluation indicator display area 805 change depending on the contents of the selected allocation plan. The evaluation indicator display area 805 displays evaluation indicators such as the predicted sales, predicted costs, and predicted profits of the allocation plan.

[0096] <Operation> An example of the operation of the server 20 when executing the event support process will be described with reference to the flowcharts of Figures 13 to 15. In this example of operation, the event support process is assumed to be composed of an allocation plan specification process, a provisional reservation process, a document creation process, a settlement process, and a management process. Note that it is not essential for the server 20 to execute the provisional reservation process, the document creation process, the settlement process, and the management process. The server 20 only needs to execute at least the allocation plan specification process.

[0097] FIG. 13 is a flowchart showing an example of the operation of the server 20 when executing the allocation plan specifying process.

[0098] First, in step S101 (acquisition step), the information acquisition unit 220 of the server 20 accepts and acquires the case information sent from the client terminal 10. This acceptance is received, for example, as a POST request of HTTP (Hypertext Transfer Protocol). The information acquisition unit 220 executes a verification process on the received case information to check for missing required fields, errors in the data format, etc. If the verification results in no deficiencies, the information acquisition unit 220 executes an INSERT statement in the well-known SQL (Structured Query Language), writes the received case information into the case management table 501, and assigns a unique case ID.

[0099] Next, in step S102 (acquisition step), the information acquisition unit 220 acquires facility information and human resource information based on the job information received in step S901. Specifically, the information acquisition unit 220 refers to the facility management table 502 based on the desired area information included in the job information, and identifies a list of facilities that exist in the area corresponding to the desired area, and the linked API information of each facility (for example, API endpoint URL, authentication key, etc.).

[0100] Next, the information acquisition unit 220 sends an API request, such as an HTTP GET request, including, as a parameter, information about the desired period included in the project information, to the API endpoint of the identified one or more facility management systems 30. The one or more facility management systems 30 return facility information, including the asset availability status and usage fees for the requested period, to the server 20 in a data format such as JSON (JavaScript Object Notation) or XML (Extensible Markup Language). The information acquisition unit 220 analyzes the received JSON, XML, or other data and stores or updates it in the facility management table 502.

[0101] Furthermore, the information acquisition unit 220 acquires human resource information. Specifically, for example, the information acquisition unit 220 executes an SQL SELECT statement on the database 270. This SELECT statement uses the desired period and required skills included in the job information as constraints to extract a list of staff members who are available to work during the desired period and who possess the required skills from the human resource management table 503. Alternatively, the information acquisition unit 220 may send an API request to an external attendance management system, human resources management system, or the like, using the desired period and required skills as parameters, and acquire a list of staff members who meet the constraints as human resource information.

[0102] Next, in step S103 (searching step), the plan specifying unit 230 searches for a combination of assets and staff that satisfies the constraints based on the list of available assets and the list of available staff acquired in step S102. In the following explanation, a combination of assets and staff will be abbreviated as a "combination."

[0103] This search process is similar to a known combinatorial optimization problem (e.g., a resource-constrained scheduling problem or a multidimensional knapsack problem). The plan determination unit 230 uses known techniques such as constraint programming, integer programming, or a heuristic algorithm to efficiently enumerate one or more combinations that satisfy the constraint conditions from among a huge number of combinations.

[0104] Next, in step S104 (step of determining an allocation plan), the plan specifying unit 230 executes the following calculation process of evaluation indexes for the group of allocation plan candidates obtained by the search. The group of allocation plan candidates is composed of one or more combinations obtained by the search that satisfy the constraint conditions.

[0105] That is, the plan specifying unit 230 searches the database 270 based on the asset IDs and staff ID list included in the group of allocation plan candidates. Specifically, the plan specifying unit 230 obtains information indicating the usage fees of the assets that make up the combination from the facility management table 502. The plan specifying unit 230 also obtains information indicating the unit labor cost of each staff member that makes up the combination from the human resource management table 503. Then, the plan specifying unit 230 calculates the predicted cost of the combination as an evaluation index according to a predetermined algorithm (e.g., cost = (usage fee × number of days of use) + Σ (unit labor cost × operating time)). The plan specifying unit 230 performs this calculation process for all combinations that make up the group of allocation plan candidates.

[0106] Next, the plan specifying unit 230 predicts sales using a predetermined algorithm. The predetermined algorithm may be the AI ​​algorithm described above. In this case, the plan specifying unit 230 inputs the event information (e.g., industry, area) and facility information (e.g., asset ID) corresponding to the combination as input data to the AI ​​model. The AI ​​model calculates predicted sales as an evaluation index using information indicating past event results (e.g., number of visitors and sales results for similar events) stored in the results management table 505 or internal parameters learned based on people flow data. The plan specifying unit 230 executes this calculation process for all combinations constituting the candidate group for the allocation plan. This calculation process may be executed within the server 20, or the server 20 may request processing from an AI system (with an AI model built in) and receive the predicted sales as the processing result.

[0107] Next, the plan specifying unit 230 calculates the predicted profit as the final evaluation index according to a predetermined algorithm (e.g., profit = sales - cost) (calculating step). The plan specifying unit 230 associates each of the calculated evaluation indexes of predicted cost, predicted sales, and predicted profit with each combination constituting the group of allocation plan candidates, and temporarily stores them in the allocation plan management table 504.

[0108] Next, in step S105 (step of determining an allocation plan), the plan determination unit 230 determines the best combination to be the allocation plan based on the evaluation indexes temporarily stored in the allocation plan management table 504. This determination process is realized, for example, by the plan determination unit 230 executing an SQL query that sorts the predicted profit, which is the final evaluation index, in descending order and acquiring the first record.

[0109] Next, in step S106, the information presenting unit 240 acquires the allocation plan identified in step S105 and candidate allocation plans (e.g., the allocation plans with the second and third highest profits) whose evaluation indexes satisfy a predetermined threshold value from the allocation plan management table 504. The information presenting unit 240 acquires detailed information (e.g., name, map information, staff name, etc.) from related tables (project management table 501, facility management table 502, human resource management table 503) based on the ID of each allocation plan. Then, the information presenting unit 240 formats this information into data in JSON format or the like that can be rendered on the allocation plan screen 800 (see FIG. 12) of the client terminal 10, and transmits the data to the client terminal 10 as an HTTP response. Note that it is not essential that other candidate plans be presented to the client terminal 10; for example, the information presenting unit 240 may cause the client terminal 10 to present only the allocation plan identified in step S105.

[0110] FIG. 14 is a flowchart showing an example of the operation of the server 20 when executing the temporary reservation process and the document generation process.

[0111] First, in step S201, the execution control unit 250 of the server 20 accepts an approval operation for the identified allocation plan (plan ID) as an HTTP request. This HTTP request is transmitted to the server 20 by, for example, a user operation (e.g., pressing the approve button) on the allocation plan screen 800 (see FIG. 12) displayed on the client terminal 10.

[0112] Next, in step S202, the execution control unit 250 refers to the allocation plan management table 504 based on the received plan ID, and identifies the asset ID and staff ID list included in the corresponding allocation plan. Then, the execution control unit 250 requests a tentative reservation via the API from the facility management system 30 corresponding to the identified asset ID. Furthermore, based on the identified staff ID list, the execution control unit 250 updates the schedule column of the corresponding staff member in the human resource management table 503 to a "tentative reservation" status.

[0113] Next, in step S203, the execution control unit 250 searches the database 270 based on the approved plan ID and the related case ID. Then, the execution control unit 250 extracts predetermined information to be incorporated into template data for a document (e.g., a usage application form or a business contract) from at least one of the case information (e.g., project details), facility information (e.g., usage fee), human resource information (e.g., staff name), or allocation plan (e.g., usage date and time).

[0114] Next, in step S204, the execution control unit 250 uses a publicly known library to incorporate the extracted predetermined information into document template data to generate document data. The generated document data may be sent to the client terminal 10 or may be stored in a predetermined storage area.

[0115] 15 is a flowchart showing an example of the operation of the server 20 when executing the settlement process and management process. Note that the processing order of steps S301 to S306 described below is not limited to the example of FIG. 15 and can be changed as appropriate.

[0116] First, in step S301, the management unit 260 of the server 20 associates the identified allocation plan (plan ID) with the corresponding case information (case ID), facility information (asset ID), and human resource information (staff ID list), and stores them in the allocation plan management table 504 as a single management unit.

[0117] Next, in step S302, the management unit 260 receives notification of the completion of the tentative reservation process or a status change operation from the client terminal 10, and updates the information stored in the "progress status" column of the allocation plan management table 504 (e.g., updates from "matching in progress" to "tentative reservation").

[0118] Next, in step S303, the information presenter 240 transmits data including the updated progress status ("tentative reservation") to the client terminal 10, and updates the display of the case list screen 700 (see FIG. 11).

[0119] Next, in step S304, the event is carried out based on the allocation plan, and a completion report or performance information (for example, actual operation time) is received from the client terminal 10 or the like.

[0120] Next, in step S305, the executive control unit 250 recalculates the "usage fee" of the facility information and the "unit labor cost" of the human resource information based on the results of the event (performance information), and executes a settlement process to determine the final costs.

[0121] Next, in step S306, the executive control unit 250 generates billing data for the event organizer, facility manager, etc. based on the settlement result, and transmits it to the accounting system, payment system, etc.

[0122] <Summary> As described above, according to this embodiment, the server 20 centrally acquires project information, facility information, and human resource information, searches for combinations based on constraints, calculates evaluation indexes using a predetermined algorithm, and identifies allocation plans. This makes it possible to automate and optimize the inefficient matching work that previously relied on the manpower of event organizers, significantly improving work efficiency and reducing opportunity losses.

[0123] In addition, by presenting multiple allocation plan candidates, the system can support event organizers in making their final decision. Furthermore, because the system can seamlessly execute provisional reservations, document generation, and settlement based on the identified plan, the entire process from event planning to implementation and settlement is made more efficient. Furthermore, by treating related information as a single management unit and displaying its progress, the system can improve the visibility of project management, which was previously cumbersome, and significantly simplify management tasks.

[0124] [Modification] The above-described embodiment is merely an example of the present disclosure, and various modifications are possible without departing from the spirit of the invention.

[0125] <First Modification> For example, in the above embodiment, an example was shown in which a predetermined algorithm calculates profit as the final evaluation index, but this is not limiting. As described above, at least one of the costs, sales, and profits predicted by holding the event is used as the evaluation index.

[0126] The cost is calculated as a predicted cost, which is the total value of, for example, the asset usage fee obtained from the facility management table 502 and the labor cost based on the labor cost unit and assigned time (schedule) of each staff member obtained from the human resource management table 503. In addition to these, the predicted cost may be calculated by taking into account various expenses such as equipment rental costs, transportation costs, and travel costs included in the project information.

[0127] Sales are predicted sales calculated using a specified AI algorithm or statistical model based on, for example, past event results stored in the performance management table 505 (e.g., similar industries, past sales data for the same asset, number of visitors), and people flow data obtainable from outside (e.g., traffic volume around the asset by day of the week and time of day).

[0128] The predetermined algorithm may be a simple rule-based algorithm (e.g., extracting items whose costs are below a predetermined amount and that satisfy skill requirements) or the AI ​​algorithm described above. When an AI algorithm is used, the plan specifying unit 230 or an AI system (not shown) can generate a more complex and optimal allocation plan that maximizes the profits of the entire event based on a variety of data such as predicted sales, predicted number of visitors, and past event performance.

[0129] Specifically, the plan specification unit 230 uses, as an AI algorithm, an AI model such as multiple regression analysis, random forest, gradient boosting, support vector machine, or a neural network model using deep learning. This AI model is trained in advance using past event data (e.g., asset ID, industry, period, number of staff deployed, skills, weather, sales, number of visitors, people flow data, etc.) stored in the performance management table 505 as training data.

[0130] The plan identification unit 230 inputs the combinations obtained by the search (asset ID, staff skills, number of staff, period, etc.), project information (plan content, industry, etc.), and related data (e.g., weather forecast) obtained from external systems, etc., into the AI ​​model as input data. Based on this input data, the AI ​​model outputs predicted values ​​for sales and / or number of visitors when an event is held using the combinations obtained by the search as an allocation plan.

[0131] When the server 20 cooperates with an AI system, the plan determination unit 230 transmits the input data described above to the AI ​​system in JSON format, for example, via a REST (Representational State Transfer) API. The AI ​​system executes a prediction process and returns the prediction results (e.g., predicted sales) to the server 20 in JSON format. The plan determination unit 230 uses the prediction results and the calculated predicted costs to calculate predicted profits as the final evaluation index. This makes it possible to determine a truly optimal allocation plan based on highly accurate demand and revenue forecasts that take into account a variety of factors (asset characteristics, staff skill composition, time of year, weather, etc.) that would be difficult to achieve manually.

[0132] <Second Modification> Furthermore, for example, in the above embodiment, an example was shown in which facility information was automatically acquired from the facility management system 30 and human resource information was automatically acquired from the database 270, but the present invention is not limited to this.

[0133] In particular, human resource information may be acquired from a variety of sources. For example, the information acquisition unit 220 may be configured to link via API with an external attendance management system, calendar system, or personnel management system that the event organizer uses on a daily basis, or a temporary staff management system provided by a staffing agency. This link is realized, for example, by establishing a secure connection using an authentication protocol such as OAuth, and then acquiring staff schedules (availability, plans) and skill information for a predetermined period (the desired period of the project information) in JSON format, iCal format, or the like via a REST API.

[0134] Alternatively, the information acquisition unit 220 may accept manual input of human resource information by the event organizer via the client terminal 10. For example, the server 20 may provide the client terminal 10 with a screen for registering and editing staff master information (e.g., inputting staff ID, name, possessed skills, and labor cost unit price), and a user interface for manually inputting and updating staff work schedules in calendar format. In this case, the server 20 stores the input information in the human resource management table 503.

[0135] It is also possible to use a configuration that combines automatic acquisition via API integration with manual input (for example, full-time employee schedules are automatically acquired from an attendance management system, while part-time and external staff schedules are manually entered and corrected). This makes it possible to accommodate event operators with a variety of employment types and management systems, and to flexibly acquire comprehensive and up-to-date human resource information.

[0136] <Third Modification> Furthermore, for example, the client terminal 10 used to present the allocation plan and the client terminal 10 used to input the case information may be the same information processing device, or may be different information processing devices.

[0137] For example, within an organization of an event organizer, it is assumed that the task of registering and inputting a project and the task of approving and deciding on an allocation plan are performed by different personnel. In this case, the person in charge of project registration inputs project information from their own PC (client terminal 10). Then, once an allocation plan is identified, the information presentation unit 240 sends an approval request by push notification or email to another smartphone or tablet terminal (client terminal 10) owned by a manager with approval authority. The manager accesses the allocation plan screen 800 (see FIG. 12) from their own smartphone or other device and compares and considers the presented multiple allocation plan candidates and their respective evaluation indicators. Then, the manager performs an approval operation on their own smartphone or other device for the allocation plan they determine to be optimal.

[0138] In this way, by configuring the input of project information and the presentation and approval of allocation plans to be performed on different client terminals 10 operated by different users, more efficient and practical system operation can be achieved that is in line with the actual business flow (division of roles) of the event organizer.

[0139] Although several embodiments of the present disclosure have been described above, these embodiments can be embodied in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and modifications are intended to be included in the scope of the inventions and their equivalents as defined in the claims, as well as in the scope and spirit of the inventions.

[0140] [Note] The matters described in the above embodiments will be supplemented below.

[0141] <Appendix 1> A program to be executed by a computer having a processor, causing the processor to execute the following steps: acquiring project information including the planned content of the event, the desired period and area for holding the event, and the skills and number of staff required to carry out the event; facility information including the availability and usage fees for each of multiple assets provided in the facility; and human resource information including the skills and schedules of each of multiple staff members who are candidates to participate in the event; using at least a portion of the acquired project information as a constraint condition, and comparing the acquired facility information and human resource information with the constraint condition to search for combinations of assets and staff members who are candidates to participate in the event that satisfy the constraint condition; and using a predetermined algorithm for one or more combinations obtained by the search, calculating an evaluation index that evaluates at least one of the predicted costs and profits if the event is held, and identifying the combination with the best calculated evaluation index from the one or more combinations obtained by the search and creating an allocation plan.

[0142] <Appendix 2> The program described in (Appendix 1), wherein the predetermined algorithm is an algorithm that calculates profit as an evaluation indicator based on at least one of costs including usage fees and labor costs based on human resource information, predicted sales if an event is held, and past event performance of the asset.

[0143] <Appendix 3> The program described in (Appendix 2) in which sales are calculated based on at least one of the number of visitors to past events similar to the event and past foot traffic data at the asset.

[0144] <Appendix 4> A program described in any of (Appendix 1) to (Appendix 3), which further causes the processor to execute a step of presenting to the client terminal, in addition to the identified allocation plan and the evaluation index of the allocation plan, other combinations among one or more combinations obtained by the search whose evaluation indexes satisfy a predetermined threshold, and the evaluation indexes of the other combinations.

[0145] <Appendix 5> A program described in any of (Appendix 1) to (Appendix 4), which, when an approval operation for the identified allocation plan is received, further causes the processor to execute a step of requesting provisional reservation of assets and staff included in the allocation plan.

[0146] <Appendix 6> A program described in any one of (Appendix 1) to (Appendix 5), which further causes the processor to execute a step of extracting specified information necessary for asset utilization applications or staff allocation from at least one of the acquired project information, facility information, or human resource information, or the identified allocation plan, and generating document data including the extracted specified information.

[0147] <Appendix 7> A program described in any of (Appendix 1) to (Appendix 6), which further causes the processor to execute a step of performing settlement processing based on usage fees and labor costs based on human resource information after an event based on the allocation plan is implemented, and generating billing data.

[0148] <Appendix 8> A program described in any of (Appendix 1) to (Appendix 7), which further causes the processor to execute the steps of associating project information, facility information, and human resource information with the identified allocation plan and storing them as a single management unit, and accepting updates to the progress of the management unit and presenting the updated progress.

[0149] <Appendix 9> An information processing device including a processor, the processor executing all steps in the program according to any one of (Supplementary Note 1) to (Supplementary Note 8).

[0150] <Appendix 10> A method executed by a computer having a processor, wherein the processor executes all steps in the program described in any one of (Appendix 1) to (Appendix 8).

[0151] <Appendix 11> A system comprising one or more processors that execute all steps in the program described in any one of (Appendix 1) to (Appendix 8). [Explanation of symbols]

[0152] 1...Event support system (system) 10...Client terminal 20...Server (information processing device) 30...Facility Management System 40…Network 101...Control unit (processor) 102...Storage section 103…Communications Department 104...input section 105...Output section 111...Operation reception desk 112...Transmitter / receiver 113...Presentation control unit 201...Control unit (processor) 202...Storage section 203…Communications Department 204...Input / output interface 205...Event Support Program (Program) 210...Communication control unit 220…Information acquisition department 230...Planning and Specific Department 240…Information presentation section 250...Executive control unit 260…Management Department 270...Database 501...Project management table 502...Facility management table 503...Human Resource Management Table 504...Allocation plan management table 505...Results management table 700...Project list screen 800...Allocation planning screen

Claims

1. A program to be executed by a computer having a processor, the processor, acquiring project information including the planned content of the event, the desired period and area for holding the event, the skills and number of staff required to carry out the event, facility information including the availability and usage fees of each of multiple assets provided in the facility, and human resource information including the skills and schedules of each of multiple staff members who are candidates to participate in the event; a step of searching for a combination of the asset and a staff member who is a candidate to participate in the event, which satisfies the constraint conditions by comparing the acquired facility information and the acquired human resource information with at least a part of the acquired project information as the constraint conditions; For one or more of the combinations found by the search, a cost is calculated as the sum of the asset usage fee included in the facility information and the labor cost calculated based on the operating time of the event and the labor cost unit price of staff who are candidates to participate in the event included in the human resource information, and an evaluation index is calculated to evaluate at least one of the costs and profits predicted when the event is held; and a step of identifying the combination with the best calculated evaluation index from the one or more combinations obtained by the search, and setting the combination as an allocation plan.

2. the evaluation index is the profit, The program of claim 1, wherein the calculating step calculates the costs and also calculates the predicted sales if the event is held based on at least one of the actual sales from past events at the asset and the number of visitors to past events similar to the event, and calculates the profit as the evaluation index by subtracting the costs from the sales.

3. The program according to claim 2 , wherein the calculating step further calculates the sales amount based on past people flow data for the asset.

4. The program of claim 1, further causing the processor to execute a step of presenting to the client terminal, in addition to the identified allocation plan and the evaluation index of the allocation plan, other combinations among the one or more combinations obtained by the search whose evaluation index satisfies a predetermined threshold, and the evaluation index of the other combinations.

5. The program according to claim 1 , further causing the processor to execute, when an approval operation for the identified allocation plan is received, a step of requesting provisional reservation of the assets and the staff included in the allocation plan.

6. The program of claim 1, further causing the processor to execute a step of extracting specified information necessary for applying for asset use or allocating staff from at least one of the acquired project information, facility information, or human resource information, or the identified allocation plan, and generating document data including the extracted specified information.

7. The program according to claim 1 , further causing the processor to execute a step of executing settlement processing based on the usage fee and labor costs based on the human resource information after the event based on the allocation plan is implemented, and generating billing data.

8. a step of associating the project information, the facility information, and the human resource information with the identified allocation plan and storing them as a single management unit; 2. The program according to claim 1, further causing the processor to execute a step of accepting an update of the progress status of the management unit and presenting the updated progress status.

9. 9. An information processing apparatus comprising a processor, the processor executing all steps of the program according to claim 1.

10. A method executed by a computer having a processor, the processor executing all the steps of the program of any one of claims 1 to 8.

11. A system comprising one or more processors that execute all steps in the program according to any one of claims 1 to 8.

Images