Engineers expend great efforts to make devices easy to assemble, reliable to operate, and amenable to maintenance and repair tasks. Hardware constraints can frustrate these efforts because the hardware lacks appropriate functionality and because any improvements can increase costs and/or add complexity to the device. In metrology hardware (e.g., gas meters), the constraints may result from “legal metrology” standards that regulatory bodies promulgate under authority or legal framework of a given country or territory. These standards may be in place to protect public interests, for example, to provide consumer protections for metering and billing use of fuel. These protections may set definitions for units of measure, realization of these units of measure in practice, application of traceability for linking measurement of the units made in practice to the standards and, importantly, ensure accuracy of measurements.
The subject matter of this disclosure relates to metrology. Of particular interest herein are improvements that configure a metering system to perform in situ verification of components. These improvements, in turn, may permit the metering system to integrate components that are approved (or certified) to meet legal metrology standards separately or independently from the metering system. The in situ verification process may result in a “modular” structure for components to “swap” into and out of the metering system. This feature may reduce costs of manufacture, as well as to simplify tasks to expand or modify functionality of the measurement system in the field, while ensuring that the measurement system still meets legal metrology standards.
Reference is now made briefly to the accompanying figures, in which:
Where applicable like reference characters designate identical or corresponding components and units throughout the several views, which are not to scale unless otherwise indicated. The embodiments disclosed herein may include elements that appear in one or more of the several views or in combinations of the several views. Moreover, methods are exemplary only and may be modified by, for example, reordering, adding, removing, and/or altering the individual stages.
The discussion herein describes various embodiments of a metering system. These embodiments may find use in billing applications in which legal metrology standards dictate accuracy and reliability of values for measured parameters because these values may find use to charge customers. Other embodiments and applications are within the scope of the subject matter.
At a high level, the accessory 126 may also be configured to ensure in situ that the metrology devices 112, 114 meet appropriate legal metrology standards. This configuration creates a “modular” structure for the metering system 100. The modular structure may permit the metrology devices 112, 114 to be certified separate from, or independent of, the metering system 100 as a whole, which often occurs at the time of manufacture, assembly, maintenance, or reconfiguration of these systems. In this way, the metrology devices 112, 114 can swap into and out of the metering system 100 in favor of a different device or to add additional devices, as desired. This feature is useful, for example, to remediate, expand, or change functionality of the metering system 100 in the field as well as to simplify manufacture, calibration, and re-calibration of the metering system 100 and its components (e.g. metrology devices 112, 114) to meet specific customer requirements.
Metrology devices 112, 114 can be configured to generate data that is useful to quantify the measured parameters for material 104. These configurations can embody stand-alone devices that couple with the accessory 126. Examples of suitable devices may process analog signals that originate, for example, from sensors that interact with material 104. These processes may result in first signals 116 in digital format. During manufacture, the devices 112, 114 can be tested and certified to meet legal metrology standards prior to use in the metering system 100. The devices 112, 114 may also undergo calibration procedures to store data (e.g., constants, coefficients, etc.) on, for example, storage memory that is resident on the device. This data may relate to analog data (from the sensors) to values that comport with the digital format of the first signals 116 that can transmit to the accessory 126.
The display 118 may be configured to operate in response to second signal 128. These configurations may embody devices that activate to provide visual (or audio) indicators of the values for the measured parameters for material 104. Exemplary devices may reside separate or remote from the accessory 126. But this disclosure does contemplate devices for the display 118 that integrate as part of the accessory 126.
Diagnostics 120 may be configured to monitor operation of the metering system 100. These configurations may embody a separate device, but executable instructions that integrate onto one or more of the metrology devices 112, 114 or accessory 126 may also be useful for this purpose. These embodiments may process data, for example, from the metrology devices 112, 114 or from other sensors and sensing devices. These processes can result in information that the accessory 126 can utilize to identify operating anomalies that might indicate problematic conditions or to operation of the metering system 100. For gas metering applications, diagnostics 120 may monitor differential pressure across the gas meter against threshold criteria to convey information that corresponds with changes in differential pressure to the accessory 126. The accessory 126 may use this information to generate alerts, faults, or other indicators of problems that might require maintenance to occur on the metering system 100.
The other peripheral components 122, 124, 125 may include devices that are useful to operate the metering system 100. The devices may integrate into the metrology devices 112, 114 and the accessory 126 or may embody separate structures that couple variously to components of the metering system 100. The power source 120 may provide electrical power. Batteries may be useful for this purpose. The timing unit 122 may maintain “standard” time to synchronize time, measurements, or calculations on the metering system 100, generally, or on the metrology devices 112, 114 or the accessory 126, individually. The communication device 125 may be configured to convert the second signal 128 from one protocol to another protocol. For example, these configurations may change the second signal 128 to a MODBUS protocol that billing systems can use to accurately associate data from the meter 112 to monetary values that are billed to customers.
The accessory 126 may be configured to process the data from first signals 116. Predominantly, the signals 116 are in digital format. The process may generate values for the measured parameters for material 104. In one implementation, the accessory 126 may operate to vary the format or substance of second signal 128. These formats may be in analog (e.g., 4-20 mA) or digital. In one example, the digital format may embody pulses that reflect the gas volume measured by the meter 112.
The devices 127, 129 can be configured to measure different characteristics and conditions that may be useful to generate the measured parameters. The configurations could provide any variety of data for processing at the accessory 126. For gas metering applications, the meter 112 may embody a gas meter that can generate data that defines a value for flowing volume of material 104. The measuring devices 127, 129 may embody modules that can generate data that defines values for fluid conditions inside of the gas meter. These fluid conditions may include, for example, temperature from measuring device 127 and pressure from measuring device 129. First signals 116 may convey the data from each of the gas meter and modules to the accessory 126 in digital format. The accessory 126 can use the data from the modules to “adjust” or “correct” the flowing volume from the gas meter. These functions account for fluid conditions that prevail in the gas meter. In practice, the modules 127, 129 and the accessory 126 may form “a volume corrector.” Second signal 128 can convey a value from the accessory 126 to one or more of the peripherals 118, 120, 122, 124, 125. This value is the result of volume correction at the accessory 126.
Operation of the method 200 may ensure integrity of the metering system 102. The method 200 may include, at stage 202, receiving validation data from a metrology device. The method 200 may also include, at stage 204, accessing a registry with stored data in a listing having entries that associate metrology devices that might find use in the metering system with a regulatory status. The method 200 may further include, at stage 206, comparing the validation data to the stored data in the listing to determine whether the metrology device is approved for use in the metering system. If negative, the method 200 may include, at stage 208, setting a fault condition and, at stage 210, populating an event to an event log. Operation of the method 200 may cease at stage 210, effectively ceasing functioning of the metering system. In one implementation, the method 200 may return to receiving validation data at stage 202. On the other hand, if the metrology device is approved, the method 200 may include, at stage 212, commissioning the metrology device for use in the metering system and, where applicable, populating an event to an event log at stage 210.
At stage 202, the method 200 may receive validation data from the metrology devices 112, 114. The validation data may define or describe information that is unique (as compared to others) to the respective metrology devices 112, 114. Examples of the information may include serial numbers, cyclic redundancy check (CRC) numbers, checksum values, hash sum values, or the like. Other information may define operative conditions or status for the metrology devices 112, 114, for example, calibration data that is stored locally on the device. This information may be stored on the metrology devices 112, 114 at the time of manufacture. In one implementation, the metrology devices 112, 114 may be configured so that all or part of the validation data cannot be changed or modified once manufacture or assembly is complete. This feature may deter tampering to ensure that the metrology devices 112, 114 and the metering system 100, generally, will meet legal and regulatory requirements for purposes of metering of material 104.
At stage 204, the method 200 may access a registry with a listing of stored data that associates metrology devices with a regulatory status. Table 1 below provides an example of this listing.
The listing above may form an “integrity” log that the accessory 126 uses to properly evaluate and integrate the metrology devices 112, 114 into the metering system 100. Stored data in the entries may define various characteristics for metrology devices. As shown above, the listing may have entries for separate metrology devices, often distinguished by identifying information such as serial number (S/N) and device type. The entries may also include operating information that may relate specifically to the metrology device of the entry in the listing. The operating information may include calibration data, for example, values for constants and coefficients, as well as information (e.g., a date, a location, an operator) that describes the status of calibration for the metrology device of the entry in the listing. The operating information may further include firmware data, for example, information that describes the latest version that might be found on the metrology device.
The operating information may provide physical data as relates to operation of the metrology devices 112, 114 in the metering system 100. This physical data may correlate, for example, each metrology device with a “port” or connection on the accessory 126. As also shown, the entries in the listing may include a regulatory status that relates to the metrology device. This regulatory status may reflect that the metrology device is “approved” or “not approved;” however other indicators to convey that the metrology devices 112, 114 may or may not be acceptable for use in the metering system may be useful as well. Approval may indicate compliance with legal metrology standards as well as with appropriate calibration expectations, but this does not always need to be the case.
At stage 206, the method 200 may compare the validation data to the stored data in the listing to determine whether the metrology device is approved for use in the metering system. This stage is useful to certify that the metrology devices 112, 114 are “approved” and meet the necessary legal metrology standards prior to being introduced into the metering system 100. This stage may include one or more stages as necessary so as to properly commission the metrology devices 112, 114. These stages may, for example, include determining whether the metrology device 112, 114 meets certain initial criteria. The initial criteria may distinguish the metrology components by type (e.g., hardware and executable instructions), version or revision, model or serial number, and other functional or physical characteristics. For hardware, the method 200 may also include one or more stages to ensure that the metrology device 112, 114 is located or coupled with the accessory 126 at a location appropriate for its type and functions. The stages may use signals from connectors to discern the location of the hardware on the accessory 126.
The stages may also evaluate the status of the metrology device 112, 114. For hardware, these stages may include stages for identifying calibration data from among the validation data that is received from the metrology component. In one implementation, the method 200 may include stages for confirming that the calibration data has not been corrupted or does not include corrupt information. Corruption might happen, for example, as are result of tampering with the hardware or by exposing the hardware to environmental conditions (e.g., radiation, temperature, etc.). For firmware, the method 200 may use version history and related items that may be useful to distinguish one set of executable instructions from another as well as for purposes of confirming that the set of executable instructions has not been corrupted.
At stage 208, the method 200 may set a fault condition in response to the assessment of the validation data (at stage 206). Examples of the fault condition may take the form of an alert, either audio or visually discernable, or, in some examples, by way of electronic messaging (e.g., email, text message, etc.) that can resolve on a computing device like a smartphone or tablet. In one implementation, the fault condition may interfere with operation of one or more functions on the metering system 100, even ceasing functionality of the whole system if desired. The fault condition may also convey information about the status of the commissioning process. This information may indicate that serial numbers are incorrect or unreadable, that calibration of the metrology device 112, 114 is out of data or corrupted, or that firmware versions and updates on the metrology device are out of date or corrupted.
At stage 210, the method 200 can populate an event to the event log. This event log may reside on the accessory 126 as well as on the metrology devices 112, 114. In one implementation, the event can describe dated records of problems or issues that arise during the commissioning process. The event can also associate data and actions taken (e.g., calibration, updates, etc.) to commission the metrology component for use in the metering system 100. Relevant data may include updated to serial numbers and time stamps (e.g., month, day, year, etc.). The actions may identify an end user (e.g., a technician) and related password that could be required in order to change the configuration or update the metering system 100 with, for example, replacements for the metrology devices 112, 114 or the additional measuring device 126.
At stage 212, the method 200 can commission the metrology device for use in the metering system. This stage may change operation of the accessory 126 to accept or use the metrology component. Changes may update local firmware on the accessory 114; although this may not be necessary for operation of the metering system 100. In one implementation, change in the accessory 126 may update the integrity log to include new entries or to revise existing entries with information about the connected and commissioned metrology devices 112, 114.
At stage 214, the method 200 detects the change in state at the connection. As noted above, the change may correspond with a signal from a “port” on the accessory 126, possibly a connector or connecting device that the metrology device 112, 114 couples with on the metering system 100. The signal may correspond with a pin on the connector. Values for this signal may correspond with a high voltage and a low or zero voltage, one each to indicate that the pin on the connector is in use or not in use with respect to the connected hardware. The signal could also arise in response to updates in executable instructions on the accessory 126. In one implementation, the method 200 may include one or more stages for initiating a “handshake” in response to the signal. This handshake may cause the accessory 126 to transmit data to the metrology device 112, 114. In return, the metrology device 112, 114 may retrieve and transmit validation data to the accessory 126, as noted herein.
At stage 216, the method 200 determines the state of the connection. This stage may include one or more stages that compare the signal from the port to a look-up table or other threshold that indicates the state of the port. Open ports may indicate that hardware has been removed or is currently unavailable. On the other hand, closed ports may indicate that hardware is available to commence in situ commissioning process.
At stage 218, the method 200 initiates the commissioning process on the metering system. This stage may include one or more stages for receiving an input. Examples of the input may arise automatically, for example, based on a timer or other component internal to the accessory 126 that automatically polls the metrology devices 112, 114. In one implementation, the input may arise externally from a remote device (e.g., computer, laptop, tablet, smartphone) that connects with the metering system 100. This input may correspond with a technician plugging or unplugging one or more of the metrology devices 112, 114 from the accessory 126 (at stage 220). The external input may be necessary to allow the metering system to operate with any new or different devices 112, 114. Data of the input may include a user name and password. In one example, the method 200 may include stages to create an event (at stage 212) that corresponds with the manipulation of the devices 112, 114.
The circuit boards 128, 130, 132 can be configured with topology that uses discrete electrical components to facilitate operation of the system 102. This topology can include a substrate, preferably one or more printed circuit boards (PCB) of varying designs, although flexible printed circuit boards, flexible circuits, ceramic-based substrates, and silicon-based substrates may also suffice. For purposes of example, a collection of discrete electrical components may be disposed on the substrate to embody the functions of circuitry 136, 138, 140. Examples of discrete electrical components include transistors, resistors, and capacitors, as well as more complex analog and digital processing components (e.g., processors, storage memory, converters, etc.). This disclosure does not, however, foreclose use of solid-state devices and semiconductor devices, as well as full-function chips or chip-on-chip, chip-on-board, system-on chip, and like designs or technology known now or developed in the future.
Referring back to
Data 162, 176, 188 may include stored data that relates to operation of the respective devices 112, 114. Examples of stored data may define or describe entries in the integrity log (discussed above), passwords, names of operators, measurement results, and events in the event log (discussed above). In one implementation, these events may also include data that relates to operation of the respective device as part of the metering system 100. Such events may indicate, for example, missing measurement data, measurements are occurring out of range, that calibration constants are corrupted, and the like. The data 162 can also include executable instructions in the form of firmware, software, and computer programs that can configure the processors 158, 180, 192 to perform certain functions. However, while information and executable instructions may be stored locally as data 162, 176, 188, these devices may also be configured to access this information and executable instruction in a remote location, e.g., storage in the “cloud.”
One or more of the stages of the methods can be coded as one or more executable instructions (e.g., hardware, firmware, software, software programs, etc.). These executable instructions can be part of a computer-implemented method and/or program, which can be executed by a processor and/or processing device. The processor may be configured to execute these executable instructions, as well as to process inputs and to generate outputs, as set forth herein.
Computing components (e.g., memory and processor) can embody hardware that incorporates with other hardware (e.g., circuitry) to form a unitary and/or monolithic unit devised to execute computer programs and/or executable instructions (e.g., in the form of firmware and software). As noted herein, exemplary circuits of this type include discrete elements such as resistors, transistors, diodes, switches, and capacitors. Examples of a processor include microprocessors and other logic devices such as field programmable gate arrays (“FPGAs”) and application specific integrated circuits (“ASICs”). Memory includes volatile and non-volatile memory and can store executable instructions in the form of and/or including software (or firmware) instructions and configuration settings. Although all of the discrete elements, circuits, and devices function individually in a manner that is generally understood by those artisans that have ordinary skill in the electrical arts, it is their combination and integration into functional electrical groups and circuits that generally provide for the concepts that are disclosed and described herein.
As used herein, an element or function recited in the singular and proceeded with the word “a” or “an” should be understood as not excluding plural said elements or functions, unless such exclusion is explicitly recited. Furthermore, references to “one embodiment” of the claimed invention should not be interpreted as excluding the existence of additional embodiments that also incorporate the recited features.
This written description uses examples to disclose the invention, including the best mode, and also to enable any person skilled in the art to practice the invention, including making and using any devices or systems and performing any incorporated methods. The patentable scope of the invention is defined by the claims, and may include other examples that occur to those skilled in the art. Such other examples are intended to be within the scope of the claims if they have structural elements that do not differ from the literal language of the claims, or if they include equivalent structural elements with insubstantial differences from the literal language of the claims.
In light of the foregoing discussion, the embodiments herein incorporate improvements to equip metering systems to perform in situ commissioning of components. A technical effect is to modularize metering systems so as to easily expand and change functionalities, while at the same time maintaining legal and regulatory compliance. In this regard, the examples below include certain elements or clauses one or more of which may be combined with other elements and clauses describe embodiments contemplated within the scope and spirit of this disclosure.
This application is a continuation of U.S. application Ser. No. 15/356,594, filed on Nov. 20, 2016, and entitled “MODULAR METERING SYSTEM,” which is a continuation-in-part of U.S. patent application Ser. No. 14/301,986, filed on Jun. 11, 2014, and entitled “SYSTEMS, DEVICES, AND METHODS FOR MEASURING AND PROCESSING FUEL METER MEASUREMENTS,” which claims the benefit of U.S. Provisional Application Ser. No. 61/835,497, filed on Jun. 14, 2013, and entitled “DIGITAL METER BODY MODULE FOR ROTARY GAS METER.” The content of these applications is incorporated herein in its entirety.
Number | Date | Country | |
---|---|---|---|
61835497 | Jun 2013 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 15356594 | Nov 2016 | US |
Child | 16502823 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 14301986 | Jun 2014 | US |
Child | 15356594 | US |