AU2012216428B2 - Systems and methods for collecting, storing and processing inspection data - Google Patents

Abstract

SYSTEMS AND METHODS FOR COLLECTING, STORING AND PROCESSING INSPECTION DATA Described herein are systems and methods for collecting, storing and processing 5 inspection data. One aspect of the present invention provides a computer implemented method (100) for generating an inspection report. The method includes the initial step (101) of providing a web-based interface for enabling a user to manage inspection data and request an inspection report based on specified input inspection request data. At step (103), in response to a request from a user of the interface, a software application is 10 generated that is executable at a mobile device. The software application is configured for receiving, from an inspector using a mobile device who is to carry out an inspection, data indicative of inspection observations. Step (103) of generating the software application includes two primary sub-steps. At sub-step (105), a database of predefined inspection prompts is accessed thereby to identify a set of inspection prompts based on the 15 inspection request data specified. At sub-step (107) the application is configured to display the set of inspection prompts and provide functionality for receiving, from the inspector, respective responses to those prompts. At step (109), the application is downloaded to a mobile device for use by an inspector. At step (111), the responses to the inspection prompts, input by the inspector input at the mobile device, are received. At 20 step (113), the received responses are stored in the database. Finally, at step (115), the received responses may be processed to generate the inspection report. (FIG. 1) Providing a web-based interface 103 ' Generating an inspection reporting software application executable at a mobile device 105 - - - - - - Accessing a database of predefined inspection prompts 107 Configuring the application to h display the inspection prompts and to receive responses to the I prompts 109 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Allowing download of the application to a mobile device 111 ________ Receiving responses to the inspection prompts Storing the received responses in the database Processing the received responses to generate the FIG. 1 inspection report

Description

AUSTRALIA PATENTS ACT 1990 COMPLETE SPECIFICATION FOR A STANDARD PATENT ORIGINAL Name of Applicant: Workflow Technologies Actual Inventors: Matthew Hanson and Darryl Posgate Address for Service is: SHELSTON IP 60 Margaret Street Telephone No: (02) 9777 1111 SYDNEY NSW 2000 Facsimile No. (02) 9241 4666 CCN: 3710000352 Attorney Code: SW Invention Title: Systems and methods for collecting, storing and processing inspection data Details of Associated Provisional Application No. 2012900098 dated 10 Jan 2012 The following statement is a full description of this invention, including the best method of performing it known to me/us: File: 73105AUP00 2 SYSTEMS AND METHODS FOR COLLECTING, STORING AND PROCESSING INSPECTION DATA FIELD OF THE INVENTION [0001] The present invention relates to systems and methods for collecting, storing and processing inspection data. Embodiments of the invention have been particularly developed for providing a computer-implemented system and method for generating an inspection application which allows an inspector to carry out an inspection and input inspection data for collection, storage and processing to produce inspection reports. While some embodiments will be described herein with particular reference to that application, it will be appreciated that the invention is not limited to such a field of use, and is applicable in broader contexts. BACKGROUND [0002] Any discussion of the background art throughout the specification should in no way be considered as an admission that such art is widely known or forms part of common general knowledge in the field. [0003] Many industries require the collection of inspection data for compliance with predefined standards. For example, in workplace health and safety, inspectors are required by legislation to obtain certain information about the condition of a workplace. Similarly, home buyers often request building inspections prior to purchasing a house in order to ascertain the condition of that house. Such inspections are typically carried out by a licensed inspector who completes a checklist or report having predefined industry or job specific checklist entries. [0004] Traditionally, inspections are carried out on paper forms. However, more recently, the ability to produce electronic reports has emerged. One new method involves the use of an inspection application accessible on a mobile computer device, tablet or Smartphone, which allows an inspector to produce and send inspection reports on the go through that device. Developing a custom application specific to an inspection job requires collecting a range of information to produce the appropriate fields for the inspection. Currently, the collection of the data necessary to produce a "customised" reporting application is time consuming and can require significant input from the customer.

3 Specifically, this information collection process imposes limitations on how quickly a custom inspection application is available to a user. [0005] There is a need in the art for improved systems and methods for collecting, storing and processing inspection data and for producing inspection reports. SUMMARY OF THE INVENTION [0006] It is an object of the present invention to overcome or ameliorate at least one of the disadvantages of the prior art, or to provide a useful alternative. [0007] In accordance with a first aspect of the present invention, there is provided a computer implemented method for generating an inspection report, the method including the steps of: providing a web-based interface for enabling a user to request an inspection report based on specified input inspection request data that is specific to a type of inspection to be carried out; in response to the request, automatically generating a downloadable customised software application executable at a mobile device, the software application being customised based on the inspection request data and being configured for receiving, from an inspector, data indicative of inspection observations, wherein generating the software application includes: accessing a database of predefined inspection prompts thereby to identify a set of inspection prompts based on the inspection request data specified; configuring the application to render a visual interface on a display of the mobile device to display the set of inspection prompts and provide input functionality for receiving, from the inspector, respective responses to those prompts; allowing download of the customised application to the mobile device; receiving, based on inspector input at the mobile device that executes the application, responses to the inspection prompts; processing the received responses thereby to generate the inspection report.

4 [0008] The inspection request data preferably includes data indicative of one or more user industries and the application is preferably populated with one or more predefined inspection prompts relating to an industry. [0009] The inspection request data preferably includes data indicative of one or more job types and the application is preferably populated with one or more predefined inspection prompts relating to a job type. [0010] The inspection request data preferably includes data indicative of one or more customers of the user and the application is preferably populated with one or more predefined inspection prompts relating to a customer. [0011] The inspection request data is preferably specified by a user of the interface through the selection of one or more of a plurality of selectable options. A user is preferably able to change the options at the interface after generation of the software application, and, upon updating the options, the software application is updated. The method preferably includes the step of storing the received responses in the database. [0012] The user is preferably linked to a user account, wherein user data corresponding to that user is stored in the database under this user account, and wherein the interface is presented to the user in a form based on the data corresponding to that user. The method preferably further includes the step of selectively controlling the permission of the user to modify or add/remove inspection prompts on the user account type, or modify how a response to a prompt is provided at the mobile device. The user preferably pays a subscription fee for maintaining a user account. The user's permission to modify inspection request data is preferably based upon the subscription fee paid. [0013] The user account is preferably linked to one or more industries, job types and/or customers based on the subscription fee paid. In one embodiment, the output format of the generated inspection report is preferably modifiable based upon the subscription fee paid. In one embodiment, the subscription fee is preferably based on the number of applications generated. In another embodiment, the subscription fee is preferably based on the number of inspection reports generated. [0014] In one embodiment, user accounts can preferably only be modified by a system administrator.

5 [0015] The inspection report is preferably output as an electronic file. The output electronic file is preferably emailed to a designated email address corresponding to the user or a related customer of the user. [0016] Inspection prompts are preferably set to be either mandatory or optional. [0017] The mobile device is preferably a computer, personal digital assistant tablet, Smartphone or Pod Touch. In one embodiment, the application is preferably configured as software for an Phone or iPad application having touch screen input capability. In another embodiment, the application is preferably configured as Android based software application for an Android compatible Smartphone having touch screen input capability. [0018] The inspection report generated is preferably user specific. The inspection report generated is preferably specific to the user's industry. The inspection report generated preferably includes only a predefined subset of the set of inspection prompts and corresponding responses. [0019] One or more of the inspection prompts are preferably associated with support images for assisting an inspector in providing a response. In one embodiment, a system administrator preferably defines what support images are included in the generated inspection report. In another embodiment, a user preferably defines whether or not support images are included in the generated inspection report. [0020] In accordance with a second aspect of the present invention, there is provided a computer system configured to perform a method according to any one of the preceding claims. [0021] In accordance with a third aspect of the present invention, there is provided a system for generating an inspection report, the system including: a database for storing predefined inspection prompts; a server for hosting a web-based interface renderable on one or more computer processors for enabling a user to input a request for an inspection report, the request including the input of specified input inspection request data that is specific to a type of inspection to be carried out, the interface being configured to; access the database of predefined inspection prompts thereby to identify a set of inspection prompts based on the input inspection request data; 6 in response to the request, automatically generate a downloadable customised software application executable at a mobile device and being customised based on the inspection request data, the software application, when executed, rendering a visual interface on a display of the mobile device to display the set of inspection prompts and provide input functionality for receiving, from an inspector, respective responses to those prompts; and processing the received responses thereby to generate the inspection report. [0022] In accordance with a fourth aspect of the present invention, there is provided a computer implemented method of generating a reporting application, the method including the steps of: providing a web-based interface for enabling a user to request a downloadable customised software reporting application that is customised based on specified input application data and that is specific to a type of reporting to be carried out; receiving input application data from the user; in response to the request from the user, accessing a database of predefined application prompts thereby to identify a set of prompts that are specific to the user's desired application; automatically generating the customised reporting application executable at a mobile device, and allowing download of the customised reporting application to a mobile device; wherein the reporting application is configured for: rendering a visual interface on a display of the mobile device to display the set of application prompts; and providing input functionality for receiving, from a user of the mobile device, respective responses to those prompts. [0023] The reporting application is preferably configured to store the received responses in the database.

7 [0024] In accordance with a fifth aspect of the present invention, there is provided a computer implemented method for collecting, storing and processing inspection data, the method including the steps of: providing a web-based interface for enabling a user to access inspection data stored in a database and to request inspection data from an inspection performed by an inspector on a mobile device; in response to the request from a user, automatically generating and providing a downloadable customised software application executable at the mobile device, the software application being customised based on the inspection request data and being configured for rendering a visual interface on a display of the mobile device and receiving, from an inspector, data indicative of inspection observations, wherein the software application includes: a set of inspection prompts displayed on the rendered visual interface that are specific to the user's desired inspection, including a type of inspection to be carried out; functionality for receiving, from the inspector, respective responses to those prompts; allowing download of the customised application to the mobile device; receiving, based on inspector input at the mobile device that executes the customised application, responses to the inspection prompts; storing the received responses in a database as inspection data accessible to a user through the web-based interface. [0025] The web-based interface is preferably configured to selectively process inspection data to produce one or more inspection reports based on user information. [0026] One embodiment provides a computer program product for performing a method as described herein. [0027] One embodiment provides a non-transitive carrier medium for carrying computer executable code that, when executed on a processor, causes the processor to perform a method as described herein.

8 [0028] One embodiment provides a system configured for performing a method as described herein. [0029] Throughout this specification, use of the term "user" is intended to mean a user of the web-interface who wishes to generate a reporting application for carrying out one or more inspections. An example user is a company employing inspectors to carry out inspections for customers. [0030] The term "customers" is interpreted to mean a customer of a user. The customer is the party who requires the inspection. An example customer is an owner or property manager of an apartment requiring a condition inspection report. [0031] Throughout this specification, use of the terms "reporting application" is intended to mean a software application executable on a mobile computing device such as a Smartphone, Tablet or "Smartpad", for example Phones and Pads. The reporting application is configured to display inspection prompts and allow input from an inspector to provide responses to those prompts during an inspection. [0032] Throughout this specification, use of the terms "inspection report" is intended to mean a report, in software or physical form, setting out the complete information indicative of a completed inspection. This includes the required inspection questions and the responses provided by the relevant inspector. The inspection report may also include additional information such as comments, company logos and inspection-specific data such as date, address etc. [0033] Throughout this specification, use of the terms "inspection prompts" is intended to mean questions or statements that require a response from an inspector. Inspection prompts are stored in a database and are displayed in a reporting application. [0034] Reference throughout this specification to "one embodiment", "some embodiments" or "an embodiment" means that a particular feature, structure or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, appearances of the phrases "in one embodiment", "in some embodiments" or "in an embodiment" in various places throughout this specification are not necessarily all referring to the same embodiment, but may. Furthermore, the particular features, structures or characteristics may be combined in any suitable manner, as would be apparent to one of ordinary skill in the art from this disclosure, in one or more embodiments. [0035] As used herein, unless otherwise specified the use of the ordinal adjectives "first", "second", "third", etc., to describe a common object, merely indicate that different 9 instances of like objects are being referred to, and are not intended to imply that the objects so described must be in a given sequence, either temporally, spatially, in ranking, or in any other manner. [0036] In the claims below and the description herein, any one of the terms comprising, comprised of or which comprises is an open term that means including at least the elements/features that follow, but not excluding others. Thus, the term comprising, when used in the claims, should not be interpreted as being limitative to the means or elements or steps listed thereafter. For example, the scope of the expression a device comprising A and B should not be limited to devices consisting only of elements A and B. Any one of the terms including or which includes or that includes as used herein is also an open term that also means including at least the elements/features that follow the term, but not excluding others. Thus, including is synonymous with and means comprising. BRIEF DESCRIPTION OF THE DRAWINGS [0037] Embodiments of the invention will now be described, by way of example only, with reference to the accompanying drawings in which: FIG. 1 schematically illustrates a method according to one aspect of the present invention; FIG. 2 schematically illustrates a system according to another aspect of the present invention; FIG. 3 illustrates schematically an example of a screen from a generated inspection application; FIG. 4 illustrates three screen shots of a reporting application generated on an Apple iPhone; FIG. 5 illustrates an example screen shot of a web page for entering and displaying user account information; FIG. 6 illustrates an example screen shot of a web page for displaying and entering data indicative of inspection jobs; FIG. 7A illustrates an upper portion of an example screen shot of a web page for displaying job details; FIG. 7B illustrates a lower portion of an example screen shot of a web page for displaying job details; 10 FIG. 8 illustrates a calendar module embedded within the web-interface for displaying and modifying an inspector's availability; FIG. 9 illustrates an example screen shot of a web page for displaying and modifying inspection question data; FIG. 10 illustrates a screen shot of an example web page providing functionality to an administrator to display, modify and add/remove question categories; FIG. 11 illustrates a screen shot of a portion of a web page providing functionality for an administrator to enter or modify a user's account details; Fig. 12 illustrates a screen shot of an example web page for allowing an administrator to modify standard report style preamble and summary text for a report entitled "Default Routine Condition Report"; Fig. 13 illustrates a screen shot of an example web page for allowing an administrator to modify the standard output report format template for a report entitled "Default Routine Condition Report"; and Fig. 14 is a screen shot of an example web page for providing visible inspection support for inspectors and an example iPhone screen displaying a support image of different fire extinguishers. DETAILED DESCRIPTION [0038] Described herein are systems and methods for collecting, storing and processing inspection data and for generating an inspection report. Referring to Fig. 1, one aspect of the present invention provides a computer implemented method 100 for generating an inspection report. The method includes the initial step 101 of providing a web-based interface for enabling a user to manage inspection data and request an inspection report based on specified input inspection request data. At step 103, in response to a request from a user of the interface, a software application is generated that is executable at a mobile device. The software application is configured for receiving, from an inspector using a mobile device who is to carry out an inspection, data indicative of inspection observations. Step 103 of generating the software application includes two primary sub-steps. At sub-step 105, a database of predefined inspection prompts is accessed thereby to identify a set of inspection prompts that are specific to the user's desired inspection. At sub-step 107 the application is configured to display the set of inspection prompts and provide functionality for receiving, from the inspector, respective 11 responses to those prompts. At step 109, the application is downloaded to a mobile device for use by an inspector. At step 111, the responses to the inspection prompts, input by the inspector input at the mobile device, are received. At step 113, the received responses are stored in the database. Finally, at step 115, the received responses may be processed to generate the inspection report. [0039] The method of Fig. 1 is configured to be performed on an internet enabled personal computer and/or a mobile device such as a tablet computer or Smartphone. However, as will be described below, in other embodiments the method is configured to be performed on other computing devices and in other configurations. General framework and system level overview [0040] Referring now to Fig. 2, there is illustrated a system 200 for managing inspection data and generating an inspection report according to one embodiment. System 200 includes a host server 202 for providing a web-based interface 204 that is hosted for access over the internet. Interface 204 is accessible to user terminals 206 through the internet and provides for enabling a user to request an inspection report based on specified input inspection request data. Examples of inspection request data will be described below. User terminals 206 may be any internet enabled computing device having capability to receive web content. Examples of terminals 206 include laptop computers 208, tablet computers 210, desktop or personal computers 212 and Smartphones 214. Interface 204 is configured to allow access by any number of users. [0041] Server 202 includes a processor 216 coupled to a memory module 218 and a communications interface 220, such as an internet connection, modem, Ethernet port, wireless network card, serial port, or the like. Interface 204 is configured for hosting interface 204 on the internet and selectively allowing access to users for accessing data from a database 222. [0042] A user accesses interface 204 through one of user terminals 206. In preferred embodiments web interface 204 includes a website having one or more navigable web pages. The term "website" should be read broadly to cover substantially any source of information accessible over the Internet or another communications network (such as WAN, LAN or WLAN) via a browser application running on a user terminal. The web browser application downloads code, such as HTML code, from the server. This code is executable through the web-browser on the user terminals 206 for providing a graphical and often interactive representation of the website on the user terminal. By way of the 12 web-browser application, a user of a terminal 206 is able to navigate between and throughout various web pages provided by the website, and access various functionalities that are provided. In one embodiment, interface 204 is realised as a web portal accessible to users through a username and password. [0043] In another embodiment, interface 204 is accessible on terminals 206 through a downloadable software application that communicates with server 202 through a web access portal or the like. [0044] User input to interface 204 is provided by means such as a keyboard, mouse, touchpad or touch screen. The user navigates through interface 204, inputs inspection request data and issues a request for an inspection. Server 202 then accesses database 222 to produce the specific inspection prompts as described below. In other embodiments, server 202 and database 222 form an integral server unit. As will be outlined below, a user can also use interface 204 to manage and process inspection data obtained from a number of inspections. [0045] Database 222 stores predefined inspection prompts and is accessible by server 202 through processor 216 and memory 218. The inspection prompts are questions or fields that are to be answered by an inspector during an inspection. Each prompt is tagged as belonging to one or more specific industries, job types or other parameters. Prompts may be indicative of industry standard questions specific to a particular industry and/or inspection job type or may be custom prompts. For example, an apartment condition inspection report includes a list of industry standard questions that must be answered to complete the report. Database 222 includes these standard questions, in addition to other possible questions, in the form of inspection prompts of an inspection report. [0046] The input inspection request data is indicative of one or more of a user industry, job type or customer. In some embodiments, additional types of request data are used. Server 202 is configured to access database 222 of predefined inspection prompts following the input of specified inspection request data by a user. The user is able to input their request at interface 204. In one embodiment, the request is input by the selection of one or more of a plurality of selectable options presented to the user of interface 204. Following the user request, processor 216 initiates a search of database 222, using the inspection request data as filter parameters, to identify a set of inspection prompts that are specific to the user's desired inspection. Retrieved inspection prompts are stored in memory 218 of server 202.

13 [0047] Server 202 uses the identified inspection prompts to generate a software application executable at a mobile device 224. Any number of different software applications may be generated for a particular user based on the inspection request data used at each request. Examples of mobile devices include Smartphones, Smartpads, tablet computers, laptop computers, Pod Touches and personal digital assistants (PDAs). Examples of capable Smartphones include Phones, Blackberries and Android-based Smartphones. In one embodiment, the application is configured as an Phone "App". In another embodiment, the application is configured as an Android based software application for an Android compatible Smartphone. [0048] The application is downloadable or installable onto mobile device 224. In one embodiment, the application is available for download by accessing a web address link on mobile device 224. In another embodiment, the application is available for download from an online platform such as the Android Market or Apple's iTunes Store. In a further embodiment, the application is transferred wirelessly to mobile device 224 by email, Bluetooth or Wi-Fi. [0049] Inspection request data includes data such as user-related industries, user related job-types and particular customer types for the requested inspection. For example, selecting a "property" type industry, "apartment condition inspection" job type and "owner request" as job type will produce a reporting application populated at least with inspection prompts indicative of the required industry standard questions to complete the condition inspection report. Other additional inspection prompts may be provided, such as prompts for additional comments. The inspection request data is able to be modified after generation of the application. If the change in request data results in different inspection prompts, then the application is similarly updated. In one embodiment, this update of the application occurs automatically. In another embodiment, a new version of the application is generated and is downloadable at mobile device 224. [0050] In one embodiment, inspection request data is in the form of predefined categories allocated to a specific user by a System Administrator. That is, the user does not individually input the request data each time an inspection application is requested. For example, a user may be allocated to a property type industry and one or more job types within this industry. In this embodiment, the user simply requests an inspection application and, based upon the inspection request data linked to that user, an application is generated with corresponding inspection prompts. The same reporting application can be used to inspect on different job types. In other embodiments, a user has capability to specify inspection request data as inputs to produce a specific reporting application.

14 [0051] The generated software application is configured for displaying the set of inspection prompts in the form of an inspection checklist to be completed by an inspector using the mobile device. The prompts are presented to the user through a predetermined navigable interface. A schematic example of a screen from a generated inspection application is shown in Fig. 3. A number of prompts 226, 228 and 230 are displayed, based on the input inspection request data used to generate the application. The application further provides functionality for receiving input from the inspector as respective responses to those prompts in the checklist. In the illustrated embodiment, the mobile device is a Smartphone with touch screen capability and the input is provided by the inspector touching the screen at specific input locations (e.g. 232, 234 and 236) corresponding to each prompt. Additional information such as an inspection title 238, location 240 and date 242 may be displayed on the reporting application and also on the inspection report subsequently generated. Additional comments may also be displayed on the application or resulting report. In one embodiment, an administrator user is able to set and vary the specific types of responses that are required by an inspector. For example, responses may be set to a simple yes/no or set to require detailed reporting comments. [0052] Reporting applications are generated with prompts requiring a range of different answer types. The input may be in the form of buttons (for example, 234 in Fig. 3) checkboxes, drop-down menus (for example, 232 in Fig. 3), scrolling menus and/or text input (for example, 236 in Fig. 3), or combinations thereof. Further, in some embodiments, capability is provided for uploading photographs taken from a camera integrated within the mobile device, for example, by executing button 234. [0053] Referring to Fig. 4 there is illustrated three screen shots of a reporting application generated on an Apple Phone, illustrating a yes/no/explanation type response. Frame a) illustrates the initial step of selecting yes or no. Frame b) illustrates the step of selecting either an explanation of the answer provided in the initial step or providing a manner of rectification. Frame c) illustrates the step of providing text input for setting out an explanation of the response entered. A similar text input is required if "rectification method" is selected in the second step. It will be appreciated that a variety of other types of responses are available. In one embodiment, an explanation and rectification method is required if the response to the inspection prompt is "No". In another embodiment, an explanation and/or rectification method is optional if the response to the inspection prompt is "No". In a further embodiment, an explanation and/or rectification method is optional regardless of the response to the inspection prompt.

15 [0054] In some embodiments, inspection prompts are set to be either mandatory or optional, wherein mandatory prompts require a response to complete the report or obtain the required information for storage and/or processing, and optional prompts do not require a response. An example of an optional field for an insurance surveyor is a field relating to cooking facilities of a business, wherein, if no cooking facilities exist for a particular business, that response field can be ignored. [0055] In one embodiment, questions are divided into categories and categories themselves can be made mandatory or optional. A mandatory category requires responses to all questions within that category, while an optional category does not require responses to the questions within it. Following from the previous example, an optional category for cooking facilities of a business can be created, wherein, if no cooking facilities exist for a particular business, that category and all included response fields can be ignored. [0056] Referring again to Fig. 2, following input of the responses to the prompts, the reporting application is configured to transmit the response data from mobile device 224 securely to sever 202. In one embodiment this data transfer occurs substantially simultaneously as the responses are input. In another embodiment, the input response data are transferred to server 202 upon execution of a command by the inspector. The response data transferred to server 202 are stored in one or both of memory 218 and database 222. [0057] If mobile device 224 is currently not connected to the internet, device 224 can store the input responses for later transmission when internet connectivity is available. [0058] In one embodiment, server 202 is linked to a "cloud"-based server network where data is able to be transferred and stored. Response data generated at mobile devices 224 are also able to be transferred or synced with the cloud server network for later transfer to server 202. [0059] After completion of all mandatory responses, the response data is collected, stored and processed by server 202. An inspection report may or may not then be generated from the processed response data. Prior to transmitting the response data from mobile device 224 to server 202, the reporting application performs a check of the input responses to ensure that all mandatory response fields are entered and that the entered responses are in the correct format. In one embodiment, the following three checks are applied to a completed inspection: 1. All Questions (other than optional questions) are answered.

16 2. At least one general photograph has been taken on the mobile device and linked to the inspection. 3. Where an inspection prompt requires that an "Explanation", "Solution" and/or "Question related-photograph" be entered, each of those requirements is complied with. [0060] If further information is required to complete an inspection, the application displays a message or notification on the screen of the mobile device to advise the inspector accordingly. [0061] In one embodiment, the report is generated by selecting a "generate report" option in interface 204. In another embodiment, the report is generated from the mobile device 224 by selecting a "generate report" option in the reporting application. The generated report is in a predefined generic or customer specific format with predefined text and lists all the inspection questions and corresponding responses. In embodiments including mandatory and optional inspection prompts, the report may include or omit questions where an optional response was not provided. In one embodiment, an inspection report is generated that only displays responses that are deemed to be "positive" responses. In some embodiments, a logo, trade mark, trade name, header, footer or other indicia indicative of the user is printed on the report. Reports may be generated such that they comply with any standards that are applicable in the relevant industry. [0062] In one embodiment, the generated inspection report is output as an electronic file, such as a PDF file. In one particular embodiment, the output electronic file is emailed to a designated email address corresponding to the user or a related customer of the user. In some embodiments, the user has the capability to modify the format and/or content of the generated report through interface 204. [0063] In some embodiments, regardless of whether an inspection report is generated, the response data is processed and stored by server 202. This data may be used to form part of a larger inspection report with further response data to come or transmitted directly to another party for processing. The stored response data is collated and is able to be accessed by users of interface 204 through user accounts as described below. [0064] It will be appreciated that, while illustrated separately in Fig. 2, user terminals 206 and mobile device 224 may be the same electronic device. That is, a user may access interface 204, download the generated reporting application and carry out input of response data on the one mobile device 224.

17 User accounts and subscriptions [0065] The framework described above provides capability for users of interface 204 to be allocated user accounts accessible, through interface 204, on terminals 206 or mobile devices 224. The user accounts are linked to a specific user and allow storage and access of user data that is stored in database 222, corresponding to that user. Once created, each user effectively sees their own personalised version of the interface, based on their personal settings and/or permission levels (described below). In preferred embodiments, the user pays a subscription fee for maintaining access to their account on server 202 and thereby retaining the ability to produce inspection reporting applications and reports. In one embodiment the subscription fee is a monthly fee. In another embodiment, the subscription fee payable by a user is determined by the number of reporting applications or number of inspection reports generated by a user. In a further embodiment, the subscription fee payable by a user is determined by the number of industries, job types, customers and/or report types that are associated with the user. For example, a user having an account linked to three industries will pay a higher subscription fee than a user having an account linked to only one industry. In some embodiments, a user will pay on a sliding scale for a batch of inspections each month. In another embodiment, the web interface and the reporting applications are used under licence to the user. In one embodiment, System Administrators assign users with user-specific sets of inspection prompts. [0066] In one embodiment, the user's access permission level is based on the subscription fee paid by the user. For example, a larger subscription fee grants a user with a higher level of permission, which gives the user the capability to modify or add/remove inspection prompts from a generated application, modify the user account details, and also provides a user with capability to modify the output format of the generated report. In some embodiments higher permission levels allow a variety of other functionality through interface 204, such as inspection scheduling described below, and other premium features. At the other end of the fee scale, a user paying a basic subscription fee may be given very little permission to customise the reporting application, user account details or the format of a generated report. In one low permission embodiment, the user account is set up by an administrator and the user has no capability to modify the account, reporting application or generated report. In addition to being low cost to the user, this option has the advantage of also not requiring substantial input from the user. Therefore, this option could be advantageous for a user who wishes to quickly and easily generate a basic industry-standard reporting application for use in preparing an inspection report.

18 [0067] The various features and options are available to users through navigable web pages, links, buttons, lists and check boxes. In one embodiment, users are able to see other options available on a more premium subscription as a unselectable option or the like. This provides users with the opportunity to see what they are missing with their current subscription level. [0068] In one embodiment, three types of client users can be created: 1. "Administrator users", that have permission to creating/allocating new jobs and inspections, creating new office/inspector users or subcontractor users, changing user types, generating inspection applications and modifying prompt and response (questions/answer) types. An example of an administrator user is a manager or designated person within a company who carries out or manages inspections. 2. "Office/Inspector users", such as employees or inspectors employed by a company who carries out or manages inspections. Office/inspector users have permission to: > Generate inspection applications based on predefined inspection prompts. > view and modify all web-interface functions, except inspection prompts (questions) that are able to be included on generated reports. > access web interface 204, for example using an email address as a user name, which; in the case of inspector staff, will be the same as the email address that they use for accessing the application; and in the case of office staff, will only be used to access the web application. > access the inspectors functionality (see below), but are only able to see (click on) their own details to modify and/or delete details. That is, an office/inspector user cannot create a new inspector, or modify an existing user other than themselves. 3. "Subcontractor users" that only have access to an inspection screen to modify the results of an inspection, and to create/issue inspection reports.

19 [0069] In addition to the above client users, there exist System Administrators who manage interface 204 and are separate to the clients themselves. System administrators are responsible for adding new client users, managing user accounts and changing user permission levels, amongst other tasks. [0070] A subcontractor user cannot view jobs, modify jobs, or enter new jobs. A subcontractor user can only view the results of his/her inspection and issue reports. A subcontractor user is typically an external inspector for whom access is to be limited. However, it is possible to use this type of user for internal employee inspectors also. An office/inspector user can create new jobs, view and modify jobs and issue reports and is therefore typically an employee who is provided with full access (excluding modifying questions). [0071] In this embodiment, initially creating a user profile for a client defines one or more associated administrator users and one or more inspector users, provided the appropriate subscription fee is paid. Further inspector users can be defined by the administrator user. Further administrator users may be set up for a specific user account by a System Administrator. This hierarchy allows a client to self-manage their various inspectors and inspections, and generate inspection reports through interface 204. Further, a common set of inspection prompts can be defined for an administrator, so that each office/inspector user and subcontractor user under that administrator user utilise the same inspection prompts for quality assurance of a business. [0072] Server 202 is also capable of storing statistics and histories of user activity in database 222. Storage of this data is used, amongst other reasons, for streamlining generation of subsequent reporting applications and establishing user usage for accounting and invoicing purposes. In some embodiments, the actual response data collected from inspection reports is also collated and stored. Example interface implementation [0073] An exemplary implementation of web interface 204 will now be described. It will be appreciated that interface 204 can be realised in a variety of different ways and the scope of the present invention should not be limited to the present example implementation. [0074] In this implementation, interface is realised as a website accessible through a web browser application on a computer, tablet, Smartphone or other electronic device. In overview, interface 204 is configured for two primary types of user parties: database 20 administrators and standard client type users (referred to simply as "users"). The web pages available and functionality provided differ depending on the particular party accessing interface 204. The interface as seen by users will be described first. The interface as seen by administrators will be described below. The illustrated example implementation is for a user with a higher level of access permission who has capability to modify a large amount of account and inspection request data. For a user with lower permission access, less flexibility to modify account information and inspection request data is available or no flexibility is available at all. [0075] Referring to Fig. 5 there is illustrated an example screen shot of a web page for entering and displaying user account information. At region 244 an email and password prompt are provided for allowing a user to login to the interface. Upon successful login, the remaining fields on this page are populated with user account information stored in the database. At region 246, user contact details are displayed in prompts allowing for modification of the details. A Google or other type of map display 248 is presented, which shows the location of the user's physical address. At region 250 the user's payment details are displayed, which is useful for subcontractor users. At region 252, the user's servicing details are displayed. Servicing details indicate the locations that inspections are carried out for the particular user. Comma separated entries may be entered to filter out inspections relating to multiple post codes or locations. [0076] Interface 204 of Fig. 2 allows a user to input job information relating to different inspection jobs and to save that information, in association with the user account, in database 222. Turning now to Fig. 6, there is illustrated an example screen shot of a web page for displaying and entering data indicative of inspection jobs. A button 254 is provided for allowing input of data for a new job. At region 256 a number of prompts are provided for searching for particular jobs that have been carried out or stored in the database. At region 258, a list of jobs resulting from the search is displayed. The displayed details include an allocated job number, the current job status, the associated owner for whom the inspection report is to be carried out, an allocated representative (such as a property manager), and address details. [0077] The desired job can be selected and the details can be modified by selecting a corresponding "modify" button (e.g. 259) or clicking the underlined job number. This navigates the user to the page shown in Figs 7a and 7b. Fig. 7a illustrates an upper portion of an example screen shot of a web page for displaying job details. At region 260, various prompts are provided for inputting and displaying information about the particular inspection job, including a physical address of the inspection. Once entered, the physical 21 address is displayed on a Google or other type map display 262. Referring to Fig. 7b, below map 262, region 264 is provided for inputting one or more inspection times. In this embodiment, up to three inspections can be established for each job. In another embodiment, up to 14 inspections can be established. In a further embodiment, an unlimited number of inspections can be established. [0078] In one embodiment, map 262 is configured to display the current inspection and other inspections scheduled for that day or other days. Map 262 is configured to display the location of each inspection and/ or a home base location. Map 262 can also display the current location of the scheduled inspector and the location of other inspectors through GPS tracking of a mobile device carried by the inspectors. In addition, map 262 can display details of other inspections that a specific inspector is scheduled to perform. At region 266, an option is provided for the user to send an acknowledgement email for the job to the customer. [0079] Referring still to Fig. 7b, a full inspection schedule 268 is displayed. The schedule includes tabs for selecting a day of the week to view and a scrollbar for scrolling through the time of each day. The functionality described in relation to Figs 7a and 7b provides users with enhanced flexibility to dynamically schedule, monitor and update inspections. Furthermore, integrating GPS location and date/time awareness into the data collection functionality of the interface provides the ability for users to: > prove that an inspection occurred at a specific place, date and time; > group inspection data across a range of locations into Management Reports (for example, Emergency Services personnel can provide real time data to Government Departments on locations impacted by a natural disaster); and > confirm that the inspector is carrying out an inspection at the correct property (i.e. a quality assurance tool). [0080] For users that employ multiple inspectors in the same or different geographical regions, interface 204 of Fig. 2 provides functionality to schedule inspectors to an inspection where that inspector: > works in that local region; and/or > works at the date and time required to carry out the inspection. [0081] In one embodiment, this inspector scheduling is provided by a calendar scheduling module within interface 204. Referring now to Fig. 8, an example calendar is 22 illustrated for a specific inspector. The different regions of the calendar illustrate the inspector's availability at those times/days. A user, or inspector with appropriate access, is able to modify the availability. Based on the availability, jobs can be allocated to appropriate inspectors for efficient carrying out of inspections. [0082] In one embodiment, the scheduling module allows each inspector to nominate a "base availability", where they can nominate available days of the week and/or timeslots within those days. This, for example, could account for inspectors that don't work weekends, are permanent part-time workers, and inspector lunch-time breaks, etc. Further functionality is provided to allow the user or each inspector to override the "base" availability on a day-by day basis, to account for matters such as annual leave, sickness, days off, etc. In addition, inspector "base" availability can be overridden on a timeslot basis, to account for one-off appointments (e.g. dentist appointment, unrelated meeting, etc). [0083] As mentioned above, depending upon permission rights, users can modify the predefined inspection prompts generated prior to producing the reporting application. This capability is provided through interface 204 of Fig. 2 after inputting user information but prior to the reporting application being generated. Referring now to Fig. 9, there is illustrated an example screen shot of a web page for displaying and modifying inspection question data. This web page provides, amongst other things, functionality to modify the text displayed on the report for that question, define a preferred answer type, allocate a job type and/or category, add text notes and add a diagram or photograph relevant to the question. The reporting application accessible on mobile device 224 can also be configured to upload and display text notes and/or photographs. [0084] Functionality of interface 204 as seen by administrator users will be described below with reference to Figs 10 to 13. Referring initially to Fig. 10, there is illustrated a screen shot of an example web page providing functionality to display, modify and add/remove question categories. At region 270, a prompt is provided for allowing a user to search for keywords within a selected industry. Once a search button 272 is selected, the search results are displayed in region 274. Each displayed result has options for modifying the question categories or deleting them. Button 276 is provided for adding a new question category. [0085] Administrator users are also able to create new users and modify the accounts of existing users. Referring to Fig. 11 there is illustrated a screen shot of a portion of a web page providing functionality to enter or modify a user's account details. At region 278 prompts are provided for inputting user information such as a physical address, a 23 company logo and a company or report footer. At region 280, accounting information is displayed. The current amount of money owed by that user for their subscription is displayed and prompts are provided for modifying the user's subscription and providing accounting notes. At region 282, various check boxes are provided for allocating specific job types to the user and defining a user report template. [0086] An administrator user is also able to modify the default inspection report content and layout provided for users. Turning to Figs 12 and 13 there are illustrated screen shots of example web pages for modifying a standard report style entitled "Default Routine Condition Report". In Fig. 12, text editors 284 and 286 are provided for allowing a report preamble and report summary to be inserted. In Fig. 13, another text editor 288 is provided for modifying the primary content of the report. The editors 284, 286 and 288 are capable of receiving and defining formatted text and formatting code such as HTML code. At region 290 additional options are provided for defining a report orientation, setting answer (response) types that appear in the inspection report and defining an email template for emailing the generated inspection report to a customer. [0087] More advanced reporting layouts, including for example, tables, images or graphics such as company logos, can optionally be added to the inspection report through HTML code. The overall report generating functionality allows user-specific inspection reports to be generated. Alternatively, System Administrators are able to set predefined report templates for specified customers so that those customers can only produce standard industry-wide inspection reports. By way of example, some customers may wish to produce reports in a government-prescribed format. In one embodiment, these non customisable standardised reports are available to the customer at a reduced subscription rate. [0088] In addition to modifying the layout of inspection reports, the actual content of the reports can also be modified. The interface allows a user to customise what inspection data, gathered from the responses to inspection prompts in the mobile application, will be displayed in the end report. Depending upon particular questions answered and to whom the report is to be sent, the user may wish to remove certain responses to inspection prompts. The interface provides capability to do this. Further, certain answer types may be removed from the end report such as responses to optional prompts left unanswered. [0089] Administrator users are able to set inspection support content for inspectors carrying out an inspection. Referring now to Fig. 14, there is illustrated a screen shot of an 24 example web page for providing visible inspection support content for inspectors. The interface allows the activation of support content visible to an inspector and/or visible on an inspection report subsequently produced from that inspection. The support information available to an inspector may be in the form of links to explanatory web pages, images, documents or audio files. Also shown in Fig. 14 is an example Phone screen displaying a support image of different fire extinguishers to assist an inspector in responding to an inspection prompt. [0090] The inspection support content is linked to one or more inspection prompts and, in one embodiment, the support content is accessed by selecting a help icon or assistance button. More than one support content items may be linked to one inspection prompt. System Administrators are able to set what, if any, support content is included in the inspection report. If System Administrators allow support content in the inspection report, administrator users are then able to select whether they want certain support content included in an inspection report. Calculation functionality [0091] As server 202 is configured to store usage of each user, the collected information can be used to automatically generate invoices, quotations or invoice entries for administrators to charge a user and for users to charge their customers. From the administrator's perspective, collection of data indicative of the number of reporting applications or end inspection reports generated by a user allows a user to be easily invoiced for their use of interface 204. From the user's perspective, enabling the web interface 204 to automatically produce an invoice when producing an inspection report will result in productivity savings to the user. Further, upon the request of a user or a new inspection, a quotation can be generated based on input inspection data. [0092] In some embodiments, the auto-invoicing of user customers is based on a table of values for reporting prompts. In one embodiment, each reporting prompt requiring a response is given a monetary weight or dollar value. For example, inspection of a bedroom may have a dollar value of $10 while inspection of housing support pylons may have a dollar value of $50 due to increased labour cost. In this embodiment, the amount to invoice calculated from the specific fields that are input by the inspector. In some cases, certain prompts may have a dollar value of $0. From the entries, the final invoice can be generated.

25 [0093] In other embodiments, a table of values is used to assist in calculating quotations. For example, inspection of carpet in an office building may have a value of $50/M 2 . In this embodiment, the amount to quote is calculated by the above field in combination with other fields input by an inspector. For example, if an inspector inputs that there is 25 m 2 the generated amount produced is $50/m 2 x25m 2 =$1,250/m 2 . [0094] In some embodiments, interface 204 and server 202 are configured to allow: > Users to pre-define/confirm which responses constitute invoicing/quotation fields; > Users to pre-define/select what monetary weight or dollar amount to invoice if certain responses are selected by the user; > Users to determine what dollar amount to apply for various travel distances to/from an inspection site; > Users to select a manual over-ride option where an inspector chooses a value that is not included in the table; > Users and/or inspectors to select a manual override on a per-job or per customer basis to issue a manual invoice. [0095] With invoicing and accounting capability, the system can allow a user to maintain an account without paying a subscription fee. In this embodiment, payment for use of interface 204 occurs in the manner of a commission from revenue based on inspections carried out using the generated reporting applications. Auto-repair functionality [0096] Some inspection types recognise the need for repairs/maintenance of a building/asset to be carried out. In one embodiment, an inspection report is generated such that it lists the repairs/maintenance required and can be used as a source document to request a repair quotation from a builder or repairer. In this embodiment, interface 204 is enabled to allow the inspection report to automatically issue to one or more builders to request quotations. In another embodiment, interface 204 is configured to automatically issue a second report, based on a variation of the inspection report, to one or more builders/repairers. [0097] In some embodiments, interface 204 is further enabled to allow: 26 > The selected one or more builders to upload a quotation through a web link such that the quotation auto-populates the database; > Automatically notify the inspector (or their customer) of the quote; > The inspector or customer to accept the quote by uploading a work order/acceptance through a web link, and to auto-notify the builder to commence work; > The builder to upload an invoice through a web link, and notify the inspector or customer; and > Copies of all emails (which integrate the web link) to be included in the email log for each job/inspection. Additional functionality / alternative embodiments [0098] In some embodiments, interface 204 provides capability for integrating dynamic user signatures. In these embodiments, a user or inspector can sign a name with his/her finger, or a stylus, onto the screen of portable device 224 (such as a Smartphone or tablet) which is then saved and synced to the database. In further embodiments, this functionality is extended to allow other parties (e.g. customers of users) to also sign their name. This can be helpful in obtaining authorisation for completing inspection reports, invoices and work orders. [0099] In some embodiments, interface 204 and/or generated reporting applications are configured for enabling input in the form of diagrams, with the use of a finger/stylus, built-in tools like line/curve/circle/square drawing, text overlays, text, arrows, and diagrams to be drawn over photographs taken within the app. [00100] Most Smartphones, tablets and PDAs have the ability to capture video and/or audio. In some embodiments, interface 204 is configured for enabling the reporting application to receive captured video footage and/or audio data relating to particular reporting prompts, or relating to the inspection generally. [00101] In some embodiments, the generated reporting applications are configured to record the time taken to carry out an inspection, and transmit that time to database 222 for each job. This functionality allows users to use that data to invoice customers and as a productivity/training tool. [00102] In some embodiments, interface 204 is configured to produce management report templates, wherein a user is able to: 27 > Determine what data fields populate a table; > What calculations occur within that table; and/or > How that data is presented (e.g. raw data in table, graph, Google map, or a combination thereof). [00103] In some embodiments, interface 204 is configured to allow a user or administrator to add more inspection prompts to database 222. In some embodiments, server 202 scans databases of industry standards and updates database 222 with inspection prompts to reflect changes in industry standards. [00104] In some embodiments, interface 204 is accessible via the same mobile device 224 used to carry out the inspection. In one embodiment, a software application for accessing and navigating interface 204 is downloadable to mobile device 224 or other devices. [00105] At a commercial level, use of the interface is able to be licensed to various users. When licensing the interface, the licensor is able to set a company logo that is present within web pages of the interface. The licensee may also be able to set their company logo within certain web pages of the interface. For example, the licensor's company logo is displayed in the top left hand corner of web pages relating to the interface and the licensee's company logo is displayed in the top right hand corner of web pages relating to the interface. In some embodiments, the licensee is able to replace the licensor's logo with their own, potentially at a higher licensing fee. Conclusions [00106] It will be appreciated that the disclosure above provides various significant systems and methods for collecting, storing and processing inspection data and for producing inspection reports. [00107] The above-described systems and methods provide for easily and efficiently generating a reporting application for allowing an inspector to carry out an inspection. The input inspection data is collected and stored in a database for processing. Web interface 204 allows for managing and accessing the inspection data and for subsequently producing an inspection report based upon one or more inspections. Web-interface 204 provides a comprehensive inspection management system, allowing users to easily generate reporting applications, carry out inspections, produce inspection reports, schedule inspections, invoice a customer and facilitate repairs through work orders. The 28 system removes the need for a middle level commercial IT developer/consultant, which reduces overall cost to the customer. [00108] The data stored in database 222 is accessed by users through interface 204. The users, depending upon their permission level, select specific inspection data and rules for carrying out the inspection. These data and rules are synced with a mobile application accessible on mobile device 224. The application displays the data to an inspector who carries out an inspection in accordance with the specified rules. Modification of the inspection data or rules at the interface can be synced directly with the mobile application, providing simply flexibility for carrying out customised inspections. Further, the application can be configured to store inspection data from a number of different inspections, allowing an inspector to carry out different inspections using the same application. [00109] The systems and methods described above provide various advantageous functions, including: Capability to provide customer relationship management for an unlimited number of users. Capability for creating an unlimited number and type of mobile data collection reporting applications. Capability for a System Administrator or user to modify/add/delete any number of inspection prompts and response types. Capability for a System Administrator or user to create any number of users or sub-users and install one or more reporting applications for each user. [00110] Efficient management of data in the system is achieved by utilizing the fact that a number of similar data are collected for each industry, specifically relating to industry standard requirements. An example is Real Estate Property Managers, who are required by legislation to collect certain minimum information about the condition of a property, and government department checklists exist. Another example is pre-purchase building inspectors who must collect data and prepare reports in accordance with Australian or other national standards. The capability to generate a detailed reporting application based on a user's industry, job type and customer type reduces the overall input required from the user. [00111] The system of the present invention allows the creation of "industries" to which a standard set of checklist questions can be attached. It also provides the ability for a 29 number of customers from that same industry to be created, to which the same set of standard checklist questions is automatically attached. The result is that users can create specific industries, for example, a "Default Property Manager Industry", or a "Default Pre purchase Inspection Industry", etc. There is no limit to the number of industries that can be created, and no limit to the number of users that are associated with that industry. The web interface allows non-programming-trained System Administrators to create Smartphone or tablet apps and web applications for customers in a range of industries. [00112] The data collected by the customer is stored in a secure database for the customer for as long as they are prepared to continue to pay the subscription. This reduces the customer input required on subsequent uses as their information is already stored on the system. [00113] The user accounts allow flexibility to a user and provide control of information to an administrator of the system. Paying a higher subscription fee provides a user with increased permission and more flexibility in generating a customised reporting application and subsequent inspection report. Paying a lower subscription fee provides the user with less permission and therefore a more generic reporting applications and reports. In either case, a user can simply and easily generate an industry standard inspection report. [00114] The web interface 204 can be thought of as a web portal that controls the bidirectional flow of information between users and server 200. System administrators control the amount of information available to users through the setting of permission levels in a user account. [00115] While the invention has been described with particular reference to inspections, it will be appreciated that the invention is relevant in other contexts. For example, in other embodiments, system 200 is configured to collect, store and process information indicative of testing, personal performance assessment or recruitment and interviewing. Interpretation [00116] Unless specifically stated otherwise, as apparent from the following discussions, it is appreciated that throughout the specification discussions utilizing terms such as "processing," "computing," "calculating," "determining", analysing" or the like, refer to the action and/or processes of a computer or computing system, or similar electronic computing device, that manipulate and/or transform data represented as physical, such as electronic, quantities into other data similarly represented as physical quantities.

30 [00117] In a similar manner, the term "processor" may refer to any device or portion of a device that processes electronic data, e.g., from registers and/or memory to transform that electronic data into other electronic data that, e.g., may be stored in registers and/or memory. A "computer" or a "computing machine" or a "computing platform" may include one or more processors. [00118] The methodologies described herein are, in one embodiment, performable by one or more processors that accept computer-readable (also called machine-readable) code containing a set of instructions that when executed by one or more of the processors carry out at least one of the methods described herein. Any processor capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken are included. Thus, one example is a typical processing system that includes one or more processors. Each processor may include one or more of a CPU, a graphics processing unit, and a programmable DSP unit. The processing system further may include a memory subsystem including main RAM and/or a static RAM, and/or ROM. A bus subsystem may be included for communicating between the components. The processing system further may be a distributed processing system with processors coupled by a network. If the processing system requires a display, such a display may be included, e.g., a liquid crystal display (LCD) or a cathode ray tube (CRT) display. If manual data entry is required, the processing system also includes an input device such as one or more of an alphanumeric input unit such as a keyboard, a pointing control device such as a mouse, and so forth. The term memory unit as used herein, if clear from the context and unless explicitly stated otherwise, also encompasses a storage system such as a disk drive unit. The processing system in some configurations may include a sound output device, and a network interface device. The memory subsystem thus includes a computer-readable carrier medium that carries computer-readable code (e.g., software) including a set of instructions to cause performing, when executed by one or more processors, one of more of the methods described herein. Note that when the method includes several elements, e.g., several steps, no ordering of such elements is implied, unless specifically stated. The software may reside in the hard disk, or may also reside, completely or at least partially, within the RAM and/or within the processor during execution thereof by the computer system. Thus, the memory and the processor also constitute computer-readable carrier medium carrying computer-readable code. [00119] Furthermore, a computer-readable carrier medium may form, or be included in a computer program product.

31 [00120] In alternative embodiments, the one or more processors operate as a standalone device or may be connected, e.g., networked to other processor(s), in a networked deployment, the one or more processors may operate in the capacity of a server or a user machine in server-user network environment, or as a peer machine in a peer-to-peer or distributed network environment. The one or more processors may form a personal computer (PC), a tablet PC, a set-top box (STB), a Personal Digital Assistant (PDA), a cellular telephone, a web appliance, a network router, switch or bridge, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine. [00121] Note that while diagrams only show a single processor and a single memory that carries the computer-readable code, those in the art will understand that many of the components described above are included, but not explicitly shown or described in order not to obscure the inventive aspect. For example, while only a single machine is illustrated, the term "machine" shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein. [00122] Thus, one embodiment of each of the methods described herein is in the form of a computer-readable carrier medium carrying a set of instructions, e.g., a computer program that is for execution on one or more processors, e.g., one or more processors that are part of web server arrangement. Thus, as will be appreciated by those skilled in the art, embodiments of the present invention may be embodied as a method, an apparatus such as a special purpose apparatus, an apparatus such as a data processing system, or a computer-readable carrier medium, e.g., a computer program product. The computer-readable carrier medium carries computer readable code including a set of instructions that when executed on one or more processors cause the processor or processors to implement a method. Accordingly, aspects of the present invention may take the form of a method, an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of carrier medium (e.g., a computer program product on a computer-readable storage medium) carrying computer-readable program code embodied in the medium. [00123] The software may further be transmitted or received over a network via a network interface device. While the carrier medium is shown in an exemplary embodiment to be a single medium, the term "carrier medium" should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated 32 caches and servers) that store the one or more sets of instructions. The term "carrier medium" shall also be taken to include any medium that is capable of storing, encoding or carrying a set of instructions for execution by one or more of the processors and that cause the one or more processors to perform any one or more of the methodologies of the present invention. A carrier medium may take many forms, including but not limited to, non-volatile media, volatile media, and transmission media. Non-volatile media includes, for example, optical, magnetic disks, and magneto-optical disks. Volatile media includes dynamic memory, such as main memory. Transmission media includes coaxial cables, copper wire and fibre optics, including the wires that comprise a bus subsystem. Transmission media also may also take the form of acoustic or light waves, such as those generated during radio wave and infrared data communications. For example, the term "carrier medium" shall accordingly be taken to included, but not be limited to, solid-state memories, a computer product embodied in optical and magnetic media; a medium bearing a propagated signal detectable by at least one processor of one or more processors and representing a set of instructions that, when executed, implement a method; and a transmission medium in a network bearing a propagated signal detectable by at least one processor of the one or more processors and representing the set of instructions. [00124] It will be understood that the steps of methods discussed are performed in one embodiment by an appropriate processor (or processors) of a processing (i.e., computer) system executing instructions (computer-readable code) stored in storage. It will also be understood that the invention is not limited to any particular implementation or programming technique and that the invention may be implemented using any appropriate techniques for implementing the functionality described herein. The invention is not limited to any particular programming language or operating system. [00125] It should be appreciated that in the above description of exemplary embodiments of the invention, various features of the invention are sometimes grouped together in a single embodiment, FIG., or description thereof for the purpose of streamlining the disclosure and aiding in the understanding of one or more of the various inventive aspects. This method of disclosure, however, is not to be interpreted as reflecting an intention that the claimed invention requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the Detailed Description are hereby expressly incorporated into this Detailed Description, with each claim standing on its own as a separate embodiment of this invention.

33 [00126] Furthermore, while some embodiments described herein include some but not other features included in other embodiments, combinations of features of different embodiments are meant to be within the scope of the invention, and form different embodiments, as would be understood by those skilled in the art. For example, in the following claims, any of the claimed embodiments can be used in any combination. [00127] Furthermore, some of the embodiments are described herein as a method or combination of elements of a method that can be implemented by a processor of a computer system or by other means of carrying out the function. Thus, a processor with the necessary instructions for carrying out such a method or element of a method forms a means for carrying out the method or element of a method. Furthermore, an element described herein of an apparatus embodiment is an example of a means for carrying out the function performed by the element for the purpose of carrying out the invention. [00128] In the description provided herein, numerous specific details are set forth. However, it is understood that embodiments of the invention may be practiced without these specific details. In other instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure an understanding of this description. [00129] Similarly, it is to be noticed that the term coupled, when used in the claims, should not be interpreted as being limited to direct connections only. The terms "coupled" and "connected," along with their derivatives, may be used. It should be understood that these terms are not intended as synonyms for each other. Thus, the scope of the expression a device A coupled to a device B should not be limited to devices or systems wherein an output of device A is directly connected to an input of device B. It means that there exists a path between an output of A and an input of B which may be a path including other devices or means. "Coupled" may mean that two or more elements are either in direct physical or electrical contact, or that two or more elements are not in direct contact with each other but yet still co-operate or interact with each other. [00130] Thus, while there has been described what are believed to be the preferred embodiments of the invention, those skilled in the art will recognize that other and further modifications may be made thereto without departing from the spirit of the invention, and it is intended to claim all such changes and modifications as falling within the scope of the invention. For example, functionality may be added or deleted from the block diagrams and operations may be interchanged among functional blocks. Steps may be added or deleted to methods described within the scope of the present invention.

Claims (20)

1. A computer implemented method for generating an inspection report, the method including the steps of: providing a web-based interface for enabling a user to request an inspection report based on specified input inspection request data that is specific to a type of inspection to be carried out; in response to the request, automatically generating a downloadable customised software application executable at a mobile device, the software application being customised based on the inspection request data and being configured for receiving, from an inspector, data indicative of inspection observations, wherein generating the software application includes: accessing a database of predefined inspection prompts thereby to identify a set of inspection prompts based on the inspection request data specified; configuring the application to render a visual interface on a display of the mobile device to display the set of inspection prompts and provide input functionality for receiving, from the inspector, respective responses to those prompts; allowing download of the customised application to the mobile device; receiving, based on inspector input at the mobile device that executes the application, responses to the inspection prompts; processing the received responses thereby to generate the inspection report.

2. A computer implemented method according to claim 1 wherein the inspection request data includes data indicative of one or more user industries, job types or customers and wherein the application is populated with one or more predefined inspection prompts relating to an industry, a job type or a customer.

3. A computer implemented method according to claim 1 or claim 2 wherein the inspection request data is specified by a user of the interface through the selection of one or more of a plurality of selectable options. 35

4. A computer implemented method according to claim 3 wherein a user is able to change the options at the interface after generation of the software application, and, upon updating the options, the software application is updated.

5. A computer implemented method according to any one of the preceding claims including the step of storing the received responses in the database.

6. A computer implemented method according to any one of the preceding claims wherein the user is linked to a user account, wherein user data corresponding to that user is stored in the database under this user account and the interface is presented to the user in a form based on the data corresponding to that user.

7. A computer implemented method according to claim 6 further including the step of selectively controlling the permission of the user to modify or add/remove inspection prompts on the user account type, or modify how a response to a prompt is provided at the mobile device.

8. A computer implemented method according to any one of the preceding claims wherein the generated inspection report is output as an electronic file and is emailed to a designated email address corresponding to the user or a related customer of the user.

9. A computer implemented method according to any one of the preceding claims wherein inspection prompts are set to be either mandatory or optional.

10. A computer implemented method according to any one of the preceding claims wherein the application is configured as third party software for a mobile device having touch screen input capability.

11. A computer implemented method according to any one of the preceding claims wherein the inspection report generated is user specific.

12. A computer implemented method according to any one of the preceding claims wherein the inspection report generated includes only a predefined subset of the set of inspection prompts and corresponding responses.

13. A computer implemented method according to any one of the preceding claims wherein one or more of the inspection prompts are associated with support images for assisting an inspector in providing a response. 36

14. A computer system configured to perform a method according to any one of the preceding claims.

15. A system for generating an inspection report, the system including: a database for storing predefined inspection prompts; a server for hosting a web-based interface renderable on one or more computer processors for enabling a user to input a request for an inspection report, the request including the input of specified input inspection request data that is specific to a type of inspection to be carried out, the interface being configured to; access the database of predefined inspection prompts thereby to identify a set of inspection prompts based on the input inspection request data; in response to the request, automatically generate a downloadable customised software application executable at a mobile device and being customised based on the inspection request data, the software application, when executed, rendering a visual interface on a display of the mobile device to display the set of inspection prompts and provide input functionality for receiving, from an inspector, respective responses to those prompts; and processing the received responses thereby to generate the inspection report.

16. A computer implemented method of generating a reporting application, the method including the steps of: providing a web-based interface for enabling a user to request a downloadable customised software reporting application that is customised based on specified input application data and that is specific to a type of reporting to be carried out; receiving input application data from the user; in response to the request from the user, accessing a database of predefined application prompts thereby to identify a set of prompts that are specific to the user's desired application; 37 automatically generating the customised reporting application executable at a mobile device, and allowing download of the customised reporting application to a mobile device; wherein the reporting application is configured for: rendering a visual interface on a display of the mobile device to display the set of application prompts; and providing input functionality for receiving, from a user of the mobile device, respective responses to those prompts.

17. A computer implemented method for collecting, storing and processing inspection data, the method including the steps of: providing a web-based interface for enabling a user to access inspection data stored in a database and to request inspection data from an inspection performed by an inspector on a mobile device; in response to the request from a user, automatically generating and providing a downloadable customised software application executable at the mobile device, the software application being customised based on the inspection request data and being configured for rendering a visual interface on a display of the mobile device and receiving, from an inspector, data indicative of inspection observations, wherein the software application includes: a set of inspection prompts displayed on the rendered visual interface that are specific to the user's desired inspection, including a type of inspection to be carried out; functionality for receiving, from the inspector, respective responses to those prompts; allowing download of the customised application to the mobile device; receiving, based on inspector input at the mobile device that executes the customised application, responses to the inspection prompts; 38 storing the received responses in a database as inspection data accessible to a user through the web-based interface.

18. A computer implemented method for collecting, storing and processing inspection data according to claim 18 wherein the web-based interface is configured to selectively process inspection data to produce one or more inspection reports based on user information.

19. A computer implemented method for collecting, storing and processing inspection data according to claim 18 wherein the web-based interface provides functionality for allowing a user to modify the content and/or template format of an inspection report and or the software application.

20. A computer implemented method for collecting, storing and processing inspection data according to claim 18 or claim 19 wherein the received responses to the inspection prompts are transmitted to the database upon completion of the inspection.