Reproducibility of Flowmeter Data Sample Clauses

Reproducibility of Flowmeter Data. A concern with any test is the reproducibility of the data. During a borehole flowmeter test, it is a good practice to repeat several flowmeter measurements without changing flowmeter position. If two measurements produce similar means and standard deviations, then the flowmeter system is assumed to be functioning properly. As standard practice, the flowmeter was considered to be performing adequately if two successive measurements produced mean values that overlapped in the range of their standard deviations. In developing a quality assurance plan for field testing, two types of duplicate measurements should be taken. The first type involves two successive measurements without moving the flowmeter. An assumption in comparing these values is that flow conditions in the aquifer have remained constant between measurements so that any differences reflect the uncertainties associated with the measurement technique. The second type involves measurements at the same location but at different times. Over periods of minutes and/or hours, the flow conditions in the aquifer may change. Differences in flow measurements would be primarily produced by variations in the saturated thickness of an unconfined aquifer in response to a pumping test, variations in the pumping rate caused by fluctuations in the performance of the pump, and inability to exactly reoccupy the same elevation in the well. The second type of duplicate measurement reflects the error associated with assuming that the flow conditions are at steady-state.
Sample 1
AutoNDA by SimpleDocs

Related to Reproducibility of Flowmeter Data

  • Accessibility of Web-Based Information and Applications For State Agency Authorized User Acquisitions: Any web-based information and applications development, or programming delivered pursuant to the contract or procurement, will comply with New York State Enterprise IT Policy NYS-P08-005, Accessibility of Web-Based Information and Applications as follows: Any web-based information and applications development, or programming delivered pursuant to the contract or procurement, will comply with New York State Enterprise IT Policy NYS-P08- 005, Accessibility of Web-Based Information and Applications as such policy may be amended, modified or superseded, which requires that state agency web-based information and applications are accessible to persons with disabilities. Web-based information and applications must conform to New York State Enterprise IT Policy NYS-P08-005 as determined by quality assurance testing. Such quality assurance testing will be conducted by the State Agency Authorized User and the results of such testing must be satisfactory to the Authorized User before web-based information and applications will be considered a qualified deliverable under the contract or procurement.

  • Technical Feasibility of String While ICANN has encouraged and will continue to encourage universal acceptance of all top-­‐level domain strings across the Internet, certain top-­‐level domain strings may encounter difficulty in acceptance by ISPs and webhosters and/or validation by web applications. Registry Operator shall be responsible for ensuring to its satisfaction the technical feasibility of the TLD string prior to entering into this Agreement.

  • Loop Testing/Trouble Reporting 2.1.6.1 Think 12 will be responsible for testing and isolating troubles on the Loops. Think 12 must test and isolate trouble to the BellSouth portion of a designed/non- designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, Think 12 will be required to provide the results of the Think 12 test which indicate a problem on the BellSouth provided Loop.

  • Testing/Trouble Reporting 1.15.1 TWTC will be responsible for testing and isolating troubles on Network Elements. TWTC must test and isolate trouble to the AT&T network before reporting the trouble to the Network Elements Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from AT&T at the time of the trouble report, TWTC will be required to provide the results of the TWTC test which indicate a problem on the AT&T network. Version: 4Q06 Standard ICA 11/30/06

  • Technical Requirements for SCPs/Databases 10.5.3.1 BellSouth shall provide physical access to SCPs through the SS7 network and protocols with TCAP as the application layer protocol.

  • Statistical Sampling Documentation a. A copy of the printout of the random numbers generated by the “Random Numbers” function of the statistical sampling software used by the IRO.

  • Updated Information Submission by Interconnection Customer The updated information submission by the Interconnection Customer, including manufacturer information, shall occur no later than one hundred eighty (180) Calendar Days prior to the Trial Operation. The Interconnection Customer shall submit a completed copy of the Electric Generating Unit data requirements contained in Appendix 1 to the LGIP. It shall also include any additional information provided to the Participating TO and the CAISO for the Interconnection Studies. Information in this submission shall be the most current Electric Generating Unit design or expected performance data. Information submitted for stability models shall be compatible with the Participating TO and CAISO standard models. If there is no compatible model, the Interconnection Customer will work with a consultant mutually agreed to by the Parties to develop and supply a standard model and associated information. If the Interconnection Customer's data is materially different from what was originally provided to the Participating TO and the CAISO for the Interconnection Studies, then the Participating TO and the CAISO will conduct appropriate studies pursuant to the LGIP to determine the impact on the Participating TO’s Transmission System and affected portions of the CAISO Controlled Grid based on the actual data submitted pursuant to this Article 24.3. The Interconnection Customer shall not begin Trial Operation until such studies are completed and all other requirements of this LGIA are satisfied.

  • Meteorological Data Reporting Requirement (Applicable to wind generation facilities only) The wind generation facility shall, at a minimum, be required to provide the Transmission Provider with site-specific meteorological data including: • Temperature (degrees Fahrenheit) • Wind speed (meters/second) • Wind direction (degrees from True North) • Atmosphere pressure (hectopascals) • Forced outage data (wind turbine and MW unavailability)

  • Line Information Database (LIDB 9.1 BellSouth will store in its Line Information Database (LIDB) records relating to service only in the BellSouth region. The LIDB Storage Agreement is included in this Attachment as Exhibit B.

  • PRESERVATION OF CONTRACTING INFORMATION 2.27.1 The requirements of Subchapter J, Chapter 552, Texas Government Code, may apply to this Agreement and the Contractor agrees that this Agreement can be terminated if the Contractor knowingly or intentionally fails to comply with a requirement of that subchapter. If the requirements of Subchapter J, Chapter 552, Texas Government Code, apply to this Agreement, then for the duration of this Agreement (including the initial term, any renewal terms, and any extensions), Contractor shall preserve all Contracting Information, as defined by Section 552.003 of the Texas Government Code, related to this Agreement as provided by the records retention requirements applicable to the City pursuant to federal or state law or regulation, city ordinance or city policy, which record retention requirements include but are not limited to those set forth in Chapters 201 and 205 of the Texas Local Government Code and Texas Administrative Code Title 13, Chapter 7. Within five business days after receiving a request from the Director, Contractor shall provide any Contracting Information related to this Agreement that is in the custody or possession of Contractor. Upon the expiration or termination of this Agreement, Contractor shall, at the Director’s election, either (a) provide, at no cost to the City, all Contracting Information related to this Agreement that is in the custody or possession of Contractor, or (b) preserve the Contracting Information related to this Agreement as provided by the records retention requirements applicable to the City pursuant to federal or state law or regulation, city ordinance or City policy.

Time is Money Join Law Insider Premium to draft better contracts faster.