A system

Abstract

A system (10) for determining report output data associated with a defined report type of a plurality of report types. The system (10) comprises a database (26) including a plurality of database table

Description

[0001] A SYSTEM

[0002] Field of the Invention

[0003] The present invention relates to a system that facilitates creation of a defined format report, for example for environmental, society and governance (ESG) accounting purposes.

[0004] Background of the Invention

[0005] Corporate accounting often requires an organisation to provide defined information in a suitable format report. For example, ESG accounting requires an organization to report on non-financial impacts associated with and value developed by the organisation.

[0006] ESG accounting data, and other similar non-financial data, increasingly requires the reporting of objectively measured scientific data regarding the status of, and impacts or improvements to, the environment or social wellbeing.

[0007] To support reported claims, objectively measured scientific data sets must be stored in and accessed from conceptually clear and logically consistent domains which are comprehensive in requiring alteration to accommodate the diversity of ESG reporting requirements.

[0008] However, corporate accounting systems at present do not incorporate underlying data architectures that support these requirements for scientific data.

[0009] Moreover, in the absence of a consistent and recognised or universal data architecture for accounting for scientific data, exchanging and auditing such data in corporate reports is complex, inefficient, and lacks transparency. of the Invention

[0010] In accordance with an aspect of the present invention, there is provided a system for determining report output data associated with a defined report type of a plurality of report types. Each report type may incorporate defined scientific data. The system may comprise a database. The database may include a plurality of database tables. The database tables may include a plurality of templates. The database tables may include a calculations dataset. The calculations dataset may comprise a plurality of calculation elements. The templates may comprise a plurality of calculation templates, each calculation template being associated with at least one of the calculation elements. The templates may comprise a plurality of information gathering templates, each information gathering template including fields for receiving information relevant to creation of a respective defined report type. The templates may comprise a plurality of report generation templates. One or more report generation template may be associated with one or more calculation template and one or more information gathering template. Each report type may be associated with a defined set of the report generation templates. The system may be arranged to receive information indicative of the desired report type. The system may be arranged to select a set of report generation templates based on the desired report type. The system may be arranged to select at least one information gathering template based on the selected set of report generation templates. The system may be arranged to receive information relevant to creation of the report. The information may be associated with the selected at least one information gathering template. The system may be arranged to determine report output data using at least some of the information relevant to creation of the report and the at least one calculation element that is associated with the calculation template that is associated with one or more of the report generation templates of the selected set of report generation templates.

[0011] In an embodiment, one or more of the calculation elements comprises a plurality of calculation parameters. In an embodiment, the database tables includes a calculation factors dataset comprising a plurality of values of one or more of the calculation parameters.

[0012] In an embodiment, the database tables comprise a qualitative input dataset comprising a plurality of qualitative input elements.

[0013] In an embodiment, one or more of the information gathering templates is associated with one or more qualitative input element.

[0014] In an embodiment, the system further comprises a user interface arranged to facilitate communications between a user and the system. In an embodiment, the user interface is arranged to enable the user to provide information indicative of the desired report type.

[0015] In an embodiment, the user interface is arranged to receive an input indicative of a report type from the user, and to make an information gathering template associated with the selected report type available to the user, for example by downloading the information gathering template to the user.

[0016] In an embodiment, the information relevant to creation of the report comprises user-provided information that is provided using the user interface. In an embodiment, the system is arranged to validate the user-provided information and to communicate a defect if the user-provided information fails validation.

[0017] In an embodiment, the database tables include at least one input data dataset arranged to store the user-provided information.

[0018] In an embodiment, the database tables include at least one output data dataset arranged to store data derived from the user-provided information.

[0019] In an embodiment, derived data is calculated from the user-provided information using at least one calculation.

[0020] In an embodiment, the system stores a plurality of data maps, each data map indicative of mapping of data to or from the database.

[0021] In an embodiment, the system comprises a federated data network.

[0022] In an embodiment, the database is a repurposed generic database.

[0023] In an embodiment, the database is repurposed by conceptually extending the definitions of particular generic table entities.

[0024] In an embodiment, the generic database may be based upon an open-source standard data architecture for scientific observations.

[0025] In an embodiment, the generic database is Observations Data Model 2 (ODM2).

[0026] In accordance with another aspect of the present invention, there is provided an accounting system for producing a report of defined report type from a plurality of report types, each report type incorporating defined scientific data, the system comprising: a user interface arranged to facilitate communications between a user and the system; and a database including a plurality of database tables; the database tables including a plurality of templates, each report type associated with at least one information gathering template including fields for receiving information relevant to creation of a defined report type, and each report type associated with a defined set of report generation templates; the user interface arranged to enable the user to provide information indicative of a desired report type; and the system arranged to: select at least one information gathering template based on the report type and to select a set of report generation templates based on the report type, use the selected at least one information gathering template to gather information relevant to creation of the report; and use the selected set of report generation templates to create the report using the gathered information.

[0027] In an embodiment, the user interface is arranged to receive data indicative of a report type from the user, and in response to make an information gathering template associated with the selected report type available to the user, for example by downloading the information gathering template to the user.

[0028] In an embodiment, the system is arranged to validate the information provided by the user and to communicate a defect if provided information fails validation.

[0029] In an embodiment, the plurality of templates include a plurality of calculation templates, each report type associated with at least one calculation template and each calculation template indicative of a calculation to be carried out on the received information.

[0030] In an embodiment, the database tables include at least one input data dataset arranged to store the received information.

[0031] In an embodiment, the database tables include at least one output data dataset arranged to store data derived from the received information.

[0032] In an embodiment, derived data is calculated from the information provided by the user using at least one calculation.

[0033] In an embodiment, the system stores a plurality of data maps, each data map indicative of mapping of data to or from the database.

[0034] In an embodiment, the information accepted from the user is as specified by a registered reporting guideline and accounting standards for the selected report type, such as the Greenhouse Gas Protocol used for one component of an Environmental Society and Governance (ESG) report.

[0035] In an embodiment, the database is a repurposed generic database. The generic database may be based upon an open-source standard data architecture for scientific observations. The generic database may be Observations Data Model 2 (ODM2).

[0036] In an embodiment, the generic database is repurposed by conceptually extending the definitions of particular generic table entities.

[0037] In an embodiment, a physical location table is extended to include a generic hypothetical location or a sample considered as the primary source of information about a location.

[0038] In an embodiment, a measurement action table is extended to include the action of producing a report, or of creating a generic template for a hypothetical collection of data and / or enumeration of an environmental or societal impact at a hypothetical location of a particular type.

[0039] In an embodiment, a measured result table is extended to include results derived from a calculation and / or standard factors extracted from a published document.

[0040] In an embodiment, a dataset table cataloguing a set of scientific measurements is extended to include sets of inputs, outputs and factors associated with a particular calculation algorithm or statistical aggregation in a report or the entirety of a report.

[0041] In an embodiment, a taxonomy table of biological or chemical species is extended to include any classification hierarchy such as the structure of a data collection form, factors used in calculations, a report structure, or gazetted regulations.

[0042] In an embodiment, a citation table of a scientific report is extended to include a source document for a calculation, a section of a standard report, a reporting guideline, a gazetted regulation or legislation, or a standard work procedure.

[0043] In an embodiment, an annotation table of user comment is extended to include a reference to a document (such as an invoice) considered as a primary source of information about a location.

[0044] Conceptually extending the entity definition of generic tables allows an existing database such as ODM2 to perform complex and interrelated functions which would typically require the development of multiple additional tables and inter-relationships that would greatly complicate extraction of data for reporting and preservation of the inter-relationships between scientific measurements, calculations, and reporting standards.

[0045] Using a generic database such as ODM2 enables transparent documentation of underlying data for audit purposes to occur, and importantly interoperability with other scientific data collection systems. Brief of the

[0046] The present invention will now be described, by way of example only, with reference to the accompanying drawings, in which:

[0047] Figure 1 is a schematic block diagram of a system in accordance with an embodiment of the present invention;

[0048] Figure 2 is a schematic block diagram of functional components of the system shown in Figure 1 ;

[0049] Figure 3 is a flow diagram illustrating a method of creating a report using the system shown in Figures 1 and 2;

[0050] Figures 4 and 5 show a representation of a report definition page displayed to a user by the system during use;

[0051] Figure 6 shows a representation of a file transfer page displayed to a user by the system during use;

[0052] Figures 7 to 15 show representations of tabs of an information gathering template provided to a user for completion by the system during use;

[0053] Figures 16 to 23 show example report generation examples;

[0054] Figures 24 to 30 show representations of tabs of a report produced by the system using the information provided in the information gathering template; and

[0055] Figure 31 is a schematic block diagram of a system in which a number of database systems form part of a federated data network in accordance with an embodiment of the present invention. of an Embodiment of the Invention

[0056] The present system facilitates capture, management, derivation, and exchange of non- financial accounting information, for example corporate information such as ESG related information. In the present example, this is achieved using an existing open architecture database framework - Observations Data Model 2 (ODM2), a framework for managing scientific data - which is repurposed to provide organisational reporting capability by incorporating templates in the database that can be used to provide structure for information gathering, data calculation, and report generation.

[0057] Referring to Figure 1 of the drawings, an example system 10 according to an embodiment of the present invention is shown. The system 10 may be referred to as an accounting system 10. The system 10 is configured to produce report output data. Producing the report output data may comprise determining the report output data. The report output data is associated with a defined report type. In particular, the report output data is associated with a defined report type of a plurality of report types. Each report type incorporates scientific data.

[0058] The system 10 includes a database system 12. The database system 12 may be referred to as a computer system 12. The database system 12 may be in the form of a computing device. The database system 12 may be referred to as an accounting component 12. The database system 12 may be said to comprise an accounting component 12. The database system 12 may comprise a computer system. The database system 12 may comprise a server. The database system 12 may be in the form of a federated data network of computing devices. The database system 12 may comprise a plurality of networked computing devices.

[0059] The database system 12 is accessible online by a user computing device 14 that for example may include a personal computer, laptop computer, tablet computer or smartphone, in this example through a wide real network such as the Internet 16. The user computing device 14 may be in the form of, or comprise, a user interface through which the user can interact with the system 10. The user interface device 14 is arranged to facilitate communications between the user and the database system 12. As described herein, the user interface device 14 is arranged to enable the user to provide information indicative of the desired report type to the database system 12.

[0060] Figure 1 also shows a report receiving computing device 18. The report receiving computing device 18 is configured to be in communication with the database system 12 and / or the user computing device 14. For example, the report receiving computing device may receive a report generated by the system 10, for example through a communications network 16. The communications network 16 may be in the form of the Internet 16.

[0061] In this example, the database system 12 includes a web server 20. The web server 20 is arranged to enable a user to access the database system 12 through the Internet 16 and interact with the database system 12 in order to instigate a new report and provide the database system 12 with information required for generation of a report using web pages.

[0062] The database system 12 also includes a report management component 22. The report management component 22 manages interactions with the user and manages functionality of the system 10, in this example carried out by functional components 25 implemented by a database management system 24.

[0063] The database system 12 also includes a database 26. The database 26 stores information received from a user to be used for generation of a report. The database 26 includes a plurality of templates. The templates are stored in the database 26. The templates are usable to generate the desired report based on the received information. The database 26 provides the report in the desired format.

[0064] In this example, the database 26 is an Observations Data Model 2 (ODM2) database that has been repurposed for organisational reporting use, in the present example for use in creation of an ESG type report.

[0065] In the present example, the database 26 includes a plurality of database tables. The database tables are stored in the database 26. The database tables include one or more templates. In particular, the database tables include a plurality of templates. One or more of the database tables is associated with a generic ODM2 database structure that has been repurposed to store templates usable to generate desired report types by conceptually extending the definitions of the generic table entities. The database tables may comprise at least one of a physical location table, measurement action table, a measured result table, a dataset table, a taxonomy table, an annotation table and a citation table.

[0066] In an example, a physical location table is extended to include a generic hypothetical location considered as the primary source of information about a location; a measurement action table is extended to include the action of producing a report, or of creating a generic template for a hypothetical collection of data and / or enumeration of an environmental or societal impact at a hypothetical location of a particular type; a measured result table is extended to include results derived from a calculation and / or standard factors extracted from a published document; a dataset table cataloguing a set of scientific measurements is extended to include sets of inputs, outputs and factors associated with a particular calculation algorithm or statistical aggregation in a report or the entirety of a report; a taxonomy table of biological or chemical species is extended to include any classification hierarchy such as the structure of a data collection form, factors used in calculations, a report structure, or gazetted regulations; an annotation table of a user comment is extended to include a reference to a document (such as an invoice) considered as a primary source of information about a location; and a citation table of a scientific report is extended to include a source document for a calculation, a section of a standard report, a reporting guideline, a gazetted regulation or legislation, or a standard work procedure.

[0067] Use of the ODM2 framework may involve the use of a simulations entity. The simulations entity represents, or is associated with computational experiments or modelling activities (e.g. conducted to simulate environmental processes or phenomena). The simulations generate data that can be stored and managed within an ODM2 framework. The simulations entity can be used to catalogue a modelled simulation of a specified set of input data. In the present disclosure, the simulations entity is used to track changes to a particular Reporting Programme over time, specifying which Calculations Methodologies or Calculation Algorithms or Datasets are current with a start and end date. In the present system, the InputDataset of the simulations entity is conceptually extended to a Calculation Template dataset of Input Data, Factors and Output Results, or a Reporting Templates dataset.

[0068] The system 10 includes at least one information gathering template 32. In the illustrated embodiment, the system 10 includes a plurality of information gathering templates 32. The database 26 includes the information gathering templates 32. The information gathering templates 32 are stored in the database 26. The plurality of database tables comprises the information gathering templates 32. That is, the information gathering templates 32 form part of the database tables. In particular, the templates comprise the information gathering templates 32. In some embodiments, each information gathering template 32 may be considered a respective template of the database tables. The information gathering templates 32 comprise information gathering template data.

[0069] Each of the information gathering templates 32 is associated with one or more different report type. Each information gathering template 32 contains one or more sections, in this example using one or more spreadsheet tabs, that define information fields required for generation of the relevant report type. In other words, each information gathering template 32 includes one or more fields for receiving information. The information may be relevant to the creation of a respective defined report type.

[0070] The system 10 includes at least one report generation template 34. In the illustrated embodiment, the system 10 includes a plurality of report generation templates 34. In particular, the database system 12 comprises the report generation templates 34. The report generation templates 34 comprise report generation template data.

[0071] The database 26 includes the report generation templates 34. The report generation templates 34 are stored in the database 26. The plurality of database tables comprises the report generation templates 34. That is, the report generation templates 34 form part of the database tables. In particular, the templates comprise report generation templates 34. In some embodiments each report generation template 34 may be considered a respective template of the database tables.

[0072] One or more of the report generation templates 34 is associated with one or more information gathering template 32. For example, one or more of the report generation templates 34 may comprise a reference to one or more of the information gathering templates 32. Similarly, one or more of the information gathering templates 32 may comprise a reference to one or more of the report generation templates 34. The reference may be in the form of a number that is associated with the respective information gathering template 32 and / or report generation template 34. The report generation template data comprises the reference^) to the information gathering templates. The information gathering template data may comprise the reference(s) to the respective report generation template(s).

[0073] The system 10 includes a number of sets of report generation templates 34. Each set of report generation templates 34 comprises a group of the report generation templates 34. Each report generation template 34 set is for selection and use during creation of a particular report type.

[0074] Each report type is associated with one or more of the report generation templates 34. In particular, each report type is associated with a defined set of the report generation templates 34. One or more of the report generation templates 34 may comprise a reference that is indicative of the report type(s) that is associated with the respective report generation template 34. The reference may be referred to as a report type reference. Where a report generation template 34 is associated with more than one report type, the report generation template may comprise a reference for each associated report type. The reference may be in the form of a number. The report generation template data may comprise the reference.

[0075] The system 10 includes at least one calculation template 35. In the illustrated embodiment, the system 10 comprises a plurality of calculation templates 35. In particular, the database system 12 comprises the calculation templates 35. The calculation templates 35 comprise calculation template data.

[0076] The database 26 includes the calculation templates 35. The calculation templates 35 are stored in the database 26. The plurality of database tables comprises the calculation templates 35. That is, the calculation templates 35 form part of the database tables. In particular, the templates comprise the calculation templates 35. In some embodiments, each calculation template 35 may be considered a respective template of the database tables. One or more of the report generation templates 34 is associated with one or more respective calculation template 35. For example, one or more of the report generation templates 34 may comprise a reference to one or more of the calculation templates 35. Similarly, one or more of the calculation templates 35 may comprise a reference to one or more of the report generation templates 34. The reference may be in the form of a number that is associated with the respective calculation templates 35 and / or report generation template 34. The report generation template data may comprise the reference(s) to the relevant calculation template(s) 35. The calculation template data may comprise the reference(s) to the relevant report generation template(s) 34.

[0077] The system 10 comprises a plurality of datasets 36. In particular, the database tables 26 comprise the datasets 36. That is, one or more of the datasets 36 may be considered a database table 26. The datasets 36 are associated with one or more report types. The datasets 36 may be considered to be associated with a desired report. That is, one or more of the datasets 36 may be used in the generation of one or more desired report.

[0078] The datasets 36 comprise an input data dataset 38. The input data dataset 38 contains data gathered from a user according to the selected information gathering template(s) 32.

[0079] The datasets 36 comprise a qualitative input dataset 37. The qualitative input dataset comprises a plurality of qualitative input elements. The qualitative input elements may comprise a string. The qualitative input elements may be associated with qualitative inputs that can be sought in the process of completion of an information gathering template 32. For example, a qualitative input element may be a question seeking a written answer from the user. One or more of the information gathering templates 32 is associated with a respective qualitative input element. Where an information gathering templates 32 is associated with a respective qualitative input element, the information gathering template 32 may include the string of that qualitative input element when provided to the user.

[0080] The datasets 36 comprise a calculations dataset 40. The calculations dataset 40 contains data indicative of calculations used to produce calculated data for inclusion in a report. The calculations dataset 40 comprises a plurality of calculation elements. Each calculation element is associated with one or more calculations that may be performed by the system 10. For example, one or more calculation element may be in the form of a formula that is to be executed by the database system 12. Each formula may comprise one or more calculation parameters. The calculation parameters may take particular values depending on the calculation. That is, the calculation parameters are variables of the relevant calculation element. One or more calculation element may be in the form of a parameter that is to be used in a calculation.

[0081] Each calculation template 35 is associated with at least one of the calculation elements. In some embodiments, one or more calculation template 35 is associated with a plurality of calculation elements of the calculations dataset.

[0082] The datasets 36 comprise a calculation factors dataset 42. The calculation factors dataset 42 contains calculation factors. The calculation factors are associated with the calculations to be performed by the system 10. In particular, each of the calculation factors may be associated with one or more of the calculation elements. For example, one or more calculation factor may be a value of one or more parameters of a calculation element (e.g. where a calculation element is a formula).

[0083] As described herein, the report generation templates 34 are associated with respective calculation templates 35, which are in turn associated with one or more calculation elements. One or more of the calculation templates 35 is associated with at least one of the calculation elements. In some embodiments, each calculation template 35 is associated with at least one of the calculation elements. These associations are determined based on the particular calculations that need to be performed for a specified report type.

[0084] Each calculation template 35 of the plurality of calculation templates 35 may be thought of as a map to a particular set of the calculation elements required to generate a particular report type. That is, when a user wishes to generate a particular report type, the user provides an input indicative of that report type. The system 10 determines the associated report generation template 34, which is associated with one or more particular calculation template(s) 35. The calculation template(s) 35 that are associated with a particular report generation template 34 are also associated with the calculation elements (e.g. the formulae) that are required to be calculated to generate the report of the desired report type. The system 10 may therefore determine the calculations necessary to be performed based on the desired report type and the associations between the report generation templates 34, the calculation templates 35 and the calculation elements of the calculations dataset 40.

[0085] The datasets 36 comprise a calculation outputs dataset 44. The calculation outputs dataset 44 stores data produced by the calculations. That is, the system 10 performs a calculation based on the calculations dataset 40, with the output of the calculation being stored in the calculation outputs dataset 44.

[0086] The database tables also include at least one data map 46. The at least one data map 46 defines, for each report type, mapping of information gathered according to the information gathering templates 32 or produced by the system 10 to or from the relevant database tables 26.

[0087] It will be understood that by storing information gathering templates 32, report generation templates 34, calculation templates 35 and data maps 46 in dedicated database tables 26, a powerful, scalable, readily configurable arrangement is provided whereby the type of information and structure of a report are easily defined and managed simply by managing the content of the information gathering templates 32, the report generation templates 34, calculation templates 35 and the data maps 46.

[0088] Functional components 25 implemented by the database system 12, for example by the database management system 24 and / or the report management component 22, are shown in Figure 2. The functional components 25 may be in the form of software modules stored in the memory of the database system 12. The functional components 25, when in the form of software modules, may be configured to be executed by a processor of the database system 12, to enable the functionality described herein.

[0089] The functional components 25 include a template selector 50. The template selector 50 is arranged to receive information indicative of the desired report type. The template selector 50 is also arranged to select a set of report generation templates 34 based on the report type selected by a user for use in generating a report according to the selected report type. That is, the template selector 50 is arranged to select a set of report generation templates 34 based on the desired report type. Specifically, the template selector 50 is arranged to select the set of report generation templates 34 based on the information indicative of the desired report type. The template selector 50 is arranged to select at least one information gathering template 32. The template selector 50 selects the at least one information gathering template 32 based at least in part on the information indicative of the desired report type. In particular, the template selector 50 determines the information gathering templates 32 that are associated with the report generation templates 34 of the selected set of report generation templates 34 and selects these information gathering templates 32. The template selector 50 communicates the selected information gathering template(s) 32 to the user, in this example by serving template data to a web browser implemented on the user’s computing device 14.

[0090] The functional components 25 also include a data validator 51 arranged to check the data provided by the user in the information gathering template(s) 32 for validation purposes, and provide the user with an alert if any entered data fails validation. In other words, the data validator 51 is arranged to validate the user-provided information. The data validator 51 is arranged to communicate a defect if the user-provided information fails validation. The defect may be communicated to the user computing device 14, such that the user can be notified.

[0091] The functional components 25 also include a calculation implementor 52. The calculation implementor 52 is arranged to carry out calculations required for the generation of a report based on the selected set of report generation templates 34 for the report type and export the results of the calculations to the calculation outputs dataset 44.

[0092] The functional components 25 also include a data populator 54 arranged to populate data received from a user using the relevant information gathering template(s) 32 into relevant datasets 36, for example according to the data map 46. The functional components 25 also include a report generator 56 arranged to create a report based on the selected report type and the associated set of report generation templates 34.

[0093] The functional components 25 also include a data map selector 58 arranged to select the relevant data map 46 based on the report type selected by the user.

[0094] In this example, the database system 12 is implemented using a suitable computing device that at least includes a processor, memory and data storage for implementing programs and in this way carrying out the desired functionality of the system. It will be appreciated that in some embodiments, the database system 12 may be implemented using a plurality of suitable computing devices that communicate over a network.

[0095] In some embodiments, the system 10 comprises one or more API gateways. The API gateways may facilitate communication between the user computing device 14 and the database system 12. In some embodiments, the database system 12 comprises such an API gateway. In some embodiments, the API gateway may be considered a user interface of the database system 12.

[0096] An example implementation of the system 10 during use will now be described in relation to flow diagram 70 shown in Figure 3 and representations shown in Figures 4 to 30.

[0097] The flow diagram 70 includes steps 72 to 98 and indicates an example process of creating a report in association with a user.

[0098] As indicated at step 72, in this example a user must first register with the system 10 in order to be able to use the system to create reports. The user interacts with the system 10 through the user computing device 14. The user computing device 14 is in communication with the database system 12 via a network 16. The network 16 may be the Internet 16. The user accesses the database system 12 via the network 16. In particular, the user sends data to, and receives data from, the database system 12 via the network 16. The user may send data to and / or receive data from the database system via a web browser. After accessing the database system 12, in this example by directing the web browser to a website associated with the system 10, a report definition page 110 is displayed, as shown in Figures 4 and 5. As indicated at steps 74 and 76, the report definition page 110 is used to define basic information in relation to the desired report and for this purpose includes a report type drop down box 112 that enables the user to select the report type in a report type field 114, a report requestor field 116 usable to specify information indicative of the requestor, a requestor postcode field 118 usable to specify requestor postcode details, and start and end date fields 120, 122 usable to specify the date range to be covered by the selected report.

[0099] After providing the basic report details including the report type, the user selects a ‘create’ button on the report definition page 110, as indicated at step 78, which causes the entered basic report details to be communicated to the database system 12. These details may be considered information indicative of the desired report type.

[0100] The template selector 50 receives these details. That is, the template selector 50 receives this information indicative of the desired report type. Based on the selected report type, the template selector 50 selects the relevant report generation template(s) 34. The template selector 50 selects at least one information gathering template 32 based on the selected report type. The template selector 50 makes the selected information gathering template(s) 32 available for download by the user, and, in some embodiments, may cause a file transfer page to be displayed 124, as shown in Figure 6 and indicated at step 80.

[0101] At step 82, the user selects a download template button 126. In response to selection of the template download button 126 on the file transfer page 124, the database system 12 serves data indicative of the relevant information gathering template(s) 32 to the user’s computing device 14, as indicated at steps 82 and 84. The system 10 selects a set of report generation templates 34 based on the desired report type. The database system 12 selects at least one information gathering template 32 based on the selected set of report templates 34.

[0102] The system 10 transmits information gathering template data to the user computing device 14. The information gathering template data may be the data indicative of the relevant information gathering template(s) 32. In this example, the information gathering template is in Microsoft Excel format and typically includes several tabs, each tab associated with different information.

[0103] It will be appreciated that in some embodiments, alternative methods of providing the information gathering template 32 to the user and / or receiving information from the user that is relevant to the report type may be used. For example, one or more webforms could be used. That is, in some embodiments, the template selector 50 may make the information gathering template 32 available to the user by transmitting data to the user computing device 14 that is configured to be rendered by the web browser into a graphical user interface. The user may interact with the graphical user interface to provide the required information. In some embodiments, the data may be in JSON format. That is, the provision of the information gathering template 32 and the receipt of relevant information for the desired report may involve transmitting or exchanging data in JSON format between the database system 12 and the user computing device 14. In some embodiments, at least part of this process may be automated.

[0104] Using the information gathering template 32, the user provides the relevant information for the desired report by completing the spreadsheet, then selects an upload competed template button 130, as indicated at steps 86 and 88. The user computing device 14 transmits the completed information gathering template 32 to the database system 12. The database system 12 receives the completed information gathering template 32. The database system 12 therefore receives information relevant to the creation of the report. The information is associated with the selected at least one information gathering template 32 (being, in this embodiment, the completed information gathering template 32). The information relevant to the creation of the report comprises user- provided information that is provided using the user interface device 14.

[0105] An example information gathering template completed by a user is shown in Figures 7 to 15. In this example, the information gathering template is associated with a Greenhouse Gas Protocol report.

[0106] Figure 7 shows a cover page 140 of the template that includes basic report details 142 including report type information, the relevant facility associated with the information, report period dates, and contact details.

[0107] In this example, the information gathering template has multiple tabs relevant for information that may be required to prepare the selected report type. In this example, the template includes a cover sheet tab 144 associated with the cover page 140, an electricity tab 146 associated with an electricity sheet 162 shown in Figure 8, a gas tab 148 associated with a gas sheet 170 shown in Figure 9, a vehicles tab 150 associated with a vehicles sheet 176 shown in Figure 10, shown in Figure 11 , a water tab 154 associated with a water sheet 188 shown in Figure 12, a waste tab 156 associated with a waste sheet 194 shown in Figure 13, a flights tab 158 associated with a flights sheet 200 shown in Figure 14, and a land clearing tab 160 associated with a land clearing sheet 204 shown in Figure 15.

[0108] Selection of the electricity tab 146 causes the electricity sheet 162 to be displayed. The electricity sheet 162 includes electricity usage data 166 and links 168 to associated documentation for the electricity usage data 166.

[0109] Selection of the gas tab 148 causes the gas sheet 170 to be displayed. The gas sheet 170 includes gas usage data 172 and links 174 to associated documentation for the gas usage data 172.

[0110] Selection of the vehicles tab 150 causes the vehicles sheet 176 to be displayed. The vehicles sheet 176 includes vehicle fuel data 178 and links 180 to associated documentation for the vehicle fuel data 178.

[0111] Selection of the burials tab 152 causes the burials sheet 182 to be displayed. The burials sheet 182 includes burials data 184 and links 186 to associated documentation for the burials data 182.

[0112] Selection of the water tab 154 causes the water sheet 188 to be displayed. The water sheet 188 includes water usage data 190 and links 192 to associated documentation for the water usage data 190. Selection of the waste tab 156 causes the waste sheet 194 to be displayed. The waste sheet 94 includes waste data 196 and links 198 to associated documentation for the waste data 196.

[0113] Selection of the flights tab 158 causes the flights sheet 200 to be displayed. The waste sheet 200 includes waste data 202 and links (not shown) to associated documentation for the waste data 202.

[0114] Selection of the land clearing tab 160 causes the land clearing sheet 204 to be displayed. The land clearing sheet 204 includes land clearing data 206 and links (not shown) to associated documentation for the land clearing data 206.

[0115] While the above example is described in relation to information gathering by enabling a user to download an information gathering template, it will be understood that alternative information gathering arrangements are possible. For example, the system may be arranged to enable a user to directly provide information relevant to creation of a report by accessing defined web forms on the website associated with the system 10. In a particular example, the information gathering arrangement is configured such that the user first selects a location type, such as ‘electricity meter’, and in response the system presents a relevant web form containing data entry fields relevant to the location type ‘electricity meter’.

[0116] As indicated at step 90, the received information provided in the information gathering template 32 is stored in the datasets 36 of the database 26, for example according to data maps 46 defined for the report type. This received information (i.e. the information input into the information gathering template 32 by the user) may be considered information relevant to creation of the report. The data validator 51 checks the provided information for validation purposes and provides the user (via the user computing device 14) with an alert if any issues are identified.

[0117] The system 10 proceeds to determine report output data. In particular, the system 10 determines the report output data based at least in part on the information input into the information gathering template 32 by the user. That is, the system 10 determines the report output data using at least some of the information relevant to creation of the report.

[0118] As indicated at step 92, the system identifies any required calculations using the selected set of report generation templates 34.

[0119] As indicated at step 94, the system then implements the required calculations for the desired report using the information provided in the information gathering template 32 and stored in the datasets 36 and according to the relevant calculations defined for the report type in the report generation templates 34.

[0120] As described herein, the system 10 comprises calculation templates 35 that are associated with respective report generation templates 34. The system 10 determines the calculation templates 35 that are associated with the selected set of report generation templates 34. The system 10 determines the calculation elements that are associated with these calculation templates 35. The system 10 then performs the necessary calculations, based on these calculation elements. The system 10 may also perform the necessary calculations based on the calculation factors dataset (i.e. to determine the relevant values of certain parameters of the calculation elements). The results of the calculations are stored in the calculation outputs dataset 44.

[0121] As indicated at step 96, the system 10 determines report output data. The system 10 determines the report output data, at least in part, using the calculation outputs dataset 44. Due to the selection of the appropriate information gathering template(s) 32, report generation template(s) 34 and calculation template(s) 35, and the performance of the appropriate calculations, the calculations output dataset 44 will include the information required to generate the report output data for the desired report. The system 10 may therefore be said to determine the report output data using at least one calculation element that is associated with one or more of the report generation templates 34 of the selected set of report generation templates 34.

[0122] In some embodiments, the report output data may be the report itself (for example, in a PDF format). In some embodiments, the report output data may be configured to be rendered by another computing device (such as the user computing device 14) to display the information of the report. For example, the report output data may be configured to be rendered by the web browser of the user computing device 14 for display.

[0123] In some embodiments, the report generator 56 creates the report according to the desired report type. The report generator 56 may create the report based on the set of report generation templates 34. The report generator 56 may use a relevant data map to populate the required data into the report template from the database 26.

[0124] The report output data is communicated, as indicated at step 98. In some embodiments, the report output data is communicated to the user computing device 14, to be rendered to display the report, for example, by a web browser. In some embodiments, the completed report is communicated, for example to the user or to a destination selected by the user. The destination selected by the user may be the report receiving computing device 18.

[0125] An example set of report generation templates is shown in Figures 16 to 23.

[0126] In this example, the set of report generation templates 34 is associated with a Greenhouse Gas (GHG) Protocol report.

[0127] The GHG Protocol is a widely recognised framework for measuring and reporting GHG emissions. The Protocol provides detailed guidance on how to calculate and report GHG emissions. National Greenhouse Accounts (NGA) Factors are annually updated specific emission and energy factors developed by the Australian government and can be used by Australian companies to estimate their GHG emissions. With the aim of generating the GHG inventory of an organisation, the GHC Protocol can be used alongside the NGA factors to create a comprehensive understanding of a company’s GHG inventory in their sustainability report.

[0128] The report generation templates are entered into a set of specifically formatted database tables. In this example, the report generation tables include a registration table, methods table, calculation sequence table, taxonomy table, variables table, location types table, units table, set names table, and elements table. Figure 16 shows an example registration table 210 of the set of report generation templates 34 that includes basic information about the framework related to the template set, such as the publishing entity and the electronic address of the framework, and the validity period of the template set.

[0129] For the present template set, the methodology for quantifying and reporting GHG emissions are derived from the ‘GHG Protocol Corporate Accounting and Reporting Standard’ published by the Greenhouse Gas Protocol Initiative.

[0130] Figure 17 shows a methods table 214 that includes information relating to calculations used by a template set, the calculations defined by inputs, factors, and outputs. The methods table 214 of Figure 17 may be an example of a calculations dataset described herein.

[0131] All the calculations used in a template are listed in the methods table 214. In this example, calculations from the NGA Factors Workbook are utilised for quantifying emissions according to the requirements of the GHG Protocol for Business.

[0132] In this example, the calculations are defined in the methods table using the following columns:

[0133] • A method code column 216 that contains an identifier summarising the function of the calculation.

[0134] For example, the method code may be GHG-NGA-ELECTRICITY- PURCHASE-GRID-S2-V1 , which relates to a calculation of greenhouse gases emissions associated with purchase of electricity from the grid for a scope 2 emissions calculation. The source of the calculation is the NGA Factors Workbook (NGA).

[0135] • A method name column 218 that contains a concise explanation of the purpose of the calculation.

[0136] For example, the method name column may contain “Indirect emissions from consumption of purchased electricity from a grid (Scope 2 NGA Method).

[0137] Validity date range columns 220 that contain date values that are dependent on the validity period of factors used by the method and published versions of the reporting framework.

[0138] For example, the date ranges may be 01 / 07 / 2022 and 30 / 06 / 2023, reflecting that the NGA Factors Workbook is published yearly with revisions of the emission factors and calculation methods.

[0139] An input type column 222 and an output scope column 224 that contain information about input data from the user and output data generated by the system. The associated input data and output data are stored in the respective input data and calculation outputs datasets 38, 44.

[0140] For example, the input type column 222 may contain “Electricity consumption data” and the output scope column 224 may contain “Scope 2 GHG Emissions.”

[0141] A function column 226 that contains a function name for the calculation in the system.

[0142] For example, the function column 226 may contain “sp_NGAEIectricityPurchaseGridS2”

[0143] Alternatively, the function column 226 may contain Python calculation classes.

[0144] A formula column 228 that contains a calculation equation, steps and variables.

[0145] The present set of report generation templates 34 also includes a calculation sequence table (not shown) used to link calculations that generate primary outputs to calculations for secondary, tertiary, and so on, outputs. Figure 18 shows a taxonomy table 230 that defines the hierarchical classification of data values in the system. The taxonomy table 230 includes three columns, as follows:

[0146] • A classification hierarchy column 232 that defines the available levels of a particular taxonomy classification from a root classification.

[0147] • A taxonomy type column 234 that describes the function of the classification hierarchy.

[0148] • A taxa name column 236 that contains the names associated with the different levels of the classification hierarchy.

[0149] Each ‘classification hierarchy’ has a ‘taxonomy type’ and ends with a unique ‘taxa name’.

[0150] Classification hierarchies are controlled by parent-child relationships such that each child can only have one parent. In the present example, the NGA Factor Workbook records the emission factors for all the primary grids in Australian States or Territories, and each of these geographic emission factors is assigned a unique taxa name, for example “NGA Scope 2 SWIS in WA Grid.”

[0151] Figure 19 shows a variables table 240 that stores the names of measured properties, such as electricity delivered. All variables used in a report generation template set are listed in the variables table 240. Variables describe inputs, outputs and factors of the calculations identified in the methods table 214 shown in Figure 17.

[0152] The variables table 240 includes the following columns:

[0153] A types column 242 that contains a generic description of the variable, such as ‘power’ that relates to all variables associated with the amount of energy transferred or converted per unit time.

[0154] A variable code column 244 that contains a unique text code. Multiple variable codes can belong to the same variable type.

[0155] For example, the variable code column 244 may include “Electricity delivered (Grid)”, which is a variable indicative of the amount of electricity delivered from the grid as a data value in the system that is created based on requirements of an electricity consumption calculation.

[0156] • A description column 246 that contains a description of the variable such as “An amount of electricity delivered from the grid.”

[0157] Figure 20 shows a location types table 248 that stores location type information. A location type refers to a location at which observations are measured or a location that is associated with a derived output. The scale of a location varies such that a location can be for example an ‘electricity meter’, a ‘diesel heavy truck’ or a ‘steel beams bridge’.

[0158] The location types table 248 includes the following columns:

[0159] • A location type column 250 that contains information about the type of location for capture of data values, such as ‘electricity meter’.

[0160] • A location code column 252 that contains a unique location code assigned to the location.

[0161] • A location category column 254 that contains generic category information for locations that share characteristics, such as ‘meter’.

[0162] • A location name column 256 that contains a name for the location, typically a more explanatory version of the information in the location code column 252.

[0163] A location description column 258 that contains a description for each location code, such as “a device that measures the amount of electric energy consumed by a facility over a time interval” for an electricity meter. Figure 21 shows a units table 260 that stores information about units used by the system. All three types of data values used in the system - inputs, factors, and outputs - have an associated unit in the system.

[0164] The units table 260 includes the following columns:

[0165] • A unit types column 262 that contains information about the general type of measurable physical quantity, such as ‘potential’ or ‘energy’.

[0166] • A unit abbreviation column 264 that contains an abbreviation for a unit, such as ‘kWh’.

[0167] • A unit name column 266 that contains a name for the unit, such as ‘Kilowatt-hours’.

[0168] Figure 22 shows a set names table 270 that stores information about datasets used by the system to store inputs, outputs, factors, calculation data definitions, and reporting rules. The datasets can be easily queried and analysed by the system.

[0169] The set names table 270 includes the following columns:

[0170] • A dataset code column 272 that contains a unique identifier serving as a meaningful name or a combination of letters and numbers that are generated using a standardised and consistent naming convention reflecting the content of the dataset.

[0171] All inputs, factors, and outputs must be assigned with a dataset code that reflects the type of information represented. For example, the dataset code column 272 may contain ‘electricity consumption data’ for a dataset that contains input data for consumption of electricity, ‘scope 2 GHG emissions’ for a dataset that contains output data for all scope 2 emissions calculations, ‘GHG-NGA-ELECTRICITY-PURCHASE-GRID-S2-V1 for a dataset that contains calculation data definitions for GHG emissions associated with purchased electricity, or ‘NGA Factors 2022’ for a dataset that contains calculation factors.

[0172] • A dataset title column 274 that contains a concise, descriptive name for a dataset in the system.

[0173] • A dataset description column 276 that contains a description of the purpose and overview of the content of the dataset.

[0174] • A dataset type column 278 that contains information to classify and categorise datasets in the system.

[0175] For example, ‘input data, ‘output data, ‘factor table’ and ‘calculation data definition’. The dataset type describes the type of data contained in the assigned dataset. Using a standardised controlled vocabulary for the dataset types makes it easy to understand and utilise the data.

[0176] Figure 23 shows an elements table 280 used to define the elements of calculations in the system. Each element row in the elements table 280 associates several data values from several tables.

[0177] The elements table 280 includes the following columns:

[0178] • A type column 282 that contains information identifying the type of element, such as ‘factor’; ‘input’ or ‘output’.

[0179] For example, an element with an assigned type ‘factor’ is used for the data value of a factor in the system.

[0180] • A table / set name column 284 that contains the relevant dataset title for an element row.

[0181] For example, the table / set name column 284 may include “NGA Table 1 :

[0182] Indirect (Scope 2 and Scope 3) emissions from consumption of purchased electricity from a grid”, which relates to an element of type ‘factor’, the table / set name corresponding to the source of the factor numerical result. In this example, this can be found in Table 1 of the NGA Factors dataset. Data validation is used to ensure accurate usage of data from the set names 270 table

[0183] A taxonomy column 286 that contains element classification hierarchy information.

[0184] A location column 288 that contains information about the type of location for capture of data values, such as ‘electricity meter’. Data validation is used to ensure accurate usage of data from the location types table 248.

[0185] A variable column 290 that contains information about a variable used in the system, such as ‘CO2-CO2-e’, which is an element entry for a factor data value associated with the global warming potential of carbon dioxide gas in carbon dioxide equivalents. Data validation is used to ensure accurate usage of data from the variables table 240.

[0186] A unit column 292 that contains information about a unit, such as ‘kgCO2- e / kWh’, which is an element entry for a factor data value associated with the quantity of carbon dioxide equivalents emitted from the purchase electricity from the SWIS grid in WA. As this is a factor, the unit will be expressed in terms of the amount of relevant substance per unit of activity, in this example kilograms of carbon dioxide equivalents per kilowatt-hours of electricity purchased. Data validation is used to ensure accurate usage of data from the units table 260.

[0187] A qty column 294 that contains a numerical data value.

[0188] The qty column for element rows with type ‘input’ and ‘output’ are null as the ‘input’ values are entered by system users and the ‘output’ values are generated using the calculations and the ‘input’ values. • A method name column 296 that contains a method name which is assigned to all input, factor, and output element rows that use the same calculation method. Data validation is used to ensure accurate usage of data from the methods table 214.

[0189] An example report produced by the system 10 is shown in Figures 24 to 30.

[0190] In this example, the report has multiple tabs that include a scope breakdown tab 300 that when selected causes a scope breakdown report 314 as shown in Figure 24 to be displayed, a comparison table tab 302 that when selected causes a comparison table report 316 as shown in Figure 25 to be displayed, a comparison report tab 304 that when selected causes a comparison report 318 as shown in Figure 26 to be displayed, an electricity report tab 306 that when selected causes an electricity report 320 as shown in Figure 27 to be displayed, an embalming & leakage tab 308 that when selected causes an embalming & leakage report 322 as shown in Figure 28 to be displayed, a waste tab 310 that when selected causes a waste report 324 as shown in Figure 29 to be displayed, and a funerals tab 312 that when selected causes a funerals report 326 as shown in Figure 30 to be displayed.

[0191] However, it will be understood that any suitable report type is envisaged.

[0192] The described system 10 provides a number of significant technical benefits. As described herein, one or more of the information gathering templates 32, report generation templates 34 and calculation templates 35 are stored as respective database tables. Similarly, one or more of the datasets 37, 38, 40, 42, 44 are stored as respective database tables. In particular, one or more of these templates and / or datasets is stored as a respective repurposed ODM2 database table. While the data of these templates and datasets is stored in separate tables, references are included (e.g. within the relevant templates and / or datasets) that associate particular templates and datasets with other relevant templates and datasets. These references may be in the form of numerical indexes. That is, an index system may be used for the associations. Such a data structure, and the relevant associations, may decrease the memory requirements of the system 10 and may decrease the computational requirements to operate the system 10. For example, a user may require a report of a first report type, with the report of the first report type requiring a first calculation, a second calculation and a third calculation to be performed in order to be generated. The system 10 may also be capable of producing a report of a second type, with the report of the second report type requiring the second calculation, the third calculation and a fourth calculation to be performed in order to be generated. In some embodiments, one implementation may be to store in memory, for the first report type, a copy of the formula for the first calculation, the formula for the second calculation and the formula for the third calculation, in addition to storing in memory, for the second report type, another copy of the formula for the second calculation, another copy of the formula for the third calculation and a copy of the formula for the fourth type of calculation (i.e. storing two copies of the formula for the second calculation and the formula for the third calculation, one for each of the first report type and the second report type). However, in some embodiments, a single copy of each formulae that could be required by the system is instead stored in the calculations dataset 40 (in the form of a calculation element). In such an embodiment, the report generation templates 34 include a reference to particular calculation templates 35 required for the associated report type. The calculation templates 35 in turn include references to the specific calculation elements (i.e. formulae) required for the calculations. For example, where a report of a first type is selected, a first report template and a second report template may be required to generate the report. The first report template may be associated with a first calculation template, which in turn may be associated with first, second and third calculation elements (i.e. formulae) of the calculations dataset 40. Similarly, the second report template may be associated with a second calculation template, which in turn may be associated with the third calculation element, in addition to fourth and fifth calculation elements (i.e. formulae) of the calculations dataset 40. In this case, only one copy of the third calculation element (i.e. the third formulae) is stored (in the calculations dataset 40). Thus, the described implementation can enable a reduction in the total storage requirements of the system 10. Using these associations (which may, for example, involve an index reference system for one or more calculation elements, calculation templates 35 and / or report generation templates 34) may also improve the computational efficiency of generating the reports accordingly. Alternative Implementations

[0193] While the present examples are described in relation to a system implemented online, it will be understood that other arrangements are possible. For example, the system may be implemented on a single computing device. Alternatively, the system may be implemented on multiple computing devices that are connected together locally or over a federated data network that includes multiple instances of identically formatted database tables compiled by the described system 10 and that may be controlled by external groups of users.

[0194] Figure 31 is a schematic block diagram of another embodiment of a system 10A. The system 10A may be similar to, or the same as, the system 10 of Figure 1 , in one or more aspects. Features of the system 10A that are the same as, or similar to, corresponding features of the system 10 of Figure 1 may be provided with similar reference numerals in Figure 31 as were provided in Figure 1.

[0195] The system 10A comprises a user computing device 14. The user computing device 14 may be the same as, or similar to, the user computing device 14 described with reference to Figure 1 . The system 10A comprises a report receiving computing device 18. The report receiving computing device 18 may be the same as, or similar to, the report receiving computing device 18 described with reference to Figure 1.

[0196] The system 10A comprises a plurality of database systems 12A, 12B, 12C, 12D. Alternatively, the system 10A may be considered to comprise one database system that itself comprises a plurality of database system computing devices 12A, 12B, 12C, 12D. For the purposes of this disclosure however, each of 12A, 12B, 12C and 12D will be referred to as a respective database system.

[0197] The database systems 12A, 12B, 12C, 12D are configured to be in communication with each other via a communications network 16. The database systems 12A, 12B, 12C, 12D are configured to be in communication with one or more other components of the system 10A (e.g. the user computing device 14 and / or the report receiving computing device 18) via the communications network 16. Each database system 12A, 12B, 12C, 12D may be associated with a respective organisation. For example, each database system 12A, 12B, 12C, 12D may be associated with a respective company that gathers its own data that can be used in determining one or more desired reports.

[0198] The system 10A comprises a federated data network 13. The database systems 12A, 12B, 12C, 12D form at least part of the federated data network 13. The federated data network 13 may be referred to as a federated network.

[0199] One or more of the database systems 12A, 12B, 12C, 12D comprises at least one database table 26A, 26B, 26C, 26D. In the illustrated embodiment, each database system 12A, 12B, 12C, 12D comprises a respective number of database tables 26A, 26B, 26C, 26D. Each set of database tables 26A, 26B, 26C, 26D may comprise one or more respective information gathering templates 32, report generation templates 34, calculation templates 35, data maps 46, input data datasets 38, calculations datasets 40, calculation factors datasets 42, calculation outputs datasets 44 and / or qualitative input datasets 37.

[0200] The database tables 26 of the database system 12 described with reference to Figure 1 include a plurality of templates 32, 34, 35 and a plurality of data sets 37, 38, 40, 42, 44. One or more of the database systems 12A, 12B, 12C, 12D of Figure 31 may comprise a respective group of templates 32, 34, 35 and / or data sets 37, 38, 40, 42, 44. The templates 32, 34, 35 and / or data sets 37, 38, 40, 42, 44 of a respective database system 12A, 12B, 12C, 12D may be those that are associated with the operation of the organisation that is running the database system 12A, 12B, 12C, 12D and / or the data collected by that organisation.

[0201] In the generation of a particular report, data from a plurality of sources may be required to perform the necessary calculations. In the embodiment of Figure 31 , some of this data may be collected and stored by different organisations. For example, a first company may run database system 12A and a second company may run database system 12B. The first company may record data associated with groundwater and the second company may record data associated with air temperature. The database tables 26A of the database system 12A run by the first company may comprise or be associated with the groundwater data. Similarly, the database tables 26B of the database system 12B run by the second company may comprise or be associated with the air temperature data. By providing a federated data network 13 over which each of these organisations may be connected, and over which a user may interact with the system 10, organisations may retain control of their data whilst ensuring it is available to the greater network of organisations for report generation. This can be beneficial if, for example, a user wishes to generate a report that requires access to the first company’s groundwater data and the second company’s air temperature data. The federated data network 13 may enable the preservation of anonymity of the data. This may be accomplished through the use of unique universal identifiers (UUlDs) at different levels in the report, including summaries of data referencing one or more of the database tables 26, datasets 36, the input data dataset 38, the calculations dataset 40, the calculation factors dataset 42 and / or the calculation outputs 44. The UUID, while disguising the context of the data, can be used to query specific data referenced by that UUID from an instance of the database tables 26 of the federated data network 13 with permission from the owner of the respective database tables 26.

[0202] In some embodiments, the user computing device 14 may retrieve the relevant data from the database systems 12A, 12B, 12C, 12D and generate the reports. In some embodiments, one or more of the database systems 12A, 12B, 12C, 12D may retrieve the relevant data from the other database systems 12A, 12B, 12C, 12D and generate the report. In some embodiments, each database system 12A, 12B, 12C, 12D may generate part of the report, and transmit its section to the user computing device 14. In some embodiments, another computing device (e.g. one run by an organisation that controls the rules of the federated data network 13) may act as an intermediary that retrieves the necessary data, performs calculations and / or generates report output data for transmission to the user computing device 14.

[0203] The database systems 12A, 12B, 12C, 12D comprise respective network interface systems 21A, 21 B, 21C, 21 D. Each network interface system 21A, 21 B, 21C, 21 D may comprise a respective web server, report management component and / or database management system. The web servers, report management components and / or database management systems may be the same as, or similar to, the web server 20, report management component 22 and / or database management system 24 described with reference to Figure 1. The network interface systems 21 A, 21 B, 21 C, 21 D may enable the database systems 12A, 12B, 12C, 12D to interact via one or more Application Programming Interfaces (APIs). The APIs may be cloud AlPs or ingestion APIs.

[0204] The system 10 may comprise one or more app gateway that facilitates interaction between the user and the database systems 12A, 12B, 12C, 12D. The app gateway may retrieve the necessary data, perform calculations and / or generate report output data for transmission to the user computing device 14 as part of the report generation process. The system 10 may comprise one or more API gateway that facilitates interaction between the user and the database systems 12A, 12B, 12C, 12D. The database systems 12A, 12B, 12C, 12D may communicate via a message bus.

[0205] It is to be understood that, if any prior art publication is referred to herein, such reference does not constitute an admission that the publication forms a part of the common general knowledge in the art, in Australia or any other country.

[0206] In the claims which follow and in the preceding description of the invention, except where the context requires otherwise due to express language or necessary implication, the word “comprise” or variations such as “comprises” or “comprising” is used in an inclusive sense, i.e. to specify the presence of the stated features but not to preclude the presence or addition of further features in various embodiments of the invention.

[0207] Modifications and variations as would be apparent to a skilled addressee are determined to be within the scope of the present invention.

Claims

The claimsthe invention are as follows:1 . A system for determining report output data associated with a defined report type of a plurality of report types, each report type incorporating defined scientific data, the system comprising: a database including: a plurality of database tables, the database tables including: a plurality of templates; and a calculations dataset comprising a plurality of calculation elements; the templates comprising: a plurality of calculation templates, each calculation template being associated with at least one of the calculation elements; a plurality of information gathering templates, each information gathering template including fields for receiving information relevant to creation of a respective defined report type; and a plurality of report generation templates, one or more report generation template being associated with: one or more calculation template; and one or more information gathering template; each report type being associated with a defined set of the report generation templates; and the system arranged to: receive information indicative of the desired report type; select a set of report generation templates based on the desired report type; select at least one information gathering template based on the selected set of report generation templates; receive information relevant to creation of the report, the information being associated with the selected at least one information gathering template; determine report output data using: at least some of the information relevant to creation of the report; and the at least one calculation element that is associated with thecalculation template that is associated with one or more of the report generation templates of the selected set of report generation templates.

2. A system as claimed in claim 1 , wherein: one or more of the calculation elements comprises a plurality of calculation parameters; and the database tables include: a calculation factors dataset comprising a plurality of values of one or more of the calculation parameters.

3. A system as claimed in claim 1 or claim 2, wherein the database tables comprise a qualitative input dataset comprising a plurality of qualitative input elements.

4. A system as claimed in claim 3, wherein one or more of the information gathering templates is associated with one or more qualitative input element.

5. A system as claimed in any one of the preceding claims, further comprising a user interface arranged to facilitate communications between a user and the system, the user interface arranged to enable the user to provide information indicative of the desired report type.

6. A system as claimed in claim 5, wherein: the user interface is arranged to receive an input indicative of a report type from the user, and to make an information gathering template associated with the selected report type available to the user, for example by downloading the information gathering template to the user.

7. A system as claimed in any one of the preceding claims, wherein: the information relevant to creation of the report comprises user-provided information that is provided using the user interface; and the system is arranged to validate the user-provided information and to communicate a defect if the user-provided information fails validation.

8. A system as claimed in any one of the preceding claims, wherein the database tables include at least one input data dataset arranged to store the user-provided information.

9. A system as claimed in any one of the preceding claims, wherein the database tables include at least one output data dataset arranged to store data derived from the user-provided information.

10. A system as claimed in claim 9, wherein derived data is calculated from the user-provided information using at least one calculation.

11. A system as claimed in any one of the preceding claims, wherein the system stores a plurality of data maps, each data map indicative of mapping of data to or from the database.

12. A system as claimed in any one of the preceding claims, wherein the system comprises a federated data network.

13. A system as claimed in any one of the preceding claims, wherein the database is a repurposed generic database.

14. A system as claimed in claim 13, wherein the database is repurposed by conceptually extending the definitions of particular generic table entities.

15. A system as claimed in claim 13 or claim 14, wherein the generic database may be based upon an open-source standard data architecture for scientific observations.

16. A system as claimed in any one of claims 13 to 15, wherein the generic database is Observations Data Model 2 (ODM2).

Images