TECHNICAL FIELD

[0001] The present disclosure relates to devices and methods for calculating the embodied and operational carbon emissions generated during the full infrastructure project lifecycle.

BACKGROUND

[0002] Conventional approaches to evaluating a carbon footprint of a structure such as a power plant tend to limit their analyses to the amount of carbon generated by that structure during operation. In aspects, the present disclosure is directed to the need for a more comprehensive estimate of carbon emissions for a carbon emitting structure, which may be generated before and/or during the fabrication, construction, transportation of goods related to the structure, vehicular movements of personnel associated to that structure, etc. Thus, in aspects, the present disclosure addresses the need for methods by which carbon emissions could be reduced, addresses the need for enhanced approaches to carbon offsetting strategies and pricing, and addresses other needs as will become apparent from the discussion below.

SUMMARY

[0003] In aspects, the present disclosure provides a method of estimating a carbon emission lifecycle footprint of an infrastructure project. The method may include the steps of compiling a set of rules that include carbon emission rules and engineering rules, wherein each carbon emission rule and each engineering rule represent a predetermined decision; encoding the set of rules in a database; obtaining non-project specific information from suppliers and manufacturers; storing non-project specific information in the database; obtaining project specific information for the project; conveying the project specific information via a user interface to the database; generating deliverables using at least the set of rules, the non-project specific information, and the project specific information; and using the deliverables to estimate the carbon emission lifecycle footprint of the project. The method may be used to identify appropriate technology options to refine the design to reduce the carbon footprint and identifying appropriate offsetting options.

[0004] In aspects, the present disclosure also provides a method of designing an infrastructure project by estimating a carbon emission lifecycle footprint of a project. The method may include the steps of compiling a set of carbon emission and engineering rules, wherein each rule represents a predetermined decision; encoding the set of rules in a database; obtaining non-project specific information from suppliers and manufacturers; storing non- project specific information in a database; compiling a project profile for the energy project, the project profde including project specific information; conveying the project specific information via a user interface to the database; generating deliverables using the set of carbon emission and engineering rules, the non-project specific information, and the project specific information; using the deliverables to estimate the carbon emission lifecycle footprint for the project; changing the project profile based on the estimated carbon emission lifecycle footprint; and designing the project using the changed project profile.

[0005] It should be understood that certain features of the disclosure have been summarized rather broadly in order that the detailed description thereof that follows may be better understood, and in order that the contributions to the art may be appreciated. There are, of course, additional features of the disclosure that will be described hereinafter and which will in some cases form the subject of the claims appended thereto.

BRIEF DESCRIPTION OF THE DRAWINGS

[0006] For a detailed understanding of the present disclosure, references should be made to the following detailed description taken in conjunction with the accompanying drawings, in which like elements have been given like numerals and wherein: FIG. 1 schematically illustrates a system for generating an embodied and operational carbon footprint for infrastructure projects according to one embodiment of the present disclosure;

FIG. 2 illustrates a flowchart depicting a method for generating an embodied and operational carbon footprint for infrastructure projects according to one embodiment of the present disclosure;

FIG. 3 illustrates a flowchart depicting a method for generating, and leveraging technical solutions to reduce the embodied and operational carbon footprint for infrastructure projects according to another embodiment of the present disclosure; and

FIG. 4 illustrates a flowchart depicting a method for evaluating and revising a proposed energy project according to one embodiment of the present disclosure.

DETAILED DESCRIPTION

[0007] In aspects, the present disclosure provides systems and related methods for efficiently calculating the embodied and operational carbon footprint of an infrastructure project and generating options for decarbonizing the infrastructure project. As used herein, the term ‘decarbonizing’ means reducing an initial estimated carbon footprint. As used herein, an ‘infrastructure project’ may be a manufacturing plant, an energy project such as a renewable energy project, a commercial office structure, a residential facility, or any other human constructed facility. For brevity, an “infrastructure project” may be referred to simply as a “project.” The present disclosure is susceptible to embodiments of different forms. There are shown in the drawings, and herein will be described in detail, specific embodiments of the present disclosure with the understanding that the present disclosure is to be considered an exemplification of the principles of the disclosure and is not intended to limit the disclosure to that illustrated and described herein.

[0008] As will become apparent from the discussion below, the present disclosure addresses the need to construct low carbon projects as private and public entities transition away from a reliance on fossil fuels in the strive to deliver the climate change goals of the Paris Agreement. Advantageously, the teachings of the present disclosure define “low carbon” to include not only carbon emissions caused by operation, “operational emissions” or “direct carbon emissions”, but also carbon emissions caused by activities, whether or not in situ, necessitated by such operation, “embodied” or “indirect” emissions. The present teachings also define “low carbon” to include direct and indirect emissions necessitated by the planning and construction of the infrastructure project. By way of example, non-fossil fuel-based energy projects provide energy and fuel but emit a relatively lower level of greenhouse gas emissions during operation. At the same time, building these new facilities release embodied emissions into the atmosphere. Embodied emissions include those caused by the manufacture, logistics, waste, and combustion of fuels during the design, manufacture, and construction of the project.

[0009] The teachings of the present disclosure may help achieve Net Zero emissions by 2050 by considering both the operational and embodied emissions. It is believed that embodied emissions may account for a greater proportion of the total emission figure over time as industry moves from traditional, carbon intensive projects, to delivering projects which generate zero emissions during their operation through the use or production of wind, water or hydropower, for example. The teachings of the present disclosure provide systems and associated methods for calculating the expected lifecycle carbon footprint of an energy project, articulating and understanding the source of emissions, and generating one or more options for decarbonization of a project.

[0010] Referring to FIG. 1, there is illustrated a non-limiting embodiment of a system 100 for efficiently calculating the embodied and operational carbon footprint of an infrastructure project. Generally, a user enters project-specific information 110 into a user interface 120. The project-specific information 110 includes details such as the physical attributes of the prospective project, such as the weight of materials and location. The user interface 120 communicates the entered information to a database 130. The database 130 stores non project-specific information 132, as well as the project-specific information 110 and other information. The database 130 processes the project specific information 110, nonproject specific information 132 and other information in conjunction with the engineering rules 134 and carbon emission rules 136. The ultimate product of this interaction are deliverables 140 that may be used to understand the carbon emissions lifecycle of a prospective project. [0011] The project-specific information 110 includes information that is relevant to the engineering design of an energy project. As used herein, the term "project-specific" means information that physically defines the prospective project and the physical characteristics of the desired project. The project-specific information 110 may include information obtained during a project survey during which personnel measure property features, take visual images, evaluate conditions, etc. The project-specific information 110 may also be obtained using public or private databases. For example, by using GPS coordinates, information regarding transport routes, ports, and relative distances may be obtained. The user may also enter the desired features of the project, e.g., type of project (e.g., offshore jacket and topsides, wind farm, floating production storage and offloading vessel, etc.), equipment types, estimated final steel weight, project schedules, number of personnel, business travel requirements, construction and fabrication approach, etc.

[0012] The project-specific information 110 is entered into the user interface 120, which may be configured as a webproject front end. The user interface 120 transmits the entered information to the database 130, which may be a cloud database. The database 130 stores the project-specific information 110, non-project specific information 132, and well as other information. The non-project specific information 132 may include information that relates to the equipment, and materials used to construct a project. For example, the non- project specific information 132 may include technical specifications, maintenance schedules of equipment, metallurgy, and weight of equipment and materials, etc. As used herein, non- project specific information is information that may be relevant to and common between the design and / or construction of two or more projects. By way of example, GPS coordinates will be unique to each project; i.e., project specific. The features such as dimensions and costs of a specific piece of equipment, pump, valve control system, etc. will likely be the same or similar across two or more projects; i.e., non-project specific.

[0013] Other information may include secondary information that relates to requirements specified by a client in their design criteria, including but not limited to aspects such as the jurisdictional or regulatory standards which are specific to the country or region in which the project is located.

[0014] To initiate the generation of the deliverables 140, the database 130 calculates the carbon emissions based on the relevant stored project and non-project information calling on the engineering rules 134 and carbon emission rules 136. Illustrative, but not exhaustive, examples of the engineering rules 134 prepared using unique business intelligence and past undertakings include: identifying the quantity of equipment, identifying metallurgy, assigning logistical arrangements, specifying construction site locations, identifying fabrication methods, etc.

[0015] The design of energy and infrastructure projects may be constructed as a rule by calling upon the knowledge and experience base of the inventors. For example, a rule to calculate the number of people who will work across the lifecycle of the project may be expressed as follows: (i) if the project weight is greater than 5000 tonnes, (ii) if the fabrication schedule is greater 9 months, and (iii) the number of different project execution locations. In another example, the rules for the carbon emissions associated to the logistical movement of purchased goods may be expressed as follows: (i) default is that all equipment packages are procured from Europe, (ii) if the final project location is in North America, then 50% of equipment packages are procured from the Americas, (iii) if the final project location is in Australia, then 75% of equipment packages are procured from Australasia. In one embodiment, the engineering rules 134 and carbon emission rules 136 may be encoded in the database 130.

[0016] Human input, or interactive engineering 150, may be used to generate alternative carbon emission scenarios. For example, the carbon emission results 140 identify a carbon footprint result which identifies opportunity to decarbonize the project. Interactive engineering 150 is used to adjust the project specific information 110 to outturn lower carbon emission results 140. Interactive engineering 150 is a powerful tool to deliver optimization of the carbon emissions of a project, where the system identifies the opportunity to revise project approach to achieve a carbon optimized design.

[0017] Using the project and non-project specific information 110, 132, along with the engineering and carbon emission rules 134, 136, and interactive engineering 150, the database 130 generates the deliverables 140 required for the completion of the carbon emissions estimation for each energy project. The deliverables 140 may include, but not be limited to, data analytics, scenario analysis and comparisons, and Power BI dashboard, or other equivalent commercially available software. [0018] Blockchain technology may be used throughout the system 100 to provide an immutable ledger of the development and history of the carbon emissions results for a project. All information entered via the user interface 120, interactive engineering activities 150, and database entries may be tracked on the blockchain network. Using smart contracts stored on the blockchain and executed automatically, when contractually defined conditions are achieved, including the production of deliverables 140, digital signatures are requested authorizing payment.

[0019] Referring to FIG. 2, there is shown a non-limiting embodiment of a method 200 according to the present disclosure for efficiently evaluating, optimizing and developing carbon emissions calculations for an infrastructure project.

[0020] At step 210, a set of engineering and carbon emission rules are compiled. Each rule represents a predetermined design decision that has generic application across two or more projects. As noted previously, these rules may embody regulatory requirements, conventional practices, etc. At step 220, the rules are encoded in the database. The database may be a cloud database. At step 230, non-project specific information is loaded into and stored in the database. This information, which may include costs and specifications, may be received from equipment suppliers, construction companies, and other entities that influence the carbon emissions of the energy project. At step 240, a user obtains project specific information for the infrastructure project. This information may be obtained during a physical inspection of the infrastructure project and also from public and/or private databases. At step 250, the project specific information is entered via a user interface into the database. At step 260, the set of carbon emission and engineering rules, the non-project specific information, the project specific information and other information are used to generate deliverables. The generated deliverables may have a level of detail that provides a preliminary estimation of the carbon emission footprint of an infrastructure project. Alternatively or additionally, at step 270, the deliverables may be used to hold workshop engagement activities to carry out interactive engineering to obtain the desired carbon emission results and decarbonize the project. It should be understood that steps 230/240 and 250 may be reordered as needed to suit a particular situation. Moreover, the information in the database 130 may be periodically or continuously updated. [0021] Referring now to FIG. 3, there is shown one non-limiting method 300 for utilizing the teachings of the present disclosure. At step 310, an infrastructure project is characterized using project-specific information and non-project specific information. For example, a project may be defined by, among other aspects, project specific information such as its physical location. A location’s remoteness from or proximity to resources may affect carbon costs attributed to travel of personnel to and from the site as well as shipment of materials to the site. Also, the geographical nature of the location may dictate how much carbon emitting materials, such as concrete, will be used during construction. An example of non-project specific information that may be defined at this stage is availability of shipping vessels owned and operated by third parties that are able to transport the weight of the final installation. At step 310, these and other ‘embodied’ or ‘indirect’ sources of carbon emissions are defined along with sources of ‘operational’ or ‘direct’ carbon emissions.

[0022] At step 320, a service life carbon footprint is estimated for the infrastructure project. This step may be performed by using the module 130 of FIG. 1. The service life carbon profile may include the estimated carbon emissions of several discrete carbon contributing components. The carbon contributing components may be associated with a planning and design phase 321, the fabrication and construction phase 322, the logistics and transportation phase 323, the operation and maintenance phase 324, the commissioning and start-up phase 325 and the decommissioning and dismantling phase 326. Each of these phases generates carbon-contributing components which may be a ‘direct’ component such as a fossil fuel burning engine used on-site or an ‘indirect’ component such as a fossil fuel burning vehicle that transports personnel or material to support planning, construction, or operation.

[0023] The estimation step 320 may utilize various types of information to estimate carbon emissions. For example, the total weight of the construction material required for the project will affect the amount of carbon emitted during transportation of such material to the project site. Also, the distance between the project site and procurement sites will affect the amount of carbon emitted during transportation activities. As a fabrication example, the number of weld points, identified in the design and planning phase, will affect the quantity of welds and the duration of the welding process which affects the amount of energy used and therefore the carbon emitted during fabrication. It should be understood that weld points are only exemplary of fabrication processes or techniques that can affect carbon emissions.

[0024] At step 330, one or more actions are based on the estimation of step 320. It should be appreciated that step 330 can occur at a point in time early enough to allow changes in all subsequent phases of the infrastructure project. One exemplary action may be to engage in a carbon profile engagement workshop (step 322) to, amongst other activities, review the estimated profile delivered in step 320, assess project decisions, preferences, and technology to re-design the project. Decisions made during the workshop (step 332) which leverage the interactive engineering capability 150 (FIG. 1) may be used to revise the project variables to create a more desirable carbon profile (step 334). But by considering inception to end of service life timeline as well as indirect carbon emissions, the method 300 provides a more holistic view of each such project. At step 340, the one or more actions are implemented.

[0025] Of course, the actions are not mutually exclusive. For example, after selecting a project, the information obtained at step 320 may be used to further reduce a carbon footprint. Furthermore, as the project progresses through its lifecycle phases and actual decisions made, such as equipment supply locations selected, design attributes finalized, fabrication methods and locations selected, decommissioning strategies and re-use / recycling methods implemented amongst others, the actual data associated to these decisions may be entered back into Step 310 to track the effect on carbon of each decisions and monitor the projects ability to deliver its carbon profile goals set out in step 340.

[0026] Upon completion of a project, its outturn carbon profile over its lifecycle may be stored and used as an on-going benchmark against which future projects of a similar nature, or producing a similar level of mega-joules of energy, may be compared and support future improvements to continuously lower the carbon profile of each subsequent project.

[0027] Referring to FIG. 4, there is shown a non-limiting embodiment of a method to improve a carbon emission lifecycle footprint of an energy project. As discussed previously, a proposed energy project may be defined by project-specific information 110 and non- project specific information 132. A set of engineering rules, an illustrative rule being labelled with numeral 134, may be used to generate deliverables, an illustrative deliverable being labelled with numeral 140. The deliverables 140 may be used to revise one or more features or aspects of the proposed energy project. Advantageously, the revisions may be implemented during the planning stage and before construction has commenced. Thus, the revisions may maximize decarbonization opportunities.

[0028] The foregoing description is directed to particular embodiments of the present disclosure for the purpose of illustration and explanation. It will be apparent, however, to one skilled in the art that many modifications and changes to the embodiment set forth above are possible without departing from the scope of the disclosure. It is intended that the following claims be interpreted to embrace all such modifications and changes.