Photography Request System
The photography request system addresses the inefficiency of employee dispatch by enabling management companies to outsource photography tasks to third parties, reducing costs and improving target management efficiency while offering income opportunities.
Patent Information
- Application Number
- JP2024076615
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2024-05-09
- Publication Date
- 2026-11-11
- Estimated Expiration
- 2044-05-09
AI Technical Summary
Management companies face a heavy burden in confirming the state of remotely located management targets, as dispatching employees is costly and inefficient, and existing technologies like Japanese Patent Laid-Open Publication No. 2020-135873 do not address the need for requesting third parties to photograph managed items.
A photography request system that allows management companies to register photography requests, publish them to members, and manage the commissioning and data acquisition process, enabling third parties to photograph managed items and upload data efficiently.
Enables management companies to request and receive photographic data from third parties at a lower cost without dispatching employees, allowing efficient management of dispersed targets and providing income opportunities for members.
Smart Images

Figure 0007948636000001 
Figure 0007948636000002 
Figure 0007948636000003
Abstract
Description
Technical Field
[0001] The present disclosure relates to a photography request system, and more specifically, to a technology for requesting a member registered in the photography request system to perform photography of a management target.
Background Art
[0002] There are business types that manage management targets such as vehicles and real estate. In order to confirm the state of remotely located management targets, management entities that manage these management targets previously needed to dispatch employees to the site, or gather management targets from various locations at a single location. However, dispatching employees to confirm the state of remote management targets, or gathering management targets from various locations at a single location, imposes a heavy burden on business operators. Accordingly, a technology for such entities to more efficiently confirm the state of management targets is desired.
[0003] Further, in recent years, in fields such as food delivery, services exist in which producers such as restaurants outsource product delivery to third parties. Regarding delivery request technologies, for example, Japanese Patent Laid-Open Publication No. 2020-135873 (Patent Document 1) discloses a network system, which "transmits notification data to a user device to present a status notification to the user device. This status notification reminds the user to interact with the network-based service. The notification data can be selectively transmitted, and the user can selectively present the notification based on the possibility that the user has decided to issue a service request within a specific period. A metric representing such possibility is determined for the user based on historical data related to the network-based service. The metric is compared with one or more thresholds. In response to the interaction between the notification and the user, the user device presents a request user interface for a streamlined and simplified user experience when issuing a service request" (see [Abstract]).
Prior Art Documents
Patent Documents
[0004] [Patent Document 1] Japanese Patent Publication No. 2020-135873 [Overview of the Initiative] [Problems that the invention aims to solve]
[0005] According to the technology disclosed in Patent Document 1, it may be possible to request a service provider to deliver goods to service users. However, the technology disclosed in Patent Document 1 is not suitable for the purpose of a management company requesting a third party to photograph the managed items in order to check their condition. Therefore, there is a need for technology that allows a management company to request a third party to photograph the managed items.
[0006] This disclosure is made in light of the above-mentioned background, and in one aspect, its purpose is to provide a technology that allows a management company to request a third party to photograph the property under its management. [Means for solving the problem]
[0007] According to one embodiment, a photography request system is provided. The photography request system comprises a request registration unit that receives photography requests for management from a client; a request publication unit that publishes the photography request to one or more members; a commission registration unit that registers a member as a commissioned [Effects of the Invention]
[0008] According to one embodiment, a management company can request a third party to photograph the property under management.
[0009] The above and other purposes, features, aspects and advantages of this disclosure will become apparent from the following detailed description of this disclosure, which will be understood in conjunction with the attached drawings. [Brief explanation of the drawing]
[0010] [Figure 1] This diagram shows a part of the configuration of the photography request system 100. [Figure 2] This figure shows an example of the hardware configuration of the photography request system 100. [Figure 3] This figure shows an example of the first screen 300 displayed on the client terminal 110's display. [Figure 4] This figure shows an example of the second screen 400 displayed on the client terminal 110's display. [Figure 5] This figure shows an example of the third screen 500 displayed on the client terminal 110's display. [Figure 6] This figure shows an example of the fourth screen 600 displayed on the client terminal 110's display. [Figure 7] This figure shows an example of the first screen 700 displayed on the member terminal 120's display. [Figure 8] This figure shows an example of the second screen 800 displayed on the member terminal 120's display. [Figure 9] This figure shows an example of the third screen 900 displayed on the member terminal 120's display. [Figure 10] This figure shows an example of the fourth screen 1000 displayed on the member terminal 120's display. [Figure 11] This figure shows an example of the fifth screen 1100 displayed on the member terminal 120's screen. [Figure 12] This figure shows an example of the sixth screen 1200 displayed on the member terminal 120's screen. [Figure 13] This figure shows an example of a screen 1300 displayed on the terminal of the administrator of the photo request system 100. [Figure 14] This figure shows an example of a communication sequence between the photo shoot request system 100, the client terminal 110, and the member 120. [Modes for carrying out the invention]
[0011] Hereinafter, embodiments of the technical concept according to the present disclosure will be described with reference to the drawings. In the following description, the same components are denoted by the same reference numerals. Their names and functions are also identical. Therefore, detailed descriptions thereof will not be repeated. In addition, each embodiment, each modified example, each software configuration, each hardware configuration, each function, each process, and the like may be selectively combined as appropriate.
[0012] <A. System Configuration> Figure 1 is a diagram showing a part of the configuration of the photography request system 100. With reference to Figure 1, the overall overview and operation outline of the photography request system 100 according to the present embodiment will be described. In addition, main terms used in this specification will also be explained. The photography request system 100 enables a client, who is a business operator managing any management target, to request a member registered in the photography request system 100 to photograph the management target.
[0013] (a. Configuration of the Photography Request System) The photography request system 100 includes, as main functional units, a request registration unit 101, a request publication unit 102, an acceptance registration unit 103, a photography data acquisition unit 104, a notification unit 105, a storage unit 106, and an evaluation unit 107. These functional units may be implemented as programs, or may be implemented as hardware. In addition, the photography request system 100 is configured to be communicable with one or more client terminals 110 and one or more member terminals 120.
[0014] In the example of Figure 1, three client terminals 110A, 110B, 110C and three member terminals 120A, 120B, 120C are illustrated, but this is merely an example. The photography request system 100 can communicate with any number of client terminals 110. In addition, the photography request system 100 can communicate with any number of member terminals 120. Hereinafter, when collectively referring to client terminals, they are described as client terminal 110. When referring to an individual client terminal, they are described as client terminals 110A, 110B, 110C. Similarly, when collectively referring to member terminals, they are described as member terminal 120. When referring to an individual member terminal, they are described as member terminals 120A, 120B, 120C.
[0015] The request registration unit 101 receives a photography request registration request from the client terminal 110, and registers or stores information related to the request in the storage unit 106. The photography request registration request may include all or part of the information related to the request, such as the client (requester), the photography target, the range of available photography dates and times, the location of the photography target, and the contact information for the day. In a certain aspect, the client can edit, add, and delete the content of the request registered in the photography request system 100 via the client terminal 110. As an example, the client may register a photography request registration request including part of the information related to the request in the photography request system 100, and then additionally register the details of the request in the photography request system 100.
[0016] The request disclosure unit 102 discloses the requests registered in the memory unit 106 to one or more members registered in the photography request system 100. In some cases, the request disclosure unit 102 may disclose the requests to some of the members registered in the photography request system 100 based on information about the location of the subject to be photographed and information about the areas that the member is responsible for (hereinafter referred to as "responsible areas"). More specifically, the request disclosure unit 102 discloses the requests to a certain member based on the fact that the location of the subject to be photographed is included in that member's responsible area. In other cases, the request disclosure unit 102 may disclose the requests to all members registered in the photography request system 100. Members can refer to the requests disclosed to them via the member terminal 120.
[0017] The commission registration unit 103 receives a commission request from the member terminal 120 and registers or stores information related to the commission in the storage unit 106. For example, a member can accept a publicly available request by pressing a commission button or the like on the screen of the member terminal 120. Based on the fact that the commission button or the like has been pressed, the member terminal 120 sends a commission request to the photography request system 100. The commission registration unit 103 replies with a commission response message to the member terminal 120.
[0018] If the commission registration unit 103 receives multiple commission requests for a single request, it may send a commission acceptance response message to the member terminal 120 that has accepted the request, and a commission acceptance response message to the other member terminals 120 that have failed to accept the request. In some cases, the commission registration unit 103 may accept requests on a first-come, first-served basis. In other cases, the commission registration unit 103 may solicit commissions for publicly available requests for a certain period of time and select commissioners from among the applicant members by lottery or other means.
[0019] The shooting data acquisition unit 104 acquires the managed shooting data from the member terminal 120 and registers the shooting data in the storage unit 106. The shooting data acquisition unit 104 also outputs a notification to the notification unit 105 regarding the registration of the managed shooting data. In certain situations, the shooting data acquisition unit 104 may acquire any information other than shooting data. Any information other than shooting data includes text, voice, signals from various sensors, or combinations thereof. For example, suppose the managed object is a vehicle. In this case, the shooting data acquisition unit 104 may acquire information such as the smell inside the vehicle and abnormal engine noises as text or voice.
[0020] The notification unit 105 sends various notifications or messages to the client terminal 110 and the member terminal 120. For example, the notification unit 105 may send to the client terminal 110 a message indicating completion of registration of a photography request, a notification indicating registration of photography data, a notification indicating completion of payment of compensation to the member, and other optional notifications. As another example, the notification unit 105 may send to the member terminal 120 a notification indicating the publication of a new request, a notification indicating completion of acceptance, a notification indicating failure to accept an acceptance, and other optional notifications.
[0021] The memory unit 106 stores various types of data used by the photography request system 100. For example, the memory unit 106 stores information about clients, information about members, regional information, information about requests, information about accepted requests, and information about payment of remuneration.
[0022] Client information includes optional information about the client, such as client ID (Identifier), client name, client address, client contact information, and the type of services the client provides. Member information includes optional information about the member, such as member ID, member name, member address, member contact information, member's means of transportation, and one or more assigned regions of the member. Regional information includes map information and information about each region divided on the map. When a member registers with the photo shoot request system 100, they select at least one of the regions divided on the map. This allows the photo shoot request system 100 to obtain information about each member's assigned region. The photo shoot request system 100 can use the information about each member's assigned region to make the registered request available only to members who are capable of handling it.
[0023] Request information includes optional information such as the request ID, details of the subject to be photographed, location of the subject, range of possible dates and times for photography, compensation amount, contact information for the day, and emergency contact information. Acceptance registration information includes information indicating which member has accepted which request. For example, acceptance registration information may include information such as acceptance ID, member ID, request ID, and acceptance date. Request information or acceptance registration information may also include a flag indicating whether the request has been completed, photographic data, etc. Compensation payment information includes optional information regarding payment to the member. For example, compensation payment information may include the payment ID, acceptance ID, member ID, and optional information regarding compensation payment such as the payment deadline.
[0024] The evaluation unit 107 receives registration of evaluation information from clients for members who have accepted a request (sometimes referred to as "contractors"). The evaluation unit 107 registers or stores the received evaluation information in the storage unit 106. The photography request system 100 may provide incentives to each member based on the evaluation. For example, the photography request system 100 may change the amount of reward paid to members according to their evaluation. For example, a member with an evaluation of 5 may receive a higher reward for completing a request than a member with an evaluation of 1. As another example, the photography request system 100 may make each client able to refer to each member's evaluation. Each client may register a setting with the photography request system 100 via the client terminal 110 to only request work from members who have received an evaluation of a certain level or higher. Furthermore, as yet another example, the photography request system 100 may differentiate the ease of acceptance of requests for each member according to their evaluation. For example, if the photography request system 100 employs a first-come, first-served system for accepting requests, it may make requests available to members with an evaluation of 5 a certain amount of time earlier than to members with an evaluation of 1. Alternatively, if the photography request system 100 employs a lottery system for accepting commissions, it may increase the probability of a member with a rating of 5 being selected compared to a member with a rating of 1.
[0025] In certain situations, the photo shoot request system 100 may include other functional components not shown in Figure 1. For example, the photo shoot request system 100 may include a user registration unit (not shown) that accepts new client and member registrations, editing of registration information, and withdrawals. The photo shoot request system 100 may also include various UIs (User Interfaces) (not shown) for using the functions of the photo shoot request system 100. If the photo shoot request system 100 has the functionality of a web application, these UIs may be provided to the user. For example, a client may operate these UIs via the browser on the client terminal 110. All data transmission and reception between the client terminal 110 and the photo shoot request system 100 may be performed via these UIs. Similarly, the photo shoot request system 100 may provide an administrator UI to the administrator's terminal (not shown). For example, an administrator may operate the administrator UI via the browser on the administrator's terminal.
[0026] In certain situations, the client terminal 110 and the member terminal 120 may be personal computers, tablets, smartphones, or any other information devices. Furthermore, the client terminal 110 and the member terminal 120 may utilize the functions of the photography request system 100 via a browser. Additionally, the member terminal 120 may download a photography contracting program and communicate with the photography request system 100 through this program. This photography contracting program can be implemented, for example, as a smartphone application.
[0027] (b. Overview of the operation of the photo shoot request system) Next, the operation overview of the photography request system 100 will be described with reference to map 130. Map 130 is a simplified map and includes nine regions 1A, 2A, 3A, 1B, 2B, 3B, 1C, 2C, and 3C. The photography request system 100 stores information about map 130 and each region contained in map 130 in the storage unit 106. In practice, map 130 may be a map of Japan, a map of another country, or a world map, etc. Also, regions can be divided into any unit such as states, provinces, prefectures, cities, or districts. Furthermore, each of the client terminals 110A to 110C is assumed to be a terminal of clients A to C, and each of the member terminals 120A to 120C is assumed to be a terminal of members A to C.
[0028] First, each member registers with the photography request system 100 by selecting the region they are responsible for via the member terminal 120. Let's assume that Member A selects regions 1A, 2A, and 3A, Member B selects regions 1B, 2B, and 3B, and Member C selects regions 1C, 2C, and 3C. When each member is registered, the photography request system 100 associates each member with each region and stores this association information in the storage unit 106. This association information may also be included in the member's information.
[0029] Next, suppose client A registers a first request and a second request in the photography request system 100. Assume the location of the subject to be photographed in the first request is in region 1A. Also, assume the location of the subject to be photographed in the second request is in region 2C. In this case, the photography request system 100 makes the first request available to member terminal 120A of member A, who is capable of handling region 1A. Similarly, the photography request system 100 makes the second request available to member terminal 120C of member C, who is capable of handling region 2C. In this way, the photography request system 100 makes requests available to members who are capable of handling them. In certain situations, if there are no members capable of handling a request at the time of registration, the photography request system 100 may display a message to that effect on the request registration screen and reject the registration of the request. For example, if there are no members capable of handling region 1A, where the subject to be photographed in the first request is located, the photography request system 100 may reject the registration of the first request at the time of registration. In other situations, the photography request system 100 may accept the registration of a request even if there are no members available to handle the request at the time of registration. In this case, the client will wait for a member who is available to handle the request to register.
[0030] Next, the member selects a desired request from the requests made public to them via the member terminal 120 and registers to accept it. Upon successful registration, the member becomes a contractor. The contractor photographs the subject of the accepted request within the designated shooting period and uploads the photographic data to the shooting request system 100. The uploaded data may include any data other than photographic data, such as audio data and text data.
[0031] Next, the shooting request system 100 receives input from the administrator's terminal confirming whether the shooting data is pass or fail. If there are no problems with the shooting data, the shooting request system 100 may accept input from the administrator indicating a pass. In this case, the shooting request system 100 sends a completion notification to the member terminal 120 and a shooting data registration notification to the client terminal 110. If there are problems with the shooting data, the shooting request system 100 may accept input from the administrator indicating a fail. In this case, the shooting request system 100 sends a re-upload request to the member terminal 120. In some situations, the client, not the administrator, may perform the verification of the shooting data. In this case, the administrator does not need to perform the verification of the shooting data. In other situations, the shooting request system 100 may send a notification of the shooting data upload to the administrator's terminal based on the fact that the shooting data has been uploaded.
[0032] Finally, the shooting request system 100 receives a shooting data confirmation response from the client terminal 110. The shooting data confirmation response may include the contractor's evaluation information. The shooting request system 100 also performs the payment process for the reward. The shooting request system 100 may perform the payment process for each completed request. Alternatively, the shooting request system 100 may perform the payment process periodically, such as at the end of the month. When the shooting request system 100 receives a shooting data confirmation response requesting resubmission, it sends a resubmission request notification to the contractor's member terminal 120. After that, the shooting request system 100 accepts the re-upload of the shooting data to be photographed.
[0033] As described above, the shooting request system 100 includes a request registration unit 101 that receives shooting requests for management from clients, a request publication unit 102 that publishes shooting requests to one or more members, a commission registration unit 103 that registers a member as a commissioned worker based on the receipt of a commission request for a shooting request from the terminal (member terminal 120) of one or more members, a shooting data acquisition unit 104 that receives shooting data related to the shooting request from the commissioned worker's terminal (member terminal 120), and a notification unit 105 that sends a shooting data registration notification for the shooting request to the client's terminal (client terminal 110).
[0034] Furthermore, by executing the photography contracting program, the member terminal 120 can display information about the managed photography requests obtained from the photography request system 100 on its display, send a request to accept the photography request to the photography request system 100 based on the acceptance of the photography request operation, receive location information of the managed object, range information of possible dates and times for photography, and contact information of the on-site person in charge from the photography request system 100, and upload photography data related to the photography request to the photography request system 100.
[0035] In this way, the photography request system 100 receives registration requests from each client to acquire photographic data for their target areas. The photography request system 100 then makes each request available to one or more members who are capable of handling it. Members select and accept the requests they wish to take on, and upload (i.e., deliver) the photographic data for the accepted requests to the photography request system 100. Through this process, clients can, for example, manage a large number of target areas scattered in various locations at a low cost without having to dispatch employees. In addition, members can earn income without difficulty by accepting photography requests in their own living area.
[0036] (c.Term) Next, the main terms used in this specification will be explained. In this specification, “system” refers to a mechanism that provides some function. A system may consist of one or more devices. A system may also be a server, instance, or virtual machine on a cloud environment. A system may also be a server application running on one or more devices or a cloud environment. Furthermore, if a system consists of one or more devices, it may be referred to as a device. The imaging request system 100 may be both a system and a device.
[0037] In this specification, "client" refers to a corporation, organization, or individual that provides some kind of service. For example, a client may be a leasing company, a real estate company, an insurance company, or a buyer. In this specification, "member" refers to a corporation, organization, or individual that has registered as a member of the filming request system 100. A member who accepts a request may also be called a "contractor." Furthermore, a member who accepts a request may also be called a "worker" because they perform filming work on-site.
[0038] In this specification, “Managed Items” refers to any items that the client is responsible for managing. For example, managed items may include any items such as vehicles, office equipment, and real estate. Furthermore, managed items do not necessarily have to be owned by the client. For example, if the client is a car insurance company, managed items might be the vehicles of their insured customers or the condition of accident scenes. Another example is if the client is a used goods buyer; managed items might be the items subject to purchase appraisal. Therefore, managed items may be referred to as subjects for photography, subjects for appraisal, subjects for verification, or any other name as appropriate, depending on the client's industry.
[0039] Figure 2 shows an example of the hardware configuration of the photography request system 100. In a given scenario, each functional unit shown in Figure 1 can be realized by executing a program on the hardware shown in Figure 2. The client terminal 110 and the member terminal 120 may also have some or all of the configuration shown in Figure 2. In this case, the various functions of the member terminal 120 can be realized by executing the photography contract program on the hardware shown in Figure 2.
[0040] The imaging request system 100 includes a processor 201, memory 202, storage 203, external device interface 204, input interface 205, output interface 206, and communication interface 207.
[0041] The processor 201 can execute programs to realize various functions of the imaging request system 100. The processor 201 is composed of, for example, at least one integrated circuit. According to one embodiment, the integrated circuit may include at least one CPU (Central Processing Unit), at least one GPU (Graphics Processing Unit), at least one FPGA (Field Programmable Gate Array), at least one ASIC (Application Specific Integrated Circuit), at least one AI (Artificial Intelligence) chip, or a combination thereof.
[0042] Memory 202 functions as a workspace for processor 201. Memory 202 stores programs executed by processor 201 and data referenced by processor 201. In some cases, memory 202 may be implemented as DRAM (Dynamic Random Access Memory) or SRAM (Static Random Access Memory), etc.
[0043] Storage 203 is non-volatile memory that stores programs executed by processor 201 and data referenced by processor 201. Processor 201 executes programs read from storage 203 into memory 202 and references data read from storage 203 into memory 202. In some cases, storage 203 can be implemented by an HDD (Hard Disk Drive), SSD (Solid State Drive), EPROM (Erasable Programmable Read Only Memory), EEPROM (Electrically Erasable Programmable Read Only Memory), or flash memory, etc.
[0044] The external device interface 204 can be connected to any external device such as a printer, scanner, and external HDD. In some cases, the external device interface 204 can be implemented using a USB (Universal Serial Bus) terminal or the like.
[0045] The input interface 205 can be connected to any input device such as a keyboard, mouse, touchpad, or gamepad. In some cases, the input interface 205 can be implemented using a USB terminal, PS / 2 terminal, and Bluetooth® module, etc.
[0046] The output interface 206 can be connected to any output device such as a cathode ray tube display, a liquid crystal display, or an organic EL (Electro-Luminescence) display. In some cases, the output interface 206 can be implemented using a USB terminal, a D-sub terminal, a DVI (Digital Visual Interface) terminal, an HDMI® (High-Definition Multimedia Interface) terminal, or a DisplayPort terminal.
[0047] The communication interface 207 is connected to other devices via a wired network or a wireless network. In one aspect, the communication interface 207 can be implemented by a wired LAN (Local Area Network) port, a Wi-Fi (registered trademark) (Wireless Fidelity) module, or the like. In another aspect, the communication interface 207 can transmit and receive data using communication protocols such as TCP / IP (Transmission Control Protocol / Internet Protocol) and UDP (User Datagram Protocol).
[0048] <B. Screen Example> Next, an example of screens displayed on the respective displays of the client terminal 110, the member terminal 120, and the administrator's terminal will be described. FIGS. 3 to 6 show examples of screens displayed on the display of the client terminal 110. These screens may be displayed on the browser of the client terminal 110. FIGS. 7 to 12 show examples of screens displayed on the display of the member terminal 120. These screens may be screens of a photography contracting program installed in the member terminal 120. FIG. 13 shows an example of a screen displayed on the display of the administrator's terminal of the photography request system 100.
[0049] FIG. 3 is a diagram showing an example of the first screen 300 displayed on the display of the client terminal 110. The first screen 300 is a top screen provided to the client terminal 110. When the client terminal 110 logs in to the photography request system 100, the first screen 300 is displayed on the display of the client terminal 110.
[0050] The first screen 300 includes, as main display items, a menu 310, notifications from the operator 320, alert task list information 330, this month's task completion list 340, pending task execution 350, and the most recent one-week task schedule list 360.
[0051] Menu 310 contains one or more items for transitioning to other screens. By selecting an item in the menu, the client can transition from the current screen to the second screen 400 to the fourth screen 600 and other screens. Announcements from the Management 320 displays one or more announcements from the management in chronological order.
[0052] The alert work list information 330 displays a list of alerts related to registered requests. For example, a client may be able to read an urgent message from the contractor by selecting an alert. In this case, the contractor may register a message in the shooting request system 100 from the member terminal 120, such as "I can't go to the site today" or "I can't contact the manager in charge at the site."
[0053] The "Completed Work List for This Month" (340) displays a list of completed work (requests) in chronological order of completion. The "Work Awaiting Completion" (350) displays a list of currently requested work. The "Work Schedule for the Next Week" (360) displays a list of currently requested work that will be completed within the next week. In some cases, the "Work Awaiting Completion" (350) and "Work Schedule for the Next Week" (360) may display the range of possible shooting dates and times along with the subject. In other cases, the client can transition the current screen to the fourth screen (600) (see Figure 4) by selecting a subject in the "Work Awaiting Completion" (350) or "Work Schedule for the Next Week" (360).
[0054] Figure 4 shows an example of the second screen 400 displayed on the client terminal 110's screen. The second screen 400 is a screen for registering a shooting request. The client can transition from the current screen to the second screen 400 by selecting "Register Task" from menu 310.
[0055] The second screen 400 includes, as its main display items, a contact input field 410, an input field 420 for information to be managed, an input field 430 for work date and time, an input field 440 for location, an input field 450 for remarks, a cancel button 460, and a request button 470.
[0056] Contact information field 410 is for entering contact information that the contractor can reach. For example, suppose the vehicle being managed is leased to a certain corporation. In this case, the contact person on the day would be the phone number and email address of the person managing the vehicle at that corporation. The emergency contact information would be the contact information of an employee of the client corporation.
[0057] Input field 420 for managed information is an optional input field for information about the managed item. If the managed item is a vehicle, input field 420 for managed information includes items related to the vehicle, such as the manufacturer name and license plate number.
[0058] Input field 430 for work date and time is for entering the range of dates and times when photography is possible. In many cases, the subject of management is likely to be located on the premises of a corporation or similar organization. Therefore, it is desirable for the client to specify in input field 430 the range of dates and times when the on-site person in charge (such as the premises manager) is available to respond.
[0059] The location input field 440 is for entering the location to be managed. The location input field 440 may be configured to allow selection of a location from a map, or to allow input of an address. In addition, the location input field 440 may be configured to allow input of the name of the location, supplementary information such as detailed directions to the destination, etc.
[0060] The remarks input field 450 is for entering any supplementary information. The client may enter special notes or other information in the remarks input field 450. When the cancel button 460 is pressed, it discards the request and transitions the screen to the first screen 300. When the request button 470 is pressed, it sends a shooting request registration request to the shooting request system 100. In practice, the request registration unit 101 receives the shooting request registration request. In one scenario, the second screen 400 may have one or more additional input fields in addition to the items shown in Figure 4, such as the request amount, the request period (the period during which the request is made public), and the conditions of the contractor. In another scenario, suppose that no member capable of handling the area including the location to be managed is registered in the shooting request system 100. In this case, the request registration unit 101 may, without processing the shooting request registration, respond to the shooting request registration request by sending a notification to the client terminal 110 indicating that the shooting request cannot be accepted. When the client terminal 110 receives a notification indicating that the shooting request cannot be accepted, it may display a pop-up message indicating that the shooting request registration failed on the second screen 400.
[0061] A photography request registered in the photography request system 100 is made public to one or more members registered in the photography request system 100. The registered photography request may be made public to members who are responsible for the area including the location to be managed, or it may be made public to all members. The items entered on the second screen 400 are made public as the request details. Alternatively, some of the items entered on the second screen 400 (such as contact information for the day) may be made public only to the contractor's member terminal 120.
[0062] As explained with reference to Figure 4, the client can register various information necessary for photographing the managed property leased to the corporation, etc., in the photography request system 100 via the second screen 400. The contractor can then refer to this information (contact information for the day, work date and time, etc.) to photograph the managed property located on the corporation's premises, which would normally be inaccessible.
[0063] As explained with reference to Figure 4, the photography request system 100 includes a storage unit 106 that stores the area information of each of one or more members. A photography request includes location information of the subject to be photographed. Furthermore, disclosing a photography request to one or more members includes determining the area where the subject to be photographed is located by referring to the location information, and disclosing the photography request to the members responsible for the area where the subject to be photographed is located by referring to the area information.
[0064] Furthermore, the request registration unit 101 sends a notification to the client terminal 110 indicating that the photography request cannot be accepted, based on the fact that there is no member responsible for the area where the subject of photography is located.
[0065] Furthermore, the photography request includes information on the range of dates and times when photography is possible for the managed area, as well as contact information for the on-site person in charge. The contract registration unit 103 transmits or publishes the information on the range of dates and times when photography is possible, and the contact information for the on-site person in charge, to the contractor's terminal (member terminal 120).
[0066] Figure 5 shows an example of the third screen 500 displayed on the client terminal 110's display. The third screen 500 is a screen for displaying a list of shooting requests and completed work. The client can transition from the current screen to the third screen 500 by selecting "Shooting Request / Completed Work List" from menu 310.
[0067] The third screen 500 includes, as its main display items, a filtering item 510 and a list of photography requests and completed projects 520. The list of photography requests and completed projects 520 displays a list of currently requested photography requests, completed projects (requests), or both. By selecting a row in the list of photography requests and completed projects 520, the client can transition the current screen to the fourth screen 600 corresponding to each request. The filtering item 510 provides a filtering function for the display items in the list of photography requests and completed projects 520. The filtering item 510 allows filtering of the display items in the list of photography requests and completed projects 520 by arbitrary conditions such as the range of possible dates and times for photography (request date, request time, etc.), address, vehicle license plate number, etc. As an example, by selecting a request that the client wants to complete urgently from the list of photography requests and completed projects 520, the client can transition the current screen to the fourth screen 600 (editing screen) of the selected request. The client can then edit the fourth screen 600 and change the request amount for the urgent request to make it more likely to be accepted.
[0068] Figure 6 shows an example of the fourth screen 600 displayed on the client terminal 110's screen. The fourth screen 600 is a screen for editing the details of an ongoing photography request. The fourth screen 600 can also be used as a page for checking the photography data and accompanying data uploaded by the contractor.
[0069] For example, a client can transition the current screen to the fourth screen 600 corresponding to the selected shooting request by selecting a shooting request from either the first screen 300 (awaiting work execution) 350 or the list of scheduled work for the past week 360. As another example, a client can transition the current screen to the fourth screen 600 corresponding to the selected shooting request by selecting a shooting request from the list of shooting requests and completed work 520.
[0070] The fourth screen 600 includes, as its main display items, an editing field 610 for contact information, an editing field 620 for managed information, an editing field 630 for work date and time, an editing field 640 for location, an editing field 650 for remarks, an input field 660 for worker information, a display field 670 for photographed data, a display field 680 for accompanying data, a withdrawal button 690, and an edit button 692.
[0071] The Contact editing field 610 is for editing the content entered in the Contact input field 410. The Managed Information editing field 620 is for editing the content entered in the Managed Information input field 420. The Work Date and Time editing field 630 is for editing the content entered in the Work Date and Time input field 430. The Location editing field 640 is for editing the content entered in the Location input field 440. The Remarks editing field 650 is for editing the content entered in the Remarks input field 450. These fields are configured to be editable until the shooting data is uploaded.
[0072] The withdrawal button 690 is used to withdraw a request. When the withdrawal button 690 is pressed, the client terminal 110 sends a request withdrawal request to the photo shoot request system 100. Based on the receipt of the request withdrawal request, the photo shoot request system 100 deletes the photo shoot request for which a withdrawal request was made from the storage unit 106. The edit button 692 is used to activate edits made on the fourth screen 600. When the edit button 692 is pressed, the client terminal 110 sends a registration information change request to the photo shoot request system 100. Based on the receipt of the registration information change request, the photo shoot request system 100 registers the changed information in the storage unit 106 and sends a registration information change notification to the contractor's member terminal 120. As an example, the client can change the contact information for the day, the date and time of work, the amount of compensation, etc., by operating the fourth screen 600.
[0073] The worker information input field 660 is for inputting information about the contractor (i.e., the worker at the site). After uploading the shooting data, the client may input an evaluation and comments for the contractor in the worker information input field 660. The information entered in the worker information input field 660 is registered in the shooting request system 100 and is also notified to the contractor's member terminal 120 as feedback information. In some cases, some items in the worker information input field 660, such as the date and time of work completion, the worker's name, and the amount, may be automatically entered by referring to at least some of the member information, request information, and contract information in the storage unit 106. In other cases, the entered evaluation information may be used as an incentive for the member. For example, the request publication unit 102 may adjust the publication time of the shooting request for each of one or more members, or the reward for the shooting request, based on the evaluation information.
[0074] The display item 670 for the shooting data displays one or more shooting data or thumbnails uploaded by the contractor to the shooting request system 100. The client can view a larger image corresponding to each thumbnail by selecting it. The number and types of photos may be configurable on the second screen 400. The type of photo here may indicate the orientation, distance, or angle of the subject being photographed.
[0075] The 680 items of the accompanying data display include any data other than photographs. For example, if the managed object is a vehicle, it may include information such as the smell of cigarette smoke inside the vehicle and the reading of the odometer. This accompanying data may be in any format, such as text data or checkboxes.
[0076] As explained with reference to Figure 6, the photography request system 100 further includes an evaluation unit 107 that receives registration of evaluation information for contractors from clients. The request publication unit 102 can also adjust the publication time of the photography request for each of one or more members, or the compensation for the photography request, based on the evaluation information.
[0077] Figure 7 shows an example of the first screen 700 displayed on the member terminal 120. The first screen 700 is the screen for registering as a member with the photo request system 100. The first screen 700 is also the screen for editing member information or withdrawing from membership.
[0078] For example, the first screen 700 is displayed on the member terminal 120's screen when the photography contract program is first launched. The first screen 700 includes, as its main display items, input fields for member information 710, input fields for available activity areas 720, input fields for payment account 730, a cancel button 740, a register button 750, and a withdrawal button 760.
[0079] The member information input field 710 is for entering information about the member. For example, in addition to the member's name and contact information, the member information input field 710 may also include an input field for the member's means of transportation. The activity area input field 720 is for entering one or more areas (i.e., assigned areas) in which the member can conduct photography. The photography request system 100 links each member to each area based on the area information registered in the memory unit 106 and the input content of the activity area input field 720. The payment account input field 730 is for entering the account to which the member's compensation will be paid.
[0080] The Cancel button 740 is used to cancel member registration or editing of registration information. When the Cancel button 740 is pressed, the member terminal 120 discards the registration or editing content and transitions the screen to the second screen 800, which is the top screen. The Register button 750 is used to activate member registration or modification of registration information. When the Register button 750 is pressed, the member terminal 120 sends a member registration request to the photo request system 100. Based on the receipt of the member registration request, the photo request system 100 registers information about the new member in the storage unit 106 or updates information about the existing member. The Withdrawal Processing button 760 is used to delete member information from the photo request system 100. When the Withdrawal Processing button 760 is pressed, the member terminal 120 sends a withdrawal request to the photo request system 100. Based on the receipt of the Withdrawal Request, the photo request system 100 deletes information about the member who made the withdrawal request from the storage unit 106.
[0081] Figure 8 shows an example of the second screen 800 displayed on the member terminal 120's display. The second screen 800 is the top screen displayed on the member terminal 120's display. When the photography contract program installed on the member terminal 120 is started, the second screen 800 is displayed on the member terminal 120's display. The second screen 800 includes the following main display items: menu 810, announcements from management 820, completed (unfinished) list 830, and completed work for this month list 840.
[0082] Menu 810 contains one or more items for transitioning to other screens. Members can transition from the current screen to Screen 1 700, Screen 3 900-6 1200, and other screens by selecting an item in the menu. Announcements from Management 820 displays one or more announcements from management in chronological order. The Accepted (Pending) List 830 displays a list of currently accepted but incomplete requests. Members can transition from the current screen to Screen 5 1100 by selecting any row in the Accepted (Pending) List 830. The List of Work Completed This Month 840 displays a list of work (requests) completed this month, sorted by completion date.
[0083] Figure 9 shows an example of the third screen 900 displayed on the member terminal 120. The third screen 900 is a screen for displaying a list of accepted requests. Members can transition from the current screen to the third screen 900 by selecting "Accepted Requests List" from the menu 810.
[0084] The third screen 900 includes, as its main display items, a filtering item 910, a request list 920, and a map 930 showing the location of the subject to be photographed. The request list 920 displays a list of requests that the member is currently accepting. The filtering item 910 is an item for filtering the requests displayed in the request list 920. The filtering item 910 allows the display items of the request list 920 to be filtered by arbitrary conditions such as the range of possible shooting dates and times (request date, request time, etc.), address, vehicle license plate number, etc. By selecting an item in the request list 920, the member can transition from the current screen to the fifth screen 1100. On the fifth screen 1100, the member can check the details of the request. In addition, the member can understand the location of the subject to be photographed for each request by referring to the map 930 showing the location of the subject to be photographed.
[0085] Figure 10 shows an example of the fourth screen 1000 displayed on the member terminal 120. The fourth screen 1000 is a screen for confirming and accepting requests. Members can transition from the current screen to the request list page by selecting "Request List" from menu 810. Members can also transition from the current screen to the fourth screen 1000 by selecting an item within the request list.
[0086] The fourth screen 1000 includes, as its main display items, a contact item 1010, a managed item 1020, a work date and time item 1030, a location item 1040, a remarks item 1050, a cancel button 1060, and an accept button 1070. The contact item 1010, managed item 1020, work date and time item 1030, location item 1040, and remarks item 1050 display the various items entered on the second screen 400 of the client terminal 110.
[0087] The cancel button 1060 is a button to return to the top screen without accepting the request. The accept button 1070 is a button to accept the request. When the accept button 1070 is pressed, the member terminal 120 sends an acceptance request to the photo request system 100. The photo request system 100 receives the acceptance request and, based on its approval of the acceptance request, sends an acceptance response message to the member terminal 120. In some cases, the photo request system 100 may assign the request to the member who submitted the acceptance request first. In other cases, the photo request system 100 may select a member to accept the request by lottery.
[0088] Figure 11 shows an example of the fifth screen 1100 displayed on the member terminal 120. The fifth screen 1100 is a screen for confirming information about the commissioned request. The contractor heads to the location where the subject to be photographed is located on the day of the shoot, while checking the map and other information on the fifth screen 1100. In addition to the display items of the fourth screen 1000, the fifth screen 1100 includes an input button 1110. When the input button 1110 is pressed, the member terminal 120 transitions the current screen to the input screen 1120. The input screen 1120 is a screen for photographing the subject to be photographed and inputting accompanying data. Upon arrival at the location, the contractor can display the input screen 1120 on the member terminal 120 and photograph the subject to be photographed and input accompanying data.
[0089] The input screen 1120 includes, as its main display items, a license plate input field 1121, a photo shooting field 1122, an associated data input field 1123, a sample image display field 1124, a cancel button 1125, a temporary save button 1126, and a complete button 1127.
[0090] The license plate input field 1121 is for entering the license plate number. If the subject of the photograph is not a vehicle, the input screen 1120 does not need to have the license plate input field 1121. The photo shooting field 1122 includes one or more areas 1140 that contain a description of the photograph to be taken. The information for each area 1140 corresponding to multiple photographs is included in the shooting data related to the shooting request. The information for each area 1140 corresponding to multiple photographs may also be set on the second screen 400 or the fourth screen 600. The contractor transitions the current screen to the shooting screen 1130 by selecting each area 1140. In some situations, the shooting screen 1130 may display guide information for the photograph to be taken. For example, suppose the photograph to be taken is a photograph of the vehicle at an angle behind it. In this case, the shooting screen 1130 may display guide lines indicating the vehicle at an angle behind it. Members can easily understand which photograph to take by referring to the guide information. When a photo is taken on the shooting screen 1130, the screen of the member terminal 120 returns to the input screen 1120 after passing through a confirmation screen. After shooting, the selected area 1140 displays a thumbnail of the photo obtained by the shooting. The contractor can take all the necessary photos by selecting the areas 1140 in order. The supplementary data input item 1123 is configured to allow registration of arbitrary data other than photos (such as the value of the ODD meter, the presence or absence of cigarette odor, etc.). The items in the supplementary data input item 1123 differ depending on the management target. The sample image display item 1124 is an item for displaying a sample of the photo to be taken. When the sample image display item 1124 is pressed, one or more samples of the photo to be taken are displayed on the member terminal 120.
[0091] The cancel button 1125 is used to return to the fifth screen 1100. When the cancel button 1125 is pressed, the member terminal 120 transitions the current screen to the fifth screen 1100. The temporary save button 1126 is used to temporarily save the content entered on the input screen 1120 to the storage of the member terminal 120. When the temporary save button 1126 is pressed, the member terminal 120 saves the content entered on the input screen 1120 to its storage. When the input screen 1120 is opened again, the member terminal 120 reads the temporarily saved data and displays it on the input screen 1120.
[0092] The "Complete" button 1127 is used to send the data entered on the input screen 1120 to the photo request system 100. When the "Complete" button 1127 is pressed, the member terminal 120 sends the photo data to the photo request system 100. The photo data includes all the data entered on the input screen 1120.
[0093] As explained with reference to Figure 11, the photography outsourcing program includes various screens to support the contractor in fulfilling the requested tasks. By using the screens shown in Figure 11, the contractor can navigate to the shooting location without hesitation and upload the specified number and type of photographs, along with accompanying data, to the photography request system 100. Furthermore, the photography data related to the photography request includes multiple sets of photographs. The photography outsourcing program can cause the member terminal 120 to display information guiding the shooting method for each of the multiple sets of photographs, as well as input fields for information associated with the photography request, on its display.
[0094] Figure 12 shows an example of the sixth screen 1200 displayed on the member terminal 120. The sixth screen 1200 is a screen for the contractor to prove their identity. When photographing managed objects located on the premises of a corporation, it is desirable for the contractor to be able to prove to the on-site person in charge that they received a request from the client. Therefore, the photography contracting program is equipped with a function to display the sixth screen 1200 for identity verification on the member terminal 120. The sixth screen 1200 includes member information 1210, authentication number 1220, and QR code (registered trademark) 1230 as its main display items. The sixth screen 1200 includes at least one of these display items. The member terminal 120 downloads the information to be displayed on the sixth screen 1200 from the photography request system 100 by the work day (the date of photography of the managed object).
[0095] Member information 1210 includes information such as the member, client (requester), request number, and request details. Authentication number 1220 is a number issued by the photography request system 100 for each request. The photography request system 100 also sends the same authentication number to the contact person (e.g., email address) set on the second screen 400. On-site personnel can verify that the contractor is the person who received the request by comparing their authentication numbers. QR code 1230 is configured to read the authentication number or a URL to the authentication screen. On-site personnel can verify the authentication number or the authentication screen by reading QR code 1230 with a smartphone camera or similar device.
[0096] As described above, the commission registration unit 103 of the photography request system 100 transmits proof data to the contractor's terminal (member terminal 120) indicating that a photography request has been received from a client. This proof data includes information on each item to be displayed on the sixth screen 1200. The photography contracting program also causes the member terminal 120 to receive the proof data indicating that a photography request has been received and to display the proof data on its screen. This proof data is displayed on the sixth screen 1200 of the member terminal 120. In this way, the photography request system 100 and the photography contracting program have a function to present proof data indicating that the contractor has received a photography request to the on-site person in charge. This allows the contractor to prove their identity on-site and carry out the photography work smoothly.
[0097] Figure 13 shows an example of a screen 1300 displayed on the terminal of the administrator of the shooting request system 100. Screen 1300 is a screen for checking the shooting data uploaded to the shooting request system 100 from the member terminal 120.
[0098] Screen 1300 includes the following main display items: contact information (1310), managed information (1320), work date and time (1330), location (1340), remarks (1350), worker information (1360), photographic data display item (1370), accompanying data display item (1380), an NG button (1390), and an OK button (1392). The displays of items 1310 to 1380 correspond to the displays of items 610 to 680.
[0099] The administrator can view the information entered by the client on the second screen 400 and the fourth screen 600 by referring to items 1310-1360. The administrator can also view the captured data and its associated data by referring to items 670 and 680.
[0100] If there is no problem with the photographic data and its accompanying data, the administrator can complete the request by pressing the OK button 1392. More specifically, when the OK button 1392 is pressed, the photography request system 100 transmits a completion notification to the member terminal 120 that has transmitted the photographic data. In addition, the photography request system 100 registers information indicating that the request has been completed in the storage unit 106. In one aspect, the photography request system 100 may update a flag indicating whether or not the request included in the information related to the request or the information related to entrustment registration has been completed. Furthermore, the photography request system 100 transmits a photographic data registration notification to the client terminal 110.
[0101] If there is a problem with the photographic data and its accompanying data, the administrator can request the trustee to re-upload the photographic data by pressing the NG button 1390. More specifically, when the NG button 1390 is pressed, the photography request system 100 transmits a re-upload request to the member terminal 120 that has transmitted the photographic data.
[0102] As described with reference to FIG. 13, the photography request system 100 provides a function for the administrator to check the photographic data. As an example, it is assumed that the operating company of the photography request system 100 has one or more administrators who check the photographic data stationed in the office. In this case, the trustee can obtain a prompt response from the administrator without needing to wait for contact from the client regarding the photographic data uploaded at the work site.
[0103] In one aspect, the photography request system 100 may use a machine-learned model to determine pass / fail of the photographic data. In this case, the photography request system 100 can automatically perform the pass / fail determination of the photographic data, the transmission of the completion notification, the transmission of the photographic data registration notification, and the transmission of the re-upload request. In another aspect, the photography request system 100 may provide the client terminal 110 with a function for checking the photographic data.
[0104] <C. Communication Sequence> Figure 14 shows an example of a communication sequence between the photo request system 100, the client terminal 110, and the member terminal 120. The photo request system 100, the client terminal 110, and the member terminal 120 can perform the following communications via a wired network, a wireless network, or a network combining both. The transmission order of the following messages is an example, and the order of the messages may be changed. The photo request system 100 may also communicate with one or more client terminals 110 and one or more member terminals 120 simultaneously.
[0105] In step S1405, the client terminal 110 sends a client registration request to the shooting request system 100. This step registers a new client with the shooting request system 100. In some cases, the administrator of the shooting request system 100 may register a new client with the shooting request system 100 via the UI of the shooting request system 100. In step S1410, the shooting request system 100 sends a registration completion message to the client terminal 110 based on the completion of the client registration process to the storage unit 106.
[0106] In step S1415, the client terminal 110 sends a photo shoot request registration request to the photo shoot request system 100. The client can send a photo shoot request registration request to the photo shoot request system 100 by operating the second screen 400. In step S1420, the photo shoot request system 100 sends a photo shoot request registration completion message to the client terminal 110 based on the completion of the photo shoot request registration process to the storage unit 106. In some cases, the photo shoot request system 100 may not accept a photo shoot request if there are no members who can handle the area including the location of the subject to be photographed. In this case, the photo shoot request system 100 sends a photo shoot request registration failure message to the client terminal 110.
[0107] In step S1425, the member terminal 120 sends a member registration request to the photo request system 100. This step registers a new member in the photo request system 100. In step S1430, the photo request system 100 sends a registration completion message to the member terminal 120 based on the completion of the member registration process in the storage unit 106.
[0108] In step S1435, the photography request system 100 transmits a list of requests to the member terminals 120 of members registered with the photography request system 100. The processing in this step corresponds to the disclosure of requests by the request disclosure unit 102. In some cases, the photography request system 100 may transmit or disclose only requests for each member's assigned area to each member's member terminal 120. In other cases, the photography request system 100 may transmit or disclose all requests to all member terminals 120.
[0109] In step S1440, the member terminal 120 sends an acceptance request to the shooting request system 100 based on having received an acceptance input from the member. This acceptance request is for one of the requests included in the request list. The member can send an acceptance request to the shooting request system 100 by operating the fourth screen 1000. In step S1445, the shooting request system 100 sends an acceptance response message to the member's member terminal 120. The acceptance response message indicates whether the acceptance was successful or unsuccessful.
[0110] In step S1450, the member terminal 120, having accepted the request, becomes able to upload the target shooting data specified in the request to the shooting request system 100. The member terminal 120 uploads the shooting data to the shooting request system 100 based on receiving the upload input from the member. Next, the shooting request system 100 receives input from the administrator via screen 1300 regarding the pass / fail status of the shooting data. If there are no problems with the shooting data (if it is judged as pass), in step S1455, the shooting request system 100 sends a completion notification to the member terminal 120 indicating the completion of the request. If there are problems with the shooting data (if it is judged as failing), the shooting request system 100 sends a re-upload request to the member terminal 120 instead of a completion notification.
[0111] In step S1460, the shooting request system 100 sends a shooting data registration notification to the client terminal 110. This step may be executed when the client terminal 110 logs in to the shooting request system 100 and requests the first screen 300 (top screen).
[0112] In step S1465, the client terminal 110 sends a shooting data confirmation response to the shooting request system 100 based on receiving confirmation input of the shooting data from the client. In some cases, the shooting data confirmation response may include evaluation information of the contractor and feedback comments for the contractor. The contractor can check this evaluation information and feedback comments on their member terminal 120.
[0113] <D.まとめ> As described above, the photography request system 100 according to this embodiment can provide clients with a mechanism for managing a large number of properties scattered in various locations at low cost without having to dispatch employees. In addition, members can easily earn income by receiving photography requests in their own living area.
[0114] Furthermore, the photography outsourcing program includes various screens to support the contractor in fulfilling the requested tasks. By using these screens, the contractor can navigate to the shooting location without hesitation and upload the specified number and type of photographs, along with any accompanying data, to the photography request system 100.
[0115] Furthermore, the filming request system 100 and the filming contracting program are equipped with a function to present proof data to the local person in charge that the contractor has received a filming request. This allows the contractor to prove their identity on-site and carry out the filming work smoothly.
[0116] The embodiments disclosed herein should be considered in all respects to be illustrative and not restrictive. The scope of this disclosure is indicated by the claims rather than the foregoing description, and all modifications are intended to be included in the sense and scope equivalent to the claims. Furthermore, the disclosures described in the embodiments and each variation are intended to be implemented, as far as possible, individually or in combination. [Explanation of symbols]
[0117] 100 Shooting Request System, 101 Request Registration Unit, 102 Request Publication Unit, 103 Commission Registration Unit, 104 Shooting Data Acquisition Unit, 105 Notification Unit, 106 Storage Unit, 107 Evaluation Unit, 110, 110A, 110B, 110C Client Terminals, 120, 120A, 120B, 120C Member Terminals, 130 Map, 201 Processor, 202 Memory, 203 Storage, 204 External Device Interface, 205 Input Interface, 206 Output Interface, 207 Communication Interface, 300, 700 First Screen, 310, 810 Menu, 320, 820 Announcements from Management, 330 Alert Work List Information, 340 Work Completion List, 350 Work Awaiting Execution, 360 Work Schedule List, 400, 800 Second Screen, 410 Contact Input Fields, 420 Input fields for managed information, 430 Input fields for work date and time, 440 Input fields for location, 450 Input fields for remarks, 460, 740, 1060, 1125 Cancel button, 470 Request button, 500, 900 Third screen, 510, 910 Filtering fields, 520 List of shooting requests and results, 600, 1000 Fourth screen, 610 Contact editing fields, 620 Editing fields for managed information, 630 Editing fields for work date and time, 640 Editing fields for location, 650 Editing fields for remarks, 660 Input fields for worker information, 670, 1370 Display fields for shooting data, 680, 1380 Display fields for accompanying data, 690 Withdraw button, 692 Edit button, 710 Input fields for member information, 720 Input fields for available activity area, 730 Input fields for payment account, 750 Register button, 760 Unsubscribe button, 830 List of accepted (unworked) tasks, 840 List of tasks completed this month, 920 List of requests, 930 Map showing the location of the subject to be photographed, 1010, 1310 Contact information field, 1020 Items to be managed, 1030, 1330 Work date and time field, 1040, 1340 Location field, 1050,1350 Remarks field, 1070 Accept button, 1100 Fifth screen, 1110 Input button, 1120 Input screen, 1121 License plate input field, 1122 Photo shooting field, 1123 Additional data input field, 1124 Sample image display field, 1126 Temporary save button, 1127 Complete button, 1130 Shooting screen, 1140 Area, 1200 Sixth screen, 1210 Member information, 1220 Authentication number, 1230 QR code, 1300 Screen, 1320 Information field for managed items, 1360 Worker information field, 1390 NG button, 1392 OK button.
Claims
1. A request registration unit that receives shooting requests from clients for items to be managed, The request disclosure section makes the aforementioned photography request public to one or more members, Based on the receipt of a request to accept the aforementioned photography request from the terminal of one or more of the aforementioned members, the Commission Registration Department registers the aforementioned member as a commissioned worker, A shooting data acquisition unit that receives shooting data related to the shooting request from the contractor's terminal, A notification unit that sends a notification of registration of captured data to the client's terminal, The system includes a storage unit that stores information on the assigned region for each of the one or more members, The aforementioned photography request includes contact information of the local person in charge of managing the managed object, information on the range of dates and times when the local person in charge can photograph the managed object, and location information of the object to be photographed. The aforementioned contract registration unit transmits the range information of the dates and times when photography is possible, and the contact information of the on-site person in charge, to the contract holder's terminal. Disclosing the aforementioned photography request to one or more members means The region in which the subject to be photographed is located is determined by referring to the aforementioned location information, This includes, by referring to the aforementioned assigned area information, disclosing the aforementioned filming request to the members responsible for the area where the subject of filming is located, A photography request system in which the request registration unit sends a notification to the client's terminal indicating that the photography request cannot be accepted, based on the fact that there is no member responsible for the area where the subject to be photographed is located.
2. A request registration unit that receives shooting requests from clients for items to be managed, The request disclosure section makes the aforementioned photography request public to one or more members, Based on the receipt of a request to accept the aforementioned photography request from the terminal of one or more of the aforementioned members, the Commission Registration Department registers the aforementioned member as a commissioned worker, A shooting data acquisition unit that receives shooting data related to the shooting request from the contractor's terminal, A notification unit that sends a notification of registration of captured data to the client's terminal, The system includes a storage unit that stores information on the assigned region for each of the one or more members, The aforementioned photography request includes contact information of the local person in charge of managing the managed object, information on the range of dates and times when the local person in charge can photograph the managed object, and location information of the object to be photographed. Disclosing the aforementioned photography request to one or more members means The region in which the subject to be photographed is located is determined by referring to the aforementioned location information, This includes, by referring to the aforementioned assigned area information, disclosing the aforementioned filming request to the members responsible for the area where the subject of filming is located, The request registration unit, based on the fact that there is no member responsible for the area where the subject to be photographed is located, sends a notification to the client's terminal indicating that the photographing request cannot be accepted. The aforementioned contract registration unit transmits proof data to the contract holder's terminal indicating that it has received the aforementioned filming request from the client, thus forming a filming request system.
3. The aforementioned certification data includes an authentication number issued for each request, The photography request system according to claim 2, wherein the authentication number is transmitted by the photography request system to the contact information of the local person in charge of managing the managed object.
4. The system further includes an evaluation unit that receives registration of evaluation information for the contractor from the aforementioned client, The request disclosure unit adjusts the disclosure time of the request for each of the one or more members, or the compensation for the request for the request, based on the evaluation information, in the photography request system according to any one of claims 1 to 3.
Citation Information
Patent Citations
Server device, communication apparatus, and photographing request system
JP2012194889A
Imaging intermediation device
JP2017033419A
Contextual notifications for network-based service
JP2020135873A
Report support server, report support system, report support method, and report support program
JP2023014253A
Information processing apparatus, method and program, and information processing system
JP2024018302A
