CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] The subject disclosure claims priority from U.S. Provisional Appl. No. 63/363,961, filed on May 2, 2022, herein incorporated by reference in its entirety.

FIELD

[0002] The subject disclosure relates to systems and methods for monitoring methane emissions at industrial facilities, such as oil and gas facilities including well sites, compressor stations, and processing facilities.

BACKGROUND

[0003] Methane emissions in the oil and gas industry are receiving intense scrutiny as it is believed that such methane emissions contribute to global warming and/or climate change. A large portion of the methane emissions in the oil and gas industry arise from a small number of major emission events henceforth referred to as super-emitters. Super-emitters occur from a variety of sites, and recent data suggest many emission events are intermittent.

[0004] Continuous monitoring using methane emission detectors installed permanently at a site offers an effective way to identify, quantify, and mitigate intermittent methane emissions However, installing methane emission detectors across many diverse sites can be economically challenging. SUMMARY

[0005] In embodiments, an emission detector for monitoring methane emissions at one or more industrial facilities is provided that includes an enclosure that supports a plurality of sensors. The enclosure is configured to permit atmospheric gas to flow by diffusion into spaces at or near the plurality of sensors. The plurality of sensors includes at least one atmospheric sensor configured to measure atmospheric properties (e.g., temperature, humidity, atmospheric pressure) of the atmospheric gas that flows into the space at or near the plurality of sensors as well as at least one gas sensor configured to measure concentration of methane in the atmospheric gas that flows into the space at or near the plurality of sensors.

[0006] In embodiments, the enclosure can be configured to define a first test volume for the at least one atmospheric sensor, and the at least one atmospheric sensor can be configured to measure atmospheric properties of the atmospheric gas that flows into the first test volume.

[0007] In embodiments, the enclosure can be configured to define a second test volume for the at least one gas sensor, and the at least one gas sensor is configured to measure atmospheric properties of the atmospheric gas that flows into the second test volume.

[0008] In embodiments, the housing can support a gas permeable membrane that is configured to enable atmospheric gas to flow by diffusion into the space at or near the plurality of sensors but block water from flowing into such space.

[0009] In embodiments, the housing can support a particulate filter that is configured to enable atmospheric gas to flow by diffusion into the space at or near the plurality of sensors but block particulates (e g., dust) from flowing into such space.

[0010] In embodiments, the emission detector can further include acquisition and communication electronics that are operably coupled to the enclosure by at least one cable. [0011] In embodiments, automated systems and methods are provided for methane emissions monitoring of one or more industrial facilities. The automated systems and methods can be economically deployed worldwide on a large scale. The automated systems and methods employ a network of emission detectors for each industrial facility to be monitored. The emission detectors of the network are spaced from one another at different locations at the industrial facility. The emission detectors of the network are configured to perform time-series measurements of methane concentration at different locations within the industrial facility and communicate time-series sensor data representing such measurements (i.e., high-frequency location-specific methane concentration data) to an edge gateway device located at the industrial facility (or located within communication range from the industrial facility).

[0012] One or more emission detectors of the network can also include one or more atmospheric sensors that are configured to perform time-series measurements of atmospheric conditions (such as temperature, atmospheric pressure, and humidity) at one or more locations within the industrial facility. The one or more emission detectors with atmospheric sensor(s) are further configured to communicate times-series sensor data representing such measurements (i.e., high-frequency location-specific atmospheric data) to the edge gateway device.

[0013] One or more emission detectors of the network can also include one or more environmental sensors that are configured to perform time-series measurements of environmental conditions (such as wind speed, wind direction, and solar radiation) at one or more locations within the industrial facility. The one or more emission detectors with environmental sensor(s) are further configured to communicate time-series sensor data representing such measurements (i.e., high-frequency location-specific environmental data) to the edge gateway device. [0014] Each emission detector of the network can include a Global Navigation Satellite

System (GNSS) module that precisely tracks the position of the emission detector and time. The sensor data communicated from a given emission detector of the network can be stamped with location and time information as recorded by the Global Navigation Satellite System (GNSS) module in synchronization with the time-series measurements performed by the given mission detector.

[0015] The edge gateway device can be configured to collect, aggregate, and process the time-series sensor data (i.e., the high-frequency location-specific methane concentration data and the high-frequency location-specific atmospheric data and the high-frequency location-specific environmental data) communicated from the network of emission detectors, for example, by filtering and/or averaging the sensor data to derive corresponding time-series operational data and forwards such time-series operational data to a remote cloud computing environment. The time-series operational data represents i) methane concentration at specific locations within the industrial facility as a function of time as derived from the location-specific raw methane concentration data, ii) atmospheric conditions at specific location(s) within the one or more industrial facility as a function of time as derived from the location-specific atmospheric data, and iii) environmental conditions at specific location(s) within the one or more industrial facility as a function of time as derived from the location-specific environmental data. The remote cloud computing environment receives the time-series operational data communicated from the edge gateway device and processes the received time-series operational data using a suitable computational model, such as Gaussian plume dispersion model, to characterize methane emission at the industrial facility. For example, the cloud computing environment can process the received time-series operational data using a suitable computational model (e.g., Gaussian plume dispersion model) to detect the presence of methane emission at the industrial facility, the location of the methane emission at the industrial facility (when present), and the associated rate of methane emission at the industrial facility (when present). The cloud computing environment can generate data related to the methane emission (such as the location of the methane emission at the industrial facility, and the associated rate of methane emission at the industrial facility) and process such data to automatically generate an alert characterizing the methane emission at the industrial facility. The alert can be communicated to a designated party or user to initiate or schedule mitigation of the methane emission at the industrial facility.

[0016] In embodiments, each emission detector of the network can include electronics that provide for wireless data communication between the emission detector and the edge gateway device. In embodiments, the wireless data communication can implement a predefined wireless communication protocol, such as the LoRaWAN protocol. The LoRaWAN protocol employs spread spectrum modulation techniques derived from chirp spread spectrum (CSS) technology and provides a range up to 10km with a data rate of up to 50kbps.

[0017] In embodiments, the network of emission detectors can be deployed over locations within one or more oil and gas facilities, such as one or more well sites, one or more compressor stations, or one or more processing facilities.

[0018] In embodiments, the edge gateway device can be configured to collect and process time-series sensor data measured by the emission detector networks at multiple industrial facilities (e g., multiple well sites), and the cloud computing environment can be configured to process time-series operational data derived from the time-series sensor data measured by the emission detector networks at the multiple industrial facilities to characterize methane emission at the respective industrial facilities. [0019] In other embodiments, the emission detectors of the network(s) can be configured to process the real-time measurement data, for example, including filtering and/or averaging, and forward the resultant time-series data to the gateway device. The gateway device can collect, aggregate, and process such data for communication to the cloud computing environment.

[0020] In still other embodiments, the gateway device can be configured to process timeseries operational data derived from the measurements performed by the network(s) of emission detectors operably coupled thereto using a suitable computational model, such as Gaussian plume dispersion model, to characterize methane emission at one or more industrial facilities. For example, the gateway device can process the time-series operational data using a suitable computational model (e.g., simulation and inversion using a Gaussian plume dispersion model) to detect the presence of methane emission at one or more industrial facilities, the location of the methane emission at one or more industrial facilities (when present), and the associated rate of methane emission at the one or more industrial facilities (when present). The gateway device can be further configured to generate data related to the methane emission (such as the location of the methane emission at the one or more industrial facilities, and the associated rate of methane emission at the one or more industrial facilities) and process such data to automatically generate alert(s) characterizing the methane emission at the one or more industrial facilities. The alert(s) can be communicated to designated party(ies) or user(s) to initiate or schedule mitigation of the methane emission at the one or more industrial facilities.

[0021] This summary is provided to introduce a selection of concepts that are further described below in the detailed description. This summary is not intended to identify key or essential features of the claimed subject matter, nor is it intended to be used as an aid in limiting the scope of the claimed subject matter. BRIEF DESCRIPTION OF DRAWINGS

[0022] The subject disclosure is further described in the detailed description which follows, in reference to the noted plurality of drawings by way of non-limiting examples of the subject disclosure, in which like reference numerals represent similar parts throughout the several views of the drawings, and wherein:

[0023] Fig. l is a schematic block diagram that depicts an automated system for methane emissions monitoring in accordance with an embodiment of the subject disclosure;

[0024] Fig. 2 is a schematic block diagram that depicts another automated system for methane emissions monitoring in accordance with an embodiment of the subject disclosure;

[0025] Figs. 3A and 3B, collectively, is a flow chart of operations that can be carried out by the cloud computing environment of Figs. 1 and 2;

[0026] Fig. 4 is a schematic diagram that depicts the automated system for methane emissions monitoring of Fig. 1 deployed at a well site (e.g., well pad),

[0027] Fig. 5 is a schematic diagram that depicts the automated system for methane emissions monitoring of Fig. 1 deployed at another well site (e.g., well pad);

[0028] Fig. 6 is a schematic diagram of an emissions detector in accordance with the present disclosure, which is suitable for use as part of the system of Fig. 1;

[0029] Fig. 7 is a schematic diagram of a sensor enclosure that can be part of the emissions detector of Fig. 6 in accordance with the present disclosure;

[0030] Fig. 8 is a graph illustrating plots of raw and averaged methane concentrations (in ppm) as measured by the emissions detector of Figures 6 and 7 over time; the plots show raw methane concentration over time (with averaging) as well as plots that employ different averaging times that vary from 5 seconds to 30 seconds to 120 seconds; and

[0031] Fig. 9 is a schematic diagram of an example computing system.

DETAILED DESCRIPTION

[0032] The particulars shown herein are by way of example and for purposes of illustrative discussion of the embodiments of the subject disclosure only and are presented in the cause of providing what is believed to be the most useful and readily understood description of the principles and conceptual aspects of the subject disclosure. In this regard, no attempt is made to show structural details in more detail than is necessary for the fundamental understanding of the subject disclosure, the description taken with the drawings making apparent to those skilled in the art how the several forms of the subject disclosure may be embodied in practice.

Furthermore, like reference numbers and designations in the various drawings indicate like elements.

[0033] The present disclosure is directed to automated systems and methods that provide for methane emissions monitoring of one or more industrial facilities. The automated systems and methods can be economically deployed worldwide on a large scale.

[0034] In an example embodiment shown in Figure 1, an automated system is provided that includes an edge gateway device 105 that is located at or near (e.g., at a distance of 10km or less) an industrial facility 100. The edge gateway device 105 is a ruggedized computing device that can be configured to deliver performance edge computing and secure data ingestion. The edge gateway device 105 can be configured to enable real-time monitoring and control of the operational equipment at the industrial facility 100. [0035] The edge gateway device 105 can be configured to receive, collect, and aggregate data from a variety of operational equipment at the industrial facility 100 (such as sensors, controllers, actuators, programmable logic controllers, remote terminal units, and supervisory control and data acquisition (SCAD A) systems), prepare such data for transmission to the remote cloud computing environment 109 and transmit the data from the edge gateway device 105 to the remote cloud computing environment 109 over a data communication network 107 as shown in Fig. 1. The data communication network 107 can include a cellular data network, satellite link, other Wide Area Network, the Internet, and/or another mode of available data communication. The cloud computing environment 109 can be implemented by one or more processor-based systems as is well known.

[0036] In embodiments, the edge gateway device 105 can employ a compact and rugged NEMA/IP rated housing for outdoor use, making it suitable for the environments at well sites and facilities. The overall packaging can also be environmentally qualified.

[0037] In embodiments, the gateway device 105 can be configured with a bi-directional communication interface (referred to as a Southbound Interface labeled SB, 105 A) for data communication to the operational equipment at the facility 100 using either a wired communication protocol (such as a serial, Ethernet, Modbus or Open Platform Communication (OPC) protocol) or a wireless communication protocol (such as IEEE 802.11 Wi-Fi protocol, Highway Addressable Remote Transducer Protocol (HART), LoraWAN, WiFi or Message Queuing Telemetry Transport (MQTT)). The Southbound Interface 105 A can provide for direct data communication to the operational equipment at the facility 100. Alternatively, the Southbound Interface 105 A can provide for indirect data communication to the operational equipment at the facility 100 via a local area network or other local communication devices. [0038] In embodiments, the edge gateway device 105 can be configured with a bidirectional communication interface (referred to as a Northbound Interface labeled NB, 105C) to the data communication network 107 using a wireless communication protocol. In embodiments, the wireless communication protocol can employ cellular data communication, such as 4G LTE data transmission capability (or possibly 3G data transmission for fallback capability). For facilities without a cellular signal, the Northbound Interface 105C to the data communication network 107 can be provided by a bidirectional satellite link (such as a BGAN modem). Alternatively, the Northbound Interface 105C can implement other wireless communication protocols or one or more wired communication protocols implemented by the data communication network 107.

[0039] In embodiments, the edge gateway device 105 can employ an embedded processing environment (e.g., data processor and memory system) that hosts and executes an operating system and application(s) or module(s) as described herein.

[0040] In embodiments, the edge gateway device 105 can employ both hardware-based and software-based security measures. The hardware-based security measures can involve a hardware root-of-trust established using an industry-standard Trusted Platform Module (TPM) v2.0 cryptographic chip. The software-based security measures can include operating system hardening and encryption of both buffered and transmitted data.

[0041] In embodiments, the edge gateway device 105 can support a containerized microservice-based architecture. This architecture enables extensibility into several distinct and different solutions for different environments and applications at the edge, while still using the same infrastructure components. In embodiments, the edge gateway device 105 can employ one or more containers to implement one or more applications or modules executing on the gateway device 105 that perform functionality for methane emissions monitoring as described herein. A container is a standard unit of software that packages up code and all its dependencies (such as runtime environment, system tools, system libraries and settings) so that the application or module runs quickly and reliably in the computing environment of the edge gateway device 105. The container isolates the software from its environment and ensures that it works uniformly and reliably in the computing environment of the edge gateway device 105.

[0042] In embodiments, the Southbound Interface 105 A of the gateway device 105 utilizes a wireless communication protocol to interface to a network of methane emission detectors (for example, three methane emission detectors 101 and one methane emission detector with environmental sensor(s) 103) that are spaced from one another at different locations at the industrial facility 100, for example, in opposed comers of the facility as shown in Figs. 4 and 5. The network of methane emission detectors 101, 103 is configured to perform time-series measurements of methane concentration at different locations within the industrial facility 100 and communicate time-series sensor data representing such measurements (i.e., high-frequency location-specific methane concentration data) to the edge gateway device 105.

[0043] In embodiments, one or more methane emission detectors of the network can include one or more atmospheric sensors that are configured to perform time-series measurements of atmospheric conditions (such as temperature, atmospheric pressure, and humidity) at one or more locations within the industrial facility 100. The one or more methane emission detectors with atmospheric sensor(s) can be further configured to communicate timeseries sensor data representing such measurements (i.e., high-frequency location-specific atmospheric data) to the edge gateway device 105. In embodiments, the atmospheric sensor(s) can be selected from the group that includes: one or more sensors that measure temperature and humidity, and a barometer for measuring atmospheric pressure.

[0044] In embodiments, one or more methane emission detectors of the network, such as the methane emission detector 103 in Fig. 1, can include one or more environmental sensors that are configured to perform time-series measurements of environmental conditions (such as wind speed, wind direction, and solar radiation) at one or more locations within the industrial facility 100. The one or more methane emission detectors with environmental sensor(s) can be further configured to communicate time-series sensor data representing such measurements (i.e., high- frequency location-specific environmental data) to the edge gateway device 105. In embodiments, the environmental sensors can be selected from the group that includes: an anemometer for measuring wind speed and wind direction, and a pyranometer for measuring solar radiation.

[0045] In embodiments, each methane emission detector (101, 103) of the network can include a Global Navigation Satellite System (GNSS) module that precisely tracks the position of the methane emission detector and time. The time-series sensor data communicated from a given methane emission detector (101, 103) can be stamped with location and time information as recorded by the Global Navigation Satellite System (GNSS) module in synchronization with the time-series measurements performed by the given methane emission detector (101, 103). [0046] In embodiments, each methane emission detector (101, 103) of the network can include a gas sensor for measuring methane concentration in the immediate vicinity of the gas sensor together with the electronics that interface to the gas sensor and provide for data communication between the methane emission detector (101, 103) and the edge gateway device 105. In embodiments, the data communication can implement a predefined wireless communication protocol, such as the LoRaWAN protocol. The LoRaWAN protocol employs spread spectrum modulation techniques derived from chirp spread spectrum (CSS) technology and provides a range up to 10km with a data rate of up to 50kbps.

[0047] The edge gateway device 105 includes sensor data processing functionality 105B that is configured to collect, aggregate, and process the time-series sensor data (i.e., the high- frequency location-specific raw methane concentration data and the high-frequency locationspecific raw environmental data) communicated from the network of methane emission detectors 101, 103, for example, by filtering and/or averaging the data, to generate corresponding timeseries operational data. The time-series operational data represents i) methane concentration at specific locations within the industrial facility 100 as a function of time as derived from the location-specific methane concentration data, ii) atmospheric conditions at specific location(s) within the industrial facility 100 as a function of time as derived from the location-specific atmospheric data, and iii) environmental conditions at specific location(s) within the industrial facility 100 as a function of time as derived from the location-specific environmental data. The sensor data processing functionality 105B is further configured to cooperate with the Northbound Interface 105C to forward the time-series operational data to the remote cloud computing environment 109 via the data communication network 107. The cloud computing environment 109 receives the time-series operational data communicated from the edge gateway device 105 and processes the received time-series operational data to detect the presence of methane emission at the industrial facility 100, the location of the methane emission at the industrial facility 100 (when present), and the associated rate of methane emission at the industrial facility 100 (when present). The cloud computing environment 109 can generate data related to the methane emission (such as the location of the methane emission at the industrial facility 100, and the associated rate of methane emission at the industrial facility 100) and process such data to automatically generate an alert characterizing the methane emission. The alert can be communicated to a designated party or user to initiate or schedule mitigation of the methane emission at the industrial facility 100.

[0048] In embodiments, the cloud computing environment 109 can employ a suitable computational model, such as Gaussian plume dispersion model, to detect the presence of methane emission at the industrial facility 100, the location of the methane emission at the industrial facility 100, and the associated rate of methane emission at the industrial facility 100. In this embodiment, the computational model can be used as part of simulation and inversion operations that detects the presence of methane emission at the industrial facility 100, the location of the methane emission at the industrial facility 100, and the associated rate of methane emission at the industrial facility 100.

[0049] In embodiments, each methane emission detector (101, 103) of the network can include an accelerometer for measuring the acceleration of the methane emission detector. Detector-specific raw acceleration data can be communicated from the methane emission detectors (101, 103) of the network to the edge gateway device 105 and processed by the edge gateway device 105 to detect fall events for the respective methane emission detectors 101, 103. Additionally or alternatively, the edge gateway device 105 can derive detector-specific acceleration data from such measurements, and communicate the detector-specific acceleration data from the edge gateway device 105 to the cloud computing environment 109. The cloud computing environment 109 can be configured to receive and process the detector-specific acceleration data to detect fall events for the respective methane emission detectors (101, 103) of the network. The alert can be communicated to a designated party or user to initiate or schedule repair of the fallen emission detector at the industrial facility 100.

[0050] In embodiments, the edge gateway device 105 can be configured to collect and process time-series sensor data measured by methane emission detector networks at multiple industrial facilities (e.g., multiple well sites), and the cloud computing environment 109 can be configured to process time-series operational data derived from the time-series sensor data measured by the methane emission detector networks at the multiple industrial facilities to characterize methane emission at the respective industrial facilities.

[0051] For example, in another example embodiment shown in Figure 2, the edge gateway device 105 (e.g., the Southbound Interface 105A) utilizes a wireless communication protocol to interface to multiple networks of methane emission detectors for monitoring emissions for two well sites 100A and 100B as shown in Figure 2. In this embodiment, the methane emission detectors of each network are spaced from one another at different locations within the respective well sites 100A, 100B. For example, the network of methane emission detectors (101, 103) for the well site 100A can be deployed in opposed comers of the well site 100A as shown in Fig. 4, while the network of methane emission detectors (101, 103) for the well site 100B can be deployed in opposed corners of another well site 100B as shown in Fig. 5. The multiple networks of methane emission detectors (101, 103) are configured to perform timeseries measurements of methane concentration at different locations within the corresponding well sites 100A, 100B and wirelessly communicate time-series sensor data representing such measurements (i.e., high-frequency location-specific methane concentration data) to the edge gateway device 105. [0052] In embodiments, one or more methane emission detectors of each network can include one or more atmospheric sensors that are configured to perform time-series measurements of atmospheric conditions (such as temperature, atmospheric pressure, and humidity) at one or more locations within the respective well sites 100A, 100B. The one or more methane emission detectors with atmospheric sensor(s) can be further configured to wirelessly communicate time-series sensor data representing such measurements of atmospheric conditions (i.e., high-frequency location-specific atmospheric data) to the edge gateway device 105. In embodiments, the atmospheric sensors can be selected from the group that includes: one or more sensors that measure temperature and humidity, and a barometer for measuring atmospheric pressure. Furthermore, one or more methane emission detectors of each network, such as the methane emission detector 103 for well site 100A and the methane emission detector 103 for well site 100B in Fig. 2, can include one or more environmental sensors that are configured to perform time-series measurements of environmental conditions (such as wind speed, wind direction, and solar radiation) at one or more locations within the respective well sites 100A, 100B. The one or more methane emission detectors with environmental sensor(s), such as the methane emission detector 103 for well site 100A and the methane emission detector 103 for well site 100B, can be further configured to wirelessly communicate time-series sensor data representing such measurements of environmental conditions (i.e., high-frequency locationspecific environmental data) to the edge gateway device 105. In embodiments, the environmental sensors can be selected from the group that includes: an anemometer for measuring wind speed and wind direction, and a pyranometer for measuring solar radiation. [0053] In embodiments, each methane emission detector (101, 103) of the multiple networks can include a Global Navigation Satellite System (GNSS) module that precisely tracks the position of the methane emission detector and time. The time-series sensor data representing the time-series measurements communicated from a given methane emission detector (101, 103) can be stamped with location and time information as recorded by the Global Navigation Satellite System (GNSS) module in synchronization with the time-series measurements performed by the given methane emission detector (101, 103).

[0054] In embodiments, each methane emission detector (101, 103) of the multiple networks can include a gas sensor for measuring methane concentration in the immediate vicinity of the gas sensor together with the electronics that interface to the gas sensor and provide for data communication between the methane emission detector (101, 103) and the edge gateway device 105. In embodiments, the data communication can implement a predefined wireless communication protocol, such as the LoRaWAN protocol as shown in Fig. 2.

[0055] The edge gateway device 105 includes sensor data processing functionality 105B that is configured to collect, aggregate, and process the time-series data (i.e., the high-frequency location-specific methane concentration data and the high-frequency location-specific atmospheric data and the high-frequency location-specific environmental data) communicated from the multiple networks of methane emission detectors 101, 103, for example, by filtering and/or averaging the data, to generate time-series operational data. The time-series operational data represents i) methane concentration at specific locations within the well sites 100A and 100B as a function of time as derived from the location-specific methane concentration data from the well sites 100A and 100B, ii) atmospheric conditions at specific location(s) within the well sites 100A and the 100B as a function of time as derived from the location-specific atmospheric data from well sites 100A and 100B, and iii) environmental conditions at specific location(s) within the well sites 100A and 100B as a function of time as derived from the location-specific environmental data from well sites 100A and 100B. The sensor data processing functionality 105B is further configured to cooperate with the Northbound Interface 105C to forward such time-series operational data to the remote cloud computing environment 109 via the data communication network 107. The cloud computing environment 109 receives the time-series operational data communicated from the edge gateway device 105 and processes the received time-series operational data for each well site to detect the presence of methane emission at the respective well sites 100A, 100B, the location of the methane emission at the respective well sites 100A, 100B (when present), and the associated rate of methane emission at the respective well sites 100A, 100B (when present). The cloud computing environment 109 can generate data related to the methane emission for the respective well sites 100A, 100B (such as the location of the methane emission for the respective well sites 100A, 100B, and the associated rate of methane emission for the respective well sites 100A, 100B) and process such data to automatically generate an alert characterizing methane emission for the respective well sites 100A, 100B. The alert can be communicated to a designated party or user to initiate or schedule mitigation of the methane emission at the respective well sites 100A, 100B.

[0056] In embodiments, the cloud computing environment 109 can employ suitable computational models, such as Gaussian plume dispersion models, to detect the presence of methane emission at the respective well sites 100 A, 100B, the location of the methane emission at the respective well sites 100 A, 100B (when present), and the associated rate of methane emission at the respective well sites 100A, 100B (when present). Tn this case, the computational models for the respective well sites 100A, 100B can be used as part of separate simulation and inversion operations that detect the presence of methane emission at the respective well sites 100A, 100B, the location of the methane emission at the respective well sites 100A, 100B (when present), and the associated rate of methane emission at the respective well sites 100A, 100B (when present).

[0057] In this manner, the edge gateway device 105 can be configured to collect and process time-series sensor data measured by methane emission detector networks at multiple industrial facilities (e.g., multiple well sites), and the cloud computing environment can be configured to process operational data derived from the time-series sensor data measured by the methane emission detector networks at the multiple industrial facilities to detect the presence of methane emission at the respective industrial facilities, the location of the methane emission at the respective industrial facilities (when present), and the associated rate of methane emission at the respective industrial facilities (when present).

[0058] Figs. 3A and 3B, collectively, is a flow chart of operations that can be carried out by the cloud computing environment 109 of Figs. 1 and 2.

[0059] The operations begin in block 301 where the cloud computing environment 109 is configured to receive time-series operational data of location-specific methane concentration at an industrial site (e.g., a well site) as communicated from edge gateway device 105.

[0060] In block 303, the cloud computing environment 109 is configured to receive timeseries operational data of location-specific atmospheric and environmental conditions (e.g., temperature, atmospheric pressure, humidity, wind speed, wind direction, solar radiation) at the industrial site as communicated from the edge gateway device 105.

[0061] In block 305, the cloud computing environment 109 is configured to use the timeseries operational data of 303 to derive values of corresponding environmental parameters of a Gaussian plume dispersion model for the industrial site. [0062] Tn block 307, the cloud computing environment 109 is configured to determine initial values for the location and emission rate of a methane leak at the industrial site.

[0063] In block 309, the cloud computing environment 109 is configured to use the values for the location and emission rate of the methane leak (block 307 or 317) and the value of the environmental parameters of 305 as part of a Gaussian plume dispersion model for the industrial site. The cloud computing environment 109 runs (or executes) the Gaussian plume dispersion model to simulate methane concentration over the area of the industrial site given the values for the location and emission rate of methane leak and the value of the environmental parameters of 305.

[0064] In block 311, the cloud computing environment 109 is configured to extract simulated methane concentration at the locations of methane emission detectors at the industrial site as determined from the simulation of 309.

[0065] In block 313, the cloud computing environment 109 is configured to evaluate differences between the simulated methane concentrations of 311 and the corresponding location-specific methane concentrations of 301 to determine if the simulation and inversion of 309 to 313 has converged (i.e., satisfied a predetermined stopping criterion).

[0066] In block 315, the cloud computing environment 109 determines if the simulation and inversion of 309 to 313 has converged. If not, the operations continue to block 317. If so, the operations continue to blocks 319 to 321.

[0067] In block 317, the cloud computing environment 109 is configured to update the values for the location and emission rate of methane leak at the industrial site, and the processing returns to block 309. [0068] In block 319, the cloud computing environment 109 is configured to output values for the location and emission rate of suspected methane leak at the industrial site for alert and mitigation of the suspected methane leak. In embodiments, the last values for the location and emission rate of methane leak that resulted in convergence as determined in block 315 can be output as the values for the location and the emission rate of suspected methane leak at the industrial site.

[0069] In block 321, the cloud computing environment 109 can be configured to optionally repeat the operations of 301-321 (or parts thereof) with additional time-series operational data to confirm the suspected methane leak or identify/confirm another suspected methane leak.

[0070] In other embodiments, the methane emission detectors of the network(s) can be configured to process the real-time measurement data, for example, including filtering and/or averaging, and forward the resultant time-series data to the gateway device. The gateway device can collect, aggregate, and process such data for communication to the cloud computing environment.

[0071] In still other embodiments, the gateway device 105 can be configured to process time-series operational data derived from the measurements performed by the network(s) of methane emission detectors operably coupled thereto using a suitable computational model, such as Gaussian plume dispersion model, to characterize methane emission at one or more industrial facilities. For example, the gateway device can process the time-series operational data using a suitable computational model (e.g., simulation and inversion using a Gaussian plume dispersion model) to detect the presence of methane emission at one or more industrial facilities, the location of the methane emission at one or more industrial facilities (when present), and the associated rate of methane emission at the one or more industrial facilities (when present). The gateway device can be further configured to generate data related to the methane emission (such as the location of the methane emission at the one or more industrial facilities, and the associated rate of methane emission at the one or more industrial facilities) and process such data to automatically generate alert(s) characterizing the methane emission at the one or more industrial facilities. The alert(s) can be communicated to designated party(ies) or user(s) to initiate or schedule mitigation of the methane emission at the one or more industrial facilities.

[0072] Fig. 4 depicts the automated system for methane emissions monitoring of Fig. 1 deployed at a well site (e.g., well pad).

[0073] Fig. 5 depicts the automated system for methane emissions monitoring of Fig. 1 deployed at another well site (e.g., well pad).

[0074] Fig. 6 is a schematic diagram of an emissions detector 101’ in accordance with the present disclosure, which is suitable for use as part of the system of Fig. 1. The emissions detector 101’ includes acquisition and communication electronics 1001 and a sensor enclosure 1003. The acquisition and communication electronics 1001 includes electrical circuitry that interfaces to electrical interface components (e.g., PCB 1003C) of the sensor enclosure 1003 via one or more cable(s) 1005 shown. The acquisition and communication electronics 1001 further include additional electrical circuitry that supports data communication with the gateway device 105. In embodiments, the data communication can employ one or more RF antenna 1007 for wireless data communication according to one or more predefined wireless communication protocols (such as LoraWan, Zigbee, WiFi) as supported by the Southbound data communication interface of the gateway device 105. In other embodiments, the data communication can employ wired data communication, for example, via copper cables or fiber optic cables, which can be used for Ethernet or other wired data communication protocols with the gateway device 105. The electrical circuitry of the acquisition and communication electronics 1001 can be embodied by one or more printed circuit boards (PCBs) as is well known in the electronic arts. The acquisition and communication electronics 1001 can further include or interface to an electrical power source (not shown) that supplies electrical power to the electrical components of the emissions detector 101’. In embodiments, the electrical power source can include one or more batteries (e.g., lithium-ion battery(ies)), one or more solar panels, a wind-powered generator, mains power, and/or other suitable electrical power source.

[0075] The sensor enclosure 1003 includes a printed circuit board (PCB) 1003C that mechanically supports a passive atmospheric sensor 1003 A as well as a passive gas sensor 1003B. The sensor enclosure 1003 is configured to permit atmospheric gas to flow by diffusion into space at or near the passive atmospheric sensor 1003 A, and the passive atmospheric sensor 1003 A can be configured to measure gas properties (such as temperature, atmospheric pressure, and humidity) of the atmospheric gas that flows into the space at or near the passive atmospheric sensor 1003 A. The sensor enclosure 1003 is further configured to permit atmospheric gas to flow by diffusion into space at or near the passive gas sensor 1003B, and the passive gas sensor 1003B can be configured to measure the concentration of methane in the atmospheric gas that flows into the space at or near the passive gas sensor 1003B. The methane can be part of the atmospheric gas that flows into the space at or near the passive gas sensor 1003B due to a methane leak in the local vicinity of the sensor enclosure 1003. The passive atmospheric sensor 1003 A can output analog signals or digital data that represents the atmospheric properties measured by the passive atmospheric sensor 1003 A. Such analog signals or digital data are supplied to electrical components of the PCB 1003C for processing and/or output to the acquisition and communication electronics 1001 . The passive gas sensor 1003B can output analog signals or digital data that represents the methane concentration measured by the passive gas sensor 1003B. Such analog signals or digital data are supplied to electrical components of the PCB 1003C for processing and/or output to the acquisition and communication electronics 1001. For example, the electrical components of the PCB 1003C can provide for one or more of sampling, analog-to-digital (A-to-D) conversion, data fdtering and averaging, and/or data communication with the acquisition and communication electronics 1001 via the cable(s) 1005. Similarly, the electrical components of the acquisition and communication electronics 1001 can provide for one or more of sampling, A-to-D conversion, data filtering and averaging, and/or data communication with the PCB 1003C via the cable(s) 1005. The acquisition and communication electronics 1001 can be configured to generate data representing the measurements made by the passive sensor(s) 1003 A, 1003B over time and communicate such operational data to the gateway device 105 for processing as described herein. Such data can represent raw measurements of the passive sensor(s) 1003 A, 1003B over time. Alternatively or additionally, such data can be derived from filtering and/or averaging the measurements of the passive sensor(s) 1003A, 1003B over time. Similarly, the gateway device 105 can be configured to filter and/or average data that represents the raw measurements of the passive sensor(s) 1003 A, 1003B over time for processing as described herein.

[0076] Fig. 7 is a schematic diagram of a sensor enclosure 1003 that can be part of the emissions detector 101 ’ of Fig. 6 in accordance with the present disclosure. The sensor enclosure 1003 includes a housing 1011 and spacer 1013 that mechanically supports the PCB 1003C within the enclosure 1003. The PCB 1003C mechanically supports the passive atmospheric sensor 1003 A as well as a passive gas sensor 1003B as shown. The spacer 1013 defines a compartment that receives the passive atmospheric sensor 1003 A and forms a test volume 1018 for the passive atmospheric sensor 1003 A. The test volume 1018 is disposed adjacent to the filter 1016 as shown. The spacer 1013 further defines a compartment that receives the passive gas sensor 1003B and forms a test volume 1019 for the passive gas sensor 1003B. The test volume 1019 is also disposed adjacent to the filter 1016 as shown. A nut or other mechanical fastener 1015 supports the filter 1016 and a breathable membrane 1017 adjacent to the test volumes 1018 and 1019. The breathable membrane 1017 is a gas permeable membrane that allows atmospheric gas to pass through the membrane but blocks water from passing through the membrane. In embodiments, the membrane 1017 can be realized by a Gore-Tex hydrophobic membrane. In other embodiments, other permeable membranes can be used. The filter 1016 allows atmospheric gas to pass through the filter 1016 but blocks particulate contamination (e.g. dust) from passing through the filter 1016. In embodiments, the filter 1016 can be realized by a sintered metal filter that excludes particulate contamination (e.g. dust). In other embodiments, sintered metal and/or expanded PTFE (Gore-Tex) such as activated carbon or other particulate filters can be used.

[0077] In the embodiment of Fig. 7, the housing 1011 together with the filter 1016 and the membrane 1017 are configured to permit atmospheric gas to flow by diffusion into the test volume 1018 at or near the passive atmospheric sensor 1003 A, and the passive atmospheric sensor 1003 A can be configured to measure gas properties (such as temperature, atmospheric pressure, and humidity) of the atmospheric gas that flows into the test volume 1018.

Furthermore, the housing 1011 together with the filter 1016 and the membrane 1017 are configured to permit atmospheric gas to flow by diffusion into the test volume 1019 at or near the passive gas sensor 1003B, and the passive gas sensor 1003B can be configured to measure

15 the concentration of methane in the atmospheric gas that flows into the test volume 1019. The methane can be part of the atmospheric gas that flows into the test volume due to a methane leak in the local vicinity of the sensor enclosure 1003. The passive atmospheric sensor 1003 A can output analog signals or digital data that represents the atmospheric properties measured by the passive atmospheric sensor 1003 A. Such analog signals or digital data are supplied to electrical components of the PCB 1003C for processing and/or output to the acquisition and communication electronics 1001. The passive gas sensor 1003B can output analog signals or digital data that represents the methane concentration measured by the passive gas sensor 1003B. Such analog signals or digital data are supplied to electrical components of the PCB 1003C for processing and/or output to the acquisition and communication electronics 1001.

[0078] In embodiments, the passive atmospheric sensor 1003 A can be realized by off- the-shelf integrated circuit components, such as the Sensirion SHT series commercially available from Sensirion AG of Stafa, Switzerland. In other embodiments, other atmospheric sensors could be used.

[0079] In embodiments, the passive gas sensor 1003B can be realized by a metal oxide sensor that changes impedance as methane concentration changes. In other embodiments, other sensors suitable for measuring methane concentration, such as NDIR optical sensors, thermal conductivity, photoacoustic sensors, etc., could be used.

[0080] In other embodiments, other mechanical designs can be employed for the membrane 1017 and/or the fdter 1016. For example, the fdter 1016 can be placed on the cylindrical sides of the enclosure instead of the end of the enclosure.

[0081] Note that the installation of emissions detectors across many diverse industrial sites can be challenging as this requires a system that optimally trades off between power consumption, size, robustness, metrology performance, and many other factors. A key parameter is whether the chosen sensor requires a pump or fan to actively move air from outside across the sensor or if the sensor can be passively exposed to the outside air and utilize only diffusion to bring the gas of interest into contact with it. A passively exposed sensor has many significant advantages including lower power consumption and increased mechanical robustness due to the removal of the fan/pump. Additionally, the electronics and other sensitive parts apart from the gas sensor itself can then be hermetically sealed from dust/moisture/etc., which significantly reduces complications that may shorten the lifespan of the product.

[0082] Advantageously, the sensor enclosure of Figures 6 and 7 mount the sensors in a housing that relies on diffusion of atmospheric gas to bring the atmospheric gas (including methane in the atmospheric gas that results from a methane leak) into contact with the sensors, and thus avoids using a fan or other mechanical device to move air past the sensors. This passive design has significant advantages due to its simplicity but can also introduce constraints related to response time that need to be addressed. The core physics of the equilibration of the air outside of the sensor with that inside the protective housing can be described via a diffusion equation where C _sensor is the concentration of methane inside the sensor, C _air is the concentration of methane outside:

Here A^ _ater is the effective cross-sectional area of the particulate filter and permeable membrane, V _sensor is the volume of the sensor cavity (test volume) within the housing, 8 is the effective thickness of the filter and membrane, and D is the diffusivity of the filter and membrane. Comparing this with the equation for an exponentially weighted moving average where x is the function being averaged, y is the averaged value, and a is the time constant: dy

-a ¹ y - x). Eqn. (2) dt

One can observe that adding the particulate filter and permeable membrane to a sensor results in an exponential averaging behavior with time constant of:

Eqn. (3)

[0083] Fig. 8 is a graph illustrating plots of raw and averaged methane concentrations (in ppm) as measured by the emissions detector of Figures 6 and 7 over time. The plots show raw methane concentration over time (with averaging) as well as plots that employ different averaging times that vary from 5 seconds to 30 seconds to 120 seconds. Fig. 8 shows the effect of large and small-time constants produced via varying these parameters on the measured concentration.

[0084] There are several different ways to match this coefficient to the desired sensor behavior for use in further processing and interpretation steps. If the primary goal is for a fast response in order to utilize temporal fluctuations of the methane concentrations, one can immediately see that we should design a sensor with minimal dead volume (F) and the largest possible filter cross-sectional area (A). The membrane and the particulate filter should be designed to be as thin with as large a diffusivity as possible while still maintaining mechanical performance. Fig. 7 shows a design that can be adapted to meet this objective.

[0085] For many implementations, an analog and/or digital signal processing filter can be implemented to average the sensor measurements over a desired period of time to reduce noise and communication bandwidth. For this, it is optimum to also match the sensor response time to this averaging time and thus we can adjust the time constant parameters to match this time which will further improve the sensor performance. [0086] Finally, the interpretation of the methane concentrations measured from these sensors in order to infer leak existence, rate, and position can employ a Gaussian plume model as described herein. The coefficients of the Gaussian plume model are typically derived based on a specified averaging time (for example, 5 minutes). It thus is advantageous to have the emissions detector itself average concentrations over this period of time. This enables the use of a low duty cycle measurement by only making a single measurement every given window rather than having continuous measurements which are later averaged.

[0087] The emission detector of the present disclosure can have many advantages as follows: i) low dead-volume, environmentally protected sensor mounting with no fan which enables low power consumption, mechanical robustness, and electrical robustness. Note that sensors may be embedded in the same enclosure to measure simultaneously any needed additional variables with the same pocket of gas (humidity, temperature, pressure, other gases, etc.). The environmental protection improves dust and frost protection of the system and enables explosion-proof sensors; ii) the response time of the sensors can be matched to digital averaging time or other operations that average the measurement data of the sensors over time; and iii) the response time of the sensors can be matched to atmospheric correlations.

[0088] In other embodiments, the sensor enclosure can be adapted to include passive sensors suitable for measuring the concentration of other gases, such as SF6, NH3, NOx, H2S, etc.

[0089] In some embodiments, the methods and system of the present disclosure may involve a computing system. Fig. 9 illustrates an example computing system 2500, with a processor 2502 and memory 2504 that can be configured to implement various embodiments of the automated systems and methods for methane emissions monitoring as discussed in the present application. Memory 2504 can also host one or more databases and can include one or more forms of volatile data storage media such as random-access memory (RAM), and/or one or more forms of nonvolatile storage media (such as read-only memory (ROM), flash memory, and so forth).

[0090] Device 2500 is one example of a computing device or programmable device and is not intended to suggest any limitation as to scope of use or functionality of device 2500 and/or its possible architectures. For example, device 2500 can comprise one or more computing devices, programmable logic controllers (PLCs), etc.

[0091] Further, device 2500 should not be interpreted as having any dependency relating to one or a combination of components illustrated in device 2500. For example, device 2500 may include one or more of computers, such as a laptop computer, a desktop computer, a mainframe computer, etc., or any combination or accumulation thereof.

[0092] Device 2500 can also include a bus 2508 configured to allow various components and devices, such as processors 2502, memory 2504, and local data storage 2510, among other components, to communicate with each other.

[0093] Bus 2508 can include one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures. Bus 2508 can also include wired and/or wireless buses.

[0094] Local data storage 2510 can include fixed media (e g., RAM, ROM, a fixed hard drive, etc.) as well as removable media (e.g., a flash memory drive, a removable hard drive, optical disks, magnetic disks, and so forth). One or more input/output (I/O) device(s) 2512 may also communicate via a user interface (UT) controller 2514, which may connect with I/O device(s) 2512 either directly or through bus 2508.

[0095] In one possible implementation, a network interface 2516 may communicate outside of device 2500 via a connected network. A media drive/interface 2518 can accept removable tangible media 2520, such as flash drives, optical disks, removable hard drives, software products, etc. In one possible implementation, logic, computing instructions, and/or software programs comprising elements of module 2506 may reside on removable media 2520 readable by media drive/interface 2518.

[0096] In one possible embodiment, input/output device(s) 2512 can allow a user (such as a human annotator) to enter commands and information to device 2500, and also allow information to be presented to the user and/or other components or devices. Examples of input device(s) 2512 include, for example, sensors, a keyboard, a cursor control device (e.g., a mouse), a microphone, a scanner, and any other input devices known in the art. Examples of output devices include a display device (e g., a monitor or projector), speakers, a printer, a network card, and so on.

[0097] Various systems and processes of present disclosure may be described herein in the general context of software or program modules, or the techniques and modules may be implemented in pure computing hardware. Software generally includes routines, programs, objects, components, data structures, and so forth that perform particular tasks or implement particular abstract data types. An implementation of these modules and techniques may be stored on or transmitted across some form of tangible computer-readable media. Computer- readable media can be any available data storage medium or media that is tangible and can be accessed by a computing device. Computer readable media may thus comprise computer storage media. “Computer storage media” designates tangible media, and includes volatile and nonvolatile, removable, and non-removable tangible media implemented for storage of information such as computer readable instructions, data structures, program modules, or other data.

Computer storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other tangible medium which can be used to store the desired information, and which can be accessed by a computer.

[0098] Some of the methods and processes described above, can be performed by a processor. The term “processor” should not be construed to limit the embodiments disclosed herein to any particular device type or system. The processor may include a computer system. The computer system may also include a computer processor (e.g., a microprocessor, microcontroller, digital signal processor, general-purpose computer, special-purpose machine, virtual machine, software container, or appliance) for executing any of the methods and processes described above.

[0099] The computer system may further include a memory such as a semiconductor memory device (e.g., a RAM, ROM, PROM, EEPROM, or Flash-Programmable RAM), a magnetic memory device (e.g., a diskette or fixed disk), an optical memory device (e.g., a CD- ROM), a PC card (e.g., PCMCIA card), or other memory device.

[00100] Alternatively or additionally, the processor may include discrete electronic components coupled to a printed circuit board, integrated circuitry (e.g., Application Specific

Integrated Circuits (ASIC)), and/or programmable logic devices (e.g., a Field Programmable Gate Arrays (FPGA)). Any of the methods and processes described above can be implemented using such logic devices.

[00101] Some of the methods and processes described above, can be implemented as computer program logic for use with the computer processor. The computer program logic may be embodied in various forms, including a source code form or a computer executable form. Source code may include a series of computer program instructions in a variety of programming languages (e.g., an object code, an assembly language, or a high-level language such as C, C++, or JAVA). Such computer instructions can be stored in a non-transitory computer readable medium (e.g., memory) and executed by the computer processor. The computer instructions may be distributed in any form as a removable storage medium with accompanying printed or electronic documentation (e.g., shrink wrapped software), preloaded with a computer system (e.g., on system ROM or fixed disk), or distributed from a server or electronic bulletin board over a communication system (e.g., the Internet or World Wide Web).

[00102] Although only a few example embodiments have been described in detail above, those skilled in the art will readily appreciate that many modifications are possible in the example embodiments without materially departing from this invention. Accordingly, all such modifications are intended to be included within the scope of this disclosure as defined in the following claims. In the claims, means-plus-function clauses are intended to cover the structures described herein as performing the recited function and not only structural equivalents, but also equivalent structures. Thus, although a nail and a screw may not be structural equivalents in that a nail employs a cylindrical surface to secure wooden parts together, whereas a screw employs a helical surface, in the environment of fastening wooden parts, a nail and a screw may be equivalent structures. It is the express intention of the applicant not to invoke 35 U.S.C. § 112, paragraph 6 for any limitations of any of the claims herein, except for those in which the claim expressly uses the words ‘means for’ together with an associated function.