Methods and apparatus to analyze emissions for industry operations

Abstract

Methods and apparatus to analyze emissions for industry operations include obtaining a definition of at least one of a first part, product, activity or usage, or service. Applicable emissions and activity data for the at least one of the first part, product, activity or usage, or service are identified. One or more differences between the at least one of the first part, product, activity or usage, or service and at least one of a second part, product, activity or usage, or service for which the applicable emissions data was collected are determined. Emissions for the at least one of the first part, product, activity or usage, or service are estimated by modifying the applicable emissions data based on the one or more differences, and the estimate emissions are presented.

Description

METHODS AND APPARATUS TO ANALYZE EMISSIONS FOR INDUSTRYOPERATIONSPRIORITY APPLICATION

[0001] This application claims priority to, and the benefit of the earlier filing date of U.S. provisional patent application entitled “METHODS AND APPARATUS TO ANALYZE EMISSIONS FOR OIL AND GAS OPERATIONS”, filed August 29, 2023, Serial Number 63 / 579,336, pursuant to 35 USC 119, the contents of all of which are incorporated herein by reference.BACKGROUND

[0002] Many companies have committed to reduce emissions associated with their products and / or services in line with the United Nations Sustainable Development Goals (SDGs) and / or the Paris Agreement of 2015.BRIEF DESCRIPTION OF THE DRAWINGS

[0003] The present disclosure is best understood from the following detailed description when read with the accompanying figures. It is emphasized that, in accordance with the standard practice in the industry, various features are not drawn to scale. In fact, the dimensions of the various features can be arbitrarily increased or reduced for clarity' of discussion.

[0004] FIGS. 1 A and IB illustrate an architecture of an emissions life cycle analyzer shown in an environment of use. according to an embodiment.

[0005] FIG. 2 illustrates a flowchart representative of a workflow for estimating emissions, according to an embodiment.

[0006] FIGS. 3A and 3B illustrate an example user interface that can be used to control the analysis engine of FIGS. 1 A and IB to obtain emission estimates, according to an embodiment.

[0007] FIG. 4 illustrates a schematic view of a computing system for performing at least a portion of the method(s) described herein, according to an embodiment.

[0008] Components of disclosed examples have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the examples of the disclosure so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.DETAILED DESCRIPTION

[0009] Illustrative examples of the subject matter claimed below will now be disclosed. In the interest of clarity, not all features of an actual implementation are described in this disclosure. It will be appreciated that in the development of any such actual implementation, numerous implementation-specific decisions can be made to achieve the developers’ specific goals, such as compliance with system-related and business-related constraints, which will vary from one implementation to another. Moreover, it will be appreciated that such a development effort, even if complex and time-consuming, would be a routine undertaking for those of ordinary skill in the art having the benefit of this disclosure.

[0010] Further, as used herein, the article “a” is intended to have its ordinary meaning in the patent arts, namely “one or more.” Moreover, examples herein are intended to be illustrative only and are presented for discussion purposes and not by way of limitation.

[0011] To meet emissions reduction goals, such as those set forth in the United Nations Sustainable Development Goals (SDGs) and / or the Paris Agreement of 2015, it is necessary to be able to compute an estimate of the carbon footprint associated with products and services along their entire life cycle. A carbon footprint can include carbon dioxide (CO2) or equivalent emissions. While existing software tools can be used to compute the emissions generated along the life cycle of a product or a service, use of existing tools can be very complex and requires a significant time investment. Use of existing tools typically requires a high level of expertise in emissions to understand their assumptions, methodologies, and quantity definitions. Such tools do not readily segregate high carbon footprint impact elements for which a high level of detail is needed from low carbon footprint impact elements which could be considered with less scrutiny. Two users of an existing tool can therefore come up with different emissions estimates for the same product or service.

[0012] Emissions life cycle analysis tools are disclosed herein that enable an expert for a particular product or service to easily (re-)quantify the emissions of the product or service along its life cycle in various life cycle phases using a simple user interface based on their knowledge of the product and / or sendee without having to be an expert in the computation of emission estimates. It has been found that disclosed tools provide estimate emissions that can be used to facilitate emissions reduction efforts, quantification of technologies enabling emission savings, computation / consohdation of corporate emissions and the understanding of those along the lifecycle, etc. According to certain embodiments, the emissions life cycle analysis tools may be used to associate a particular tool or service to its corresponding product carbon footprint.The disclosed emissions life cycle analysis tools can be used by users across a company or industry to provide consistent emissions estimates across parts, products, usages or activities, and / or services due to the ease of use. The disclosed emissions life cycle analysis tools allow users to easily estimate emissions across the life cycle of a product and / or service and. thus, can be used to provide visibility into the effects of efforts to reduce emissions and provide a competitive advantage in accelerating the path to reduced emissions (e.g., net zero emissions) for the energy industry by offering a reduced carbon footprint. Disclosed tools can be used to obtain a clearer picture of the life cycle phase(s) in which the impact on the environment will be the strongest, and to quantitatively evaluate the emissions impact of a design change or decision, for example. Disclosed tools can moreover be used to assess newly designed products, previous products, and / or competitors' products and their associated carbon footprints. Disclosed examples enable life cycle emissions estimates to become increasingly more accurate over time as further data is collected by using operational data representing actual historical usage and operational behaviors of products and services to estimate emissions. Disclosed life cycle analysis tools can be used to estimate emissions of, among other things, rigs for oil and gas operations according to operational states rig type, and other oil and gas operations related equipment such as burners, motors, utilities, wireline units, seismic activities, gas processing facilities, refineries, petrochemical plants, etc., or the like, in some implementations.

[0013] As used herein, “parts'’ refers to any component or item that is combined with other components or items in order to produce, manufacture, fabricate, or otherwise provide a “product”. For example, a circuit board may be a “product” which includes multiple different “parts” including transistors, capacitors, and resistors, among others. As used herein, “usage” or “activity” refers to an act, physical or otherwise, that when performed with multiple other acts provides a “service."’ For example, running an air conditioning unit for a specified amount of time is a “usage” or “activity’”, however maintaining a facility at a specified temperature using a cooling system having multiple air conditioning units is defined as a “service.”

[0014] Example Emissions Life Cycle Analyzer

[0015] FIGS. 1A and IB are a block diagram of an example emissions life cycle analyzer 100 in accordance with some implementations of the disclosure. The emissions life cycle analyzer 100 can be used to estimate emissions for a company’s parts, products, usages or activities, and / or services across the life cycle(s) of the parts, products, usages or activities, and / or services. According to certain embodiments, the emissions life cycler analyzer 100 incudes aone or more analysis engines 140 and a user interface 145 and can be connected, locally or through an internal or external network 125, to an emissions factor database 105, a data collector 110, and an activity database 135, in the example shown. The emissions life cycle analyzer 100 estimates emissions based on emissions data representing activity data and / or emissions factors stored in the example emissions factor database 105 and the activity database 135. The emissions data stored in the emissions factor database 105 can include historical, collected and / or actual emissions and / or emissions factors received from a primary emissions factor database 132 containing emissions data made available by other enterprises within the same industry, and from a secondary emissions factor database 131 containing emissions data set forth by industry standards, regulations, and / or third-party secondary emission factor providers. The data stored in the activity database 135 can include data or definitions related to actual parts, products, usages or activities, and / or services. Example data from the emission factor database 105 and the activity database 135 may be combined as to provide emissions for the extraction of a particular amount of a particular material, emissions resulting from historical usage of a particular part or product for a particular length of time, emissions computed for a particular part and / or product, emissions computed for actual transport of a particular part and / or product with a particular vehicle, or the like. While the emissions data stored in the emissions factor database 105 represents historical, collected, theoretical models, and / or actual emissions factors, for clarity of description, such data will simply be referred to herein as “emissions factor data”. Emissions factor data stored in the emissions factor database 105 is structured to enable the emissions life cycle analyzer 100 to estimate emissions for a part, product, usage or activity, and / or service with design and activities data that is stored in the activity’ database 135 for the same or similar parts, products, usages or activities, and / or services. The emissions life cycle analyzer 100 can use the emissions factor data stored in the emissions factor database 105 to estimate emissions for new, current, re-designed, modified, and / or future related or similar parts, products, usages or activities, and / or services, for example. The emissions factor data stored in the emissions factor database 105 can be hard- coded, and / or can be dynamically determined or adapted over time as additional data representing actual emission factors related to parts, products, usages or activities, and / or services is available. Emission estimates made by the emissions life cycle analyzer 100 using the emissions factor database 105 can accordingly become more accurate over time.

[0016] The emissions life cycle analyzer 100 includes the example data collector 110 that collects and aggregates emissions factor data related to actual parts, products, usages oractivities, and / or services into the emissions factor database 105. The data collector 110 can collect activity data for parts, products, usages or activities, and / or services from a plurality of internal or external databases which form the activity database 135 as seen in FIGS. 1A and IB. The activity database 135 can contain proprietary activity data for parts, products, usages, and / or services provided by a company. Example internal or external databases forming the activity database 135 include: a manufacturing database 120 storing data related to the manufacture and / or remanufacturing of parts, and / or products; a supply chain / procurement database 121 storing data related to the supply, procurement, and / or transport of parts and / or products; a usage database 122 storing data related to the usage of parts and / or products to provide services; a maintenance database 123 storing data related to the maintenance, and / or end-of-life activities for parts and / or products; or design data 150 that has been provided directly to the activity database 135. The data collector 110 can collect data from alternative and / or additional internal or external databases, and the internal or external databases accessed can change over time as new or alternate internal or external databases become available, for example. According to certain embodiments, the data collector 110 is communicated to a data allocation module 112 which is configured to allocate consolidated data, for example energy or material consumption from a facility for instance, to a particular or granular level process and product. The data collector 110 can collect data from the databases 120-123 and design data 150 via any number and / or type(s) of internal and / or external networks 125.

[0017] The data collector 110 can additionally and / or alternatively collect emissions data from a plurality of external databases forming the emission factors database 105. Example external databases include a secondary database 131 storing averaged or standardized emissions data applicable to broad range of materials, parts, products, manufacturing processes, etc. across a broad range of industries, and a primary7database 132 storing emissions data applicable to various aspects of a particular industry7, such as the oil and gas operations industry. Examples of the primary database 132 include technical datasheets, data based on a particular supplier generator set emissions technical data sheet, or any other data related to specific suppliers providing emissions data for particular products, or the like. Examples of the secondary database 131 include Carbonminds®, Ecoinvent®, GaBi®, Sustamize®, the EU Emission factor database, the Oil Production Greenhouse Gas Emissions Estimator (OPGEE), or the Intergovernmental Panel on Climate Change (1PCC). or the like. The data collector 110 can collect data from alternative and / or additional external databases 131, 132, and the external databases 131, 132 accessed can change over time as, for example, new or alternate externaldatabases 131, 132 become available. According to certain embodiments, the data collector 110 is communicated to a data retrieval module 111 which is configured to select the best option or most appropriate data from the emissions factor database 105 related to the actual parts, products, usages or activities, and / or services. The data collector 110 can collect data from the databases 131, 132 via the network(s) 125.

[0018] The emissions life cycle analyzer 100 includes the example activity database 135 that stores data representing various aspects of parts, products, usages and / or services and / or activity data representing past activities related to or usages of various parts and / or products. The activity database 135 can store the materials and dimensions used to make or manufacture parts and / or products, and how products are used, for example.

[0019] The emissions life cycle analyzer 100 includes the example analysis engines 140 that estimates emissions for a particular part, product, usage or activity, and / or service defined by the user via the example user interface 145. According to certain embodiments, the analysis engine 140 includes a modeling module 142 for performing different tasks ranging from but not limited to a simple multiplication of selected emissions factors by correct activity data provided by the data retrieval module 111 and / or the data allocation module 112. to more complex outputting of proprietary emission factors that would be multiplied by applicable activity data. According to certain embodiments, the analysis engine 140 may also include a standards computation module 141 which is configured to adapt the final results to be compliant to different sets of rules, such as though guided by different emerging standards, guidelines, or regulations. Therefore, when the standards computation module 141 is used, the final result provided by the analysis engine 140 can be standards or regulations specific.

[0020] The user provides a product or sendee definition 151 of one or more parts, products, usages or activities, and / or services to be analyzed, but does not have to know or provide emissions factor data and / or activities data for the defined part(s), product(s), usage(s), and / or service(s). The definition 151 can also include a selection of one or more life cycle phases for which emissions estimates are to be provided. Example life cycle phases include (i) procurement of raw materials, (ii) pre-processing of parts, (iii) manufacturing of parts and products, (iv) transport of parts and products, (v) usage of parts and products, (vi) remanufacturing of parts and products, and (vii) end-of-life activities. The user can provide the definition 151 via a computing device 155 that the user uses to access the user interface 145. The user can manually create the definition 151 and use it in conjunction with the activity database 135 via the user interface 145 to obtain activity details regarding the defined part(s),product(s), usage(s), and / or service(s) and / or to obtain the type(s), material(s) used, and / or dimensions of a part or product, for example. Alternatively, the user need only provide a reference or part number for a part and / or product, and a technical details computation engine 152 communicated to the analysis engine 140 obtains the technical details, on behalf of the user, from design data 150 stored in the activity database 135 as seen in FIGS. 1A and IB.

[0021] The analysis engine 140 may obtain applicable emissions factor data from the emissions factor database 105 through the data retrieval module 111, or based on the definition 151 manually selected by a user via the user interface 145 and / or activity’ or design details obtained from the activity database 135 based on aspects of the definition 151, and uses the applicable activities data to compute emission estimates for the life cycle phase(s) selected by the user for the defined part(s), product(s), usage(s), and / or service(s). According to certain embodiments, the analysis engine 140 obtains and uses that emissions factor data to estimate emissions for the defined part(s). product(s). usage(s), and / or service(s) when the defined part(s). product(s), usage(s), and / or service(s) have corresponding emissions factor data in the emissions factor database 105. The analysis engine 140 obtains and uses emissions factor data for similar or related part(s), product(s), usage(s). and / or service(s) to estimate emissions for the defined part(s), product(s). usage(s). and / or service(s) when the defined part(s), product(s), usage(s), and / or service(s) do not have associated emissions factor data in the emissions factor database 105.

[0022] The data retrieval module 111 can identify applicable emissions factor data in the emissions factor database 105 by querying the emissions factor database 105 for the defined part(s). product(s), usage(s), and / or service(s) and by using appropriate selection and prioritization algorithms based on the type of data. The data retrieval module 1 1 1 can additionally and / or alternatively identify applicable emissions factor data in the emissions factor database 105 by querying the emissions factor database 105 based on one or more aspects of the defined part(s), product(s). usage(s). and / or service(s) provided by a user and / or obtained from the activity database 135. According to certain embodiments, the data retrieval module 111 may also adjust the identified emissions factor data according to the one or more aspects. Example aspects include type of product, material(s) used, dimensions, usage(s), and / or service(s).

[0023] The data retrieval module 111 can estimate emission factors for a defined part, product, usage, activity, and / or service by scaling the emissions factor data obtained from the emissions factor database 105 based on differences between the defined part, product, usage or activity7and / or sen ice and the part, product, usage or activity, and / or service associated with the emissions factor data. For example, an emissions factor for a generator could be scaled based on its efficiency, etc. The emissions associated with the acquisition of raw stainless steel used to make a part can be adjusted based on the carbon intensity of the plant it has been produced in and the emissions associated with a generator can be scaled based on an amount of fuel burned per period of time, and an efficiency, for example.

[0024] The analysis engine 140 provides or presents estimated emissions for the defined part, product, usage or activity and / or service to a user via the user interface 145. The analysis engine 140 can break down the estimated emissions by part, product, usage or activity, service, and / or life cycle phase. The analysis engine 140 can provide or present the estimated emissions in a table and / or a graph, for example.

[0025] The analysis engine 140 can have a modeling module 142 for computing emission estimates for various different types of parts, different life cycle phases, different types of activities, different ty pes of transport, etc., in some implementations, according to different sets of rules established by applicable standards, guidelines, or regulations using the standards computation module 141 which may adapt the final computed emission estimates to known standards, or guidelines.

[0026] The emissions factor database 105 stores emissions data obtained for at least one of a first part, a first product, a first usage or activity, or a first service in an example. According to certain embodiments, the analysis engine 140 may be configured to obtain, via the user interface 145, design data 150 of at least one of a first part, a first product, a first usage or activity, or a first service, the design data including one or more technical details of at least one of the first part, the first product, the first usage or activity, or the first service, and identify, in the emissions factor database 105, the applicable emissions data based on the one or more design details. The analysis engine 140 is configured to: (i) obtain, via the user interface 145, design data 150 of at least one of a second part, a second product, a second usage or activity, or a second service, the design data including one or more design details of at least one of the second part, the second product, the second usage or activity7or the second service; (ii) identify, in the emissions factor database 105, the applicable emissions data based on the one or more design details through the data retrieval module 111; (iii) determine one or more differences between at least one of the first part, the first product, the first usage or activity or the first service and at least one of the second part, the second product, the second usage or activity or the second sendee; (iv) estimate emissions for at least one of the second part, the secondproduct, the second usage or activity or the second service by modifying the applicable emissions data based on the one or more differences; and (v) present, via the user interface 145, the estimated emissions for the at least one of the second part, the second product, the second usage or activity or the second service, for example. According to certain embodiments, the design data 150 may be obtained by either the user manually entering the design data as a product or service definition 151 via the user interface 145, or via the technical details computation engine 152 which is configured to feed the design data through to the analysis engine 140.

[0027] Example Methods for Estimating Emissions

[0028] FIG. 2 is a flowchart 200 representative of an example method for estimating emissions, in accordance with the disclosure. The method of FIG. 2 starts with the analysis engine 140 or, more generally, the emissions life cycle analyzer 100 obtaining a product or service definition 151 of at least one of a first part, a first product, a first usage or activity, or a first service for which emissions estimates are to be determined (block 202). The definition 151 is obtained from a user via the user interface 145 of FIGS. 1A and IB, for example, or from design data 150 that forms part of the activity database 135 via the technical data computation engine 152, according to certain embodiments. The selection(s) of one or more life cycle phases for which emissions estimates are to be determined are obtained (block 204). The selection(s) are obtained via the user interface 145 of FIGS. 1A and IB, for example. One or more design details of the definition 151 can be obtained from the user via the user interface and / or from the activity databasel35 based on the definition 151 and / or the selected life cycle phases (block 206). The analysis engine 140 can obtain the technical details from the activity database 135 based on one or more aspects of the definition 151 and / or one or more aspects of the selected life cycle phases.

[0029] The analysis engine 140 or, more generally, the emissions life cycle analyzer 100 obtains applicable emissions data from the emissions factor database 105 and activities data from the activity database 135 for at least one of the first part, the first product, the first usage or activity or the first service (block 208). The applicable emissions data can be identified in the emissions factor database 105 by, for example, query ing the emissions factor database 105 based on one or more technical details of at least one of the first part, the first product, the first usage or activity, or the first service via the data retrieval module 111. The applicable activities data can be identified in the activity7database 105 by, for example, querying the activitydatabase 105 based on one or more manufacturing details of at least one of the first part, the first product, the first usage or activity, or the first service via the data allocation module 112.

[0030] The data retrieval module 111 or, more generally, the emissions life cycle analyzer 100 estimates emissions for at least one of the first part, the first product, the first usage, or the first service by scaling, adjusting, modeling, or selecting the best available option from the emissions factor database 105 based on one or more differences. The emissions associated with the acquisition of raw stainless steel used to make a part can be scaled based on the energy mixed or the processes used in manufacturing the raw material, and the emissions associated with a generator can be scaled based an amount of fuel burned per period of time, and / or an efficiency, for example.

[0031] According to certain embodiments, the analysis engine 140 or, more generally, the emissions life cycle analyzer 100 determines an absolute emissions assessment, or a total emissions output or value for at least one of the first part, the first product, the first usage or activity or the first service (block 210). As used herein, an absolute emissions value refers to the total calculated emissions associated with a selected part, product, usage, or service over a period of time or selected life cycle phase of the part, product, usage, or service. For example, an absolute emissions value may relate to the emissions that are produced when a particular part of an engine is manufactured and then transported to a facility for installation, or to the total emissions produced by a generator over the course of its functional life while disposed on an offshore oil rig or other facility. The analysis engine 140 may then perform at least a second assessment wherein the analysis engine 140 determines one or more differences between at least one of the first part, the first product, the first usage or activity', or the first service and at least one of a second part, a second product, a second usage or activity, or a second service for which the applicable emissions data was collected (block 212). According to certain embodiments, the analysis engine 140 may determine an absolute emissions assessment to provide a first total emissions output or value for at least one of the first part, the first product, the first usage or activity or the first service, a second total emissions output or value for at least one of the second part, the second product, the second usage or activity- or the second service, and then comparing the first and second emissions output or value.

[0032] The estimated emissions are presented or provided via the user interface 145 to the user as a table and / or graph, for example (block 214). According to certain embodiments, a action may be performed based upon or in response to the estimated emissions. The action may be or include generating and / or transmitting a signal (e.g., using a computing system) that instructsor causes a physical action to occur at the facility or another facility. The action may also or instead include performing the physical action at the facility, or another facility. The physical action may include replacing, improving, adjusting, discontinuing, or implementing one or more parts, products, usages, or services disposed on or associated with the facility.

[0033] Example User Interface

[0034] FIGS. 3A and 3B is an example user interface 300 that can be used to implement the example user interface 145 of FIGS. 1 A and IB. A user can use the user interface 300 to interact with the analysis engine 140 of FIGS. 1A and IB to obtain emission estimates for one or more defined part(s). product(s). usage(s) or activity(-ies). and / or services(s) for one or more selected life cycle phases. Emission estimates may be computed based on one or more data entry fields of the user interface 300 that define one or more parts, products, usages or activities, sendees, and / or life cycle phases for which emissions estimates are to be computed.

[0035] According to certain embodiments, the user interface 300 includes a plurality of check boxes 310 which can be used to select life cycle phases for which emissions estimates are to be computed. A check box 311 enables computation of emissions estimates for a raw materials acquisition phase, a check box 312 enables computation of emissions estimates for a preprocessing phase, and a check box 313 enables computation of emissions estimates for a manufacturing phase. A check box 314 enables computation of emissions estimates for transport phases, a check box 315 enables computation of emissions estimates for a usage or operation phase, and a check box 316 enables computation of emissions estimates for a maintenance phase. A check box 317 enables computation of emissions estimates for a remanufacturing phase and a check box 318 enables computation of emissions estimates for an end-of-life activities phase. The check boxes 31 1-318 enable or activate the modeling module 142 and / or the standards computation module 141 of the analysis engine 140 that compute estimate emissions for the associated life cycle phase, in some implementations. Each of the check boxes 311-318 are checked such that emissions are to be estimated for each of the life cycle phases, in the example shown.

[0036] According to certain embodiments, the user interface 300 includes an example output table 330 and an example graph 335 that provide or depict the emissions estimated for each of the selected life cycle phases. The graph 335 graphically presents the emissions estimates shown in the table 330. The table 330 has a plurality of columns 340 for the life cycle phases corresponding to the check boxes 311-318. Each column 340 of the table 330 reflects both (a) estimated emissions for the respective life cycle phase itself, and (b) estimated emissions fortransportation associated with the respective life cycle phase. For example, for the preprocessing life cycle phase, an entry' 341 of the table 330 reflects that the pre-processing life cycle phase is estimated to cause 343 kg of CO2 emissions or its equivalents, and an entry 342 of the table 330 reflects that transport associated with the pre-processing life cycle phase is estimated to cause 271 kg of CO2 emissions or its equivalents. The results in each column of the table 330 for the estimated emissions for the respective life cycle phase itself can be computed by respective modules 141, 142 of the analysis engine 140, in some implementations.

[0037] The user interface 300 includes another example output table 350 that provides or depicts the estimated emissions of defined part(s). product(s), usage(s) or activity (— ies) and / or service(s) cumulatively across all of the life cycle phases selected by the check boxes 311-318. According to certain embodiments, the output table 350 may be adjusted by the standards computational module 141 to different sets of rules defined by different standards, guidelines, or regulations. An entry’ 355 of the table 350 reflects that an estimated 3,968 kg of CO2 emissions or its equivalents will occur across the selected lifecycle phases of the defined part(s), product(s), usage(s), service(s) and an entry' 360 of the table 350 reflects that transport will cause an additional estimated 64 kg of CO2 or its equivalents for transportation across the selected lifecycle phases of the defined part(s), product(s), usage(s) or activity(-ies). and / or service(s), for example. An entry 365 of the table 350 reflects that the defined part(s), product(s), usage(s) or activity(-ies), and / or service(s), across the selected life cycle phases will, thus, cause a cumulative net of 4,032 kg of CO2 or its equivalents across the selected lifecycle phases. The output table 350 includes estimated emissions 380 broken down by or normalized by year, and estimated emissions 390 for a fleet of units, in some implementations.

[0038] According to certain embodiments, the user interface 300 also includes a plurality' of check boxes 370 that can be used to select which aspects of the usage life cycle phase are to be included in emissions estimated for the usage life cycle phase. A check box 371 enables inclusion of computed emissions estimates for rig emissions including drill and idle activities, a check box 372 enables inclusion of computed emissions estimates for burners, and a check box 373 enables inclusion of computed emissions estimates for flaring and / or venting. A check box 374 enables inclusion of computed emissions estimates for artificial lift motors and a check box 375 enables inclusion of computed emissions estimates for utility consumption. A check box 376 enables inclusion of computed emissions estimates for wirelines units and a check box 377 enables inclusion of computed of emissions estimates for seismic activities. There can be additional check boxes in other implementations that enable emissions estimates for otherforms of usage, such as production activities, refining activities, gas processing activities, chemical plant activities, fluid related activities, petrochemical related activities, or the like. The check boxes 371-377 enable or activate respective modules 141, 142 of the analysis engine 140 that compute estimate emissions for the associated activities of the usage life cycle phase, in some implementations. The check boxes 371 and 374 are checked such that emissions for the usage life cycle phase as enabled by the check box 315 are to include just rig emissions and artificial lift motors, in the example shown.

[0039] Estimated Emissions for Raw Materials Acquisition Life Cycle Phase

[0040] When the check box 311 of FIG. 3 A is checked, one or more modules 141, 142 ofthe analysis engine 140 and / or, more generally, the analysis engine 140 computes emission estimates for one or more defined part(s), product(s), usage(s), and / or services(s) for a raw materials acquisition life cycle phase.

[0041] The module(s) 141, 142 and / or the analysis engine 140 can present one or more user interfaces 145 that include a plurality of data entry fields that can be used to define one or more mechanical parts or parameters, for example those associated with check boxes 370, used as part of a product, used in an activity', and / or used to provide a service. A portion of the data entry fields can have values entered or provided by a user to specify one or more physical aspects of the parts such as to specific materials and dimensions, for example. Alternatively, the data entry' fields can be filled in part or in whole by the analysis engine 140 in response to an identification of a part, product, activity', sendee, and / or usage by a user in the design data 150, for example.

[0042] The module(s) 141, 142 and / or the analysis engine 140 can compute, for each part, an amount of raw materials that must be acquired to manufacture the part based on the dimensions, materials, and the types of mechanical processes involved, for example. In certain embodiments, the technical data computation engine 152 may compute the total weight of material, including any waste portions, that may be required based on the dimensions of the part and its associated manufacturing process. According to certain embodiments, the amount of required raw materials may be part of the design data 150 that is either entered manually by a user via the user interface 145 or computed by the technical data computation engine 152. The module(s) 141, 142 and / or the analysis engine 140 may compute based on the dimensions of the part and associated processes, a total weight of material (including waste) that is used to manufacture the part. Based on the amount of raw material for each part, an estimated amount of emissions can be computed for each part based on a ratio of emissions to amount of material,as reflected in the emissions factor database 105. A total estimated emissions to obtain all raw materials can be computed by summing together the estimated emissions for each part. The total estimated emissions for the raw materials life cycle phase is reflected in the output table 330 and graph 335, as discussed above.

[0043] Estimated Emissions for Pre-Processing Life Cycle Phase

[0044] When the check box 312 of FIG. 3A is checked, one or more modules 141, 142 of the analysis engine 140 and / or, more generally, the analysis engine 140 computes emission estimates for one or more defined part(s), product(s), usage(s), and / or services(s) for a preprocessing life cycle phase, that is, the making of parts that will be assembled into a product. The estimated emissions are associated with any processing done at suppliers before assembly takes place, which can vary7with country, for example.

[0045] The module(s) 141, 142 and / or the analysis engine 140 can compute for each of the mechanical parts specified as discussed above in the raw materials life cycle phase, for example, estimated emissions associated with machining or processing of the raw materials to form each of the parts, landfill emissions associated with disposal of any removed materials, and other processing of waste materials including but not limited to recycling. A total estimated emissions to pre-process all the materials for all the parts can be computed by summing together the estimated emissions for pre-processing for each part. The emissions can be estimated based on emissions data associated with material removal and disposal, as reflected in the emissions factor database 105.

[0046] The module(s) 141, 142 and / or the analysis engine 140 can present one or more other user interfaces 145 having a plurality- of data entry fields that can be used to define one or more circuit boards used as part of a product, used for an activity, and / or used to provide a service. A portion of the data entry fields can be used by a user to specify one or more physical aspects of the circuit boards such as to specific materials, type, number of layers, and dimensions, for example. Alternatively, the data entry fields can be filled in part or in whole by the analysis engine 140 in response to an identification of a particular circuit board.

[0047] The module(s) 141, 142 and / or the analysis engine 140 can compute an estimated amount of emissions for making each circuit board based on a ratio of emissions for the same or similar circuit boards, as reflected in the emissions factor database 105 and based on the data entry fields. A total estimated emissions to make all the circuit boards can be computed by summing together the estimated emissions for each circuit board.

[0048] The user interface(s) and / or one or more additional user interfaces can have a plurality of additional data entry fields for defining one or more physical aspects of respective wiring harnesses used as part of a product, the ty pe and number of components used in the product, used for an activity, and / or used to provide a service. The additional data entry fields can be filled in by a user and / or be filled in part or in whole by the analysis engine 140 based on the activity database 135, the emissions factor database 105, and / or the design data 150 in response to an identification of a particular wiring harness.

[0049] The module(s) 141, 142 and / or the analysis engine 140 can compute an estimated amount of emissions for making each wiring harness based on a ratio of emissions for the same or similar wiring harness and the type and number of components used in the product, as reflected in the emissions factor database 105 and based on the additional data entry' fields. A total estimated emissions to make all the wiring harnesses can be computed by summing together the estimated emissions for each wiring harness.

[0050] A total estimated emissions for all of the pre-processing of materials can be computed by summing together the estimated emissions for each of the pre-processing activities described above. The total estimated emissions for the pre-processing life cycle phase is reflected in the output table 330 and graph 335, as discussed above.

[0051] Estimated Emissions for Manufacturing Life Cycle Phase

[0052] When the check box 313 of FIG. 3A is checked, one or more modules 141, 142 of the analysis engine 140 and / or, more generally, the analysis engine 140 computes emission estimates for one or more defined part(s), product(s), usage(s), and / or services(s) for a manufacturing life cycle phase, that is, the making or assembly of parts into a product.

[0053] The module(s) 141 , 142 and / or the analysis engine 140 can compute emissions estimates based on the amount of time, energy', or material spent during assembly and any related activities required to complete an assembly. The translation from an assembly duration and material spent to CO2 equivalent emissions can be based on standard emissions rates for a facility in North America or other specified facility, for example.

[0054] The module(s) 141, 142 and / or the analysis engine 140 can present one or more other user interfaces 145 having a plurality' of data entry' fields that can be used to define a number of units to be manufactured, an indicated manufacturing center, and an estimated percentage usage of the manufacturing center to make all of the units or the specific usage for a product line, for example. According to certain embodiments, the module(s) 141, 142 may propose a set of processes to the users with associated emission factors from the emission factors database105, or alternatively, the module(s) 141, 142 may propose a set of processes to the users with associated emission factors from proprietary emission factors, for example computed by the analysis engine 140 in conjunction with the computations enabled by the data allocation module 112 to allocate facility data to a specific process, product and / or service.

[0055] The module(s) 141, 142 and / or the analysis engine 140 can compute an estimated amount of CO2 emissions or its equivalents based on the specified number of units to be manufactured, an indicated manufacturing center, and the estimated percentage usage of the manufacturing center to make all of the units or the specific usage for a product line. The module(s) 141, 142 and / or the analysis engine 140 can query a table of emissions data for various manufacturing centers based on the indicated manufacturing center to obtain yearly emissions associated with the indicated manufacturing center, and scale the yearly emissions based on the number of units, the estimated usage, or a specified usage. The data can be obtained from the emissions factor database 105 and the activity’ database 135, for example. The estimated emission for the manufacturing life cycle phase is reflected in the output table 330 and graph 335, as discussed above.

[0056] Estimated Emissions for Transport

[0057] When the check box 314 of FIG. 3A is checked, one or more modules 141, 142 of the analysis engine 140 and / or, more generally, the analysis engine 140 computes emission estimates for one or more defined part(s), product(s), usage(s), and / or services(s) for transport of goods, parts, products, etc.

[0058] The module(s) 141, 142 and / or the analysis engine 140 can compute estimated emissions associated with transportation for various phases of a life cycle, as shown in FIG. 3A. Estimated emissions are computed for typical cycles of transportation for a product life cycle. Wherever that does not make sense for a product and / or life cycle phase, transport distances of zero can be provided.

[0059] The module(s) 140 and / or the analysis engine 140 can compute estimated emissions for transporting raw materials to a pre-processing center, estimated emissions for transporting parts to a manufacturing center, estimated emissions for transporting products from the manufacturing center to an operations site and / or another site, estimated emissions for transporting products to a client location, estimated emissions for transportation related to, for example, a manufacturer or a maintenance site for maintenance activities, estimated emissions for transportation related to re-manufacturing activities, and / or estimated emissions for transportation related to end-of-life activities. The estimated emissions are computed based onthe part and / or product information described above, and based on entered transport information which can be retrieved from the emissions factor database 105 and the activity database 135. Example transport information includes a number of trips, a transport distance, and transport method indications which could retrieved from the activity database 135, while emission factor data is collected from the emission factors database 105. The estimated emissions for transportation are reflected in the output table 330 and graph 335, as discussed above.

[0060] The module(s) 141. 142 and / or the analysis engine 140 can estimate emissions associated with road vehicles using the emissions factors given by the GHG protocol which can be retrieved from the emissions factor database 105 and the secondary emission database 131 , for example.

[0061] Estimated Emissions for Usage Life Cycle Phase

[0062] When the check box 315 of FIG. 3 A is checked, one or more modules 141, 142 of the analysis engine 140 and / or, more generally, the analysis engine 140 computes emission estimates for one or more defined part(s), product(s), usage(s) or activity (-ies), and / or services(s). The module(s) 141, 142 and / or the analysis engine 140 can compute estimated emissions for the usage life cycle phase for each of the usage or activities (e.g., rig operation, burner operation, venting / flaring, artificial lift motors, utility consumption, wireline trucks, seismic equipment, etc.) selected by the check boxes 370.

[0063] The module(s) 141, 142 and / or the analysis engine 140 can present one or more user interfaces 145 in which a user can enter a variety of information related to usage of goods, parts, and / or products. The information can alternatively be populated by the analysis engine 140 based on information stored in the activity database 135 and / or the product or sendee definition 151. Example entered information includes a type of fuel used to power a generator, a mud type, an indication of whether mud gaseous releases are vented or flared, an operation time, a casing cementing duration, distances between sites for crew, distances between sites for equipment, percentages of time spent tripping, drilling, circulating off-bottom and idle, and a distribution of job across different rig types.

[0064] The module(s) 141, 142 and / or the analysis engine 140 can compute estimated emissions for each of the activities selected with the check boxes 370. According to certain embodiments, the emissions estimate for an activity can be computed by multiplying an emissions factor related to the activity for a specified ty pe of facility, for example a rig, as reflected in the emissions factor database 105 or provided by the modeling module 142, by theduration of the activity as defined in, for example, the activity database 135. A total estimated emissions for all of the usage or activities can be computed by summing together the estimated emissions for each activity. The total estimated emission for the usage life cycle phase is reflected in the output table 330 and graph 335, as discussed above.

[0065] The module(s) 141, 142 and / or the analysis engine 140 can compute generator emissions as part of the computed emissions estimates for rig emissions including drill and idle activities when check box 371 is enabled using generator emissions factors derived from emissions factor data obtained from the emission factor database 105 for various combinations of generator type and fuel type, and converting power consumption to gas emissions using the emissions factors. Alternatively, emissions factors found in Stanford Calculator "OPGEE" - Oil Production Greenhouse Gas Emissions Estimator - originating from GREET - Greenhouse Gases, Regulated Emissions and Energy use in Technologies Model" and relying on Caterpillar Generator Set technical data sheets can be used.

[0066] The module(s) 141, 142 and / or the analysis engine 140 can estimate emissions as part of the computed emissions estimates for rig emissions including drill and idle activities when check box 371 is enabled that are associated with drilling activities by categorizing drilling activities into multiple groups, each group having a specific emission factor, in order to use emissions data collected during past drilling activities, for example. The emissions for a particular activity can be estimated by multiplying the proprietary emissions factor for the activity with the duration of the activity without the use of technical data sheets or outside sources for emission factors. Example groups are (i) drilling, (ii) circulating off bottom, and (iii) tripping. Times for these activities can be computed as:Drilling hours = Rotary Drilling hours + Sliding hours + Reaming hours Circulating off bottom= Pumping hours — Sliding hours — Reaming hours— Rotary Drilling hoursTripping hours = BRT hours — Pumping hours

[0067] The module(s) 141, 142 and / or the analysis engine 140 can compute fuel consumption per rig type, drilling activity type and duration using a table of fuel consumption amounts per unit of time for various combinations of activity type (e.g., tripping, drilling, circulating off- bottom, cementing, and idle) and rig type. The CO2 generation per rig type and drilling activity can be computed by converting fuel consumption to CO2 or its equivalents by multiplying thevolume of fuel consumed by hour with the CO2 or equivalent emissions per volume of fuel consumed.

[0068] The module(s) 141, 142 and / or the analysis engine 140 can compute overall CO2 emissions or its equivalents as:E CO2 ^Driling ^Drilling 4 ^^Tripping ^Trippingwhere EFXare the emission factors described above, and txis the duration of each activity.

[0069] The module(s) 141, 142 and / or the analysis engine 140 can estimate the emissions associated with mud degassing based on a CH4 emissions factor (tonnes CH4 / drilling days) as defined in the emissions factor database 105 and / or by the EP A. and, when the gas is flared, total combustion of the CH4 can be assumed. Accordingly, if venting, the module(s) 141, 142 and / or the emissions factor database 105 can estimate CH4 emissions generated during a period of time by multiplying an emissions factor that is based on the type of mud used with a global warming potential factor GWP for CH4. Alternatively, if flared, the module(s) 141. 142 and / or the emissions factor databasel05 can estimate the CO2 emissions or its equivalents produced by the complete combustion of the generated CH4. Assuming the reaction is CEU + 2O2 CO2 + 2 H2O, for each mole of burnt CH4 we get a mole of CO2, and the module(s) 141, 142 and / or the emissions factor databaselO5 can estimate CO2 emissions or its equivalents as the multiplication of CPU emissions by the ratio of the CO2 molar weight and the CH4 molar weight.

[0070] Estimated Emissions for Maintenance Life Cycle Phase

[0071] When the check box 316 of FIG. 3A is checked, one or more modules 141, 142 of the analysis engine 140 and / or, more generally, the analysis engine 140 computes emission estimates for one or more defined part(s), product(s), usage(s), and / or services(s) for maintenance of goods, parts and products.

[0072] The module(s) 141, 142 and / or the analysis engine 140 can present one or more user interfaces 145 having a plurality of data entry fields that can be used to specify projected maintenance activities. Data for the data entry fields can be populated by a user and / or the analysis engine 140 based on information stored in the activity database 135 and / or the product or service definition 151, for example. Example maintenance activities include a number of replacement parts per year, and other aspects of replacement parts.

[0073] The module(s) 141, 142 and / or the analysis engine 140 can compute estimated emissions for each of the projected maintenance activity, and can compute a total emissions estimate that is a sum of the per activity estimated emissions. The estimated emissions can be computed by multiplying emissions factors for example from the pre-processing life cycle phase and data defining the maintenance activities, while in certain embodiments the maintenance related emissions may be calculated independently from the pre-processing life cycle phase or any other phase. The module(s) 141, 142 and / or the analysis engine 140 can also compute estimated emissions related to assembly / disassembly of the parts for the projected maintenance activities independently, or according to certain embodiments, as described above in connection with, for example, the manufacturing life cycle phase. In certain embodiments, assembly / disassembly could include energy consuming activities such as testing or heating boards in an oven. A total estimated emissions for all projected maintenance activities can be computed by summing together the estimated emissions for each activity. The total estimated emission for the maintenance life cycle phase is reflected in the output table 330 and graph 335, as discussed above.

[0074] Estimated Emissions for Re-Manufacturing Life Cycle Phase

[0075] When the check box 317 of FIG. 3 A is checked, one or more modules 141, 142 of the analysis engine 140 and / or, more generally, the analysis engine 140 computes emission estimates for one or more defined part(s), product(s), usage(s), and / or services(s) for remanufacturing of goods, parts and products.

[0076] The module(s) 141, 142 and / or the analysis engine 140 can present one or more user interfaces 145 having a plurality of data entry fields that can be used by a user to provide projected numbers of parts that will be needed for re-manufacturing a product. The data entry fields can alternatively be populated by the analysis engine 140 based on information stored in the activity database 135 and / or the product or service definition 151. The data entry' fields and / or the product or service definition 151 can also specify a number of times the product will be re-manufactured, and relative effort or complexity to re-manufacture the product compared to initial manufacture. According to certain embodiments, the data entry' fields could also be used to calculate an absolute emissions estimate that is either dependent or independent from initial manufacturing assessments.

[0077] The module(s) 141, 142 and / or the analysis engine 140 can compute estimated emissions associated with each specified replacement part, and can compute total emissions for replacement parts which is a sum of the estimated emissions for each replacement part asdescribed above in connection with or independently from the pre-processing life cycle phase, according to certain embodiments. Estimated emissions associated with disassembly, cleaning, testing, qualifying, and assembly can be computed independently, or according to certain embodiments, by scaling the manufacturing estimate described above, according to one particular embodiment, with the specified relative effort or complexity. The module(s) 141, 142 and / or the analysis engine 140 can compute total estimated emissions for all projected remanufacturing activities by summing together the estimated emissions for the replacement parts, and estimated emission for disassembly, cleaning, testing, qualifying, and assembly. The total estimated emissions for the re-manufacturing life cycle phase is reflected in the output table 330 and graph 335, as discussed above.

[0078] Estimated Emissions for Disposal Life Cycle Phase

[0079] When the check box 318 of FIG. 3A is checked, one or more modules 141, 142 of the analysis engine 140 and / or, more generally, the analysis engine 140 can compute emission estimates for one or more defined part(s), product(s), usage(s), and / or services(s) for end-of- life activities for goods, parts, and products.

[0080] The module(s) 141, 142 and / or the analysis engine 140 can compute estimated emissions to dispose of each of the parts used to assemble a product based on the materials and the amounts of materials used for each part as discussed above in connection with the raw materials life cycle phase. Alternatively, emissions factors for other types of end-of-life activities can be used to estimate emissions for each part based upon a respective type of end- of-life activity that is specified to be applied to each part. For example, circularity related processes for the computation may be taken into account when calculating emissions for end- of-life activities in case the material is recycled. A total estimated emissions for all projected disposal activities can be computed by summing together the estimated emissions for each disposal activity. The total estimated emission for the disposal life cycle phase is reflected in the output table 330 and graph 335, as discussed above.

[0081] Example Processing Platform

[0082] In some embodiments, the methods of the present disclosure may be executed by a computing system. FIG. 4 illustrates an example of such a computing system 400, in accordance with some embodiments. The computing system 400 may include a computer or computer system 401 A, which may be an individual computer system 401 A or an arrangement of distributed computer systems. The computer system 401A includes one or more analysis modules 402 that are configured to perform various tasks according to some embodiments,such as one or more methods disclosed herein. To perform these various tasks, the analysis module 402 executes independently, or in coordination with, one or more processors 404, which is (or are) connected to one or more storage media 406. The processor(s) 404 is (or are) also connected to a network interface 407 to allow the computer system 401 A to communicate over a data network 409 with one or more additional computer systems and / or computing systems, such as 401B, 401C, and / or 401D (note that computer systems 401B, 401C and / or 401D may or may not share the same architecture as computer system 401A, and may be located in different physical locations, e g., computer systems 401A and 401B may be located in a processing facility, while in communication with one or more computer systems such as 401 C and / or 40 ID that are located in one or more data centers, and / or located in varying countries on different continents).

[0083] A processor may include a microprocessor, microcontroller, processor module or subsystem, programmable integrated circuit, programmable gate array, or another control or computing device.

[0084] The storage media 406 may be implemented as one or more computer-readable or machine-readable storage media. Note that while in the example embodiment of FIG. 4 storage media 406 is depicted as within computer system 401 A, in some embodiments, storage media 406 may be distributed within and / or across multiple internal and / or external enclosures of computing system 401 A and / or additional computing systems. Storage media 406 may include one or more different forms of memory including semiconductor memory' devices such as dynamic or static random access memories (DRAMs or SRAMs), erasable and programmable read-only memories (EPROMs), electrically’ erasable and programmable read-only memories (EEPROMs) and flash memories, magnetic disks such as fixed, floppy and removable disks, other magnetic media including tape, optical media such as compact disks (CDs) or digital video disks (DVDs), BLURAY® disks, or other types of optical storage, or other ty pes of storage devices. Note that the instructions discussed above may be provided on one computer- readable or machine-readable storage medium, or may be provided on multiple computer- readable or machine-readable storage media distributed in a large system having possibly plural nodes. Such computer-readable or machine-readable storage medium or media is (are) considered to be part of an article (or article of manufacture). An article or article of manufacture may refer to any manufactured single component or multiple components. The storage medium or media may’ be located either in the machine running the machine-readableinstructions, or located at a remote site from which machine-readable instructions may be downloaded over a network for execution.

[0085] In some embodiments, computing system 400 contains one or more artificial intelligence module(s) 408. In the example of computing system 400, computer system 401 A includes the artificial intelligence module 408. In some embodiments, a single artificial intelligence module may be used to perform some aspects of one or more embodiments of the methods disclosed herein. For example, the artificial intelligence module 408 may be an artificial intelligence model for a specific facility and enable actions to be taken which reduce the impact of facility related operations on the computed emissions. In other embodiments, a plurality of artificial intelligence modules may be used to perform some aspects of methods herein.

[0086] It should be appreciated that computing system 400 is merely one example of a computing system, and that computing system 400 may have more or fewer components than shown, may combine additional components not depicted in the example embodiment of FIG. 4, and / or computing system 400 may have a different configuration or arrangement of the components depicted in FIG. 4. The various components shown in FIG. 4 may be implemented in hardware, software, or a combination of both hardware and software, including one or more signal processing and / or application specific integrated circuits.

[0087] Further, the steps in the processing methods described herein may be implemented by running one or more functional modules in information processing apparatus such as general- purpose processors or application specific chips, such as ASICs, FPGAs. PLDs, or other appropriate devices. These modules, combinations of these modules, and / or their combination with general hardware are included within the scope of the present disclosure.

[0088] Computational interpretations, models, and / or other interpretation aids may be refined in an iterative fashion; this concept is applicable to the methods discussed herein. This may include use of feedback loops executed on an algorithmic basis, such as at a computing device (e.g., computing system 400, FIG. 4), and / or through manual control by a user who may make determinations regarding whether a given step, action, template, model, or set of curves has become sufficiently accurate.

[0089] Additional Considerations

[0090] The abstract is provided to allow7the reader to quickly ascertain the nature of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. Further, while several examples have beendisclosed herein, any features from any examples can be combined with or replaced by other features from other examples. Moreover, while several examples have been disclosed herein, changes can be made to the disclosed examples within departing from the scope of the claims.

[0091] Examples in the present disclosure can also be directed to a non-transitory computer- readable medium storing computer-executable instructions and executable by one or more processors of the computer via which the computer-readable medium is accessed. A computer- readable media can be any available media that can be accessed by a computer. By way of example, such computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. Disk and disc, as used herein, includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu- ray® disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers.

[0092] Note also that the software implemented aspects of the subject matter claimed below are usually encoded on some form of program storage medium or implemented over some ty pe of transmission medium. The program storage medium is a non-transitory’ medium and can be magnetic (e.g., a floppy disk or a hard drive) or optical (e.g., a compact disk read only memory, or ‘'CD ROM”), and can be read only’ or random access. Similarly, the transmission medium can be twisted wire pairs, coaxial cable, optical fiber, or some other suitable transmission medium known to the art. The claimed subject matter is not limited by these aspects of any given implementation.

[0093] As used herein, each of the terms '‘tangible machine-readable medium,” “non-transitory machine-readable medium” and “machine-readable storage device” is expressly defined as a storage medium (e.g., a platter of a hard disk drive, a digital versatile disc, a compact disc, flash memory, read-only memory, random-access memory, etc.) on which machine-readable instructions (e.g., program code in the form of, for example, software and / or firmware) are stored for any suitable duration of time (e.g., permanently, for an extended period of time (e.g., while a program associated with the machine-readable instructions is executing), and / or a short period of time (e.g., while the machine-readable instructions are cached and / or during a buffering process)). Further, as used herein, each of the terms “tangible machine-readable medium,” “non-transitory machine-readable medium” and “machine-readable storage device” is expressly defined to exclude propagating signals. That is, as used in any claim of this patent,none of the terms “tangible machine-readable medium,” “non-transitory machine-readable medium,” and “machine-readable storage device” can be read to be implemented by a propagating signal.

[0094] The foregoing description, for purposes of explanation, used specific nomenclature to provide a thorough understanding of the disclosure. However, it will be apparent to one skilled in the art that the specific details are not required in order to practice the systems and methods described herein. The foregoing descriptions of specific examples are presented for purposes of illustration and description. They are not intended to be exhaustive of or to limit this disclosure to the precise forms described. Obviously, many modifications and variations are possible in view of the above teachings. The examples are shown and described in order to best explain the principles of this disclosure and practical applications, to thereby enable others skilled in the art to best utilize this disclosure and various examples with various modifications as are suited to the particular use contemplated. It is intended that the scope of this disclosure be defined by the claims and their equivalents below.

Claims

What is claimed is:

1. A method for obtaining an emissions estimate, the method comprising: obtaining a definition of at least one of a first part, a first product, a first usage, or a first service; identifying applicable data for the first part, the first product, the first usage, or the first service based upon the definition; estimating emissions for the at least one of the first part, the first product, the first usage, or the first service based upon the applicable data; presenting the estimated emissions to a screen via a graphical interface; and performing an action in response to the estimated emissions.

2. The method of claim 1. wherein obtaining a definition of the first part, the first product, the first usage, or the first service comprises: inputting the definition of the first part, the first product, the first usage, or the first service via the graphical interface; or obtaining the definition of the first part, the first product, the first usage, or the first service from design data stored on an activity database.

3. The method of claim 1, wherein identifying applicable data for the first part, the first product, the first usage, or the first service comprises selecting at least one life cycle phase for the first part, the first product, the first usage, or the first service via the graphical interface.

4. The method of claim 3, wherein selecting a life cycle phase for the first part, the first product, the first usage, or the first service comprises selecting at least one of the following life cycle phases: a raw materials acquisition phase; a processing phase; a manufacturing phase; a transportation phase; a usage phase; a maintenance phase; a remanufacturing phase; oran end-of-life phase.

5. The method of claim 3, wherein estimating emissions for the at least one of the first part, the first product, the first usage, or the first service comprises estimating emissions across the at least one selected life cycle phase for the first part, the first product, the first usage, or the first service to provide an absolute emissions value.

6. The method of claim 1, wherein identifying applicable data for the first part, the first product, the first usage, or the first service comprises selecting emission factors from emissions data provided by a supplier stored in a primary factor database and from publicly available or industry7standard emissions data stored in a secondary factor database.

7. The method of claim 3. wherein estimating emissions for the first part, the first product, the first usage, or the first service comprises: determining one or more differences over the at least one selected life cycle phase between the first part, the first product, the first usage, or the first service and a second part, a second product, a second usage, or a second service; and estimating the emissions for the first part, the first product, the first usage, or the first service based on the determined differences.

8. The method of claim 3, wherein presenting the estimated emissions to a screen via a graphical interface comprising presenting the estimated emissions according to the at least one selected life cycle phase.

9. The method of claim 1, further comprising estimating a total emissions related to the first product across a plurality of life cycle phases related to the first product, wherein the total emissions are defined by:Total Emissions = EE X fy + EF2t2+ EF3X t3+ EF4X t4+ EFnX tn, wherein EFn is an emission factor corresponding an activity and tn is a duration of the activity.

10. The method of claim 1, wherein performing an action in response to the estimated emissions comprises replacing the first part or the first product, improving the first part or the first product, discontinuing the first usage or the first service, adjusting the first usage or thefirst service, or implementing the first part, the first product, the first usage, or the first service into a facility.

11. A computing system, comprising: one or more processors; an emissions factor database storing emissions data related to at least one of a first part, a first product, a first usage, or a first service communicated to the one or more processors; an activity database storing activities data related to the first part, first product, first usage, or first service communicated to the one or more processors; a memory system comprising one or more non-transitory computer-readable media storing instructions that, when executed by at least one of the one or more processors, cause the computing system to perform operations, the operations comprising: obtaining a definition of at least one of a first part, a first product, a first usage, or a first service; identifying applicable data for the first part, the first product, the first usage, or the first service based upon the definition; estimating emissions for the at least one of the first part, the first product, the first usage, or the first service based upon the applicable data; presenting the estimated emissions to a screen; and performing an action in response to the estimated emissions.

12. The computing system of claim 11. wherein identifying applicable data for the first part, the first product, the first usage, or the first service comprises: identify ing applicable emissions data from the emissions factor database; or identifying applicable activities data from the activity database.

13. The computing system of claim 11 , wherein the emissions factor database comprises: a primary factor database storing emissions data provided by a supplier related to the definition of the first part, the first product, the first usage, or the first service; and a secondary factor database storing publicly available emissions data and / or industry standard emissions data related to the definition of the first part, the first product, the first usage, or the first service.

14. The computing system of claim 11, wherein activity database comprises: a manufacturing database storing data related to the manufacture and / or remanufacturing of the first part or the first product: a supply chain database storing data related to the supply, procurement, and / or transport of the first part or the first product; a usage database storing data related the first usage or first service; a maintenance database related to the maintenance and / or end-of-life activities for the first part or the first product; or design data input into the computing system by a user via a graphical interface.

15. The computing system of claim 11, wherein the emissions factor database and the activity database are communicated to the one or more processors via a network.

16. The computing system of claim 11, wherein identifying applicable data for the first part, the first product, the first usage, or the first service comprises: identifying applicable emissions factor data related to the first part, the first product, the first usage, or the first service stored in the emissions factor database; and identifying applicable activities data related to the first part, the first product, the first usage, or the first service stored in the activity database.

17. The computing system of claim 16, wherein estimating emissions for the first part, the first product, the first usage, or the first service comprises estimating an absolute emissions value for the first part, the first product, the first usage, or the first service based on the emissions factor data identified with the emissions factor database and the activities data identified within the activity database.

18. The computing system of claim 16, wherein estimating emissions for the first part, the first product, the first usage, or the first service comprises: determining one or more differences between the first part, the first product, the first usage, or the first service and a second part, a second product, a second usage, or a second service; and estimating the emissions for the first part, the first product, the first usage, or the first service based on the determined differences.

19. The computing system of claim 12, further comprising a data collector communicated to the one or more processors, the data collector storing the emissions data identified from the emissions factor database and the activities data identified from the activity database20. A non-transitory computer-readable medium storing instructions that, when executed by one or more processors of a computing system, cause the computing system to perform operations, the operations comprising: obtaining a definition of at least one of a first part, a first product, a first usage, or a first service; identifying applicable data for the first part, the first product, the first usage, or the first service based upon the definition, wherein identifying applicable data comprises identifying applicable emissions factors or activities data, wherein identifying applicable data for the first part, the first product, the first usage, or the first service comprises: identify ing applicable emissions factor data related to the first part, the first product, the first usage, or the first sendee stored in an emissions factor database; and identifying applicable activities data related to the first part, the first product, the first usage, or the first service stored in an activity database; estimating emissions for the at least one of the first part, the first product, the first usage, or the first sen ice based upon the applicable data, wherein estimating emissions for the first part, the first product, the first usage, or the first service comprises: estimating an absolute emissions value for the first part, the first product, the first usage, or the first service based on the identified applicable emissions factor data and activities data; or estimating an emissions value for the first part, the first product, the first usage, or the first service based on a comparison with at least one of a second part, a second product, a second usage, or a second service that is related to the definition of the first part, the first product, the first usage, or the first service, wherein estimating an emissions value for the first part, the first product, the first usage, or the first service based on a comparison with at least one of a second part, a second product, a second usage, or a second service compnses: estimating the emissions for the second part, the second product, the second usage, or the second service;determining one or more differences between the first part, the first product, the first usage, or the first service and the second part, the second product, the second usage, or the second service; and estimating the emissions for the first part, the first product, the first usage, or the first service based on the determined differences; presenting the estimated emissions to a screen via the graphical interface; and performing an action in response to the estimated emissions, wherein performing a action in response to the estimated emissions comprises replacing the first part or the first product, improving the first part or the first product, discontinuing the first usage or the first service, adjusting the first usage or the first sendee, or implementing the first part, the first product, the first usage, or the first sendee into a facility.

Images