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

  • Loop Testing/Trouble Reporting 2.1.6.1 Telepak Networks will be responsible for testing and isolating troubles on the Loops. Telepak Networks 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, Telepak Networks will be required to provide the results of the Telepak Networks test which indicate a problem on the BellSouth provided Loop. 2.1.6.2 Once Telepak Networks has isolated a trouble to the BellSouth provided Loop, and had issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Users. 2.1.6.3 If Telepak Networks reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge Telepak Networks for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Loop’s working status. 2.1.6.4 In the event BellSouth must dispatch to the end-user’s location more than once due to incorrect or incomplete information provided by Telepak Networks (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will xxxx Xxxxxxx Networks for each additional dispatch required to repair the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Trouble Determination rates from BellSouth’s FCC or state tariffs.

  • Review of legality and data minimisation (a) The data importer agrees to review the legality of the request for disclosure, in particular whether it remains within the powers granted to the requesting public authority, and to challenge the request if, after careful assessment, it concludes that there are reasonable grounds to consider that the request is unlawful under the laws of the country of destination, applicable obligations under international law and principles of international comity. The data importer shall, under the same conditions, pursue possibilities of appeal. When challenging a request, the data importer shall seek interim measures with a view to suspending the effects of the request until the competent judicial authority has decided on its merits. It shall not disclose the personal data requested until required to do so under the applicable procedural rules. These requirements are without prejudice to the obligations of the data importer under Clause 14(e). (b) The data importer agrees to document its legal assessment and any challenge to the request for disclosure and, to the extent permissible under the laws of the country of destination, make the documentation available to the data exporter. It shall also make it available to the competent supervisory authority on request.

  • 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.‌ b. A description or identification of the statistical sampling software package 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.

  • Meteorological Data Reporting Requirement (Applicable to wind generation facilities only)

  • Certain Calculations and Tests (a) Notwithstanding anything to the contrary herein, but subject to Sections 1.10(b) and (c) and Section 1.11, all financial ratios and tests (including the Total Leverage Ratio, the First Lien Leverage Ratio, the Secured Leverage Ratio, the Interest Coverage Ratio and the amount of Consolidated Total Assets and Consolidated Adjusted EBITDA) contained in this Agreement that are calculated with respect to any Test Period during which any Subject Transaction occurs shall be calculated with respect to such Test Period and each such Subject Transaction on a Pro Forma Basis. Further, if since the beginning of any such Test Period and on or prior to the date of any required calculation of any financial ratio or test (i) any Subject Transaction has occurred or (ii) any Person that subsequently became a Restricted Subsidiary or was merged, amalgamated or consolidated with or into the Borrower or any of its Restricted Subsidiaries or any joint venture since the beginning of such Test Period has consummated any Subject Transaction, then, in each case, any applicable financial ratio or test shall be calculated on a Pro Forma Basis for such Test Period as if such Subject Transaction had occurred at the beginning of the applicable Test Period (it being understood, for the avoidance of doubt, that solely for purposes of (x) calculating compliance with Section 6.12(a) and (y) calculating the First Lien Leverage Ratio for purposes of the definitions of “Applicable Rate” and “Commitment Fee Rate”, in each case, no Subject Transaction occurring after the end of the relevant Test Period shall be taken into account). (b) For purposes of determining the permissibility of any action, change, transaction or event that requires a calculation of any financial ratio or test (including, without limitation, Section 6.12(a), any First Lien Leverage Ratio test, any Secured Leverage Ratio test, any Total Leverage Ratio test and/or any Interest Coverage Ratio test, the amount of Consolidated Adjusted EBITDA and/or Consolidated Total Assets), such financial ratio or test shall be calculated at the time such action is taken (subject to Section 1.11), such change is made, such transaction is consummated or such event occurs, as the case may be, and no Default or Event of Default shall be deemed to have occurred solely as a result of a change in such financial ratio or test occurring after the time such action is taken, such change is made, such transaction is consummated or such event occurs, as the case may be. (c) Notwithstanding anything to the contrary herein, with respect to any amounts incurred or transactions entered into (or consummated) in reliance on a provision of this Agreement (including any covenant or the definition of “Incremental Cap”) that does not require compliance with a financial ratio or test (including, without limitation, Section 6.12(a), any First Lien Leverage Ratio test, any Secured Leverage Ratio test, any Total Leverage Ratio test and/or any Interest Coverage Ratio test) (any such amounts, the “Fixed Amounts”) substantially concurrently with any amounts incurred or transactions entered into (or consummated) in reliance on a provision of this Agreement (including any covenant or the definition of “Incremental Cap”) that requires compliance with a financial ratio or test (including, without limitation, Section 6.12(a), any First Lien Leverage Ratio test, any Secured Leverage Ratio test, any Total Leverage Ratio test and/or any Interest Coverage Ratio test) (any such amounts, the “Incurrence-Based Amounts”), it is understood and agreed that the Fixed Amounts shall be disregarded in the calculation of the financial ratio or test applicable to the Incurrence-Based Amounts.

  • 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 C. 9.2 BellSouth will provide LIDB Storage upon written request to <<customer_name>>’s Account Manager stating a requested activation date.

  • Electronic and Information Resources Accessibility and Security Standards a. Applicability: The following Electronic and Information Resources (“EIR”) requirements apply to the Contract because the Grantee performs services that include EIR that the System Agency's employees are required or permitted to access or members of the public are required or permitted to access. This Section does not apply to incidental uses of EIR in the performance of the Agreement, unless the Parties agree that the EIR will become property of the State of Texas or will be used by HHSC’s clients or recipients after completion of the Agreement. Nothing in this section is intended to prescribe the use of particular designs or technologies or to prevent the use of alternative technologies, provided they result in substantially equivalent or greater access to and use of a Product.

  • Line Information Database LIDB is a transaction-oriented database accessible through Common Channel Signaling (CCS) networks. For access to LIDB, ONS must purchase appropriate signaling links pursuant to Section 10 of this Attachment. LIDB contains records associated with End User Line Numbers and Special Billing Numbers. LIDB accepts queries from other Network Elements and provides appropriate responses. The query originator need not be the owner of LIDB data. LIDB queries include functions such as screening billed numbers that provides the ability to accept Collect or Third Number Billing calls and validation of Telephone Line Number based non-proprietary calling cards. The interface for the LIDB functionality is the interface between BellSouth’s CCS network and other CCS networks. LIDB also interfaces to administrative systems.

  • Data Return and Destruction of Data (a) Protecting PII from unauthorized access and disclosure is of the utmost importance to the EA, and Contractor agrees that it is prohibited from retaining PII or continued access to PII or any copy, summary or extract of PII, on any storage medium (including, without limitation, in secure data centers and/or cloud-based facilities) whatsoever beyond the period of providing Services to the EA, unless such retention is either expressly authorized for a prescribed period by the Service Agreement or other written agreement between the Parties, or expressly requested by the EA for purposes of facilitating the transfer of PII to the EA or expressly required by law. As applicable, upon expiration or termination of the Service Agreement, Contractor shall transfer PII, in a format agreed to by the Parties to the EA. (b) If applicable, once the transfer of PII has been accomplished in accordance with the EA’s written election to do so, Contractor agrees to return or destroy all PII when the purpose that necessitated its receipt by Contractor has been completed. Thereafter, with regard to all PII (including without limitation, all hard copies, archived copies, electronic versions, electronic imaging of hard copies) as well as any and all PII maintained on behalf of Contractor in a secure data center and/or cloud-based facilities that remain in the possession of Contractor or its Subcontractors, Contractor shall ensure that PII is securely deleted and/or destroyed in a manner that does not allow it to be retrieved or retrievable, read or reconstructed. Hard copy media must be shredded or destroyed such that PII cannot be read or otherwise reconstructed, and electronic media must be cleared, purged, or destroyed such that the PII cannot be retrieved. Only the destruction of paper PII, and not redaction, will satisfy the requirements for data destruction. Redaction is specifically excluded as a means of data destruction. (c) Contractor shall provide the EA with a written certification of the secure deletion and/or destruction of PII held by the Contractor or Subcontractors. (d) To the extent that Contractor and/or its subcontractors continue to be in possession of any de-identified data (i.e., data that has had all direct and indirect identifiers removed), they agree not to attempt to re-identify de-identified data and not to transfer de-identified data to any party.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!