Patent Description:
The present invention applies to monitoring and controlling flare systems.

Flare systems include gas flares (or flare stacks) that provide gas combustion at industrial plants such as at onshore and offshore oil and gas production sites. Flare systems can provide venting during start-up or shut-down, and can handle emergency releases from safety valves, blow-down, and de-pressuring systems.

<CIT> describes a flare control method and a flare apparatus for automatically controlling, in real-time, the flow of one or more of fuel, steam, and air to a flare.

<CIT> describes a system for flare combustion control includes a sound speed measurement device for measuring sound speed in a flare vent gas, and a flare combustion controller including a memory and a processor. The processor is configured to receive the measured sound speed and determine, based on the measured sound speed, a molecular weight of the flare vent gas. The processor is further configured to determine, based on the determined molecular weight, a net heating value of the flare vent gas, and adjust the net heating value of the flare vent gas by regulating an amount of a supplemental fuel gas in the flare vent gas.

The present invention describes techniques that can be used for monitoring and controlling flare systems. In some implementations, a computer-implemented method includes the following. Instantaneous flaring flowrate data is received from flaring sources of a flare network of a processing facility. The instantaneous flaring flowrate data is analyzed in conjunction with physical properties of relief sources obtained from a heat and material balance of the processing facility. A heating value and a molecular weight are determined for each relief source and flare header using a processing model associated with a relief source type, size, and identifications. The relief sources are connected using a data signal received and processed using the processing model. Reports are generated showing average daily heating values and molecular weights for each flare header. A real-time display is provided for monitoring instantaneous heating values and molecular weights for each flare header on a real-time basis.

The previously described implementation is implementable using a computer-implemented method; a non-transitory, computer-readable medium storing computer-readable instructions to perform the computer-implemented method; and a computer-implemented system including a computer memory interoperably coupled with a hardware processor configured to perform the computer-implemented method, the instructions stored on the non-transitory, computer-readable medium.

The subject matter described in this specification can be implemented in particular implementations, so as to realize one or more of the following advantages. The flare monitoring and controlling system can aid operators in reducing, for example, supplement cover gas that is added in acid gas flare systems. This can occur when the flared gas heating value is below a minimum design requirement or below a minimum standard requirement of a company running the system. Reducing supplement cover gas can lead to a significant reduction in intermittent purge gas used as a supplement. The flare monitoring and controlling system can also help a plant in reducing their emissions by improving the combustion efficiency of flare gas. Knowledge of instantaneous heating values of flared gas can help operators to control assist gas and air to achieve smokeless operations, which can then lead to minimizing emissions. Since every flare tip is designed for a minimum heating value in order for it operate within its smokeless capacity, knowing the heating value can allow operators to meet the design requirement and hence improve the reliability of the flare tip. In addition, real-time molecular weight results can aid operators in minimizing the downtime of flow maters and in improving the emissions calculation accuracy. This can help to measure and monitor the heating value of each flare header and the molecular weight which will help in: reducing combustible fluid losses (or de-carbonization), reducing emissions by improving combustion efficiency, enhancing flare tip reliability, calibrating flow meters, and improving the accuracy of greenhouse gas (GHG) emission calculations. The techniques of the present invention can compute heating values based on data from individual flaring sources. This provides a higher accuracy as compared to utilizing composition at the end of the header, as done by conventional systems, which may have a limitation on measuring ranges and may require frequent calibration and maintenance. The techniques of the present invention have no limitations in reading range and require no maintenance, ensuring accurate results at all times and avoiding uncertainties in the readings. No costly devices are required to be installed at a facility.

The details of one or more implementations of the subject matter of this specification are set forth in the Detailed Description, the accompanying drawings, and the claims. Other features, aspects, and advantages of the subject matter will become apparent from the Detailed Description, the claims, and the accompanying drawings.

The following detailed description describes techniques for monitoring and controlling flare systems. Various modifications, alterations, and permutations of the disclosed implementations can be made and will be readily apparent to those of ordinary skill in the art, and the general principles defined may be applied to other implementations and applications, without departing from scope of the invention. In some instances, details unnecessary to obtain an understanding of the described subject matter may be omitted so as to not obscure one or more described implementations with unnecessary detail and inasmuch as such details are within the skill of one of ordinary skill in the art. The present invention is not intended to be limited to the described or illustrated implementations, but to be accorded the widest scope consistent with the described principles and features.

A flare system heating value monitoring system can be used as a solution that provides the capability to compute actual heating values (for example, heat of combustion) and molecular weights of flared gas for each header of a flare network. The system can receive instantaneous flaring flowrate data from a processing facility's flaring sources and can analyze the data in conjunction with the heat and material balance of the processing facility. The data can then be used to perform a comprehensive heating value and molecular weight calculation for each flare header throughout the flare network.

The results of the analysis can be provided to operators in the form of reports that show average daily heating values and molecular weights for each flare header. A user interface can provide a real-time display to monitor instantaneous heating values and molecular weights for each flare header. This solution can aid operators in monitoring the flare gas heating value and molecular weights in real-time and can help in maintaining required minimum heating values. The term real-time can correspond to events that occur within a specified period of time, for example, within a few seconds or a few minutes.

The system can also aid in optimizing supplement assist gas that is added to a network when the flare gas heating value is below a design value. The system can also help in enhancing the smokeless operation of flare systems by overcoming the challenge of the dynamic changes in compositions.

In some implementations, utilizing volumetric flowrate of each relief source by a flare network monitoring system can include the following. A flare monitoring system can receive real-time data associated with the release of a processing facility's combustible fluids to a flare stack. The data can be analyzed in conjunction with parameters of the processing facility's flare-through elements such as manual valves, control valves, restriction orifices, flow meters, and the like. The results of the analysis can be provided to operators in the form of reports that indicate: whether flaring events are of a routine or non-routine nature; the flared volume; the contribution of the flare-through elements to the flared volume; and so forth. The results can aid operators in reducing combustible fluid losses due to flaring and in mitigating emissions of sulfur, nitrogen and carbon dioxide.

The discharge composition of each relief source connected to the flare network can be used, for example, in calculating corresponding heating values and molecular weights of each relief device: <MAT> <MAT> <MAT> where HHVai is a higher heating value of relief device <NUM> (for example, in standard cubic feet (scf) per British thermal unit (scf/btu)); LHV d1 is a lower heating value of relief device <NUM> (for example, in scf/btu); MWd1 is the molecular weight of relief device <NUM> (for example, in pounds per pound-mole (lb/lb-mol)); Xi is a mole fraction of the component i; HHVi is a higher heating value of component i (for example, in scf/btu); LHVi is a lower heating value of component i (for example, in scf/btu); and MWi is the molecular weight of component i (for example, in lb/lb-mol).

Calculating the corresponding heating values and molecular weight of each flare header yields: <MAT> <MAT> <MAT> where HHVh1 is a higher heating value of flare header <NUM> (for example, in scf/btu); and LHVh1 = is a lower heating value of flare header <NUM> (for example, in scf/btu); MWh1 is the molecular weight of flare header <NUM> (for example, in lb/lb-mol); Xi is the mole fraction of the component i; HHVi is the higher heating value of component i (for example, in scf/btu); LHVi is the lower heating value of component i (for example, in scf/btu); and MWi is the molecular weight of component i (for example, in lb/lb-mol).

Performance equation (for example, a performance index (PI) expiration) can be developed using Equations (<NUM>) to (<NUM>) to create PI tags on a PI server. The PI tags can be used in a real-time display of a facility, for example, in a monitoring dashboard used to illustrate and monitor actual flaring compositions.

<FIG> is a flow diagram showing an example of a workflow <NUM> for generating a real-time display for a flare monitoring system, according to some implementations of the present invention. At <NUM>, flare sources flow performance equations are established by a flare monitoring system (FMS) <NUM>. At <NUM>, the compositions <NUM> of each relief source are used to calculate HHV, LHV, and MW values for each device. At <NUM>, HHV, LHV, and MW values are calculated for each header. At <NUM>, performance equations are developed for each component and stored on a PI server <NUM>. At <NUM>, a real-time display and reporting dashboard is developed, using the PI server <NUM>, to display daily values.

<FIG> is a screenshot showing an example of a user interface <NUM> for displaying composition information, according to some implementations of the present invention.

The user interface <NUM> includes a graph area <NUM> which demonstrates a daily trend of the lower and higher heating value of the flared hydrocarbon. An area <NUM> includes a display of hydrocarbon flaring and non-hydrocarbon flaring volumes. An area <NUM> illustrates a dropdown list of operating facilities that the user can select to view the results. The dropdown list is based on mapping each individual operating facility with a unique site ID in the data base.

An area <NUM> displays information that demonstrates the cumulative values of emissions for the selected operating facility, header, and time frame. The emissions include methane, carbon dioxide, nitrogen oxide, and sulfur dioxide. An area <NUM> shows an average value of a carbon dioxide equivalent attributed to flaring for the selected operating facility and timeframe. An area <NUM> this shows an average value of molecular weight attributed to flaring for the selected operating facility and timeframe. An area <NUM> shows an average value of heating value attributed to flaring for the selected operating facility and timeframe. An area <NUM> includes navigation buttons from which users can display daily trends of the selected parameters including the flaring molecular weight and heating value.

<FIG> is a graph <NUM> showing example sour header values over time, according to some implementations of the present invention. For example, the graph <NUM> shows real-time trends of the heating value <NUM> and molecular weight <NUM>. Region <NUM> on the graph <NUM> shows a time period during which the heating value of the flared gasses has elevated, indicating that a flaring source with higher hydrocarbon content was flowing into the flare system. Region <NUM> on the graph <NUM> also shows the molecular weight was reduced during the flaring event which indicated the properties of the relief sources that caused flaring.

<FIG> and <FIG> are graphs <NUM>, <NUM> showing examples of a molecular weight (MW) plot <NUM> and a heating value plot <NUM>. The MW plot is plotted relative to a time axis <NUM> and a MW axis <NUM>. The heating value plot <NUM> is plotted relative to a time axis <NUM> and a heating value axis <NUM>. Graphs <NUM> and <NUM> demonstrate that the molecular weight and heating value of the flared gasses fluctuates based on the sources of the flaring events which is computed by implementations of the present invention.

<FIG> is a block diagram showing an example of a system data flow <NUM> for flare analysis, according to some implementations of the present invention. A key <NUM> shows line styles for elements of the system data flow <NUM>, including tables <NUM>, views <NUM>, C# scripts <NUM>, and business intelligence (BI) units <NUM> for elements related to flare analyzers (FA) <NUM> and flare monitoring systems (FMS) <NUM>. Elements of the system data flow <NUM> include FMS. factDevice table <NUM>, FMS. factHeader table <NUM>, FA. component table <NUM>; FA. device table <NUM>, flare analyzer script(s) <NUM>, FA. D_PhysicalProperties view <NUM>; FA. factDevice table <NUM>, FA. factHeader table <NUM>, FA. environmentalPotential table <NUM>, FA. AnalyzerDevice table <NUM>, FA. FD_AnalyzerDevice view <NUM>, FA. FD_FH_AnalyzerHeader view <NUM>, flare analyzer script(s) <NUM>, FA. AnalyzerDevice table <NUM>, and FA. AnalyzerHeader table <NUM>.

<FIG> is a block diagram showing an example of a system data flow <NUM> for flare analysis, according to some implementations of the present invention. The system data flow <NUM> includes some of the same elements and types of elements as the system data flow <NUM> of <FIG>. Together, data flows <NUM> and <NUM> are used for flare analysis. The system data flow <NUM> includes FA. AnalyzerDevice table <NUM>, FA. plant table <NUM>, FA. AnalyzerHeader table <NUM>, FA. device table <NUM>, FA. v_byPlantEmissions <NUM>, FA. v_date view <NUM>, FA. v_AnalyzerHeader view <NUM>, FA. v_emissions view <NUM>, FA. v_ComponentsDailyFlaring view <NUM>, FA. v_HCvsNonHC view <NUM>, FA. v_site, view <NUM> FA. v_headers view <NUM>, Emissions by Plant BI <NUM>, Date Slicer BI <NUM>, By Header Dashboard BI <NUM>, Emissions Reporting BI <NUM>, Flaring by Component BI <NUM>, Daily Flaring BI <NUM>, Site Slicer BI <NUM>, and Header Slicer BI <NUM>.

The resulting two tables from <FIG>, FA. AnalyzerDevice table <NUM> and FA. AnalyzerHeader table <NUM> can be used as the main data sources for the POWER BI elements, including Emissions by Plant <NUM>, Date Slicer <NUM>, By Header Dashboard <NUM>, Emissions Reporting <NUM>, Flaring by Component <NUM>. and Daily Flaring <NUM>.

<FIG> is a flowchart of an example of a method <NUM> for generating a real-time display to monitor instantaneous heating values and molecular weights for flare headers, according to some implementations of the present invention. For clarity of presentation, the description that follows generally describes method <NUM> in the context of the other figures in this description. However, it will be understood that method <NUM> can be performed, for example, by any suitable system, environment, software, and hardware, or a combination of systems, environments, software, and hardware, as appropriate. In some implementations, various steps of method <NUM> can be run in parallel, in combination, in loops, or in any order.

At <NUM>, instantaneous flaring flowrate data is received from flaring sources of a flare network of a processing facility. For example, flaring data can be received from an onshore or offshore oil or gas production site or refinery. From <NUM>, method <NUM> proceeds to <NUM>.

At <NUM>, the instantaneous flaring flowrate data is analyzed in conjunction with the physical properties of a relief source using a heat and material balance of the processing facility. For example, analyzing the instantaneous flaring flowrate data includes using a data flow network of tables, views, scripts, and power business intelligence (BI) elements, as described with reference to <FIG> and <FIG>. The data flow network of tables, views, and scripts can further be stored in a data historian model operable to store into memory: parameters of flare-through elements concerning a relationship between generated data signals and a quantitative heating value and a molecular weight at each relief source; data associated with a heating value and a molecular weight of the flare header; and data associated with a heating value and a molecular weight for each plant. From <NUM>, method <NUM> proceeds to <NUM>.

At <NUM>, a heating value and a molecular weight for each relief source and flare header are determined using one or more processors and using a processing model associated with a relief source type, size, and identifications. This can be part of performing a comprehensive heating value and molecular weight calculation for each flare header throughout the flare network. The relief sources can be connected using a data signal received and processed using the processing model. As an example, graphs <NUM> and <NUM> can be generated that display the MW plot <NUM> and the heating value plot <NUM>, respectively. The calculations can be based on Equations (<NUM>) to (<NUM>), for example. From <NUM>, method <NUM> proceeds to <NUM>.

At <NUM>, reports are generated showing average daily heating values and molecular weights for each flare header. As an example, generating reports can include identifying whether particular flaring events are of a routine or non-routine nature, a flared volume, and a contribution of the flare-through elements to the flared volume. The reports can be accessible from within a user interface, such as described with reference to <FIG>. From <NUM>, method <NUM> proceeds to <NUM>.

At <NUM>, a real-time display is provided to monitor instantaneous heating values and molecular weights for each flare header in real time basis. For example, providing the real-time display can include displaying, for each flare header, heating values over time. In another example, the real-time display can include displaying molecular weights and a heating value. In another example, providing the real-time display can include displaying, for each flare header, a graph showing significant fluctuations in reading relative to a time period. After <NUM>, method <NUM> can stop.

Pilot experiments were run on a refinery using techniques of the present disclosure. Unexpected (high) heating values of flared gas were detected at one of the flare headers, leading to further investigation on the relief sources. The investigation results determined that the refinery was using a significant amount of hydrogen in its flare system which was resulting in high heating values.

<FIG> is a block diagram of an example computer system <NUM> used to provide computational functionalities associated with described algorithms, methods, functions, processes, flows, and procedures described herein, according to some implementations of the present invention. The illustrated computer <NUM> is intended to encompass any computing device such as a server, a desktop computer, a laptop/notebook computer, a wireless data port, a smart phone, a personal data assistant (PDA), a tablet computing device, or one or more processors within these devices, including physical instances, virtual instances, or both. The computer <NUM> can include input devices such as keypads, keyboards, and touch screens that can accept user information. Also, the computer <NUM> can include output devices that can convey information associated with the operation of the computer <NUM>. The information can include digital data, visual data, audio information, or a combination of information. The information can be presented in a graphical user interface (UI) (or GUI).

The computer <NUM> can serve in a role as a client, a network component, a server, a database, a persistency, or components of a computer system for performing the subject matter described herein.

At a top level, the computer <NUM> is an electronic computing device operable to receive, transmit, process, store, and manage data and information associated with the described subject matter. According to some implementations, the computer <NUM> can also include, or be communicably coupled with, an application server, an email server, a web server, a caching server, a streaming data server, or a combination of servers.

The computer <NUM> can receive requests over network <NUM> from a client application (for example, executing on another computer <NUM>). The computer <NUM> can respond to the received requests by processing the received requests using software applications. Requests can also be sent to the computer <NUM> from internal users (for example, from a command console), external (or third) parties, automated applications, entities, individuals, systems, and computers.

Each of the components of the computer <NUM> can communicate using a system bus <NUM>. In some implementations, any or all of the components of the computer <NUM>, including hardware or software components, can interface with each other or the interface <NUM> (or a combination of both) over the system bus <NUM>. Interfaces can use an application programming interface (API) <NUM>, a service layer <NUM>, or a combination of the API <NUM> and service layer <NUM>. The API <NUM> can include specifications for routines, data structures, and object classes. The API <NUM> can be either computer-language independent or dependent. The API <NUM> can refer to a complete interface, a single function, or a set of APIs.

The service layer <NUM> can provide software services to the computer <NUM> and other components (whether illustrated or not) that are communicably coupled to the computer <NUM>. The functionality of the computer <NUM> can be accessible for all service consumers using this service layer. Software services, such as those provided by the service layer <NUM>, can provide reusable, defined functionalities through a defined interface. For example, the interface can be software written in JAVA, C++, or a language providing data in extensible markup language (XML) format. While illustrated as an integrated component of the computer <NUM>, in alternative implementations, the API <NUM> or the service layer <NUM> can be stand-alone components in relation to other components of the computer <NUM> and other components communicably coupled to the computer <NUM>. Moreover, any or all parts of the API <NUM> or the service layer <NUM> can be implemented as child or sub-modules of another software module, enterprise application, or hardware module without departing from the scope of the present invention.

The computer <NUM> includes an interface <NUM>. Although illustrated as a single interface <NUM> in <FIG>, two or more interfaces <NUM> can be used according to particular needs, desires, or particular implementations of the computer <NUM> and the described functionality. The interface <NUM> can be used by the computer <NUM> for communicating with other systems that are connected to the network <NUM> (whether illustrated or not) in a distributed environment. Generally, the interface <NUM> can include, or be implemented using, logic encoded in software or hardware (or a combination of software and hardware) operable to communicate with the network <NUM>. More specifically, the interface <NUM> can include software supporting one or more communication protocols associated with communications. As such, the network <NUM> or the interface's hardware can be operable to communicate physical signals within and outside of the illustrated computer <NUM>.

Generally, the processor <NUM> can execute instructions and can manipulate data to perform the operations of the computer <NUM>, including operations using algorithms, methods, functions, processes, flows, and procedures as described herein.

The computer <NUM> also includes a database <NUM> that can hold data for the computer <NUM> and other components connected to the network <NUM> (whether illustrated or not). For example, database <NUM> can be an in-memory, conventional, or a database storing data consistent with the present invention. In some implementations, database <NUM> can be a combination of two or more different database types (for example, hybrid in-memory and conventional databases) according to particular needs, desires, or particular implementations of the computer <NUM> and the described functionality. Although illustrated as a single database <NUM> in <FIG>, two or more databases (of the same, different, or combination of types) can be used according to particular needs, desires, or particular implementations of the computer <NUM> and the described functionality. While database <NUM> is illustrated as an internal component of the computer <NUM>, in alternative implementations, database <NUM> can be external to the computer <NUM>.

The computer <NUM> also includes a memory <NUM> that can hold data for the computer <NUM> or a combination of components connected to the network <NUM> (whether illustrated or not). Memory <NUM> can store any data consistent with the present invention. In some implementations, memory <NUM> can be a combination of two or more different types of memory (for example, a combination of semiconductor and magnetic storage) according to particular needs, desires, or particular implementations of the computer <NUM> and the described functionality. Although illustrated as a single memory <NUM> in <FIG>, two or more memories <NUM> (of the same, different, or combination of types) can be used according to particular needs, desires, or particular implementations of the computer <NUM> and the described functionality. While memory <NUM> is illustrated as an internal component of the computer <NUM>, in alternative implementations, memory <NUM> can be external to the computer <NUM>.

There can be any number of computers <NUM> associated with, or external to, a computer system containing computer <NUM>, with each computer <NUM> communicating over network <NUM>. Further, the terms "client," "user," and other appropriate terminology can be used interchangeably, as appropriate, without departing from the scope of the present invention. Moreover, the present invention contemplates that many users can use one computer <NUM> and one user can use multiple computers <NUM>.

Implementations of the subject matter and the functional operations described in this specification can be implemented in digital electronic circuitry, in tangibly embodied computer software or firmware, in computer hardware, including the structures disclosed in this specification and their structural equivalents, or in combinations of one or more of them. Software implementations of the described subject matter can be implemented as one or more computer programs. Each computer program can include one or more modules of computer program instructions encoded on a tangible, non-transitory, computer-readable computer-storage medium for execution by, or to control the operation of, data processing apparatus. Alternatively, or additionally, the program instructions can be encoded in/on an artificially generated propagated signal. For example, the signal can be a machine-generated electrical, optical, or electromagnetic signal that is generated to encode information for transmission to a suitable receiver apparatus for execution by a data processing apparatus. The computer-storage medium can be a machine-readable storage device, a machine-readable storage substrate, a random or serial access memory device, or a combination of computer-storage mediums.

The terms "data processing apparatus," "computer," and "electronic computer device" (or equivalent as understood by one of ordinary skill in the art) refer to data processing hardware. For example, a data processing apparatus can encompass all kinds of apparatuses, devices, and machines for processing data, including by way of example, a programmable processor, a computer, or multiple processors or computers. The apparatus can also include special purpose logic circuitry including, for example, a central processing unit (CPU), a field-programmable gate array (FPGA), or an application-specific integrated circuit (ASIC). In some implementations, the data processing apparatus or special purpose logic circuitry (or a combination of the data processing apparatus or special purpose logic circuitry) can be hardware- or software-based (or a combination of both hardware- and software-based). The apparatus can optionally include code that creates an execution environment for computer programs, for example, code that constitutes processor firmware, a protocol stack, a database management system, an operating system, or a combination of execution environments. The present disclosure contemplates the use of data processing apparatuses with or without conventional operating systems, such as LINUX, UNIX, WINDOWS, MAC OS, ANDROID, or IOS.

A computer program, which can also be referred to or described as a program, software, a software application, a module, a software module, a script, or code, can be written in any form of programming language. Programming languages can include, for example, compiled languages, interpreted languages, declarative languages, or procedural languages. Programs can be deployed in any form, including as stand-alone programs, modules, components, subroutines, or units for use in a computing environment. A program can be stored in a portion of a file that holds other programs or data, for example, one or more scripts stored in a markup language document, in a single file dedicated to the program in question, or in multiple coordinated files storing one or more modules, sub-programs, or portions of code. A computer program can be deployed for execution on one computer or on multiple computers that are located, for example, at one site or distributed across multiple sites that are interconnected by a communication network. While portions of the programs illustrated in the various figures may be shown as individual modules that implement the various features and functionality through various objects, methods, or processes, the programs can instead include a number of sub-modules, third-party services, components, and libraries. Conversely, the features and functionality of various components can be combined into single components as appropriate. Thresholds used to make computational determinations can be statically, dynamically, or both statically and dynamically determined.

Computers suitable for the execution of a computer program can be based on one or more of general and special purpose microprocessors and other kinds of CPUs. The elements of a computer are a CPU for performing or executing instructions and one or more memory devices for storing instructions and data. Generally, a CPU can receive instructions and data from (and write data to) a memory.

Graphics processing units (GPUs) can also be used in combination with CPUs. The GPUs can provide specialized processing that occurs in parallel to processing performed by CPUs. The specialized processing can include artificial intelligence (AI) applications and processing, for example. GPUs can be used in GPU clusters or in multi-GPU computing.

A computer can include, or be operatively coupled to, one or more mass storage devices for storing data. In some implementations, a computer can receive data from, and transfer data to, the mass storage devices including, for example, magnetic, magneto-optical disks, or optical disks. Moreover, a computer can be embedded in another device, for example, a mobile telephone, a personal digital assistant (PDA), a mobile audio or video player, a game console, a global positioning system (GPS) receiver, or a portable storage device such as a universal serial bus (USB) flash drive.

Computer-readable media (transitory or non-transitory, as appropriate) suitable for storing computer program instructions and data can include all forms of permanent/non-permanent and volatile/non-volatile memory, media, and memory devices. Computer-readable media can include, for example, semiconductor memory devices such as random access memory (RAM), read-only memory (ROM), phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), and flash memory devices. Computer-readable media can also include, for example, magnetic devices such as tape, cartridges, cassettes, and internal/removable disks. Computer-readable media can also include magneto-optical disks and optical memory devices and technologies including, for example, digital video disc (DVD), CD-ROM, DVD+/-R, DVD-RAM, DVD-ROM, HD-DVD, and BLU-RAY. The memory can store various objects or data, including caches, classes, frameworks, applications, modules, backup data, jobs, web pages, web page templates, data structures, database tables, repositories, and dynamic information. Types of objects and data stored in memory can include parameters, variables, algorithms, instructions, rules, constraints, and references. Additionally, the memory can include logs, policies, security or access data, and reporting files. The processor and the memory can be supplemented by, or incorporated into, special purpose logic circuitry.

Implementations of the subject matter described in the present invention can be implemented on a computer having a display device for providing interaction with a user, including displaying information to (and receiving input from) the user. Types of display devices can include, for example, a cathode ray tube (CRT), a liquid crystal display (LCD), a light-emitting diode (LED), and a plasma monitor. Display devices can include a keyboard and pointing devices including, for example, a mouse, a trackball, or a trackpad. User input can also be provided to the computer through the use of a touchscreen, such as a tablet computer surface with pressure sensitivity or a multi-touch screen using capacitive or electric sensing. Other kinds of devices can be used to provide for interaction with a user, including to receive user feedback including, for example, sensory feedback including visual feedback, auditory feedback, or tactile feedback. Input from the user can be received in the form of acoustic, speech, or tactile input. In addition, a computer can interact with a user by sending documents to, and receiving documents from, a device that the user uses. For example, the computer can send web pages to a web browser on a user's client device in response to requests received from the web browser.

The term "graphical user interface," or "GUI," can be used in the singular or the plural to describe one or more graphical user interfaces and each of the displays of a particular graphical user interface. Therefore, a GUI can represent any graphical user interface, including, but not limited to, a web browser, a touch-screen, or a command line interface (CLI) that processes information and efficiently presents the information results to the user. In general, a GUI can include a plurality of user interface (UI) elements, some or all associated with a web browser, such as interactive fields, pull-down lists, and buttons. These and other UI elements can be related to or represent the functions of the web browser.

Implementations of the subject matter described in this specification can be implemented in a computing system that includes a back-end component, for example, as a data server, or that includes a middleware component, for example, an application server. Moreover, the computing system can include a front-end component, for example, a client computer having one or both of a graphical user interface or a Web browser through which a user can interact with the computer. The components of the system can be interconnected by any form or medium of wireline or wireless digital data communication (or a combination of data communication) in a communication network. Examples of communication networks include a local area network (LAN), a radio access network (RAN), a metropolitan area network (MAN), a wide area network (WAN), Worldwide Interoperability for Microwave Access (WIMAX), a wireless local area network (WLAN) (for example, using <NUM> a/b/g/n or <NUM> or a combination of protocols), all or a portion of the Internet, or any other communication system or systems at one or more locations (or a combination of communication networks). The network can communicate with, for example, Internet Protocol (IP) packets, frame relay frames, asynchronous transfer mode (ATM) cells, voice, video, data, or a combination of communication types between network addresses.

Cluster file systems can be any file system type accessible from multiple servers for read and update. Locking or consistency tracking may not be necessary since the locking of exchange file system can be done at application layer. Furthermore, Unicode data files can be different from non-Unicode data files.

While this specification contains many specific implementation details, these should not be construed as limitations on the scope of what may be claimed, but rather as descriptions of features that may be specific to particular implementations. Certain features that are described in this specification in the context of separate implementations can also be implemented, in combination, in a single implementation. Conversely, various features that are described in the context of a single implementation can also be implemented in multiple implementations, separately, or in any suitable sub-combination. Moreover, although previously described features may be described as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can, in some cases, be excised from the combination, and the claimed combination may be directed to a sub-combination or variation of a sub-combination.

Moreover, the separation or integration of various system modules and components in the previously described implementations should not be understood as requiring such separation or integration in all implementations. It should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products.

Accordingly, the previously described example implementations do not define or constrain the present invention. Other changes, substitutions, and alterations are also possible without departing from the claims.

Claim 1:
A computer-implemented method, comprising:
receiving (<NUM>) instantaneous flaring flowrate data from flaring sources of a flare network of a processing facility;
analyzing (<NUM>) the instantaneous flaring flowrate data in conjunction with the physical properties of relief sources obtained from a heat and material balance of the processing facility;
determining (<NUM>), using a processing model associated with a relief source type, size, and identifications, a heating value and a molecular weight for each relief source and flare header, wherein the relief sources are connected using a data signal received and processed using the processing model;
generating (<NUM>) reports showing average daily heating values and molecular weights for each flare header; and
providing (<NUM>) a real-time display (<NUM>, <NUM>, <NUM>, <NUM>) to monitor instantaneous heating values and molecular weights for each flare header on a real-time basis.