JP7546871B1 - Security guard reservation system - Google Patents

Abstract

To provide a security guard reservation system that is suitable for reflecting the needs of a client.
[Solution] Dispatch information relating to multiple periods, areas, and the number of people available for dispatch for each of the multiple periods when a security company can dispatch security guards is registered in association with security company information, request information relating to the area to which a construction contractor requests the dispatch of security guards is obtained, and based on the dispatch information corresponding to the area related to the obtained request information, multiple periods when dispatch is available and the number of people available for dispatch for each of the multiple periods are presented. Request information relating to the periods and number of people set by the construction contractor within the presented range of periods and number of people is obtained, the obtained request information is registered in association with construction contractor information, and based on the dispatch information and request information, security companies and construction contractors whose periods, areas, and number of people match those related to the dispatch information and request information are matched.
[Selection diagram] Figure 12

Description

Article 30, paragraph 2 of the Patent Act applies. Published on April 13, 2023 at https://hiken-ccs.com/login

The present invention relates to a system for reserving security guards, and in particular to a security guard reservation system that is suitable for reflecting the needs of clients.

Conventionally, a technology for reserving security guards is known, for example, as described in Patent Document 1.

The technology described in Patent Document 1 includes a security integration center that registers multiple security service providers as members and manages each security service provider and the services they provide in a member database. The security integration center accepts security requests from security service clients. When accepting a security request, the security integration center requests information such as 1) the security location, 2) the purpose of the security, 3) the content of the security, and 4) the target of the security. Based on the security location, purpose of the security, content of the security, and target provided by the security service client, the security integration center narrows down the security service providers that are optimal for the security location, purpose of the security, content of the security, and target of the security request based on the service content of each security service provider stored in the member database and the security information knowledge accumulated in the security information database. The security service request from the security service client is then notified to the narrowed down optimal security service provider.

JP 2002-175365 A ([0048] [0049])

However, the technology described in Patent Document 1 only narrows down security service providers based on the location, purpose, content, and target of security, which means that it has the problem of not being able to fully reflect the needs of the client.

Therefore, the present invention was made with a focus on these unresolved issues in the conventional technology, and aims to provide a security guard reservation system that is suitable for reflecting the needs of the client.

When requesting the dispatch of security guards, the requester would like to request not only the location to which the security guards are to be dispatched, as in the technology of Patent Document 1, but also one or more time periods and the number of people that can be dispatched for each of the one time period or multiple time periods. However, the technology of Patent Document 1 cannot reflect such requests. Therefore, the inventor has come up with the following invention to solve the above-mentioned conventional problems.

[Invention 1] In order to achieve the above object, the security guard reservation system of invention 1 includes a dispatch information registration means for registering dispatch information relating to one or more periods and locations when a dispatcher is able to dispatch security guards, and the number of people who can be dispatched for each of the one period or the multiple periods, in a dispatch information storage means in association with dispatcher information relating to the dispatcher; a first request information acquisition means for acquiring request information relating to a location where a requester requests the dispatch of the security guards; and a second request information acquisition means for acquiring request information relating to the one or more periods and the one or the multiple periods, based on the dispatch information in the dispatch information storage means corresponding to the location related to the request information acquired by the first request information acquisition means. a second request information acquisition means for acquiring request information related to the time and number of people set by the requester within the range of time and number of people presented by the dispatch information acquisition means; a request information registration means for registering the request information acquired by the first request information acquisition means and the second request information acquisition means in a request information storage means in association with requester information related to the requester; and a matching means for matching the dispatcher and the requester with the time, place and number of people related to the dispatch information and the request information based on the dispatch information in the dispatch information storage means and the request information in the request information storage means.

In this configuration, the dispatch information registration means registers in the dispatch information storage means dispatch information relating to one or more time periods and locations to which the dispatcher can dispatch security guards, and the number of people who can be dispatched for each of the one time period or the multiple time periods, in association with the dispatcher information.

The first request information acquisition means acquires request information relating to a location where a client requests the dispatch of security guards, and the dispatch information presentation means presents one or more time periods when dispatch is possible and the number of people that can be dispatched for each of the one or more time periods, based on the dispatch information in the dispatch information storage means that corresponds to the location related to the acquired request information. When the client sets a time period and number of people within the range of the presented time period and number of people, the second request information acquisition means acquires request information relating to the set time period and number of people, and the request information registration means registers the acquired request information in the request information storage means in association with client information. Then, the matching means matches a dispatcher and a client whose time, location and number of people related to the dispatch information and the request information are compatible, based on the dispatch information in the dispatch information storage means and the request information in the request information storage means.

Here, time includes, for example, a period of time separated by seconds, minutes, hours, am, pm, morning, midday, night, days, months, years, or any other units, or a point in time specified by seconds, minutes, hours, am, pm, morning, midday, night, days, months, years, or any other units.

Matching by the matching means includes, for example, (1) matching dispatch information and request information that match the time, location, and number of people, and registering them in the storage means; (2) matching dispatcher information and requester information that match the time, location, and number of people, and registering them in the storage means; (3) providing request information or requester information to the dispatcher's terminal, etc., of the dispatchers and requesters whose time, location, and number of people match; and (4) providing dispatch information or dispatcher information to the requester's terminal, etc., of the dispatchers and requesters whose time, location, and number of people match.

Furthermore, the dispatcher and the client may be natural persons or corporations.
The dispatch information and request information can be configured, for example, as information for identifying the time, location, or number of people (for example, link information such as a name, number, ID, code, URL, etc.). The dispatch information and request information can be configured, for example, as letters, numbers, figures, codes, symbols, images, sounds, and other information. The dispatch information and request information can be configured as keywords relating to the time, location, or number of people (for example, one or more keywords indicating part of the time, location, or number of people). The dispatch information and request information can be configured to have the same structure or format, or different structures or formats.

The dispatcher information can be configured, for example, as information for identifying the dispatcher (for example, a name, a number, an ID, a code, link information such as a URL). The dispatcher information can be configured, for example, as letters, numbers, figures, codes, symbols, images, sounds, or other information. The dispatcher information and the requester information can be configured as keywords related to the dispatcher (for example, one or more keywords indicating part of the dispatcher's name). The same applies to the requester information. The dispatcher information and the requester information can be configured to have the same structure or format, or different structures or formats.

The first request information acquisition means may, for example, input the request information from an input device or the like, acquire or receive the request information from an external terminal or the like, read the request information from a storage device or storage medium or the like, or generate or calculate the request information by information processing or the like. Therefore, acquisition includes at least input, acquisition, reception, reading (including search), generation and calculation. The same applies to the second request information acquisition means and to the concept of acquisition below.

The dispatch information storage means stores the dispatch information by any means and at any time, and may store the dispatch information in advance, or may not store the dispatch information in advance and may store the dispatch information by input from outside while the system is operating. The same applies to the request information storage means and to other storage means described below.

Storing dispatch information in association with dispatcher information includes, for example, (1) storing the dispatch information and dispatcher information in a direct association, such as by registering them in the same record, and (2) storing the information via one or more pieces of intermediate information, such as by providing a table for registering dispatch information and intermediate information in association with each other, and a table for registering dispatcher information and intermediate information in association with each other. In other words, any data structure can be adopted as long as the dispatch information can be traced from the dispatcher information. Note that it is sufficient for the dispatch information to be stored in the dispatch information storage means in association with the dispatcher information, and it is not necessarily required that the dispatcher information be stored in the dispatch information storage means. The same applies to storing request information in association with requester information, and to the concept of storing information in association with each other below.

The system may be realized as a single device, terminal, or other equipment, or as a network system in which multiple devices, terminals, or other equipment are communicatively connected. In the latter case, each component may belong to any one of the multiple devices, etc., as long as they are communicatively connected.

[Invention 2] Furthermore, the security guard reservation system of invention 2 is the security guard reservation system of invention 1, wherein the dispatch information is information regarding the one or more time periods and locations where dispatch is possible, and the number of qualified security guards and the number of unqualified security guards that the dispatcher can dispatch for each of the one time period or the multiple time periods, and the request information is information regarding the number of qualified security guards and the number of unqualified security guards that the requester requests to be dispatched for each of the one or more time periods and locations set.

In this configuration, the dispatch information registration means registers dispatch information related to one or more time periods and locations when the dispatcher can dispatch security guards, as well as the number of qualified security guards and the number of unqualified security guards that the dispatcher can dispatch for each of the one time period or the multiple time periods, in the dispatch information storage means in association with the dispatcher information.

The request information registration means also registers request information related to one or more time periods and locations set by the client, as well as the number of qualified security guards and the number of unqualified security guards requested by the client for each of the one time period or the multiple time periods, in the request information storage means in association with the client information.

[Invention 3] Furthermore, the security guard reservation system of invention 3 is the security guard reservation system of either invention 1 or 2, and further includes a material information acquisition means for acquiring material information regarding materials to be used by the client at the site where the security guard is to be deployed, and the request information registration means registers the material information acquired by the material information acquisition means in the material information storage means in association with the client information.

In this configuration, the material information acquisition means acquires material information related to the material, and the request information registration means registers the acquired material information in the material information storage means in association with the requester information.

[Invention 4] Furthermore, the security guard reservation system of invention 4 is the security guard reservation system of either invention 1 or 2, and further includes a contract information providing means for providing contract information to a dispatcher and a client matched by the matching means based on the dispatcher information of the dispatcher, or for providing contract information to a client based on the client information of the client, so that the dispatcher and the client can enter into a contract for dispatching the security guard.

In this configuration, the contract information providing means provides the dispatcher with contract information for the matched dispatcher and client to enter into a contract for dispatching security guards based on the dispatcher's dispatcher information, or provides the client with contract information based on the client's client information.

Here, providing the contract information to the dispatcher includes, for example, (1) providing the contract information to the dispatcher's terminal, (2) associating the contract information with the dispatcher's account information, and (3) instructing other terminals to execute these operations. The same applies to providing the contractor information to the requester.

[Invention 5] Furthermore, the security guard reservation system of invention 5 is a security guard reservation system of either invention 1 or 2, and further comprises a request information presentation means for presenting request items related to the request information based on the request information in the request information storage means, a request change information acquisition means for acquiring request change information related to changes to the request items presented by the request information presentation means, and a report information generation means for generating report information on the work performed by the dispatcher who dispatched the security guard based on the request information in the request information storage means and the request change information acquired by the request change information acquisition means.

In this configuration, the request information presentation means presents the requested items based on the request information in the request information storage means. When changes are made to the presented requested items, the request change information acquisition means acquires request change information related to the changes to the requested items, and the report information generation means generates report information on the work performed by the dispatcher who dispatched the security guards based on the request information and the request change information.

[Invention 6] Furthermore, the security guard reservation system of invention 6 is a security guard reservation system of either invention 1 or 2, and further comprises a request information presentation means for presenting request items related to the request information based on the request information in the request information storage means, a request change information acquisition means for acquiring request change information related to changes to the request items presented by the request information presentation means, and a cost information generation means for generating cost information for the work performed by the dispatcher by dispatching the security guard based on the request information in the request information storage means and the request change information acquired by the request change information acquisition means.

In this configuration, the request information presentation means presents the requested items based on the request information in the request information storage means. When changes are made to the presented requested items, the request change information acquisition means acquires request change information related to the changes to the requested items, and the cost information generation means generates cost information for the work performed by the dispatcher by dispatching the security guard based on the request information and the request change information.

As described above, the security guard reservation system of Invention 1 matches dispatchers and requesters whose dispatch information and request information are compatible in terms of time, location, and number of people, so that the requester's requests regarding the time, location, and number of security guards requested can be reflected more than in the past.

Furthermore, the security guard reservation system of Invention 2 can reflect requests regarding the number of qualified and unqualified security guards.

Furthermore, according to the security guard reservation system of Invention 3, materials can be set when requesting the dispatch of a security guard.

Furthermore, according to the security guard reservation system of Invention 4, contract information is provided to the dispatcher or the client, making the contract relatively easy.

Furthermore, with the security guard reservation system of invention 5, you can obtain work report information by making changes to the requested items.

Furthermore, with the security guard reservation system of invention 6, you can obtain cost information for the service by making changes to the request details.

FIG. 1 is a block diagram showing a configuration of a network system. 1 is a diagram showing the hardware configuration of a security guard reservation server 100. FIG. 1 is a diagram showing the data structures of a security company information table 400, a contractor information table 402, a dispatch information table 404, a request information table 406, an estimate information table 408, a request change information table 410, a report information table 412, a billing information table 414, and a material information table 416. 13 is a flowchart showing a security company information registration process. This is the screen that is displayed when logging in to the security guard reservation server 100 using a security company account. This is the screen that is displayed when logging in to the security guard reservation server 100 using a security company account. 13 is a flowchart showing a contractor information registration process. This is the screen that is displayed when logging in to the security guard reservation server 100 using a contractor's account. This is the screen that is displayed when logging in to the security guard reservation server 100 using a contractor's account. 13 is a flowchart showing a dispatch information registration process. This is the screen that is displayed when logging in to the security guard reservation server 100 using a security company account. 13 is a flowchart showing a request information registration process. This is the screen that is displayed when logging in to the security guard reservation server 100 using a contractor's account. This is the screen that is displayed when logging in to the security guard reservation server 100 using a contractor's account. This is the screen that is displayed when logging in to the security guard reservation server 100 using a contractor's account. This is the screen that is displayed when logging in to the security guard reservation server 100 using a contractor's account. This is the screen that is displayed when logging in to the security guard reservation server 100 using a contractor's account. This is the screen that is displayed when logging in to the security guard reservation server 100 using a contractor's account. This is the screen that is displayed when logging in to the security guard reservation server 100 using a contractor's account. This is the screen that is displayed when logging in to the security guard reservation server 100 using a contractor's account. This is the screen that is displayed when logging in to the security guard reservation server 100 using a contractor's account. 13 is a flowchart showing a task report process. This is the screen that is displayed when logging in to the security guard reservation server 100 using a security company account. This is the screen that is displayed when logging in to the security guard reservation server 100 using a security company account.

The following describes an embodiment of the present invention. Figures 1 to 24 show this embodiment.

When carrying out construction work, construction companies need to deploy security guards at the construction site. To do so, construction companies request security guards from security companies and deploy them at the site. In this embodiment, multiple security companies and multiple construction companies are registered as members, and security companies and construction companies with suitable timing, area, and number of people are matched.

First, the configuration of this embodiment will be described.
FIG. 1 is a block diagram showing the configuration of a network system.

As shown in FIG. 1, the Internet 199 is connected to a security guard reservation server 100 that reserves security guards, a number of security company terminals 200 used by each of a number of security companies, a construction contractor terminal 210 used by each of a number of construction contractors, and a contract information management server 220 that manages contract information related to contracts for the dispatch of security guards (hereinafter referred to as "security guard dispatch contracts").

Next, the configuration of the security guard reservation server 100 will be described.
FIG. 2 is a diagram showing the hardware configuration of the security guard reservation server 100.

As shown in Figure 2, the security guard reservation server 100 is composed of a CPU (Central Processing Unit) 30 that controls calculations and the entire system based on a control program, a ROM (Read Only Memory) 32 in which the control program and the like for the CPU 30 is stored in advance in a specified area, a RAM (Random Access Memory) 34 for storing data read from the ROM 32 etc. and calculation results required in the calculation process of the CPU 30, and an I/F (InterFace) 38 that mediates the input and output of data to and from external devices. These are connected to each other and capable of sending and receiving data by a bus 39, which is a signal line for transferring data.

Connected to the I/F 38 are external devices, such as an input device 40 consisting of a keyboard, mouse, etc. that can input data as a human interface, a storage device 42 that stores data, tables, etc. as files, and a display device 44 that displays a screen based on an image signal.

Next, the data structure of the storage device 42 will be described.
3(a) to (h) are diagrams showing the data structures of a security company information table 400, a contractor information table 402, a dispatch information table 404, a request information table 406, an estimate information table 408, a request change information table 410, a report information table 412, a billing information table 414 and a materials information table 416.

As shown in FIG. 3(a), the storage device 42 stores a security company information table 400 that registers security company information related to security companies.

The security company information table 400 contains one record for each security company. Each record contains fields for registering the security company ID, company name, phonetic spelling of the company name, qualified invoice issuer registration number, representative name, phonetic spelling of the representative name, person in charge name, phonetic spelling of the person in charge name, area of responsibility 1, area of responsibility 2, area of responsibility 3, area of responsibility 4, area of responsibility 5, postal code, address, telephone number, person in charge contact information, email address, financial institution name, branch name, account type, account number, and account holder name (kana).

Coverage areas 1 to 5 indicate areas to which a security company can dispatch security guards. Areas are in units of cities, wards, towns, and villages. If security guards can be dispatched to cities, wards, towns, and villages in one prefecture (for example, one or more cities, wards, towns, and villages in Yamaguchi prefecture), the cities, wards, towns, and villages in Yamaguchi prefecture are registered in the Coverage Area 1 field. If security guards can be dispatched to cities, wards, towns, and villages in two prefectures (for example, one or more cities, wards, towns, and villages in Yamaguchi prefecture and one or more cities, wards, towns, and villages in Fukuoka prefecture), the cities, wards, towns, and villages in Yamaguchi prefecture are registered in the Coverage Area 1 field, and the cities, wards, towns, and villages in Fukuoka prefecture are registered in the Coverage Area 2 field. Similarly, if security guards can be dispatched to cities, wards, towns, and villages in three prefectures, the Coverage Areas 1 to 3 fields are registered; if security guards can be dispatched to cities, wards, towns, and villages in four prefectures, the Coverage Areas 1 to 4 fields are registered; and if security guards can be dispatched to cities, wards, towns, and villages in five prefectures, the cities, wards, towns, and villages in each prefecture are registered in the Coverage Areas 1 to 5 fields.

As shown in FIG. 3(b), the storage device 42 stores a contractor information table 402 that registers contractor information related to contractors.

The contractor information table 402 has one record for each contractor. Each record contains fields for registering the contractor's ID, company name, phonetic name of the company, representative name, phonetic name of the representative name, person in charge name, phonetic name of the person in charge name, postal code, address, telephone number, person in charge contact information, email address, financial institution name, branch name, account type, account number, and account holder name (kana). The data structure differs from the security company information table 400 in that it does not have the qualified invoice issuing business registration number and areas of responsibility 1 to 5.

As shown in FIG. 3(c), the storage device 42 stores a dispatch information table 404 in which a security company registers dispatch information regarding the time and number of security guards that can be dispatched.

The dispatch information table 404 has one record registered for each security company ID, date when the security company can dispatch security guards, day/night classification, and qualification classification. Each record includes fields for registering the security company ID, date (year/month/day) when the security company can dispatch security guards, day/night classification (day or night as the time period when dispatch is possible), qualification classification (classification of whether the security guard is qualified or not), and the number of people that can be dispatched. For example, if 78 qualified security guards and 79 unqualified security guards can be dispatched in the daytime on January 31, 2024, and 80 qualified security guards and 81 unqualified security guards can be dispatched in the evening of the same day, four records are registered in the dispatch information table 404. The first record will have "2024/1/31", "Day", "Eligible", and "78", the second record will have "2024/1/31", "Day", "Unqualified", and "79", the third record will have "2024/1/31", "Evening", "Eligible", and "80", and the fourth record will have "2024/1/31", "Evening", "Unqualified", and "81".

As shown in FIG. 3(d), the storage device 42 stores a request information table 406 in which the construction company registers request information regarding the time, area, and number of security guards to be dispatched.

In the request information table 406, one record is registered for each request ID, the date on which the contractor requests the dispatch of security guards, the day/night division, and the qualification division. Each record is configured to include fields for registering the request ID, the requested security company ID, the requesting contractor ID, the date on which the contractor requests the dispatch of security guards, the day/night division, the qualification division, and the number of people. For example, if contractor A requests security company B to dispatch 78 qualified security guards and 79 unqualified security guards in the afternoon on January 31, 2024, and 80 qualified security guards and 81 unqualified security guards in the evening of the same day, four records are registered in the request information table 406. The first record will have "2024/1/31", "Day", "Qualified", "78", "Security Company B's ID", and "Constructor A's ID", the second record will have "2024/1/31", "Day", "Unqualified", "79", "Security Company B's ID", and "Constructor A's ID", the third record will have "2024/1/31", "Night", "Qualified", "80", "Security Company B's ID", and "Constructor A's ID", and the fourth record will have "2024/1/31", "Night", "Unqualified", "81", "Security Company B's ID", and "Constructor A's ID".

The request ID is an ID that is uniquely assigned to one request. For example, if the above example is for one request, the same request ID is set in the first through fourth records. Also, since this request is a transaction between the same security company and construction contractor, the same combination of security company ID and construction contractor ID is set in records with the same request ID.

As shown in FIG. 3(e), the storage device 42 stores an estimate information table 408 that registers estimate information regarding the estimated amount related to the requested item.

The quotation information table 408 has one record registered for each request ID and quotation ID. Each record includes fields for registering the request ID, quotation ID, and estimated amount related to the requested item.

The storage device 42 stores a request change information table 410 that registers request change information regarding changes to requested items, as shown in FIG. 3(f).

The request change information table 410 has one record registered for each request ID. Each record includes fields for registering the request ID and changes to the request items (date, day/night division, qualification classification, number of people, etc.).

As shown in FIG. 3(g), the storage device 42 stores a report information table 412 that registers report information regarding the work performed by security companies when security guards are dispatched.

The report information table 412 has one record registered for each request ID. Each record includes fields for registering the request ID and one or more report items.

As shown in FIG. 3(h), the storage device 42 stores a billing information table 414 that registers billing information related to the amount billed by a security company for services performed by dispatching security guards.

The billing information table 414 has one record registered for each request ID and billing ID. Each record includes fields for registering the request ID, billing ID, and billing amount related to the request item.

As shown in FIG. 3(i), the storage device 42 stores a materials information table 416 that registers materials information about materials used by the construction company at the site where security guards are deployed.

The materials information table 416 has one record registered for each request ID. Each record includes fields for registering the request ID, one or more materials, and their quantities.

Next, the configurations of the security company terminal 200 and the contractor terminal 210 will be described.
The security company terminal 200 and the contractor terminal 210 are configured to have the same hardware configuration as the security guard reservation server 100. The security company terminal 200 and the contractor terminal 210 may also be configured as a smartphone.

Next, the operation of this embodiment will be described.
First, a case where a security company registers security company information will be described.

FIG. 4 is a flowchart showing the security company information registration process.
In the security guard reservation server 100, the CPU 30 is composed of an MPU (Micro-Processing Unit) or the like, and starts a predetermined program stored in a predetermined area of the ROM 32, and executes the security company information registration process shown in the flowchart of Fig. 4 in accordance with the program. The security company information registration process is executed in response to access from the security company terminal 200.

Figures 5 and 6 show the screens that are displayed when logging in to the security guard reservation server 100 using a security company account.

When a security company user accesses the security guard reservation server 100 on the security company terminal 200 and logs in with their company's account, a menu list screen is displayed as shown in FIG. 5. When the user selects the "Edit registration information" menu 504 from the menu list, a screen for setting or changing security company information is displayed as shown in FIG. 6. The user can set their company's security company information on this screen.

When the security company information is set, the security guard reservation server 100 receives the security company information from the security company terminal 200 through steps S100 and S102, as shown in FIG. 4, and registers the received security company information in the security company information table 400.

Next, a case where a contractor registers contractor information will be described.
FIG. 7 is a flowchart showing the contractor information registration process.

The security guard reservation server 100 executes the contractor information registration process shown in the flowchart of FIG. 7 by the CPU 30. The contractor information registration process is executed in response to access from the contractor terminal 210.

Figures 8 and 9 show the screens that are displayed when logging in with a contractor's account on the security guard reservation server 100.

When a contractor user accesses the security guard reservation server 100 on the contractor terminal 210 and logs in using their company's account, a menu list screen is displayed as shown in FIG. 8. When the user selects the "My Page" menu 508 from the menu list, a screen for setting or changing contractor information is displayed as shown in FIG. 9. The user can set their company's contractor information on this screen.

When the security company information is set, the security guard reservation server 100 receives the contractor information from the contractor terminal 210 through steps S110 and S112, as shown in FIG. 7, and the received contractor information is registered in the contractor information table 402.

Next, a case where a security company registers dispatch information will be described.
FIG. 10 is a flowchart showing the dispatch information registration process.

The security guard reservation server 100 executes the dispatch information registration process shown in the flowchart of FIG. 10 by the CPU 30. The dispatch information registration process is executed in response to access from the security company terminal 200.

Figure 11 shows the screen that is displayed when logging in to the security guard reservation server 100 using a security company account.

When a security company user selects the "Personnel Reservation Management" menu 500 from the menu list in FIG. 5, a screen for setting or changing dispatch information is displayed, as shown in FIG. 11. The user can set the dispatch information on this screen.

The dispatch information is set as follows. In the example of FIG. 11, a calendar for the month to which the current date belongs (for example, January 2024) is displayed. A calendar for any month can be displayed by clicking "Previous Month" or "Next Month". Each day is divided into a daytime division and a nighttime division. The daytime division has a field A for setting the number of qualified security guards that can be dispatched during the daytime of that day, and a field B for setting the number of unqualified security guards that can be dispatched during the daytime of that day. The nighttime division has a field A for setting the number of qualified security guards that can be dispatched during the nighttime of that day, and a field B for setting the number of unqualified security guards that can be dispatched during the nighttime of that day. In other words, four fields, daytime A, daytime B, nighttime A, and nighttime B, are provided for each day. The user sets the number of security guards that the company can dispatch for each date, daytime/nighttime division, and qualification division.

When the dispatch information is set, the security guard reservation server 100, as shown in FIG. 10, goes through steps S120 and S122 to receive information on the date, day/night division, qualification division, and number of people from the security company terminal 200, and the dispatch information including the received information is registered in the dispatch information table 404. The dispatch information includes the security company ID of the security company that set the dispatch information.

Next, a case where a contractor registers request information will be described.
FIG. 12 is a flowchart showing the request information registration process.

The security guard reservation server 100 executes the request information registration process shown in the flowchart of FIG. 12 by the CPU 30. The request information registration process is executed in response to access from the contractor terminal 210.

Figures 13 to 21 show the screens that are displayed when logging in to the security guard reservation server 100 using a contractor's account.

When the contractor user selects the "Reservation Screen" menu 506 from the menu list in FIG. 8, a notice is displayed as shown in FIG. 13. If the user agrees to this, he or she clicks the "Agree" button 510. When the button 510 is clicked, a list of prefectures is displayed as shown in FIG. 14. When the user selects the prefecture to which the security guard is requested to be dispatched, the cities, wards, towns, and villages of the selected prefecture are displayed on the map of the prefecture and in a list as shown in FIG. 15. In the example of FIG. 15, the prefecture of Fukuoka is displayed. When the user selects the city, ward, town, and village to which the security guard is requested to be dispatched, the security guard reservation server 100 receives area information including the selected prefecture and city, ward, town, and village from the contractor terminal 210 through step S130 as shown in FIG. 12, and the request information including the received area information is registered in the request information table 406 (a record corresponding to the request ID issued for the request. The same applies to steps S138 and S150 below). Next, through steps S132 and S134, based on the received area information, security company information of the security company in which the relevant area is registered is obtained from the security company information table 400, and dispatch information corresponding to the obtained security company information is obtained from the dispatch information table 404. Specifically, dispatch information containing the same security company ID as the security company ID contained in the security company information is obtained. Then, through step S136, the obtained dispatch information is sent to the contractor terminal 210.

When the contractor terminal 210 receives the dispatch information, the dates when security guards can be dispatched, day/night classification, qualification classification, and number of people are displayed for each security company whose area of responsibility is registered based on the received dispatch information, as shown in FIG. 16. When the user wishes to select a security company to request the dispatch of security guards, the user clicks the "Book" button 512 corresponding to that security company. When button 512 is clicked, a screen for setting request information is displayed, as shown in FIG. 17. The user can set the request information on this screen.

The request information is set as follows. In the example of FIG. 17, the calendar for the month to which the current date belongs (for example, January 2024) and the dispatch information of the selected security company (hereinafter referred to as the "selected security company") are displayed. The calendar for any month can be displayed by clicking "Previous Month" or "Next Month". Each day is divided into a daytime division and a nighttime division. The daytime division is provided with a column A for setting the number of qualified security guards to be dispatched during the daytime of that day, and a column B for setting the number of unqualified security guards to be dispatched during the daytime of that day. The column A displays the number of qualified security guards that the selected security company can dispatch during the daytime of that day, and the column B displays the number of unqualified security guards that the selected security company can dispatch during the daytime of that day, and the number of security guards to be dispatched can be set as the upper limit. The nighttime division is provided with a column A for setting the number of qualified security guards to be dispatched during the nighttime of that day, and a column B for setting the number of unqualified security guards to be dispatched during the nighttime of that day. Column A displays the number of qualified guards the selected security company can dispatch that night, and column B displays the number of unqualified guards the selected security company can dispatch that night. The number of guards the user wishes to request to be dispatched can be set as an upper limit. The number of guards available for dispatch is displayed based on the received dispatch information. That is, as in FIG. 11, four columns are provided for each day: day A, day B, night A, and night B. The user sets the number of guards the user wishes to request to be dispatched by date, day/night category, and qualification category.

When the request information setting is completed and materials are to be arranged, the user clicks the button 514 "Click here if you are requesting a set of restricted materials." When the button 514 is clicked, the security guard reservation server 100, as shown in FIG. 12, receives information on the date, day/night classification, qualification classification, and number of people from the contractor terminal 210 through step S138, and the request information including the received information is registered in the request information table 406. On the other hand, the contractor terminal 210 can set material information as shown in FIG. 18. The user sets the necessary materials and clicks the "Confirm" button 518. When the button 518 is clicked, the security guard reservation server 100, as shown in FIG. 12, receives material information from the contractor terminal 210 through step S142, and the received material information is registered in the material information table 416. Next, through step S144, estimate information is generated based on the request information in the request information table 406, and the generated estimate information is registered in the estimate information table 408. Then, after step S146, information on the request, including the generated estimate information, is sent to the contractor terminal 210.

When the contractor terminal 210 receives the information on the requested items, the requested items are displayed based on the received information, as shown in FIG. 19. If the user is satisfied with the content, he/she clicks the "Confirm" button 520. When button 520 is clicked, the estimated amount is displayed as an estimate, as shown in FIG. 20. If the user is satisfied with the content, he/she clicks the "Order request" button 522. When button 522 is clicked, a message is displayed indicating that the request has been accepted, as shown in FIG. 21.

When the request is accepted, as shown in FIG. 12, in the security guard reservation server 100, through step S150, the request information including the requested security company ID and the requesting contractor ID is registered in the request information table 406. This allows matching between security companies and contractors with matching areas, dates, day/night classification, qualification classification, and number of people. Then, through step S152, a request is sent to the contract information management server 220 to send contract information to the security company terminal 200 of the security company, which is the contractor of the security guard dispatch contract, and the contractor terminal 210 of the contractor, which is the contractor of the same contract. The request includes security company information and contractor information. As a result, the contract information is sent to the security company terminal 200 and the contractor terminal 210, respectively, and when the security company and the contractor each sign electronically, the security guard dispatch contract is established. After that, the security company dispatches security guards to the specified site as requested, and the contractor deploys the dispatched security guards at the construction site and carries out the construction work.

When the request information has been set and no materials are to be arranged, the user clicks on the "Click here if you are only arranging a guide" button 516 on the screen in FIG. 17. When button 516 is clicked, the screen transitions to that in FIG. 19.

Next, a case where a security company makes a business report will be described.
FIG. 22 is a flowchart showing the operation report process.

The security guard reservation server 100 executes the business report process shown in the flowchart of FIG. 22 by the CPU 30. The business report process is executed in response to access from the security company terminal 200.

Figures 23 and 24 show the screens that are displayed when logging in to the security guard reservation server 100 using a security company account.

When a security company user selects the "Work Completion Report" menu 502 from the menu list in FIG. 5, a list of security guard dispatch contracts that the security company has received is displayed, as shown in FIG. 23. When the user clicks the "Select" button 524 corresponding to the security guard dispatch contract for which the user wishes to make a work report, the security guard reservation server 100, as shown in FIG. 22, goes through steps S160 and S162, and obtains the request information and estimate information related to the selected security guard dispatch contract from the request information table 406 and estimate information table 408, and transmits the obtained request information and estimate information to the security company terminal 200.

When the security company terminal 200 receives the request information and estimate information, the requested items and estimated amount are displayed based on the received request information and estimate information, as shown in FIG. 24. The user can set request change information on this screen. If there are changes to the number of security guards or if transportation costs, etc. are incurred, the changes are set.

When the setting of the request change information is completed, the user clicks the "Send" button 526. When the button 526 is clicked, the security guard reservation server 100 receives the request change information from the security company terminal 200 through steps S166 and S168, as shown in FIG. 22, and the received request change information is registered in the request change information table 410. Then, through steps S170 and S172, report information is generated based on the request information acquired in step S160 and the request change information received in step S166, and the generated report information is registered in the report information table 412. Also, through steps S174 and S176, billing information is generated based on the request information and estimate information acquired in step S160 and the request change information received in step S166, and the generated billing information is registered in the billing information table 414.

Next, the effects of this embodiment will be described.
In this embodiment, dispatch information regarding one or more periods (dates and day/night divisions) when a security company can dispatch security guards, the area, and the number of people who can be dispatched for each of those one or more periods is registered in the dispatch information table 404 in correspondence with the security company information, request information regarding the area to which a construction contractor requests the dispatch of security guards is obtained, and based on the dispatch information in the dispatch information table 404 that corresponds to the area related to the obtained request information, one or more periods when dispatch is possible and the number of people who can be dispatched for each of those one or more periods is presented, request information regarding the period and number of people set by the construction contractor within the presented range of period and number of people is obtained, the obtained request information is registered in the request information table 406 in correspondence with the construction contractor information, and based on the dispatch information in the dispatch information table 404 and the request information in the request information table 406, security companies and construction contractors whose period, area and number of people related to the dispatch information and request information are compatible are matched.

This allows security companies and contractors to be matched with those that match the timing, area and number of people related to the dispatch information and request information, making it possible to better reflect contractors' requests regarding the timing, area and number of people when requesting the dispatch of security guards than was previously possible.

Furthermore, in this embodiment, the dispatch information is information regarding the number of qualified security guards and the number of unqualified security guards that the security company can dispatch for one or more time periods, areas, and each of the one or more time periods when dispatch is possible, and the request information is information regarding the number of qualified security guards and the number of unqualified security guards that the construction company requests to be dispatched for one or more set time periods, areas, and each of the one or more set time periods.

This will allow us to reflect your needs regarding the number of qualified and unqualified security guards.

Furthermore, in this embodiment, material information regarding materials to be used by the construction contractor at the site where security guards are deployed is acquired, and the acquired material information is associated with the construction contractor information and registered in the material information table 416.

This allows the resources to be set when requesting the dispatch of security guards.
Furthermore, in this embodiment, contract information for the matched security company and construction contractor to enter into a contract regarding the dispatch of security guards is provided to the security company based on the security company information of the security company, or is provided to the construction contractor based on the construction contractor information of the construction contractor.

This makes it relatively easy to conclude a contract as the contract information is provided to the security company or construction company.

Furthermore, in this embodiment, based on the request information in the request information table 406, the request items related to the request information are presented, request change information regarding changes to the presented request items is obtained, and report information is generated based on the request information in the request information table 406 and the obtained request change information.

This allows you to obtain report information on the work if you make changes to the requested items.
Furthermore, in this embodiment, based on the request information in the request information table 406, request items related to the request information are presented, request change information regarding changes to the presented request items is obtained, and billing information is generated based on the request information in the request information table 406 and the obtained request change information.

This allows you to obtain billing information for the work by making changes to the request items.
In this embodiment, step S122 corresponds to the dispatch information registration means of invention 1, step S130 corresponds to the first request information acquisition means of invention 1, steps S132 and S134 correspond to the dispatch information presentation means of invention 1, and step S138 corresponds to the second request information acquisition means of invention 1. Also, steps S130 and S138 correspond to the request information registration means of invention 1 or 3, step S142 corresponds to the material information acquisition means of invention 3, step S150 corresponds to the matching means of invention 1 or 4, and step S152 corresponds to the contract information provision means of invention 4.

In this embodiment, steps S160 and S162 correspond to the request information presenting means of invention 5 or 6, step S166 corresponds to the request change information acquiring means of invention 5 or 6, step S170 corresponds to the report information generating means of invention 5, and step S174 corresponds to the cost information generating means of invention 6. In addition, the dispatch information table 404 corresponds to the dispatch information storing means of invention 1, the request information table 406 corresponds to the request information storing means of invention 1, 5 or 6, and the material information table 416 corresponds to the material information storing means of invention 3.

[Modifications]
In the above embodiment and its modified example, a configuration has been given in which one security company and one construction company enter into a security guard dispatch contract for one request, but this is not limited to the above, and the following configuration can also be adopted.

In the first configuration, multiple security companies and one construction company enter into a security guard dispatch contract for one request. Based on dispatch information related to the multiple security companies, one or more periods when the security companies can dispatch and the number of people that can be dispatched for each of the one or more periods are presented. For example, the total number of people that the multiple security companies can dispatch is displayed on the calendar shown in FIG. 17. Then, request information related to the period and number of people set by the construction company within the range of the presented period and number of people is obtained, and multiple security companies that satisfy the content of the obtained request information are matched with the construction company. In this way, even if one security company cannot handle the number of people requested by the construction company, multiple security companies may be able to handle it, so the construction company's requests can be reflected.

In the second configuration, one security company and multiple contractors enter into a security guard dispatch contract for one request. Based on the dispatch information for one security company, the security company presents one or more periods when it can dispatch and the number of people it can dispatch for each of the one or more periods. In addition, one of the multiple contractors is set as the representative contractor. The multiple contractors are set as a group, and group information indicating that one of the contractors belonging to the group is the representative is stored in a table or the like of the storage device 42. Then, request information related to the period and number of people set by the representative contractor within the range of the presented period and number of people is obtained, and based on the group information, one security company is matched with the multiple contractors represented by the representative contractor. This makes it possible to reflect the desire of multiple contractors to jointly arrange security guards for the same site.

The third configuration is one in which multiple security companies and multiple contractors enter into a security guard dispatch contract for one request. Based on dispatch information related to the multiple security companies, the system presents one or more periods during which the security companies can dispatch and the number of people available for each of the one or more periods. In addition, one of the multiple contractors is set as the representative contractor. Then, request information related to the period and number of people set by the representative contractor within the range of the presented period and number of people is obtained, and multiple security companies that satisfy the contents of the obtained request information are matched with multiple contractors represented by the representative contractor.

In addition, in the above embodiment and its modified example, it was not explained that the number of people that the security company can dispatch or the number of people requested by the construction company may change after the contract is concluded. In order to deal with this, for example, the following configuration can be adopted.

The first configuration is a configuration for matching a construction company (hereinafter referred to as a "deficient construction company") with another security company (hereinafter referred to as an "accommodating security company") that can dispatch the shortage of personnel during the period related to the request when the number of people that a security company can dispatch has decreased due to some circumstances or the number of people requested by the construction company has increased. The shortage construction company is identified based on construction company information and shortage information regarding the shortage of personnel, the accommodation security company is identified based on security company information and dispatch information, and the identified shortage construction company and accommodation security company are matched. As a matching configuration, for example, (1) one or more accommodating security companies are presented to the shortage construction company, and the shortage construction company selects one from among them and matches the shortage construction company with that accommodation security company, (2) one or more shortage construction companies are presented to the accommodating security company, and the accommodating security company selects one from among them and matches the shortage construction company with that accommodation security company, (3) a security company that dispatches security guards to a time and area close to the time and area related to the request is asked to dispatch, and a security company that responds to this request is matched with the shortage construction company, and (4) a matching configuration can be adopted according to a specified algorithm without selecting a security company or construction company.

The second configuration is a configuration that matches a security company when an excess of personnel occurs due to an increase in the number of people a security company can dispatch or a decrease in the number of people requested by a construction contractor for some reason (hereinafter referred to as an "excess security company") with another construction contractor (hereinafter referred to as an "accommodating construction contractor") that requests a number of people that falls within the total of the number of people that other security companies can dispatch and the excess number of people at the time related to the request. Excess security companies are identified based on security company information and excess information regarding the excess number of people, accommodating construction contractors are identified based on construction contractor information and request information, and the identified excess security companies and accommodating construction contractors are matched. As a matching configuration, for example, (1) a configuration in which one or more accommodation construction companies are presented to an excess security company, and the excess security company selects one from among them and matches that excess security company; (2) a configuration in which one or more excess security companies are presented to an accommodation construction company, and the accommodation construction company selects one from among them and matches that accommodation construction company; (3) a configuration in which a construction company that has requested security guards for a time and area close to the time and area related to the request is approached about an additional request, and a construction company that responds to this request is matched with the excess security company; and (4) a configuration in which matching is performed according to a specified algorithm without selecting a security company or construction company.

The third configuration matches a shortage contractor related to a certain request with an excess security company related to another request. The shortage contractor is identified based on contractor information and shortage information related to the number of people, and an excess security company is identified based on security company information and excess information related to the number of people, and the identified shortage contractor and excess security company are matched. Examples of matching configurations include: (1) a configuration in which one or more excess security companies are presented to a shortage contractor, and the shortage contractor matches an excess security company selected from among them with the shortage contractor; (2) a configuration in which one or more shortage contractors are presented to an excess security company, and the excess security company matches a shortage contractor selected from among them with the excess security company;
(3) A configuration in which, although the shortage cannot be handled, surplus security companies that have requested security guards for a time and area close to the time and area related to the request are approached to send guards, and the surplus security companies are matched with shortage construction contractors in response; (4) A configuration in which, although the shortage cannot be handled, surplus construction contractors that have requested security guards for a time and area close to the time and area related to the request are approached to send additional requests, and the shortage construction contractors are matched with surplus security companies in response; (5) A configuration in which matching is performed according to a predetermined algorithm without selecting security companies and construction contractors.

In addition, in the above embodiment and its modified examples, we did not explain how the operator of the security guard reservation server 100 earns revenue, but for example, the following configuration can be adopted.

The first configuration is a configuration in which a predetermined percentage of the amount paid by the construction company to the security company is collected as revenue. Based on billing information regarding the amount paid by the construction company to the security company, the predetermined percentage of that amount is calculated, payment information is generated based on the calculation result, and payment processing is performed based on the generated payment information.

The second configuration is a configuration in which an amount according to the number of people, number of times, and other scale of the security company's dispatch is collected as revenue from the security company. Payment information is generated based on scale information related to the number of people, number of times, and other scale of the security company's dispatch, and payment processing is performed based on the generated payment information.

The third configuration is a configuration in which an amount according to the number of people, number of times, and other scale requested by the construction company is collected as revenue from the construction company. Payment information is generated based on scale information related to the number of people, number of times, and other scale requested by the construction company, and payment processing is performed based on the generated payment information.

In addition, in the above embodiment and its variations, the contract information is sent to both the security company and the construction company, but this is not limited, and the contract information can be sent to only some of the contractors.

In addition, in the above embodiment and its modified examples, the contract information management server 220 is provided separately from the security guard reservation server 100, but this is not limited to the above, and they can be configured as an integrated unit. In this case, the security guard reservation server 100 is configured to have the functions of the contract information management server 220.

In addition, in the above embodiment and its modified examples, the security guard reservation server 100 is realized as a single device, but this is not limited, and it can be realized as a network system. As an example of a network system, some or all of the functions of the security guard reservation server 100 can be configured as a virtual server on a server that provides cloud computing services.

In addition, in the above embodiment and its modified examples, the processes shown in the flowcharts of FIG. 4, FIG. 7, FIG. 10, FIG. 12, or FIG. 22 are executed by executing a program that is pre-stored in ROM 32. However, this is not limited to the above, and the program showing these procedures may be read from a storage medium on which the program is stored, into RAM 34, and executed.

Here, storage media refers to semiconductor storage media such as RAM and ROM, magnetic storage media such as FD and HD, optically readable storage media such as CD, CDV, LD and DVD, and magnetic storage/optically readable storage media such as MO, and includes any storage media that can be read by a computer, regardless of the reading method (electronic, magnetic, optical, etc.).

Moreover, the above-described embodiments and their modifications can be applied to each other.
Furthermore, the present invention is not limited to the above-described embodiment and its modified examples, but can be applied to other cases without departing from the spirit of the present invention.

100...security guard reservation server, 200...security company terminal, 210...contractor terminal, 220...contract information management server, 199...internet, 30...CPU, 32...ROM, 34...RAM, 38...I/F, 39...bus, 40...input device, 42...storage device, 44...display device, 400...security company information table, 402...contractor information table, 404...dispatch information table, 406...request information table, 408...quotation information table, 410...request change information table, 412...report information table, 414...billing information table, 416...material information table, 500-508...menus, 510-526...buttons

Claims (11)

a dispatch information registration means for registering dispatch information relating to one or more periods and locations during which a dispatcher can dispatch security guards, and multiple numbers of people available for dispatch during each of the one period or multiple periods, in a dispatch information storage means in association with dispatcher information relating to the dispatcher;
a first request information acquisition means for acquiring request information relating to a location where a requester requests the dispatch of the security guard;
a dispatch information presentation means for presenting the one or more time periods during which the dispatch can be performed and the multiple number of people available for dispatch for each of the one time period or the multiple time periods based on the dispatch information in the dispatch information storage means corresponding to the location related to the request information acquired by the first request information acquisition means;
a second request information acquisition means for acquiring request information relating to a time and number of people set by the requester within the range of time and number of people presented by the dispatch information presentation means;
a request information registering means for registering the request information acquired by the first request information acquiring means and the second request information acquiring means in a request information storage means in association with requester information relating to the requester;
A security guard reservation system characterized by having a matching means for registering information in a storage means that matches the dispatcher and the requester whose timing, location and number of people related to the dispatch information and the request information match based on the dispatch information in the dispatch information storage means and the request information in the request information storage means , or for presenting such matching information . In claim 1,
The dispatch information presentation means presents, based on the dispatch information related to one of the dispatchers, one or more periods during which the dispatcher can be dispatched and the number of people available for dispatch for each of the one period or the multiple periods;
The second request information acquisition means acquires request information relating to a time period and number of people set by a representative requester within the range of the time period and number of people presented by the dispatch information presentation means,
A security guard reservation system characterized in that the matching means sets the multiple clienters as a group and, based on group information in a group information storage means which stores group information indicating that one of the multiple clienters is the representative client, registers information matching the one dispatcher and the multiple clienters represented by the representative client in the storage means or presents the matching information. In claim 1,
The dispatch information presentation means presents, based on the dispatch information related to the plurality of dispatchers, one or more periods during which the plurality of dispatchers can be dispatched and the number of people available for dispatch for each of the one period or the plurality of periods;
The second request information acquisition means acquires request information relating to a time period and number of people set by a representative requester within the range of the time period and number of people presented by the dispatch information presentation means,
A security guard reservation system characterized in that the matching means sets the multiple clienters as a group and registers information in the storage means matching the multiple dispatchers and the multiple clienters represented by the representative client based on group information in a group information storage means that stores group information indicating that one of the multiple clienters is the representative client, or presents the matching information. In claim 1,
a shortage requester etc. specifying means for specifying the shortage requester, who is the requester for whom the shortage has occurred, based on shortage information on the number of people available for dispatch related to the request or the number of people who have made the request and the requester information, and for specifying a receiving dispatcher, who is the dispatcher who can dispatch the shortage of people at the time related to the request, based on the dispatcher information and the dispatch information;
The matching means (1) presents one or more receiving dispatchers identified by the shortage requester etc. identifying means to a shortage requester identified by the shortage requester etc. identifying means, and registers information in the storage means that matches the receiving dispatcher selected by the shortage requester and the shortage requester in question, or (2) presents one or more shortage requesters identified by the shortage requester etc. identifying means to a shortage dispatcher identified by the shortage requester etc. identifying means, and registers information in the storage means that matches the shortage requester selected by the receiving dispatch and the receiving dispatch in question, or presents the matching information.A security guard reservation system characterized by the above-mentioned. In claim 1,
a means for identifying an excess dispatcher, etc., which identifies the dispatcher who is the dispatcher for whom the excess occurs, based on surplus information on the surplus number of people when the surplus occurs in the number of people available for dispatch related to the request or the number of people who made the request, and the dispatcher information, and which identifies a receiving requester who is the requester requesting a number of people that falls within the sum of the number of people available for dispatch by the dispatcher and the surplus number during the period related to the request, based on the requester information and the request information;
The matching means (1) presents one or more accommodation requesters identified by the excess dispatched person, etc. identifying means to an excess dispatched person identified by the excess dispatched person, etc. identifying means, and registers information in the storage means that matches the accommodation requester selected by the excess dispatched person and the excess dispatched person in question, or presents such matching information; or (2) presents one or more excess dispatched persons identified by the excess dispatched person, etc. identifying means to an accommodation requester identified by the excess dispatched person, etc. identifying means, and registers information in the storage means that matches the excess dispatched person selected by the accommodation requester and the accommodation requester in question, or presents such matching information. In claim 1,
a shortage requester etc. specifying means for specifying a shortage requester, who is the requester for whom a shortage has occurred, based on shortage information on the shortage of the number of people available for dispatch or the number of people who have made the request and the requester information, and for specifying an excess dispatcher, who is the dispatcher for whom a surplus has occurred, based on surplus information on the surplus of the number of people available for dispatch or the number of people who have made the request and the dispatcher information;
The matching means (1) presents one or more excess dispatchers identified by the shortage requester, etc. identifying means to a shortage requester identified by the shortage requester, etc. identifying means, and registers information in the storage means that matches the excess dispatcher selected from among the shortage requesters and the shortage requester, or (2) presents one or more shortage requesters identified by the shortage requester, etc. identifying means to an excess dispatcher identified by the shortage requester, etc. identifying means, and registers information in the storage means that matches the shortage requester selected from among the shortage requesters and the excess dispatcher, or presents the matching information.A security guard reservation system characterized by the above. In claim 1,
The dispatch information is information regarding one or more possible time periods and locations for dispatch, and the number of qualified security guards and the number of unqualified security guards that the dispatcher can dispatch for each of the one time period or the multiple time periods;
A security guard reservation system characterized in that the request information is information regarding the set one or more periods, locations, and the number of qualified security guards and the number of unqualified security guards that the client requests to be dispatched for each of the set one or more periods. In any one of claims 1 to 7 ,
a material information acquisition means for acquiring material information on materials to be used at the site where the client deploys the security guards,
The security guard reservation system is characterized in that the request information registration means registers the material information acquired by the material information acquisition means in a material information storage means in association with the requester information. In any one of claims 1 to 7 ,
A security guard reservation system characterized by having a contract information providing means for providing contract information to a dispatcher and a client matched by the matching means based on the dispatcher's dispatcher information, or for providing contract information to a client based on the client's client information, so that the dispatcher and client can enter into a contract regarding the dispatch of the security guard. In any one of claims 1 to 7 ,
a request information presenting means for presenting a request item related to the request information based on the request information in the request information storage means;
a request change information acquisition means for acquiring request change information relating to changes to the request items presented by the request information presentation means;
A security guard reservation system characterized by comprising a report information generation means for generating report information on the work performed by the dispatcher after dispatching the security guard based on the request information in the request information storage means and the request change information acquired by the request change information acquisition means. In any one of claims 1 to 7 ,
a request information presenting means for presenting a request item related to the request information based on the request information in the request information storage means;
a request change information acquisition means for acquiring request change information relating to changes to the request items presented by the request information presentation means;
A security guard reservation system characterized by comprising a cost information generation means for generating cost information for the work performed by the dispatcher by dispatching the security guard based on the request information in the request information storage means and the request change information acquired by the request change information acquisition means.

Images