Security guard reservation system

Abstract

To provide a security guard reservation system suitable to reflect desire of a client.SOLUTION: A security guard reservation system: registers a plurality of periods during which a security company can dispatch a security guard, an area and dispatch information related to the number of persons who can be dispatched about each of the plurality of periods in association with security company information; acquires request information related to the area in which a contractor requests dispatch of the security guard; and presents the plurality of periods during which the security guard can be dispatched and the number of persons who can be dispatched about each of the plurality of periods, on the basis of the dispatch information corresponding to the area related to the acquired request information. The security guard reservation system: acquires the request information related to the period and the number of persons set by the contractor in the range of the presented period and the number of persons; registers the acquired request information in association with contractor information; and matches the security company and the contractor suitable to the period, the area and the number of persons related to the dispatch information and the request information, on the basis of the dispatch information and the request information.SELECTED DRAWING: Figure 12

Description

[Technical Field]

[0001] The present invention relates to a system for reserving security guards, and more particularly to a security guard reservation system that is suitable for reflecting the requests of clients. [Background technology]

[0002] BACKGROUND ART Conventionally, a technique for reserving a security guard is known, for example, as described in Patent Document 1.

[0003] 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 requesters. 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 security. Based on the security location, purpose, content, and target of security provided by the security service requester, the security integration center narrows down the security service providers that are optimal for the security location, purpose, content, and target of security related to 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 requester is then notified to the narrowed down optimal security service provider. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2002-175365 A (

[0048]

[0049] ) Summary of the Invention [Problem to be solved by the invention]

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

[0006] Therefore, the present invention was made with a focus on the unresolved issues of the conventional technology, and aims to provide a security guard reservation system that is suitable for reflecting the requests of clients. [Means for solving the problem]

[0007] When requesting the dispatch of security guards, the requester not only requests the location to which the security guards are to be dispatched, as in the technology of Patent Document 1, but also requests one or more time periods and the number of guards available for dispatch at each of the one time period or multiple time periods. However, the technology of Patent Document 1 cannot reflect such requests. Therefore, the present inventors have conceived the following invention to solve the above-mentioned conventional problems.

[0008] [Invention 1] In order to achieve the above object, the security guard reservation system of Invention 1 comprises a dispatch information registration means for registering dispatch information relating to one or more periods and locations when a dispatcher can dispatch security guards and the number of people who can be dispatched for each of the one or more 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 locations from which a requester requests the dispatch of the security guards; and a first request information acquisition means for acquiring request information relating to the one or more periods when dispatch is possible and the one or more periods in accordance with the dispatch information in the dispatch information storage means that corresponds to the locations 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 the 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 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 relating to the requester; and a matching means for matching the dispatcher and the requester whose time, place 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.

[0009] With this configuration, the dispatch information registration means registers dispatch information regarding one or more periods and locations at which the dispatcher can dispatch security guards, and the number of people who can be dispatched for each of those one or more periods, in correspondence with the dispatcher information in the dispatch information storage means.

[0010] Furthermore, the first request information acquisition means acquires request information regarding a location where a client requests the dispatch of security guards, and the dispatch information presentation means presents one or more periods during which dispatch is possible and the number of people who can be dispatched for each of the periods or multiple 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 period and number of people within the presented period and number of people range, the second request information acquisition means acquires request information regarding the set 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 period, 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.

[0011] Here, the time period includes, for example, a period of time divided into seconds, minutes, hours, morning, afternoon, morning, noon, night, days, months, years, or any other units, or a point in time specified by seconds, minutes, hours, morning, afternoon, morning, noon, night, days, months, years, or any other units.

[0012] Furthermore, matching by the matching means includes, for example, (1) correlating dispatch information and request information that match in terms of time, location, and number of people and registering them in a storage means, (2) correlating dispatcher information and requester information that match in terms of time, location, and number of people and registering them in a storage means, (3) providing request information or requester information to the terminal, etc. of the dispatcher and requester who match in terms of time, location, and number of people, and (4) providing dispatch information or dispatcher information to the terminal, etc. of the requester and dispatcher who match in terms of time, location, and number of people.

[0013] The dispatcher and the client may be natural persons or corporations. Furthermore, the dispatch information and request information can be configured as, for example, 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 as, for example, letters, numbers, figures, codes, symbols, images, sounds, or other information. The dispatch information and request information can be configured as keywords related 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 have the same structure or format, or different structures or formats.

[0014] Furthermore, the dispatcher information can be configured, for example, as information for identifying the dispatcher (for example, a name, number, ID, code, link information such as a URL). The dispatcher information can be configured, for example, as characters, numbers, figures, codes, symbols, images, sounds, and 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 may have the same structure or format, or may have different structures or formats.

[0015] Furthermore, the first request information acquisition means may, for example, input request information from an input device or the like, acquire or receive request information from an external terminal or the like, read request information from a storage device or storage medium or the like, or generate or calculate 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 hereinafter to the concept of acquisition.

[0016] 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 store the dispatch information by input from an external source during operation of the system without storing the dispatch information in advance. The same applies to the request information storage means and to other storage means hereinafter.

[0017] Furthermore, 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 registering them in the same record, and (2) storing the information via one or more intermediate pieces of information, such as providing a table that registers dispatch information and intermediate information in association with each other, and a table that registers 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 the dispatch information only needs 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 the concept of storing information in association with each other below.

[0018] 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 of the multiple devices, etc., as long as they are communicatively connected.

[0019] [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 relating to the one or more periods and locations during which 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 period or multiple periods, and the request information is information relating to the number of qualified security guards and the number of unqualified security guards that the client requests to be dispatched for each of the one or more set periods and locations, and the one period or multiple periods.

[0020] With this configuration, the dispatch information registration means registers dispatch information regarding one or more 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 period or multiple periods, in correspondence with dispatcher information in the dispatch information storage means.

[0021] In addition, the request information registration means registers request information regarding one or more periods and locations set by the client, as well as the number of qualified security guards and the number of unqualified security guards that the client requests to be dispatched for each of the one or more periods, in correspondence with the client information in the request information storage means.

[0022] [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 comprises 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.

[0023] With this configuration, the material information acquisition means acquires material information relating 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.

[0024] [Invention 4] Furthermore, the security guard reservation system of Invention 4 is the security guard reservation system of either Invention 1 or 2, and is equipped with a contract information providing means for providing contract information to the dispatcher and the client matched by the matching means based on the dispatcher information of the dispatcher, or for providing contract information to the client based on the client information of the client.

[0025] With this configuration, the contract information providing means provides the matched dispatcher and client with contract information for the dispatch of security guards based on the dispatcher's dispatcher information, or provides the client with contract information based on the client's client information.

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

[0027] [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.

[0028] With this configuration, the request information presentation means presents request items based on the request information stored in the request information storage means. When changes are made to the presented request items, the request change information acquisition means acquires request change information relating to the changes to the request items, and the report information generation means generates report information on the work performed by the dispatcher after dispatching the security guards, based on the request information and the request change information.

[0029] [Invention 6] Furthermore, the security guard reservation system of Invention 6 is the 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.

[0030] With this configuration, the request information presentation means presents request items based on the request information stored in the request information storage means. When changes are made to the presented request items, the request change information acquisition means acquires request change information relating to the changes to the request items, and the cost information generation means generates cost information for the work performed by the dispatcher when the security guard was dispatched, based on the request information and the request change information. [Effects of the Invention]

[0031] As explained above, the security guard reservation system of Invention 1 matches a dispatcher and a requester whose dispatch information and request information match the timing, location, and number of people, so that the requester's requests regarding the timing, location, and number of security guards requested can be reflected more effectively than in the past.

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

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

[0034] Furthermore, according to the security guard reservation system of Invention 4, contract information is provided to the dispatcher or the client, making it relatively easy to make a contract.

[0035] Furthermore, according to the security guard reservation system of Invention 5, if changes are made to the requested items, work report information can be obtained.

[0036] Furthermore, according to the security guard reservation system of Invention 6, if changes are made to the requested items, cost information for the work can be obtained. [Brief explanation of the drawings]

[0037] [Figure 1] FIG. 1 is a block diagram showing a configuration of a network system. [Figure 2] FIG. 2 is a diagram illustrating the hardware configuration of a security guard reservation server 100. [Figure 3] 4 shows 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. [Figure 4] 10 is a flowchart showing a security company information registration process. [Figure 5] This is the screen that is displayed when logging in to the security guard reservation server 100 using a security company account. [Figure 6] This is the screen that is displayed when logging in to the security guard reservation server 100 using a security company account. [Figure 7] 10 is a flowchart showing a contractor information registration process. [Figure 8] This is the screen that is displayed when logging in to the security guard reservation server 100 using the contractor's account. [Figure 9]This is the screen that is displayed when logging in to the security guard reservation server 100 using the contractor's account. [Figure 10] 10 is a flowchart showing a dispatch information registration process. [Figure 11] This is the screen that is displayed when logging in to the security guard reservation server 100 using a security company account. [Figure 12] 10 is a flowchart showing a request information registration process. [Figure 13] This is the screen that is displayed when logging in to the security guard reservation server 100 using the contractor's account. [Figure 14] This is the screen that is displayed when logging in to the security guard reservation server 100 using the contractor's account. [Figure 15] This is the screen that is displayed when logging in to the security guard reservation server 100 using the contractor's account. [Figure 16] This is the screen that is displayed when logging in to the security guard reservation server 100 using the contractor's account. [Figure 17] This is the screen that is displayed when logging in to the security guard reservation server 100 using the contractor's account. [Figure 18] This is the screen that is displayed when logging in to the security guard reservation server 100 using the contractor's account. [Figure 19] This is the screen that is displayed when logging in to the security guard reservation server 100 using the contractor's account. [Figure 20] This is the screen that is displayed when logging in to the security guard reservation server 100 using the contractor's account. [Figure 21] This is the screen that is displayed when logging in to the security guard reservation server 100 using the contractor's account. [Figure 22] 10 is a flowchart showing a business report process. [Figure 23] This is the screen that is displayed when logging in to the security guard reservation server 100 using a security company account. [Figure 24]This is the screen that is displayed when logging in to the security guard reservation server 100 using a security company account. DETAILED DESCRIPTION OF THE INVENTION

[0038] An embodiment of the present invention will be described below, with reference to Figures 1 to 24.

[0039] When a construction company carries out construction work, it is necessary to deploy security guards at the construction site. Therefore, the construction company requests a security company to dispatch security guards and deploys the security guards at the site. In this embodiment, multiple security companies and multiple construction companies are registered as members, and security companies and construction companies that match in terms of time, area, and number of people are matched.

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

[0041] As shown in Figure 1, the Internet 199 is connected to a security guard reservation server 100 that reserves security guards, multiple security company terminals 200 used by multiple security companies, multiple contractor terminals 210 used by multiple contractors, and a contract information management server 220 that manages contract information regarding contracts for the dispatch of security guards (hereinafter referred to as "security guard dispatch contracts").

[0042] 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 FIG.

[0043] 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 that stores the control program and other programs for the CPU 30 in a predetermined area, a RAM (Random Access Memory) 34 that stores data read from the ROM 32 and the 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 components are connected to each other and capable of sending and receiving data via a bus 39, which is a signal line for transferring data.

[0044] External devices connected to the I / F 38 include 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.

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

[0046] As shown in FIG. 3(a), the storage device 42 stores a security company information table 400 in which security company information relating to security companies is registered.

[0047] One record is registered for each security company in the security company information table 400. Each record includes fields for registering the security company ID, company name, phonetic name of the company, qualified billing business registration number, representative name, phonetic name of the representative name, person in charge name, phonetic name of the person in charge, area under responsibility 1, area under responsibility 2, area under responsibility 3, area under responsibility 4, area under 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).

[0048] Coverage areas 1 to 5 indicate areas to which a security company can dispatch security guards. Areas are measured 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), register the cities, wards, towns, and villages in Yamaguchi prefecture 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), register the cities, wards, towns, and villages in Yamaguchi prefecture in the Coverage Area 1 field and the cities, wards, towns, and villages in Fukuoka prefecture in the Coverage Area 2 field. Similarly, if security guards can be dispatched to cities, wards, towns, and villages in three prefectures, register the cities, wards, towns, and villages in the Coverage Areas 1 to 3 fields; if security guards can be dispatched to cities, wards, towns, and villages in four prefectures, register the cities, wards, towns, and villages in the Coverage Areas 1 to 4 fields; and if security guards can be dispatched to cities, wards, towns, and villages in five prefectures, register the cities, wards, towns, and villages in each prefecture in the Coverage Areas 1 to 5 fields.

[0049] As shown in FIG. 3(b), the storage device 42 stores a contractor information table 402 in which contractor information relating to contractors is registered.

[0050] The contractor information table 402 has one record registered for each contractor. Each record includes 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, postal code, address, telephone number, contact information for the person in charge, 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 include the qualified bill issuing business registration number and areas of responsibility 1 to 5.

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

[0052] The dispatch information table 404 registers one record 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, and day) when the security company can dispatch security guards, day / night classification (daytime or nighttime as the time period when dispatch is available), qualification classification (whether the security guard is qualified), and the number of security guards that can be dispatched. For example, if 78 qualified security guards and 79 unqualified security guards can be dispatched in the afternoon 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 will be registered in the dispatch information table 404. The first record will contain "2024 / 1 / 31", "Day", "Qualified", and "78", the second record will contain "2024 / 1 / 31", "Day", "Unqualified", and "79", the third record will contain "2024 / 1 / 31", "Evening", "Qualified", and "80", and the fourth record will contain "2024 / 1 / 31", "Evening", "Unqualified", and "81".

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

[0054] The request information table 406 registers one record 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 includes fields for registering the request ID, the security company ID of the requesting contractor, the date on which the contractor requests the dispatch of security guards, the day / night division, the qualification division, and the number of guards. 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 will be registered in the request information table 406. The first record will contain "2024 / 1 / 31", "Daytime", "Qualified", "78", "Security Company B's ID", and "Construction Contractor A's ID", the second record will contain "2024 / 1 / 31", "Daytime", "Unqualified", "79", "Security Company B's ID", and "Construction Contractor A's ID", the third record will contain "2024 / 1 / 31", "Night", "Qualified", "80", "Security Company B's ID", and "Construction Contractor A's ID", and the fourth record will contain "2024 / 1 / 31", "Night", "Unqualified", "81", "Security Company B's ID", and "Construction Contractor A's ID".

[0055] A request ID is an ID that is uniquely assigned to one request. For example, if the above example is one request, the same request ID is set in the first to fourth records. Furthermore, 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 the records with the same request ID.

[0056] As shown in FIG. 3(e), the storage device 42 stores an estimate information table 408 for registering estimate information relating to the estimated amount of money related to the requested item.

[0057] One record is registered for each request ID and quote ID in the quote information table 408. Each record includes fields for registering the request ID, quote ID, and quote amount related to the requested item.

[0058] As shown in FIG. 3(f), the storage device 42 stores a requested change information table 410 for registering requested change information relating to changes to requested items.

[0059] One record is registered for each request ID in the request change information table 410. Each record includes fields for registering the request ID and changes to the request (date, day / night division, qualification division, number of people, etc.).

[0060] As shown in FIG. 3(g), the storage device 42 stores a report information table 412 in which report information relating to the work performed by the security company when the security guard is dispatched is registered.

[0061] One record is registered for each request ID in the report information table 412. Each record includes fields for registering the request ID and one or more report items.

[0062] As shown in FIG. 3(h), the storage device 42 stores a billing information table 414 in which billing information relating to the amount billed by a security company for services performed by dispatching security guards is registered.

[0063] One record is registered for each request ID and billing ID in the billing information table 414. Each record includes fields for registering the request ID, billing ID, and billing amount related to the requested item.

[0064] As shown in FIG. 3(i), the storage device 42 stores a material information table 416 in which material information on materials used by a construction company at a site where security guards are deployed is registered.

[0065] One record is registered for each request ID in the material information table 416. Each record includes fields for registering the request ID, one or more materials, and their quantities.

[0066] 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 can also be configured as smartphones.

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

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

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

[0070] When a security company user accesses the security guard reservation server 100 on the security company terminal 200 and logs in using 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.

[0071] Once 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.

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

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

[0074] 8 and 9 show screens that are displayed when the contractor logs in to the security guard reservation server 100 using his / her account.

[0075] 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.

[0076] Once 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 Figure 7, and registers the received contractor information in the contractor information table 402.

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

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

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

[0080] When a user of a security company 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.

[0081] Dispatch information is set as follows. In the example of FIG. 11, a calendar for the month to which the current date belongs (e.g., 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 and a nighttime division. The daytime division has a field A for setting the number of qualified security guards available for dispatch that day, and a field B for setting the number of unqualified security guards available for dispatch that day. The nighttime division has a field A for setting the number of qualified security guards available for dispatch that night, and a field B for setting the number of unqualified security guards available for dispatch that night. In other words, four fields are provided for each day: daytime A, daytime B, nighttime A, and nighttime B. The user sets the number of security guards their company can dispatch for each date, daytime / nighttime division, and qualification division.

[0082] 10, the security guard reservation server 100 receives information on the date, day / night classification, qualification classification, and number of people from the security company terminal 200 through steps S120 and S122, 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.

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

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

[0085] 13 to 21 are screens that are displayed when a contractor logs in to the security guard reservation server 100 using their account.

[0086] 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 "Accept" button 510. When 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 a 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 as shown in FIG. 12, through step S130, and request information including the received area information is registered in the request information table 406 (a record corresponding to the request ID issued for that 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 whose area of ​​responsibility is registered is obtained from security company information table 400, and dispatch information corresponding to the obtained security company information is obtained from dispatch information table 404. Specifically, dispatch information including a security company ID that is the same as the security company ID included in the security company information is obtained. Then, through step S136, the obtained dispatch information is sent to contractor terminal 210.

[0087] When the contractor terminal 210 receives the dispatch information, based on the received dispatch information, the dates when security guards can be dispatched, the day / night classification, the qualification classification, and the number of security guards are displayed for each security company whose area of ​​responsibility is registered, as shown in FIG. 16. When the user wants to select a security company from which to request the dispatch of security guards, the user clicks the "Reservation" 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.

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

[0089] Once the request information has been set and the user wishes to arrange for the materials, the user clicks the "Click here if you are requesting a complete set of restricted materials" button 514. When button 514 is clicked, the security guard reservation server 100, as shown in FIG. 12, receives information on the date, day / night status, qualification status, and number of people from the contractor terminal 210, and registers the received request information in the request information table 406, through step S138. Meanwhile, the contractor terminal 210 allows the user to set material information, as shown in FIG. 18. The user sets the necessary materials and clicks the "Confirm" button 518. When button 518 is clicked, the security guard reservation server 100, as shown in FIG. 12, receives material information from the contractor terminal 210, and registers the received material information in the material information table 416, through step S142. Next, 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, through step S144. Then, through step S146, information on the requested items including the generated estimate information is transmitted to the contractor terminal 210.

[0090] 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 indicating that the request has been accepted is displayed, as shown in FIG. 21.

[0091] When the request is accepted, the security guard reservation server 100, as shown in FIG. 12, registers request information in the request information table 406 through step S150, including the ID of the security company receiving the request and the ID of the contractor making the request. This matches security companies and contractors with matching area, date, day / night shift, qualification classification, and number of employees. 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 that is the contractor of the security guard dispatch contract and the contractor terminal 210 of the contractor that is the contractor of the security guard dispatch 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 once the security company and the contractor each sign electronically, the security guard dispatch contract is established. Thereafter, the security company dispatches security guards to the specified site according to the request, and the contractor deploys the dispatched security guards at the construction site and performs the work.

[0092] When the user has completed setting the request information and does not wish to arrange for materials, he or she clicks the "Click here if you only wish to arrange for a guide" button 516 on the screen of Fig. 17. When button 516 is clicked, the screen transitions to the screen of Fig. 19.

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

[0094] The security guard reservation server 100 executes the service report process shown in the flowchart of Fig. 22 using the CPU 30. The service report process is executed in response to access from the security company terminal 200.

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

[0096] When a user of a security company 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, through steps S160 and S162 as shown in Fig. 22, 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.

[0097] 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 Figure 24. The user can set request change information on this screen. If there are changes in the number of security guards or if transportation costs or the like are incurred, the user sets the changes.

[0098] When the setting of the request change information is complete, the user clicks the "Send" button 526. When 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 registers the received request change information 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. Furthermore, 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.

[0099] 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 that can be dispatched for each of those one or more periods is registered in the dispatch information table 404 in association with security company information; request information regarding the area for which a construction company requests the dispatch of security guards is obtained; based on the dispatch information in the dispatch information table 404 that corresponds to the area related to the obtained request information, the one or more periods when dispatch is possible and the number of people that 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 company 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 association with construction company 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 companies that match the period, area, and number of people related to the dispatch information and request information are matched.

[0100] 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 reflect the contractor's requests regarding the timing, area, and number of people when requesting the dispatch of security guards more effectively than before.

[0101] 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 periods, areas, and each of the one or more periods during which 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 periods, areas, and each of the one or more set periods.

[0102] This allows for the reflection of desires regarding the number of qualified and unqualified security guards.

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

[0104] 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.

[0105] This makes it relatively easy to conclude a contract because the contract information is provided to the security company or construction company.

[0106] 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 report information is generated based on the request information in the request information table 406 and the obtained request change information.

[0107] This allows you to obtain business report information if you make changes to the requested items. 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 billing information is generated based on the request information in the request information table 406 and the obtained request change information.

[0108] This allows you to obtain billing information for the work by making changes to the requested 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.

[0109] 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 storage means of invention 1, the request information table 406 corresponds to the request information storage means of invention 1, 5 or 6, and the material information table 416 corresponds to the material information storage means of invention 3.

[0110] [Modification] In the above embodiment and its variants, an example was given of a configuration 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 this and the following configuration can also be adopted.

[0111] In the first configuration, multiple security companies and one contractor enter into a security guard dispatch contract for one request. Based on dispatch information related to the multiple security companies, one or more periods during which the security companies can dispatch and the number of personnel available for each period or periods are presented. For example, the calendar shown in FIG. 17 displays the total number of personnel available for dispatch by the multiple security companies. Then, request information related to the period and number of personnel set by the contractor within the range of the presented period and number of personnel is obtained, and multiple security companies that satisfy the content of the obtained request information are matched with the contractor. This allows the contractor's requests to be reflected, as multiple security companies may be able to accommodate the number of personnel requested by the contractor even if one security company cannot accommodate the number of personnel requested by the contractor.

[0112] 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 during which it can dispatch and the number of people it can dispatch for each of the periods or periods. 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 contractor belonging to the group is the representative is stored in a table or the like in the storage device 42. Then, request information regarding 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.

[0113] The third configuration is one in which multiple security companies and multiple contractors enter into security guard dispatch contracts 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 period or periods. One of the multiple contractors is then set as the representative contractor. 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 then obtained, and multiple security companies that meet the content of the obtained request information are matched with the multiple contractors represented by the representative contractor.

[0114] Furthermore, in the above embodiment and its variants, 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, but in order to deal with this, for example, the following configuration can be adopted.

[0115] The first configuration is a configuration that matches 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, for some reason, the number of personnel that a security company can dispatch decreases or the number of personnel requested by a construction company increases.The shortage construction company is identified based on construction company information and shortage information regarding the shortage of personnel, and an accommodating security company is identified based on security company information and dispatch information, and the identified shortage construction company and accommodating security company are matched. As a matching configuration, for example, (1) one or more accommodating security companies are presented to a shortage construction company, and the shortage construction company selects one from among them and matches that shortage construction company; (2) one or more shortage construction companies are presented to a accommodating security company, and the accommodating security company selects one from among them and matches that shortage construction 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 approached, and the security company that responds is matched with the shortage construction company; or (4) a configuration in which matching is performed according to a predetermined algorithm without selecting a security company or construction company.

[0116] The second configuration is a configuration that matches a security company (hereinafter referred to as an "excess security company") when there is an excess of personnel due to an increase in the number of people that a security company can dispatch or a decrease in the number of people requested by a construction company for some reason, with another construction company (hereinafter referred to as an "accommodating construction company") that requests a number of people that fits 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, and accommodating construction companies are identified based on construction company information and request information, and the identified excess security companies and accommodating construction companies are matched. Examples of matching configurations include: (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 an additional request is made to a construction company that has requested security guards for a period and area close to the time and area related to the request, and a construction company that responds to this request is matched with an excess security company; and (4) a configuration in which matching is performed according to a predetermined algorithm without selecting a security company or construction company.

[0117] The third configuration matches a shortage contractor related to a certain request with an excess security company related to another request. This configuration identifies a shortage contractor based on contractor information and shortage information related to the number of people in shortage, identifies an excess security company based on security company information and excess information related to the number of people in shortage, and matches the identified shortage contractor with the excess security company. 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 selects an excess security company from among them and matches 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 selects an shortage contractor from among them and matches the excess security company; (3) A configuration can be adopted in which, although the shortage of personnel is not possible, an excess security company that has requested security guards for a time and area close to the time and area related to the request is approached to dispatch security guards, and the excess security company is matched with the shortage construction company in response; (4) A configuration can be adopted in which, although the shortage of personnel is not possible, an excess construction company that has requested security guards for a time and area close to the time and area related to the request is approached to request an additional security guard, and the shortage construction company is matched with the excess security company in response; or (5) A configuration can be adopted in which matching is performed according to a predetermined algorithm without selecting security companies and construction companies.

[0118] Furthermore, in the above embodiment and its variations, no explanation has been given of the mechanism by which the operator of the security guard reservation server 100 earns profits. However, for example, the following configuration can be adopted.

[0119] 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. The predetermined percentage of the amount paid by the construction company to the security company is calculated based on billing information related to the amount, payment information is generated based on the calculation result, and payment processing is performed based on the generated payment information.

[0120] The second configuration is a configuration in which an amount according to the scale of the number of people dispatched by the security company, the number of times, etc. is collected as revenue from the security company. Payment information is generated based on scale information regarding the number of people dispatched by the security company, the number of times, etc., and payment processing is performed based on the generated payment information.

[0121] The third configuration is a configuration in which an amount according to the scale of the number of people, number of times, etc. requested by the construction company is collected as revenue from the construction company. Payment information is generated based on the scale information regarding the number of people, number of times, etc. requested by the construction company, and payment is processed based on the generated payment information.

[0122] Furthermore, in the above embodiment and its modifications, the contract information is sent to both the security company and the contractor, but this is not limiting, and the contract information may be sent to only some of the contractors.

[0123] In the above embodiment and its variations, the contract information management server 220 is provided separately from the security guard reservation server 100, but this is not limiting and they can be configured as an integrated server. In this case, the security guard reservation server 100 is configured to have the functions of the contract information management server 220.

[0124] In the above embodiment and its variations, the security guard reservation server 100 is implemented as a single device, but this is not limiting and it can also be implemented 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.

[0125] Furthermore, in the above-described embodiments and their variations, when executing the processes shown in the flowcharts of Figures 4, 7, 10, 12, or 22, a program pre-stored in ROM 32 is executed, but this is not limiting, and the program showing these procedures may be read into RAM 34 from a storage medium on which the program is stored and executed.

[0126] 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 all storage media that can be read by a computer, regardless of the reading method (electronic, magnetic, optical, etc.).

[0127] Furthermore, 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 modifications, but can also be applied to other cases within the scope of the present invention. [Explanation of symbols]

[0128] 100...security guard reservation server, 200...security company terminal, 210...construction 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...construction 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

1. a dispatch information registration means for registering dispatch information relating to one or more periods and locations when a dispatcher can 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 guard; a dispatch information presentation means for presenting the one or more periods during which dispatch is possible and the number of people who can be dispatched for each of the one or more 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 comprising a matching means for matching the dispatcher and the requester whose timing, 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.

2. In claim 1, The dispatch information is information regarding one or more periods and locations during which the 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 period or the multiple periods; A security guard reservation system characterized in that the request information is information regarding the one or more set periods, locations, and the number of qualified and unqualified security guards that the client requests to be dispatched for each of the one or more periods.

3. In any one of claims 1 and 2, a material information acquisition means for acquiring material information relating to 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.

4. In any one of claims 1 and 2, 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 to a client based on the client's client information, for the dispatcher and client to enter into a contract for the dispatch of the security guard.

5. In any one of claims 1 and 2, a request information presentation means for presenting a request item related to the request information based on the request information stored 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.

6. In any one of claims 1 and 2, a request information presentation means for presenting a request item related to the request information based on the request information stored 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