Patent Description:
In general, construction photographs are taken at a construction site when various device systems are constructed. The construction photographs taken at this time are included in various documents (for example, a finalized document, and the like) and delivered to a customer.

However, as the scale of a device system increases, the number of construction photographs to be taken also increases, and as a result, the workload in creating various documents increases. <CIT> discloses a task support apparatus according to the preamble of claim <NUM>.

The present disclosure provides a task support apparatus and a task support program for reducing the workload in creating a document for reporting a construction status.

A first aspect of the present disclosure is a task support apparatus according to claim <NUM>.

According to the first aspect of the present disclosure, a task support apparatus for reducing the workload in creating a document for reporting a construction status can be provided.

A second aspect of the present disclosure is the task support apparatus according to the first aspect, wherein the insertion rule includes an insertion order, and the insertion order is determined by the construction detail or the photographing timing included in each of the pieces of attribute information.

A third aspect of the present disclosure is the task support apparatus according to the first aspect or the second aspect, further including a selecting unit configured to select a given captured image from among a plurality of captured images in a case where the plurality of captured images are associated with same attribute information.

A fourth aspect of the present disclosure is the task support apparatus according to the first aspect, wherein each of the pieces of attribute information further includes information for identifying a constructor, information for identifying a photographer, evaluation on a captured image, information for identifying a photographing date and time, and information relating to a construction observer.

A fifth aspect of the present disclosure is the task support apparatus according to the first aspect, further including a providing unit configured to provide the construction detail and the photographing timing to the terminal device, wherein the terminal device includes an imaging unit configured to capture an image.

A sixth aspect of the present disclosure is a task support program according to claim <NUM>.

According to the sixth aspect of the present disclosure, a task support apparatus for reducing the workload in creating a document for reporting a construction status can be provided.

In the following, embodiments will be described with reference to the accompanying drawings. In the specification and drawings, elements having substantially the same functions or configurations are referred to by the same numerals and the description thereof will not be repeated.

First, a system configuration of a task support system according to a first embodiment will be described. <FIG> is a diagram illustrating an example of a system configuration of a task support system. As illustrated in <FIG>, a task support system <NUM> includes an information input apparatus <NUM>, a server apparatus <NUM>, an information output apparatus <NUM>, and a terminal device <NUM>. In the task support system <NUM>, each of the information input apparatus <NUM>, the information output apparatus <NUM>, and the terminal device <NUM> is communicably connected to the server apparatus <NUM>.

The information input apparatus <NUM> is an apparatus used by an engineering business operator (hereinafter simply referred to as a "business operator") <NUM>. In response to a request from a customer, the business operator <NUM> designs a device system. At this time, the business operator <NUM> inputs "various kinds of information necessary for construction" via the information input apparatus <NUM>. Further, the business operator <NUM> generates a document for reporting a construction status (referred to as a "finalized document" in the present embodiment), and delivers the document to a customer <NUM>.

Note that, in the present embodiment, a device system to be constructed is described as an air conditioning system, but the device system to be constructed is not limited to the air conditioning system and may be any other device system.

Further, the "various kinds of information necessary for construction" includes information relating to a constructor <NUM> who actually performs construction at a construction site, and information relating to an application downloaded to the terminal device <NUM> when the constructor <NUM> performs the construction at the construction site. Further, the "various kinds of information necessary for construction" includes attribute information relating to the construction of an air conditioning system (hereinafter referred to as "attribute information"), rule information used to generate a finalized document, and the like.

The server apparatus <NUM> is an example of a task support apparatus, and is configured to support:.

A task support program is installed in the server apparatus <NUM>, and the server apparatus <NUM> is configured to, by executing the program, function as:.

The registration unit <NUM> stores information relating to the constructor <NUM>, input by the business operator <NUM> via the information input apparatus <NUM>, in a constructor information storage unit <NUM>. When the constructor <NUM> accesses the server apparatus <NUM> via the terminal device <NUM>, the registration unit <NUM> refers to the constructor information storage unit <NUM> and performs an authentication process for the constructor <NUM>.

The application providing unit <NUM> stores information relating to an application, input by the business operator <NUM> via the information input apparatus <NUM>, in an application storage unit <NUM>. When the constructor <NUM> makes a request to download an application via the terminal device <NUM>, the application providing unit <NUM> downloads the requested application to the terminal device <NUM>.

The attribute information providing unit <NUM> is an example of a providing unit. The attribute information providing unit <NUM> stores attribute information, input by the business operator <NUM> via the information input apparatus <NUM>, in an attribute information storage unit <NUM>. Further, if the registration unit <NUM> determines that authentication is successful in response to the constructor <NUM> starting an application and performing a login operation, the attribute information providing unit <NUM> provides the attribute information to the terminal device <NUM>.

The rule acquiring unit <NUM> is an example of a second acquiring unit. As rule information input by the business operator <NUM> via the information input apparatus <NUM>, the rule acquiring unit <NUM> acquires description rules, in accordance with which description items of attribute information are set when generating a finalized document, and and/or insertion rules, in accordance with which captured image data is inserted into the finalized document.

The description rules are rules that define description items of attribute information to be associated with captured image data when the captured image data is inserted into a finalized document. The captured image data is generated by the constructor <NUM> taking a photograph at a construction site. The description rules are determined by, for example, the business operator <NUM>. The insertion rules are rules that define the order in which pieces of captured image data are inserted into the finalized document. The insertion rules are determined by, for example, the business operator <NUM>.

The rule acquiring unit <NUM> inputs description items of attribute information into a finalized document template in accordance with the acquired description rules so as to generate "pre-insertion information", and stores the "pre-insertion information" in the pre-insertion information storage unit <NUM>. The pre-insertion information is information before captured image data is inserted.

The rule acquiring unit <NUM> indicates the acquired insertion rules and the generated pre-insertion information to the finalized document generating unit <NUM>.

The construction photograph acquiring unit <NUM> is an example of a first acquiring unit. The construction photograph acquiring unit <NUM> receives, from the terminal device <NUM>, captured image data generated by the constructor <NUM> starting an application on the terminal device <NUM> and taking a construction photograph at a construction site. Further, the construction photograph acquiring unit <NUM> stores the received captured image data in the construction photograph storage unit <NUM> as the construction photograph.

Note that attribute information provided by the attribute information providing unit <NUM> to the terminal device <NUM> is recorded in the header section of captured image data generated by taking a photograph while the application is running.

The finalized document generating unit <NUM> is an example of a generating unit and a selecting unit. The finalized document generating unit <NUM> generates finalized document data when the construction of an air conditioning system is completed. Specifically, the finalized document generating unit <NUM> retrieves captured image data from the construction photograph storage unit <NUM> as a construction photograph. Further, the finalized document generating unit <NUM> generates finalized document data by inserting the retrieved captured image data into pre-insertion information in accordance with the insertion rules.

The finalized document generating unit <NUM> stores the generated finalized document data in the finalized document storage unit <NUM>. Further, the finalized document generating unit <NUM> retrieves the finalized document data stored in the finalized document storage unit <NUM> and sends the finalized document data to the information output apparatus <NUM>, in response to the customer <NUM> requesting the server apparatus <NUM> to send the finalized document data via the information output apparatus <NUM>.

The terminal device <NUM> is a device carried by the constructor <NUM> at a construction site. The constructor <NUM> carries the terminal device <NUM> when constructing an air conditioning system including an air conditioner <NUM> (reference numeral 170_1) to an air conditioner n (reference numeral 170_n).

The constructor <NUM> requests the server apparatus <NUM> to download an application via the terminal device <NUM>, and installs the application, downloaded by the server apparatus <NUM>, in the terminal device <NUM>.

Further, the constructor <NUM> acquires attribute information from the server apparatus <NUM> by starting an application on the terminal device <NUM> and logging into the server apparatus <NUM>. Further, the constructor <NUM> takes a construction photograph via the started application, and transmits captured image data, generated by taking the construction photograph, via the server apparatus <NUM>.

Next, an example configuration of a finalized document will be described. <FIG> is a diagram illustrating an example configuration of a finalized document. As illustrated in <FIG>, a finalized document <NUM> includes a cover, a device delivery document, an instruction manual, a completion drawing, an air conditioner test operation table, an airtightness test result table, a water flow test result table, an airflow volume measurement test comparison table, a construction photograph ledger, a facility management ledger, a guarantee form, a maintenance contact list, and the like.

The server apparatus <NUM> according to the present embodiment mainly supports:.

Therefore, from among various processes performed by the task support system <NUM>, a process related to generation of construction photograph ledger data will be mainly described below.

The process related to generation of construction photograph ledger data, performed by the task support system <NUM>, are mainly divided into a preparation phase and a construction phase. The preparation phase and the construction phase will be separately described below.

First, a flow of a process performed by the task support system <NUM> in the preparation phase will be described. <FIG> is a sequence diagram illustrating a flow of a process performed by the task support system in the preparation phase.

As illustrated in <FIG>, in step S301, the customer <NUM> makes a construction request to the business operator <NUM>. The customer <NUM> may make a construction request to the business operator <NUM> via a telephone (not illustrated) or via the information output apparatus <NUM> and the information input apparatus <NUM>.

In step S302, in response to receiving the construction request from the customer <NUM>, the business operator <NUM> performs registration tasks for registering various kinds of information necessary for construction via the information input apparatus <NUM>. The registration tasks performed by the business operator <NUM> include a registration task for registering constructor information, a registration task for registering an application, and a registration task for registering attribute information.

In step S303, in response to the business operator <NUM> performing the registration tasks, the server apparatus <NUM> registers the constructor information, the application, and the attribute information received from the information input apparatus <NUM>.

Specifically, the registration unit <NUM> stores the constructor information in the constructor information storage unit <NUM>. The application providing unit <NUM> stores the application and information relating to the application in the application storage unit <NUM>. Further, the attribute information providing unit <NUM> stores the attribute information in the attribute information storage unit <NUM>.

In step S304, the terminal device <NUM> makes a request to download the application based on an instruction from the constructor <NUM>. Specifically, the terminal device <NUM> sends a request to download the application to the server apparatus <NUM>.

In step S305, in response to receiving the download request from the terminal device <NUM>, the application providing unit <NUM> of the server apparatus <NUM> downloads the application stored in the application storage unit <NUM> to the terminal device <NUM>.

In step S306, the terminal device <NUM> installs the downloaded application.

Next, a flow of a process performed by the by the task support system <NUM> in the construction phase will be described. <FIG> is a sequence diagram illustrating a flow of a process performed by the by the task support system in the construction phase will be described.

As illustrated in <FIG>, in step S401, the business operator <NUM> generates a construction photograph ledger template, and the information input apparatus <NUM> transmits the construction photograph ledger template generated by the business operator <NUM> to the server apparatus <NUM>.

In step S402, the rule acquiring unit <NUM> of the server apparatus <NUM> acquires the construction photograph ledger template transmitted from the information input apparatus <NUM>.

In step S403, the business operator <NUM> determines description rules, and the information input apparatus <NUM> transmits the description rules determined by the business operator <NUM> to the server apparatus <NUM>.

In step S404, the rule acquiring unit <NUM> of the server apparatus <NUM> acquires the description rules transmitted from the information input apparatus <NUM>.

In step S405, the rule acquiring unit <NUM> of the server apparatus <NUM> retrieves the attribute information stored in the attribute information storage unit <NUM>, and sets description items defined in the acquired description rules for the construction photograph ledger template so as to generate pre-insertion information.

In step S406, the constructor <NUM> starts the application installed in the terminal device <NUM>, and performs a login operation to log into the server apparatus <NUM>. The terminal device <NUM> transmits a password input by the constructor <NUM> at the time of the login operation to the server apparatus <NUM>.

In step S407, the server apparatus <NUM> performs an authentication process based on the password transmitted from the terminal device <NUM>. If the server apparatus <NUM> determines that the authentication is successful, the process proceeds to step S408.

In step S408, the attribute information providing unit <NUM> of the server apparatus <NUM> performs an attribute information providing process. Specifically, the attribute information providing unit <NUM> of the server apparatus <NUM> provides the attribute information stored in the attribute information storage unit <NUM> to the terminal device <NUM>.

In the present embodiment, the attribute information includes "case information", "construction details", and "photographing timing information". The "construction details" are divided into "location and device information", classified based on locations and devices, and "process and task information", classified based on processes and tasks, and the "location and device information" and "process and task information" are stored in the attribute information storage unit <NUM>.

In step S408, the attribute information providing unit <NUM> of the server apparatus <NUM> provides the "case information", the "location and device information", the "process and task information", and the "photographing timing information" to the terminal device <NUM> as the attribute information.

In step S409, the terminal device <NUM> acquires the attribute information via the application.

Specifically, the terminal device <NUM> displays the "case information" transmitted from the server apparatus <NUM>, and receives a selection of a case from the constructor <NUM>.

Further, the terminal device <NUM> displays the "location and device information" transmitted from the server apparatus <NUM>, and receives a selection of a location and device from the constructor <NUM>.

Further, the terminal device <NUM> displays the "process and task information" transmitted from the server apparatus <NUM>, and receives a selection of a process and a task from the constructor <NUM>.

Further, the terminal device <NUM> displays the "photographing timing information" transmitted from the server apparatus <NUM>, and receives a selection of a photographing timing from the constructor <NUM>.

In step S410, the constructor <NUM> starts an imaging device <NUM> of the terminal device <NUM> via the application, and takes a construction photograph at a construction site. When the constructor <NUM> takes a construction photograph at a construction site, the constructor <NUM> may input "additional information" into the terminal device <NUM> as necessary.

The additional information includes, for example, information for identifying a constructor, information for identifying a photographer, evaluation on captured image data, information for identifying a photographing date and time (hereinafter simply referred to as a "photographing date"), and information relating to a construction observer. Note that the additional information may include location and device information and process and task information. That is, the constructor <NUM> may select and input a location and a device from the "location and device information" transmitted from the server apparatus <NUM>, and a process and a task from the "process and task information" transmitted from the server apparatus <NUM>. Alternatively, the constructor <NUM> may directly input a location, a device, a process, and a task as additional information.

When the constructor <NUM> finished taking the photograph, the terminal device <NUM> transmits captured image data, generated by taking the photograph, to the server apparatus <NUM> via the application. As described above, as attribute information, the following information is recorded in the header section of the captured image data transmitted from the terminal device <NUM>:.

In step S411, the construction photograph acquiring unit <NUM> of the server apparatus <NUM> stores, as the construction photograph, the captured image data transmitted from the terminal device <NUM> in the construction photograph storage unit <NUM>.

In step S412, the business operator <NUM> determines insertion rules, and the information input apparatus <NUM> transmits the insertion rules determined by the business operator <NUM> to the server apparatus <NUM>.

In step S413, the rule acquiring unit <NUM> of the server apparatus <NUM> acquires the insertion rules transmitted from the information input apparatus <NUM>.

In step S414, the finalized document generating unit <NUM> of the server apparatus <NUM> performs a finalized document generating process (in the present embodiment, a process for generating construction photograph ledger data) (which will be described later in detail with reference to <FIG>).

Specifically, the finalized document generating unit <NUM> of the server apparatus <NUM> arranges pieces of captured image data, stored in step S411, in accordance with the insertion rules while referring to attribute information (selection results and additional information) recorded in the header sections of the pieces of captured image data. Further, the finalized document generating unit <NUM> of the server apparatus <NUM> sequentially inserts the pieces of the captured image data, arranged in accordance with the insertion rules, into the pre-insertion information generated in step S405. Accordingly, the insertion process can be accelerated by arranging and inserting the captured image data in accordance with the insertion rules.

Note that pre-insertion information into which captured image data is inserted is displayed on the information input apparatus <NUM>, in response to a request from the business operator <NUM>. At this time, if a plurality of pieces of captured image data are associated with the same attribute information, one captured image data is selected by the business operator <NUM>. Accordingly, construction photograph ledger data, into which one appropriate captured image data selected on a per attribute information basis is inserted, is generated and stored in the finalized document storage unit <NUM>.

Specifically, in step S415, the information input apparatus <NUM> receives pages of the pre-insertion information into which the captured image data is inserted from the server apparatus <NUM> and displays the pages of the pre-insertion information. If a plurality of pieces of captured image data are associated with the same attribute information on each of the displayed pages, the business operator <NUM> selects one captured image data. Further, the information input apparatus <NUM> transmits the selection of the one captured image data by the business operator <NUM> to the server apparatus <NUM>. Accordingly, the finalized document generating unit <NUM> generates construction photograph ledger data into which one captured image data selected on a per attribute information basis is inserted.

In step S416, the information output apparatus <NUM> sends a request to download finalized document data to the server apparatus <NUM> in response to an instruction from the customer <NUM>. The finalized document generating unit <NUM> downloads the finalized document data to the information output apparatus <NUM>. The information output apparatus <NUM> acquires and displays the finalized document data downloaded by the server apparatus <NUM>.

Next, a hardware configuration of each of the server apparatus <NUM> and the terminal device <NUM> will be described. <FIG> is a diagram illustrating an example of a hardware configuration of each of the server apparatus and the terminal device.

As illustrated in 5a of <FIG>, the server apparatus <NUM> includes a central processing unit (CPU) <NUM>, a read-only memory (ROM) <NUM>, and a random-access memory (RAM) <NUM>. The CPU <NUM>, the ROM <NUM> and the RAM <NUM> form what is referred to as a computer.

Further, the server apparatus <NUM> includes an auxiliary storage device <NUM>, a display device <NUM>, an operation device <NUM>, a communication device <NUM>, and a drive device <NUM>. The hardware elements of the server apparatus <NUM> are connected to each other via a bus <NUM>.

The CPU <NUM> is a calculation device that executes various programs (for example, the task support program and the like) installed in the auxiliary storage device <NUM>.

The ROM <NUM> is a non-volatile memory. The ROM <NUM> functions as a main storage device that stores various programs, data, and the like necessary for the CPU <NUM> to execute various programs installed in the auxiliary storage device <NUM>. Specifically, the ROM <NUM> functions as a main storage device that stores a boot program or the like, such as a basic input/output system (BIOS) or an extensible firmware interface (EFI).

The RAM <NUM> is a volatile memory such as a dynamic random-access memory (DRAM) or a static random-access memory (SRAM). The RAM <NUM> functions as a main storage device that provides a work area in which various programs installed in the auxiliary storage device <NUM> are loaded when executed by the CPU <NUM>.

The auxiliary storage device <NUM> is an auxiliary storage device that stores various programs and information used when the various programs are executed. The constructor information storage unit <NUM>, the application storage unit <NUM>, the attribute information storage unit <NUM>, the pre-insertion information storage unit <NUM>, the construction photograph storage unit <NUM>, and the finalized document storage unit <NUM> are implemented by the auxiliary storage device <NUM>.

The display device <NUM> is a display device that displays an internal state of the server apparatus <NUM>. The operation device <NUM> is an input device used when an administrator (not illustrated) of the server apparatus <NUM> inputs various instructions into the server apparatus <NUM>.

The communication device <NUM> is a communication device that is connected to a network <NUM> and communicates with the information input apparatus <NUM>, the information output apparatus <NUM>, the terminal device <NUM>, and the like.

The drive device <NUM> is a device for setting a recording medium <NUM>. The recording medium <NUM> includes a medium for optically, electrically, or magnetically recording information, such as a CD-ROM, a flexible disk, or a magnetooptical disc. Further, the recording medium <NUM> may include a semiconductor memory or the like that electrically records information, such as a ROM, a flash memory, or the like.

Various programs to be installed in the auxiliary storage device <NUM> are installed by, for example, setting the distributed recording medium <NUM> in the drive device <NUM> and reading the various programs recorded in the recording medium <NUM> by the drive device <NUM>. Alternatively, various programs to be installed in the auxiliary storage device <NUM> may be installed by being downloaded from the network <NUM> via the communication device <NUM>.

As illustrated in 5b of <FIG>, the terminal device <NUM> has a hardware configuration (a CPU <NUM> to a communication device <NUM>) similar to that of the server apparatus <NUM>. Therefore, the difference from the server apparatus <NUM> will be described here.

The difference from the server apparatus <NUM> is that the terminal device <NUM> includes an imaging device <NUM> that functions as an imaging unit. The imaging device <NUM> is operated based on an operation performed by the constructor <NUM> and generates captured image data.

Next, specific examples of various kinds of information (constructor information, application information, and attribute information) stored in the server apparatus <NUM> will be described.

First, constructor information stored in the constructor information storage unit <NUM> of the server apparatus <NUM> and application information stored in the application storage unit <NUM> of the server apparatus <NUM> will be described.

<FIG> is a diagram illustrating examples of constructor information and application information. In <FIG> indicates an example of constructor information <NUM>. As illustrated in 6a of <FIG>, the constructor information <NUM> stores information relating to all constructors under contract with the business operator <NUM> to construct air conditioning systems.

Specifically, the constructor information <NUM> includes "constructor ID", "constructor name", "address", "contact", "construction supervisor", "user ID", and "password" as information items.

In "constructor ID", an identifier for identifying a constructor under contract with the business operator <NUM> to construct an air conditioning system is stored. In "constructor name", the name of the constructor is stored. In "address", the address of the constructor is stored, and in "contact", the contact information of the constructor is stored. In "construction supervisor", the name of a construction supervisor of the constructor is stored. In "user ID" and "password", a user ID and a password used by the constructor to access the server apparatus <NUM> via a corresponding terminal device (for example, used by the constructor <NUM> to access the server apparatus <NUM> via the terminal device <NUM>) are stored.

Further, 6b of <FIG> indicates an example of application information <NUM>. As illustrated in 6b of <FIG>, the application information <NUM> stores information relating to applications used on terminal devices carried by the constructors, under contract with the business operator <NUM> to construct the air conditioning systems, at the construction site.

Specifically, the application information <NUM> includes "app ID", "app name", "type", "version", "updated date and time", and "storage URL" as information items.

In "app ID", an identifier for identifying an application is stored. In "app name", the name of the application is stored. In "type", "version", and "updated date and time", the type, the version, and the updated date and time of the application are stored, respectively. In "storage URL", an URL that stores the application is stored.

Next, attribute information stored in the attribute information storage unit <NUM> of the server apparatus <NUM> will be described. As described above, the attribute information include case information, construction details, and photographing timing information. The construction details are divided into "location and device information" and "process and task information", and the "location and device information" and the "process and task information" are stored. Therefore, in the following, the case information, the location and device information, the process and task information, and the photographing timing information will be described.

<FIG> is a diagram illustrating examples of case information, location and device information, process and task information, and photographing timing information. In <FIG> illustrates an example of case information <NUM>. As illustrated in 7a of <FIG>, the case information <NUM> stores information relating to construction cases of air conditioning systems to be constructed by the business operator <NUM> as requested by various customers.

Specifically, the case information <NUM> includes "property name", "case ID", "case name", "requester", "responsible person", "detailed information", and "contractor" as information items.

In "property name", the name of a property (for example, the name of a building) in which an air conditioning system is constructed is stored. In "case ID", an identifier for identifying a construction case is stored. In "case name", the name of the construction case is stored.

In "requester", information relating to a customer who requested the construction case is stored. In "responsible person", the name of a responsible person responsible determined by the business operator <NUM> for the construction case is stored. In "detailed information", detailed information of the construction case is stored. In "contractor", the constructor ID of a constructor under contract with the business operator <NUM> for the construction case is stored.

Further, 7b-<NUM> of <FIG> illustrates an example of location and device information <NUM>. The location and device information <NUM> is recorded for each construction case. In 7b-<NUM> of <FIG>, location and device information of a construction case having a case name of "AAA" is depicted.

As illustrated in 7b-<NUM> of <FIG>, the location and device information <NUM> includes "location and device group", "floor", "room/zone", "location", "system", and "device" as information items.

In "location and device group", an identifier for identifying each location and device group of the location and device information is stored. In "floor", the name and the floor level of a building in which construction is performed is stored. In "room/zone", the name of a room or a zone in which the construction is performed is stored. In "location", information indicating a location where a device is installed is stored.

In "system", information indicating a refrigerant system to which the device is connected is stored. In "device", the model name of the device is stored.

For example, in the location and device information <NUM>, a location and device group of "<NUM>" indicates that a device having a model name of "FFF001DD" is installed in the attic of a "1st grade, class <NUM>" classroom on the first floor of a north building, and is connected to a system A.

Similarly, a location and device group of "<NUM>" indicates that a device having a model name of "FFF001DD" is installed in the attic of a "1st grade, class <NUM>" classroom on the first floor of the north building, and is connected to the system A.

Further, 7b-<NUM> of <FIG> illustrates an example of process and task information <NUM>. Similar to the location and device information <NUM>, the process and task information <NUM> is recorded for each construction case. Specifically, in 7b-<NUM> of <FIG>, process and task information of the construction case having the case name of "AAA" is depicted.

As illustrated in 7b-<NUM> of <FIG>, the process and task information <NUM> includes "process and task group", "process", and "task" as information items.

In "process and task group", an identifier for identifying each process and task group of the process and task information is stored.

In "process", either "construction work" or "test" is stored. In "task", details of a task to be performed are stored.

For example, in the process and task information <NUM>, a process and task group of "<NUM>" indicates construction work for installing an indoor unit. A process and task group of "<NUM>" indicates a water flow passing test. A process and task group of "<NUM>" indicates construction work for laying refrigerant pipes.

Further, 7c of <FIG> illustrates an example of photographing timing information <NUM>. As illustrated in 7c of <FIG>, the photographing timing information <NUM> includes "before operation", "during operation", and "after operation".

Next, a specific example of a process for generating construction photograph ledger data performed by the task support system <NUM> (steps S402 to S405, steps S409 and S410, and steps S412 to S414) in the sequence diagram of <FIG> will be described.

First, a specific example of a process from step S402 (acquiring a template) to step S405 (generating pre-insertion information) in the sequence diagram of <FIG> will be described.

<FIG> is a diagram illustrating a specific example of a process from acquiring a template to generating pre-insertion information. In <FIG>, a template <NUM> is a construction photograph ledger template, and includes a case name input field <NUM> in which a case name is input, a construction photograph insertion field <NUM> into which captured image data is inserted, and an attribute information input field <NUM> in which attribute information is input.

First, the rule acquiring unit <NUM> acquires the construction photograph ledger template <NUM>. Next, the rule acquiring unit <NUM> acquires description rules from the information input apparatus <NUM>. Next, the rule acquiring unit <NUM> refers to the case information <NUM> stored in the attribute information storage unit <NUM>, and sets a case name, corresponding to a description item defined in the description rules, in the case name input field <NUM>.

Next, the rule acquiring unit <NUM> refers to the location and device information <NUM>, the process and task information <NUM>, and the photographing timing information <NUM> stored in the attribute information storage unit <NUM>, and sets, in the attribute information input field <NUM>, description items defined in the description rules. Further, the rule acquiring unit <NUM> sets, in the attribute information input field <NUM>, description items that are defined in the description rules and are not included in the location and device information <NUM>, the process and task information <NUM>, and the photographing timing information <NUM>.

Accordingly, the rule acquiring unit <NUM> generates pre-insertion information <NUM>, and stores the pre-insertion information <NUM> in the pre-insertion information storage unit <NUM>.

In the example of <FIG>, the case name of "AAA" is set in the case name input field <NUM> based on the case information <NUM>. Further, in the example of <FIG>, from among items included in the location and device information <NUM>, the process and task information <NUM>, and the photographing timing information <NUM>, description items (floor, room/zone, device, task, and photographing timing) defined in the description rules are set. Further, in the example of <FIG>, a description item (photographing date) that is defined in the description rules and is not included in the location and device information <NUM>, the process and task information <NUM>, and the photographing timing information <NUM> is set.

Accordingly, items to be input in the attribute information input field <NUM> can be set in accordance with the description rules. Thus, the workload of the business operator <NUM> in generating construction photograph ledger data can be reduced.

Next, a specific example of a process from step S409 (acquiring attribute information) to step S410 (taking a photograph) in the sequence diagram of <FIG> will be described. <FIG> is a diagram illustrating a specific example of a process from acquiring attribute information to taking a photograph.

If it is determined that authentication is successful in response to the constructor <NUM> starting an application on the terminal device <NUM> and logging into the server apparatus <NUM> (step S406 of <FIG>), the terminal device <NUM> acquires attribute information as illustrated in <FIG>.

Specifically, the server apparatus <NUM> transmits case information (for example, the case information <NUM>) to the terminal device <NUM>. The terminal device <NUM> displays the received case information in a list. At this time, the constructor <NUM> selects a case from the case information displayed in the list.

Next, the server apparatus <NUM> transmits location and device information (for example, location and device information <NUM>) and process and task information (for example, process and task information <NUM>), which are associated with the selected case, to the terminal device <NUM>. The terminal device <NUM> displays the location and device information and the process and task information in a list. At this time, the constructor <NUM> selects a location, a device, a process, and a task, for the construction by the constructor <NUM>, from the location and device information and the process and task information in the list.

Next, the server apparatus <NUM> transmits photographing timing information (for example, photographing timing information <NUM>) to the terminal device <NUM>. The terminal device <NUM> displays the photographing timing information in a list. At this time, the constructor <NUM> selects a photographing timing from the photographing timing information displayed in the list.

Selection results selected by the constructor <NUM> are reflected on blackboard information <NUM> of the terminal device <NUM>. The blackboard information <NUM> is displayed on a screen of the terminal device <NUM> when the constructor <NUM> takes a construction photograph at a construction site (see image data <NUM>).

The constructor <NUM> takes a construction photograph with the blackboard information <NUM> being displayed. Thus, the terminal device <NUM> can generate captured image data <NUM> in which the image data <NUM> is recorded in a body section <NUM>. The blackboard information <NUM> is superimposed on the image data <NUM>. The selection results selected by the constructor <NUM> are recorded in a header section <NUM> of the captured image data <NUM>.

Accordingly, the workload of the constructor <NUM> in taking construction photographs can be reduced by providing attribute information to the terminal device <NUM> and allowing the constructor <NUM> to select information (that is, by saving time to input attribute information).

When the constructor <NUM> finished taking the photograph, the constructor <NUM> inputs additional information. As described above, the additional information includes information for identifying a constructor, information for identifying a photographer, evaluation on captured image data, information for identifying photographing date and time, and information relating to a construction observer. Note that the evaluation on captured image data may be a simple evaluation as to whether the captured image data is "OK" or "NG", or may be a detailed evaluation.

For example, the detailed evaluation includes:.

As illustrated in <FIG>, when the additional information is input by the constructor <NUM>, the terminal <NUM> records the input additional information in the header section <NUM> of the captured image data <NUM>. Therefore, attribute information (the selection results and the additional information) is recorded in the header section <NUM> of the captured image data <NUM>.

As illustrated in <FIG>, the constructor <NUM> repeats the same process each time the constructor <NUM> takes a photograph at the construction site. Accordingly, when taking all photographs are completed, a plurality of pieces of captured image data <NUM> are stored in the terminal device <NUM>.

The terminal device <NUM> transmits the plurality of pieces of captured image data <NUM> to the server apparatus <NUM>. Note that the terminal device <NUM> may transmit captured image data to the server apparatus <NUM> after taking all photographs is completed as illustrated in <FIG> or immediately after each photograph is taken.

Next, a specific example of step S412 (determining insertion rules) in the sequence diagram of <FIG> will be described.

<FIG> is a first diagram illustrating an example of arrangement based on insertion rules. In the example illustrated in <FIG>, a plurality of pieces of captured image data are arranged in accordance with insertion rules that define the following:.

In <FIG>, a plurality of pieces of captured image data that are superimposed indicate that the plurality of pieces of captured image data are associated with the same attribute information. For example, in the case of "task = indoor unit installation", "room/zone = 1st grade, class <NUM>", "device = "FFF001DD", and "photographing timing = before operation", it can be seen that two pieces of captured image data having the same attribute information (to be input into the attribute information input field <NUM>) are associated with each other.

<FIG> is a second diagram illustrating an example of arrangement based on insertion rules. In the example illustrated in <FIG>, a plurality of pieces of captured image data are arranged in accordance with insertion rules that define the following:.

Next, a specific example of a process from step S413 (acquiring insertion rules) to step S414 (generating a finalized document) in the sequence diagram of <FIG> will be described. <FIG> is a diagram illustrating a process from acquiring insertion rules to generating a finalized document.

In response to the rule acquiring unit <NUM> acquiring insertion rules from the information input apparatus <NUM>, the finalized document generating unit <NUM> retrieves the pre-insertion information <NUM> from the insertion information storage unit <NUM>. Further, the finalized document generating unit <NUM> retrieves the plurality of pieces of captured image data <NUM> from the construction photograph storage unit <NUM>.

Next, the finalized document generating unit <NUM> arranges the retrieved plurality of pieces of captured image data <NUM> in accordance with the acquired insertion rules while referring to attribute information (selection results, in this example) recorded in header sections of the plurality of pieces of captured image data <NUM>. Captured image data <NUM> is captured image data that has been arranged in accordance with the insertion rules.

Next, the finalized document generating unit <NUM> sequentially inserts the captured image data <NUM>, arranged in accordance with the insertion rules, into the pre-insertion information <NUM> so as to generate construction photograph ledger data. Specifically, the finalized document generating unit <NUM> inserts a body section of each piece of the captured image data <NUM> into a construction photograph insertion field <NUM>, and inputs attribute information (selection results and additional information) recorded in a header section of each piece of the captured image data <NUM> into an attribute information input field <NUM>. In this manner, the finalized document generating unit <NUM> can generate construction photograph ledger data.

Accordingly, the workload of the business operator <NUM> in generating construction photograph ledger data can be reduced by automatically arranging a plurality of pieces of captured image data in accordance with insertion rules while referring to attribute information recorded in header sections.

Note that if there are a plurality of pieces of captured image data whose attribute information (in this example, selection results) recorded in header sections is the same, the finalized document generating unit <NUM> associates the plurality of pieces of captured image data with a construction photograph insertion field <NUM> and retains the plurality of pieces of captured image data associated with the construction photograph insertion field <NUM>. In other words, if a plurality of pieces of captured image data are associated with the same attribute information, the finalized document generating unit <NUM> associates the plurality of pieces of captured image data with a construction photograph insertion field <NUM> and retains the plurality of pieces of captured image data associated with the construction photograph insertion field <NUM>.

Note that from among pages constituting the construction photograph ledger data, if a page on which a body section of captured image data is associated with a construction photograph insertion field <NUM> is displayed, the body section of the captured image data is displayed in a selectable manner as a candidate to be inserted into the construction photograph insertion field <NUM>.

Next, a specific example of step S415 (a display and selection process) in the sequence diagram of <FIG> will be described. As described above, if a plurality of pieces of captured image data are associated with the same attribute information when each page of construction photograph ledger data is displayed, the information input apparatus <NUM> receives a selection of one captured image data.

<FIG> is a first diagram illustrating a specific example of a display and selection process. In <FIG>, the information input apparatus <NUM> displays a page on which a plurality of pieces of captured image data are associated with the same attribute information.

Specifically, in construction photograph ledger data <NUM>, captured image data <NUM> and captured image data <NUM> are associated with a construction photograph insertion field <NUM> and are retained as insertion candidates. Attribute information (selection results, in this example) recorded in header sections of the captured image data <NUM> and the captured image data <NUM> is as follows.

Similarly, in construction photograph ledger data <NUM>, captured image data <NUM>, captured image data <NUM>, and captured image data <NUM> are associated with a construction photograph insertion field <NUM> and retained. Attribute information (selection results, in this example) recorded in header sections of the captured image data <NUM>, the captured image data <NUM>, and the captured image data <NUM> is as follows.

When a page of the construction photograph ledger data <NUM> is displayed by the information input apparatus <NUM>, the business operator <NUM> selects either the captured image data <NUM> or the captured image data <NUM>, which are insertion candidates. The information input apparatus <NUM> transmits a selection instruction, indicating which insertion candidate is selected, to the server apparatus <NUM>.

Similarly, when a page of the construction photograph ledger data <NUM> is displayed by the information input apparatus <NUM>, the business operator <NUM> selects one of the captured image data <NUM>, the captured image data <NUM>, and the captured image data <NUM>, which are insertion candidates. The information input apparatus <NUM> transmits a selection instruction, indicating which insertion candidate is selected, to the server apparatus <NUM>.

<FIG> is a second diagram illustrating a specific example of the display and selection process. In the example of <FIG>, upon an insertion candidate being selected, the body section of the selected captured image data is inserted into the construction photograph insertion field <NUM>, and a photographing date recorded in the header section of the selected captured image data is input into a photographing date field of the attribute information input field <NUM>.

Specifically, the construction photograph ledger data <NUM> indicates that the captured image data <NUM> is selected, and the body section of the captured image data <NUM> is inserted into the construction photograph insertion field <NUM>. Further, from among additional information of attribute information recorded in the header section of the captured image data <NUM>, a photographing date is input into a photographing date field of the attribute information input field <NUM>.

Further, the construction photograph ledger data <NUM> indicates that the captured image data <NUM> is selected, and the body section of the captured image data <NUM> is inserted into the construction photograph insertion field <NUM>. Further, from among additional information of attribute information recorded in the header section of the captured image data <NUM>, a photographing date is input into a photographing date field of the attribute information input field <NUM>.

Although not illustrated in <FIG> and <FIG>, when the information input apparatus <NUM> displays captured image data associated with a construction photograph insertion field <NUM> as an insertion candidate, the information input apparatus <NUM> may be configured to display additional information recorded in the header section of the captured image data.

Accordingly, insertion candidates are associated with a construction photograph insertion field <NUM> and retained. Thus, each time a page of construction photograph ledger data is displayed, the business operator <NUM> can visually recognize insertion candidates to be inserted into a construction photograph insertion field <NUM>.

Therefore, as compared to when captured image data is selected from a plurality of pieces of captured image data <NUM> as in the conventional manner, the workload of the business operator <NUM> in selecting captured image data can be reduced. Further, when selecting one of a plurality of pieces captured image data, the business operator <NUM> can view additional information recorded in header sections. Thus, the business operator <NUM> can select more appropriate captured image data.

Next, a flow of the finalized document generating process (step S414 of <FIG>) performed by the rule acquiring unit <NUM> and the finalized document generating unit <NUM> of the server apparatus <NUM> will be described. <FIG> is a flowchart illustrating the flow of the finalized document generating process.

In step S1501, the rule acquiring unit <NUM> retrieves captured image data stored in the construction photograph storage unit <NUM>. Further, the rule acquiring unit <NUM> arrange the retrieved captured image data in accordance with the insertion rules while referring to attribute information recorded in the header sections of the captured image data.

In step S1502, the rule acquiring unit <NUM> sequentially assigns the captured image data, arranged in accordance with the insertion rules, to pre-insertion information.

In step S1503, the finalized document generating unit <NUM> determines whether a plurality of pieces of captured image data are assigned to one pre-insertion information. If the finalized document generating unit <NUM> determines that one captured image data is assigned to one pre-insertion information in step S1503 (NO in step S1503), the process proceeds to step S1504.

In step S1504, the finalized document generating unit <NUM> inputs attribute information, recorded in the header section of the captured image data, into an attribute information input field of the pre-insertion information.

In step S1505, the finalized document generating unit <NUM> inserts the body section of the captured image data into a construction photograph insertion field of the pre-insertion information.

If the finalized document generating unit <NUM> determines that a plurality of pieces of captured image data are assigned to one pre-insertion information in step S1503 (YES in step S1503), the process proceeds to step S1506.

In step S1506, the finalized document generating unit <NUM> inputs attribute information except for a photographing date, which is one of additional information from among attribute information recorded in the header sections of the pieces of captured image data, into an attribute information input field.

In step S1507, the finalized document generating unit <NUM> associates the plurality of pieces of captured image data with a construction photograph insertion field of the pre-insertion information.

In step S1508, the finalized document generating unit <NUM> determines whether a request to display construction photograph ledger data is received from the information input apparatus <NUM>. In step S1508, if the finalized document generating unit <NUM> determines that a request to display construction photograph ledger data is not received (NO in step S1508), the finalized document generating unit <NUM> waits until determining that a request to display construction photograph ledger data is received.

Conversely, in step S1508, if the finalized document generating unit <NUM> determines that a request to display construction photograph ledger data is received (YES in step S1508), the process proceeds to step S1509.

In step S1509, the finalized document generating unit <NUM> transmits a page, specified by the information input apparatus <NUM>, of the construction photograph ledger data to the information input apparatus <NUM>.

In step S1510, the finalized document generating unit <NUM> determines whether an instruction to select captured image data is received from the information input apparatus <NUM>. In step S1510, if the finalized document generating unit <NUM> determines that an instruction to select captured image data is not received (NO in step S1510), the process proceeds to step S1512.

Conversely, in step S1510, if the finalized document generating unit <NUM> determines that an instruction to select captured image data is received (YES in step S1510), the process proceeds to step S1511.

In step S1511, the finalized document generating unit <NUM> inserts the body section of the selected captured image data into the associated construction photograph insertion field. Further, the finalized document generating unit <NUM> inputs a photographing date, recorded in the header section of the selected captured image data, into a photographing date field of the attribute information input field.

In step S1512, the finalized document generating unit <NUM> determines whether a request to display another page is received from the information input apparatus <NUM>. If the finalized document generating unit <NUM> determines that a request to display another page is received in step S1512 (YES in step S1512), the process returns to step S1509.

Conversely, if the finalized document generating unit <NUM> determines that a request to display another page is not received in step S1512 (NO in step S1512), the process proceeds to step S1513.

In step S1513, the finalized document generating unit <NUM> determines whether an instruction to end the process is received from the information input apparatus <NUM>. If the finalized document generating unit <NUM> determines that an instruction to end the process is not received in step S1513 (NO in step S1513), the process returns to step S1510.

Conversely, if the finalized document generating unit <NUM> determines that an instruction to end the process is received in step S1513 (YES in step S1513), the finalized document generating unit <NUM> ends the finalized document generating process.

As is clear from the description above, the server apparatus according to the first embodiment is configured such that:.

Accordingly, in the first embodiment, the workload of the business operator in generating construction photograph ledger data can be reduced.

In the above-described first embodiment, the constructor <NUM> inputs additional information when taking a construction photograph. However, additional information may be stored in the attribute information storage unit <NUM> in advance, and when the server apparatus <NUM> provides other attribute information, the server apparatus <NUM> may also provide the additional information.

Accordingly, similar to the other attribute information, the constructor <NUM> can select any of the additional information displayed on the terminal device <NUM>.

Further, in the above-described first embodiment, the two patterns are depicted in <FIG> and <FIG> as examples of arrangement based on insertion rules. However, examples of arrangement based on insertion rules are not limited to the two patterns, and any other pattern may be applied.

Further, in the above-described first embodiment, the processes performed by the task support system <NUM> when generating construction photograph ledger data, from among data included in the finalized document <NUM>, have been described. However, the task support system <NUM> may use the processes when generating data other than the construction photograph ledger data (for example, air conditioner test operation table data, airtightness test result table data, water flow test result table data, airflow volume measurement test comparison table data, and the like).

Further, in the above-described first embodiment, the constructor <NUM> inputs a photographing date as one of additional information; however, the photographing date may be automatically input.

Further, in the above-described first embodiment, if a plurality of pieces of captured image data is associated with the same attribute information, the business operator <NUM> selects one captured image data of the plurality of pieces of captured image data. However, a method of selecting one captured image data is not limited thereto, and the last captured image data may be automatically selected. Further, if one captured image data is selected by the business operator <NUM>, and subsequently, another captured image data having the same attribute information is added, the one captured image data, selected by the business operator <NUM>, and the other captured image data, added after the one captured image data is selected, may be displayed as selection candidates. That is, captured image data not selected the first time may be excluded from selection candidates.

In the above-described first and second embodiments, construction photograph ledger data generated based on captured image data is used as a part of a finalized document that is delivered to a customer. However, construction photograph ledger data generated based on captured image data is not necessarily used as a part of a finalized document that is delivered to a customer. For example, construction photograph ledger data may be used as a part of a document (a document attached to a subsidy application form) that is submitted to an administrative agency when applying for a subsidy for construction.

If construction photograph ledger data is used as described above, a format for generating the construction photograph ledger data differs from that used as a part of a finalized document that is delivered to a customer. In a third embodiment, when generating construction photograph ledger data, it is desirable to select a plurality of formats in accordance with the uses from among a plurality of types of formats, and capture image data based on the selected plurality of formats.

In the third embodiment, a task support system that can generate construction photograph ledger data by selecting a plurality of formats in accordance with the uses will be described.

First, a system configuration of a task support system according to the third embodiment will be described. <FIG> is a diagram illustrating another example of a system configuration of a task support system. As illustrated in <FIG>, a task support system <NUM> includes a photographing terminal <NUM>, a server apparatus <NUM>, a registration terminal <NUM>, and a finalized document creating terminal <NUM>. The server apparatus <NUM> is communicably connected to the photographing terminal <NUM>, the registration terminal <NUM>, and the finalized document creating terminal <NUM> via a network. In the following, the functions of each of the apparatus and the terminals will be described.

The server apparatus <NUM> is an example of a task support apparatus, and is configured by one or more computers. The server apparatus <NUM> includes a storage unit, and the storage unit stores formats for generating construction photograph ledger data that constitutes at least a part of a finalized document. In the present embodiment, a plurality of types of formats (for example, a format for each subsidy type, a format for each customer, and the like) are stored as formats for generating construction photograph ledger data that constitutes a part of a finalized document.

The formats for generating construction photograph ledger data will be described. Each of the formats for generating construction photograph ledger data includes position information and use information of image data to be captured and inserted. The position information indicates a photographing location where image data is to be captured. For example, the position information is information indicating a photographing location (for example, "roof/ceiling", "air conditioning equipment (heat source equipment)", "air conditioning equipment + lighting equipment", or the like) where image data is to be captured. Further, each of the formats for generating construction photograph ledger data includes precautions. The precautions include, for example, precautions to be taken when capturing image data, precautions to be taken when generating construction photograph ledger data, and the like.

Further, each of the formats stored in the storage unit of the server apparatus <NUM> may be construction photograph ledger data that has already been generated (i.e., a format into which captured image data has already been inserted), or may be construction photograph ledger data that is still being generated (i.e., a format into which captured image data has not yet been inserted).

The server apparatus <NUM> transmits, to the photographing terminal <NUM>, position information and use information about image data to be captured and inserted into a plurality of formats (for example, a format for subsidy A, a format for customer B, and the like) selected from a plurality of types of formats for generating construction photograph ledger data. The functions of the server apparatus <NUM> will be described later in detail with reference to <FIG>.

The photographing terminal <NUM> is a terminal for capturing image data. The photographing terminal <NUM> has a camera function. The photographing terminal <NUM> includes a smartphone, a tablet, and the like. The photographing terminal <NUM> receives, from the server apparatus <NUM>, position information and use information about each of pieces of image data to be captured and inserted into a plurality of formats (for example, the format for subsidy A, the format for customer B, and the like) selected from a plurality of types of formats for generating construction photograph ledger data. The photographing terminal <NUM> may display the use information received from the server apparatus <NUM>. In the present embodiment, a person who operates the photographing terminal <NUM> is referred to as a photographer <NUM>. The photographing terminal <NUM> will be described later in detail with reference to <FIG>.

Use information displayed by the photographing terminal <NUM> will be described. As described above, the photographing terminal <NUM> may be configured to display use information about each of pieces of image data to be captured. With this configuration, as use information about each of pieces of image data to be captured, the photographing terminal <NUM> displays one or more uses ("for subsidy A", "for customer B", "for both subsidy A and customer B", and the like, for example) about image data to be captured.

The registration terminal <NUM> is a terminal for registering position information in the server apparatus <NUM> in advance (that is, before the photographer <NUM> captures image data) for each type of format. The position information indicates a photographing location where image data (inserted into construction photograph ledger data) is to be captured. The registration terminal <NUM> is configured by, for example, a personal computer and the like. In the present embodiment, a person who operates the registration terminal <NUM> is referred to as a registrant <NUM>. The registration terminal <NUM> will be described later in detail with reference to <FIG>.

The finalized document creating terminal <NUM> is a terminal for generating finalized document data by inserting captured image data, captured by the photographing terminal <NUM>, into a format stored in the storage unit of the server apparatus <NUM> and generating construction photograph ledger data. The finalized document creating terminal <NUM> can display construction photograph ledger data that has already been generated and is stored in the server apparatus <NUM>. The finalized document creating terminal <NUM> is configured by, for example, a personal computer and the like. In the present embodiment, a person who operates the finalized document creating terminal <NUM> is referred to as a finalized document author <NUM>. The finalized document creating terminal <NUM> will be described later in detail with reference to <FIG>.

<FIG> is a diagram illustrating an example of a functional configuration of the photographing terminal. As illustrated in <FIG>, the photographing terminal <NUM> includes an information receiving unit <NUM>, a display unit <NUM>, a camera function control unit <NUM>, an image transmission unit <NUM>. These functions of the photographing terminal <NUM> are implemented by the photographing terminal <NUM> executing a program.

The information receiving unit <NUM> receives, from the server apparatus <NUM>, position information and use information about image data to be captured and inserted into a plurality of formats (for example, the format for subsidy A, the format for customer B, and the like) selected from a plurality of types of formats for generating construction photograph ledger data. Further, the information receiving unit <NUM> receives precautions to be taken when generating construction photograph ledger data (for example, precautions to be taken when capturing image data) from the server apparatus <NUM>.

The display unit <NUM> displays the position information and the use information received from the server apparatus <NUM>. Further, the display unit <NUM> displays the precautions to be taken when generating construction photograph ledger data (for example, precautions to be taken when capturing image data), received from the server apparatus <NUM>.

The camera function control unit <NUM> controls so as to display lines for determining the position of a photographing object on a photographing screen when a screen transitions to the photographing screen. Further, in order to reduce the influence of camera shake when image data is captured, the camera function control unit <NUM> corrects the captured image data.

The image transmission unit <NUM> transmits the captured image data, captured by the photographing terminal <NUM>, to the server apparatus <NUM>.

<FIG> is a diagram illustrating an example of a functional configuration of the server apparatus. The server apparatus <NUM> includes a registration unit <NUM>, an information generating unit <NUM>, an information transmitting unit <NUM>, and a finalized document creating unit <NUM>. These functions of the server apparatus <NUM> are implemented by the server apparatus <NUM> executing a program. Further, the server apparatus <NUM> includes a format storage unit <NUM>. The format storage unit <NUM> is implemented by an auxiliary storage device (such as an auxiliary storage device <NUM> of <FIG>) of the server apparatus <NUM>.

The registration unit <NUM> receives, from the registration terminal <NUM>, position information indicating a photographing location (such as "roof/ceiling", "air conditioning equipment (heat source equipment), and "air conditioning equipment + lighting equipment") where image data (inserted into each format) is to be captured. Further, the registration unit <NUM> links property information (for example, information about a property (such as a building) where a device such as an air conditioner is installed) with position information of image data to be captured and inserted into a plurality of types of formats for generating construction photograph ledger data. Then, the registration unit <NUM> stores the property information linked with the position information in the format storage unit <NUM>.

Further, the registration unit <NUM> stores captured image data, captured by the photographing terminal <NUM>, in the format storage unit <NUM>.

The format storage unit <NUM> stores a plurality of formats (for example, a format for each subsidy, a format for each customer, and the like) for generating construction photograph ledger data. As described above, each of the formats includes position information and use information about image data to be captured and inserted into construction photograph ledger data. Further, each of the formats includes precautions to be taken when generating construction photograph ledger data.

Each of the formats stored in the format storage unit <NUM> may be construction photograph ledger data that has already been generated (i.e., a format into which captured image data has already been inserted), or may be construction photograph ledger data that is still being generated (i.e., a format into which captured image data has not yet been inserted).

For example, if a format is for generating construction photograph ledger data attached to a subsidy application form, at least one of construction photograph ledger data in the case of a subsidy being provided, construction photograph ledger data in the case of no subsidy being provided, and construction photograph ledger data into which captured image data is yet to be inserted is stored in the format storage unit <NUM>. That is, in the present embodiment, a plurality of persons can share construction photograph ledger data generated by other persons and attached to various subsidy application forms. Examples of such construction photograph ledger data include construction photograph ledger data into which captured image data has been inserted (in the case of a subsidy being provided/no subsidy being provided), and construction photograph ledger data into which construction photograph ledger data is yet to be inserted.

Further, the format storage unit <NUM> stores captured image data, captured by the photographing terminal <NUM>.

The format storage unit <NUM> is configured to permit access from a person having permission to share a format when the format is accessed. That is, only a person having a predetermined sharing permission can access a predetermined format (for example, a format shared within a company, a format shared within group companies, and the like) stored in the format storage unit <NUM>.

The information generating unit <NUM> generates position information and use information to be transmitted to the photographing terminal <NUM>. Specifically, from among a plurality of types of formats stored in the format storage unit <NUM>, the information generating unit <NUM> selects a plurality of formats in which position information has been registered by the registration terminal <NUM> (that is, a plurality of formats into which image data captured by the photographing terminal <NUM> is to be inserted). The information generating unit <NUM> generates position information about image data to be captured and inserted into at least one of the plurality of formats in which the position information has been registered by the registration terminal <NUM>. Further, based on the plurality of formats in which the position information has been registered by the registration terminal <NUM>, the information generation unit <NUM> generates use information about the image data to be captured.

The information transmitting unit <NUM> transmits the generated position information and use information to the photographing terminal <NUM>.

In response to a request from the finalized document creating terminal <NUM>, the finalized document creating unit <NUM> transmits a format for generating finalized document data to the finalized document creating terminal <NUM>. Further, the finalized document creating unit <NUM> receives finalized document data (for example, finalized document data that includes construction photograph ledger data into which captured image data has already been inserted), generated by the finalized document creating terminal <NUM>, from the finalized document creating terminal <NUM>. The finalized document creating unit <NUM> stores construction photograph ledger data (that is, construction photograph ledger data into which captured image data has already been inserted), included in the received finalized document data, in the format storage unit <NUM>. Further, the finalized document creating unit <NUM> can receive precautions to be taken when generating construction photograph ledger data from the finalized document creating terminal <NUM>. The finalized document creating unit <NUM> links the received precautions with the format, and stores the precautions linked with the format in the format storage unit <NUM>.

<FIG> is a diagram illustrating an example of a functional configuration of the registration terminal. The registration terminal <NUM> includes a registration unit <NUM>. The function of the registration terminal <NUM> is implemented by the registration terminal <NUM> executing a program.

In response to an instruction from the registrant <NUM>, the registration unit <NUM> selects a format (for example, the format for subsidy A) in which position information is to be registered.

If formats in which position information is to be registered have already been stored in the server apparatus <NUM>, the registration unit <NUM> selects a format, in which position information is to be registered, from the formats stored in the server apparatus <NUM>.

If formats in which position information is to be registered have not yet been stored in the server apparatus <NUM> (that is, if the registrant <NUM> is the first registrant who register this type of format), the registration unit <NUM> selects a format generated by the registrant <NUM> as a format in which position information is to be registered. For example, the registrant <NUM> reads guidelines for creating subsidy application forms, and creates a format. Note that an administrator or the like may check whether the format to be registered is appropriate.

The registration unit <NUM> receives an input of position information (for example, "roof/ceiling", "air conditioning equipment (heat source equipment), "air conditioning equipment + lighting equipment", and the like) about image data to be captured and inserted into the selected format (for example, the format for subsidy A). Further, the registration unit <NUM> transmits the position information, about image data to be captured and inserted into the format, to the server apparatus <NUM>. Further, the registration unit <NUM> transmits precautions to be taken when generating construction photograph ledger data, which have been input by the registrant <NUM>, to the server apparatus <NUM>.

<FIG> is a diagram illustrating an example of a functional configuration of the finalized document creating terminal. The finalized document creating terminal <NUM> includes a finalized document creating unit <NUM>. The function of the finalized document creating terminal <NUM> is implemented by the finalized document creating terminal <NUM> executing a program.

The finalized document creating unit <NUM> receives a format, used by the finalized document author <NUM> to create finalized document data, from the server apparatus <NUM>. Further, the finalized document creating unit <NUM> generates finalized document data. The finalized document creating unit <NUM> transmits the generated finalized document data to the server apparatus <NUM>. Further, the finalized document creating unit <NUM> can transmit precautions to be taken when generating construction photograph ledger data, which have been input by the finalized document author <NUM>, to the server apparatus <NUM>.

<FIG> is a sequence diagram illustrating an example of a flow of a finalized document generating process. In the following, a registration process (steps S2111 to S2112), an information generating process (step S2121), and an image capturing process (steps S2131 to S2134) included in the finalized document generating process (steps S2141 to S2144) will be described separately.

In step S2111, the registration terminal <NUM> transmits, to the server apparatus <NUM>, property information (for example, information about a property (such as a building) where a device such as an air conditioner is installed) and position information about each piece of image data to be captured and inserted into a plurality of types of formats. The plurality of types of formats are used to generate construction photograph ledger data at the time of construction of the building.

In step S2112, the server apparatus <NUM> stores the position information about the pieces of image data (to be captured and inserted into the formats), received in step S2111, in the format storage unit <NUM> of the server apparatus <NUM>.

In step S2121, the server apparatus <NUM> generates position information and use information to be transmitted to the photographing terminal <NUM>. Specifically, the server apparatus <NUM> generates position information about image data to be captured and inserted into at least one of a plurality of formats in which position information has been registered by the registration terminal <NUM> (that is, at least one of a plurality of formats into which image data captured by the photographing terminal <NUM> is to be inserted). Further, based on the plurality of formats in which the position information has been registered by the registration terminal <NUM>, the server apparatus <NUM> generates use information about the image data to be captured.

In step S2131, the photographing terminal <NUM> receives, from the server apparatus <NUM>, the position information and the use information about the image data to be captured and inserted into at least one of the plurality of formats (for example, the format for subsidy A and the format for customer B) selected from the plurality of types of formats for generating construction photograph ledger data. Further, the photographing terminal <NUM> displays the use information about the image data to be captured. Further, the photographing terminal <NUM> receives precautions to be taken when generating construction photograph ledger data (for example, precautions to be taken when capturing image data), which constitutes a part of a finalized document, from the server apparatus <NUM>.

For example, the server apparatus <NUM> transmits, to the photographing terminal <NUM>, position information and use information about property information (for example, information about a property (such as a building) where a device such as an air conditioner is installed) specified from the photographing terminal <NUM>.

In step S2132, the photographing terminal <NUM> captures image data. For example, the photographing terminal <NUM> captures image data by the photographer <NUM> operating the photographing terminal <NUM> at location(s) indicated by the position information transmitted in step S2131.

In step S2133, the photographing terminal <NUM> transmits the captured image data, captured in step S2132, to the server apparatus <NUM>.

In step S2134, the server apparatus <NUM> stores the captured image data, received in the step S2133, in the format storage unit <NUM> of the server apparatus <NUM>.

In step S2141, the finalized document creating terminal <NUM> acquires a format, used by the finalized document author <NUM> to generate finalized document data, from the server apparatus <NUM>.

In step S2142, the finalized document creating terminal <NUM> generates finalized document data. For example, the finalized document author <NUM> operates the finalized document creating terminal <NUM> such that captured image data (captured by the photographing terminal <NUM>) acquired from the server apparatus <NUM> is inserted into a predetermined portion of the format of construction photograph ledger data, acquired in step S2141. At this time, the finalized document creating terminal <NUM> may display precautions to be taken when generating construction photograph ledger data (for example, precautions to be taken when creating documents).

Note that when the finalized document author <NUM> generates construction photograph ledger data, the finalized document author <NUM> may cause the finalized document creating terminal <NUM> to display construction photograph ledger data that has been generated by any other person and stored in the server apparatus <NUM> (that is, construction photograph ledger data into which captured image data has already been inserted) or construction photograph ledger data that is still being generated (that is, construction photograph ledger data into which captured image data is yet to be inserted), so as to view the construction photograph ledger data. For example, when the finalized document author <NUM> generates construction photograph ledger data attached to a subsidy application form, the finalized document author <NUM> may display and view at least one of construction photograph ledger data in the case of a subsidy being provided, construction photograph ledger data in the case of no subsidy being provided, and construction photograph ledger data into which captured image data is yet to be inserted.

In step S2143, the finalized document creating terminal <NUM> transmits a finalized document, including the construction photograph ledger data generated in step S2142 (that is, a finalized document including the construction photograph ledger data into which the captured image data has already been inserted), to the server apparatus <NUM>. Further, the finalized document creating terminal <NUM> can transmit precautions to be taken when generating construction photograph ledger data, which have been input by the finalized document author <NUM>, to the server apparatus <NUM>.

In step S2144, the server apparatus <NUM> stores, in the format storage unit <NUM> of the server apparatus <NUM>, the construction photograph ledger data that constitutes a part of the finalized document received in step S2143 (that is, the construction photograph ledger data into which the captured image data has already been inserted). Further, the server apparatus <NUM> links the format with the precautions received in step S2143, and stores the format linked with the precautions in the format storage unit <NUM> of the server apparatus <NUM>.

Instead of the finalized document author <NUM> performing an operation for inserting captured image data into a predetermined portion of a format as described above, the server apparatus <NUM> may be configured to automatically insert captured image data into a predetermined portion of a format based on information that links the captured image data with each portion of the format. Details will be described below.

The server apparatus <NUM> assigns identifiers (hereinafter also referred to as "attribute information") to respective portions of a format, into which captured image data is to be inserted, and manage the identifiers. The photographing terminal <NUM> assigns, to captured image data, attribute information of a portion of the format, into which the captured image data is to be inserted. The server apparatus <NUM> inserts the captured image data into the portion of the format by referring to the attribute information assigned to the captured image data captured by the photographing terminal <NUM>. Accordingly, in the present embodiment, the server apparatus <NUM> can automatically generate a plurality of pieces of construction photograph ledger data in response to image data being captured.

Next, each of the processes included in the finalized document generating process will be described in detail.

<FIG> is a flowchart illustrating an example of a flow of the registration process. In step S2201, in response to an instruction from the registrant <NUM>, the registration unit <NUM> of the registration terminal <NUM> selects a format (for example, the format for subsidy A) in which position information is to be registered.

If formats in which position information is to be registered have already been stored in the server apparatus <NUM>, the registration unit <NUM> of the registration terminal <NUM> selects a format, in which position information is to be registered, from the formats stored in the server apparatus <NUM>.

If formats in which position information is to be registered have not yet been stored in the server apparatus <NUM> (that is, if the registrant <NUM> is the first registrant who register this type of format), the registration unit <NUM> selects a format generated by the registrant <NUM> as a format in which position information is to be registered. For example, the registrant <NUM> reads guidelines for creating subsidy application forms, and create a format.

In step S2202, the registration unit <NUM> of the registration terminal <NUM> receives an input of position information (for example, "roof/ceiling", "air conditioning equipment (heat source equipment), "air conditioning equipment + lighting equipment", and the like) about image data to be captured and inserted into the format (for example, the format for subsidy A) selected in step S2201. Further, the registration unit <NUM> of the registration terminal <NUM> transmits the position information about image data to be captured and inserted into the format, to the server apparatus <NUM>. Further, the registration unit <NUM> of the registration terminal <NUM> can transmit precautions to be taken when generating construction photograph ledger data, which have been input by the registrant <NUM>, to the server apparatus <NUM>.

<FIG> is a flowchart illustrating an example of a flow of the information generating process. In step S2301, from among a plurality of types of formats stored in the format storage unit <NUM>, the information generating unit <NUM> of the server apparatus <NUM> selects a plurality of formats in which position information has been registered by the registration terminal <NUM> (that is, a plurality of formats into which image data captured by the photographing terminal <NUM> are to be inserted).

In step S2302, the information generating unit <NUM> of the server apparatus <NUM> generates position information about image data to be captured and inserted into at least one of the plurality of formats selected in step S2301. Further, the information generation unit <NUM> generates use information about the image data to be captured, based on the plurality of formats in which the position information has been registered by the registration terminal <NUM>.

<FIG> is a flowchart illustrating an example of a flow of the image capturing process. In step S2401, the information receiving unit <NUM> of the photographing terminal <NUM> receives, from the server apparatus <NUM>, the position information and the use information about the image data to be captured and inserted into at least one of the plurality of formats (such as the format for subsidy A and the format for customer B) selected from the plurality of types of formats for generating construction photograph ledger data. Further, the display unit <NUM> of the photographing terminal <NUM> displays the use information about the image data to be captured. Further, the information receiving unit <NUM> of the photographing terminal <NUM> receives precautions to be taken when generating construction photograph ledger data (for example, precautions to be taken when capturing image data) from the server apparatus <NUM>, and the display unit <NUM> of the photographing terminal <NUM> displays the precautions received by the information receiving unit <NUM>.

In step S2402, the photographing terminal <NUM> captures image data. For example, the photographing terminal <NUM> captures image data by the photographer <NUM> operating the photographing terminal <NUM> at location(s) indicated by the position information transmitted in step S2401.

In step S2403, the image transmission unit <NUM> of the photographing terminal <NUM> transmits the captured image data, captured in step S2402, to the server apparatus <NUM>.

<FIG> is a flowchart illustrating an example of a flow of the finalized document data generating process. In step S2501, the finalized document creating unit <NUM> of the finalized document creating terminal <NUM> receives a format used by the finalized document author <NUM> to generate finalized document data from the server apparatus <NUM>.

In step S2502, the finalized document creating unit <NUM> of the finalized document creating terminal <NUM> generates finalized document data. The finalized document author <NUM> operates the finalized document creating terminal <NUM> such that captured image data (captured by the photographing terminal <NUM>) acquired from the server apparatus <NUM> is inserted into a predetermined portion of the format, which is for generating construction photograph ledger data, received in step S2501.

In step S2503, the finalized document creating unit <NUM> of the finalized document creating terminal <NUM> transmits the finalized document data generated in step S2502 to the server apparatus <NUM>. Note that the finalized document creating unit <NUM> of the finalized document creating terminal <NUM> may transmit precautions to be taken when generating construction photograph ledger data, which have been input by the finalized document author <NUM>, to the server apparatus <NUM>.

<FIG> is a diagram illustrating specific examples of position information and use information. A case in which both construction photograph ledger data of format A (for example, the format for subsidy A) and construction photograph ledger data of format B (for example, the format for customer B) are generated at one construction will be described.

The registration terminal <NUM> registers, in the server apparatus <NUM>, position information about image data to be captured and inserted into the format A and position information about image data to be captured and inserted into the format the format B. Specifically, in the example illustrated in the upper left of <FIG>, position information about image data to be captured and inserted into the format A is "roof/ceiling [before construction]", "roof/ceiling [during construction]", "roof/ceiling [after construction]", "air conditioning equipment (heat source equipment) [before construction]", "air conditioning equipment (heat source equipment) [during construction]", "air conditioning equipment (heat source equipment) [after construction]", "air conditioning equipment + lighting equipment [before construction]", "air conditioning equipment + lighting equipment [during construction]", and "air conditioning equipment + lighting equipment [after construction]". Further, in the example illustrated in the upper right of <FIG>, position information about image data to be captured and inserted into the format B is "air conditioning equipment (heat source equipment) [before construction]", "air conditioning equipment (heat source equipment) [during construction]", "air conditioning equipment (heat source equipment) [after construction]", "air conditioning equipment + lighting equipment [before construction]", "air conditioning equipment + lighting equipment [during construction]," and "air conditioning equipment + lighting equipment [after construction]".

The server apparatus <NUM> generates position information and use information to be transmitted to the photographing terminal <NUM>. Specifically, the server apparatus <NUM> generates position information about image data to be captured and inserted into at least one of a plurality of formats (that is, at least one of the format A and the format B) in which position information has been registered by the registration terminal <NUM>. Further, based on the plurality of formats in which the position information has been registered by the registration terminal <NUM>, the server apparatus <NUM> generates use information about the image data to be captured. For example, in the example of <FIG>, the use of image data to be captured at each of "roof/ceiling [before construction]", "roof/ceiling [during construction]", and "roof/ceiling [after construction]" is for the format A (for "subsidy A"). Further, the use of image data to be captured at each of "air conditioning equipment (heat source equipment) [before construction]", "air conditioning equipment (heat source equipment) [during construction]" "air conditioning equipment (heat source equipment) [after construction]" "air conditioning equipment + lighting equipment [before construction]", "air conditioning equipment + lighting equipment [during construction]", and "air conditioning equipment + lighting equipment [after construction]" is for both the format A and the format B (for both "subsidy A" and "customer B").

Accordingly, when the photographer <NUM> captures image data, the photographer <NUM> can know the use of the image data (for example, the use of the image data is for "subsidy A", for "customer B", or for both "subsidy A and customer B"). Further, the finalized document author <NUM> can refer to construction photograph ledger data generated by other persons.

<FIG> is a diagram illustrating an example of a hardware configuration of each of the photographing terminal, the server apparatus, the registration terminal, and the finalized document creating terminal. Each of the photographing terminal <NUM>, the server apparatus <NUM>, the registration terminal <NUM>, and the finalized document creating terminal <NUM> includes a central processing unit (CPU) <NUM>, a read-only memory (ROM) <NUM>, and a random-access memory (RAM) <NUM>. The CPU <NUM>, the ROM <NUM> and the RAM <NUM> form what is referred to as a computer.

Further, each of the photographing terminal <NUM>, the server apparatus <NUM>, the registration terminal <NUM>, and the finalized document creating terminal <NUM> include an auxiliary storage device <NUM>, a display device <NUM>, an operation device <NUM>, an interface (I/F) device <NUM>, and a drive device <NUM>. The hardware elements of each of the photographing terminal <NUM>, the server apparatus <NUM>, the registration terminal <NUM>, and the finalized document creating terminal <NUM> are connected to each other via a bus B.

The CPU <NUM> is a calculation device that executes various programs installed in the auxiliary storage device <NUM>.

The auxiliary storage device <NUM> is an auxiliary storage device that stores various programs and information used when the various programs are executed.

The display device <NUM> is a display device that displays an internal state of each of the photographing terminal <NUM>, the server apparatus <NUM>, the registration terminal <NUM>, and the finalized document creating terminal <NUM>.

The operation device <NUM> is an input device used when an administrator of each of the photographing terminal <NUM>, the server apparatus <NUM>, the registration terminal <NUM>, and the finalized document creating terminal <NUM> inputs various instructions into each of the photographing terminal <NUM>, the server apparatus <NUM>, the registration terminal <NUM>, and the finalized document creating terminal <NUM>.

The I/F device <NUM> is a communication device that is connected to a network and communicates with the photographing terminal <NUM>, the server apparatus <NUM>, the registration terminal <NUM>, the finalized document creating terminal <NUM>, and the like.

Various programs to be installed in the auxiliary storage device <NUM> are installed by, for example, setting the distributed recording medium <NUM> in the drive device <NUM> and reading the various programs recorded in the recording medium <NUM> by the drive device <NUM>. Alternatively, various programs to be installed in the auxiliary storage device <NUM> may be installed by being downloaded from the network via the I/F device <NUM>.

Note that a camera built in the photographing terminal <NUM> or a camera connected to the photographing terminal <NUM> captures image data. That is, the photographing terminal <NUM> may be configured to include a built-in camera (that is, the photographing terminal <NUM> and the camera are integrated into one device), or the photographing terminal <NUM> may be connected with a camera (that is, the photographing terminal <NUM> and the camera are separate devices).

Although embodiments have been described above, it will be understood that various changes in form and detail may be made without departing from the scope of the claims.

Claim 1:
A task support apparatus comprising:
a first acquiring unit configured to acquire a plurality of captured images associated with pieces of attribute information from a terminal device configured to associate the captured images with the pieces of attribute information, the pieces of attribute information each including a construction detail and a photographing timing;
a second acquiring unit configured to acquire at least an insertion rule and description rules of a document for reporting a construction status; and
a generating unit configured to generate image information based on the pieces of attribute information, associated with the plurality of captured images acquired by the first acquiring unit, and the at least the insertion rule acquired by the second acquiring unit,
wherein the generating unit is configured to
classify the plurality of captured images acquired by the first acquiring unit into groups, in accordance with the insertion rule,
characterized in that the generating unit is further configured to
further classify, for each specific attribute information, one or more captured images classified into each of the groups, to generate the image information,
wherein the specific attribute information comprises room/zone, device and task information.