Data Usability Sample Clauses

Data Usability. Data usability is the process of evaluating verified/validated data to determine if they can be used for the purpose of the project. Data usability includes the following: ■ Evaluating individual data sets to identify the measurement performance/usability issues/problems affecting the ultimate achievement of the DQOs; ■ Evaluating all of the data generated for the project; and ■ Documenting the project-specific measurement performance criteria and data verification/validation criteria documented in the QAPP to determine if they were appropriate for meeting project DQOs. The data validator will validate data quality, as previously discussed, to assess potential effects of deviations from the QAPP and the effect on the DQOs.
AutoNDA by SimpleDocs
Data Usability. Should The Bank determine that Business Entities’ input is unreadable or cannot be processed, Business Entity will be notified and a replacement file requested. Business Entity must then indicate when the replacement file will be available to The Bank. Should it be determined that a replacement file cannot be provided before the Processing Schedule deadline, Business Entity will be advised of available processing options.
Data Usability. Data collectors should consider all possible data end uses when developing a plan for data verification, review, and validation. Figure 5-1 presents the steps that should be used during final project data evaluation. For each data collection activity , the data collector must select analytical methods, target analytes, sensitivity requirements, and quality control requirements that meet the needs of the most critical end us e objective under consideration.
Data Usability. Following completion of the data reviews described in the Section 14.0, the QAE and SRE will determine what data, if any, is unusable. Data deemed unusable may be qualified through additional inspection, calculation, or evaluation. In cases where such data is from the contract laboratory, that facility may be asked for additional information to support that effort. Acceptable data will be evaluated to ensure the project DQOs have been satisfied. In the event data gaps still exist, additional effort to satisfy the DQOs will be specified as appropriate. This Page Intentionally Left Blank

Related to Data Usability

  • Data Use Each party may use Connected Account Data in accordance with this Agreement and the consent (if any) each obtains from each Connected Account. This consent includes, as to Stripe, consent it receives via the Connected Account Agreement.

  • Management of Special and Technical Environment Each certificated support person demonstrates an acceptable level of performance in managing and organizing the special materials, equipment and environment essential to the specialized programs.

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes.

  • Infrastructure Vulnerability Scanning Supplier will scan its internal environments (e.g., servers, network devices, etc.) related to Deliverables monthly and external environments related to Deliverables weekly. Supplier will have a defined process to address any findings but will ensure that any high-risk vulnerabilities are addressed within 30 days.

  • Reporting of Metered Data and Parameters 7.2.1 The grid connected Solar PV power plants will install necessary equipment for regular monitoring of solar irradiance (including GHI, DHI and solar radiation in the module plane), ambient air temperature, wind speed and other weather parameters and simultaneously for monitoring of the electric power (both DC and AC) generated from the Project.

  • Trunk Group Architecture and Traffic Routing The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows:

  • Data Encryption Contractor must encrypt all State data at rest and in transit, in compliance with FIPS Publication 140-2 or applicable law, regulation or rule, whichever is a higher standard. All encryption keys must be unique to State data. Contractor will secure and protect all encryption keys to State data. Encryption keys to State data will only be accessed by Contractor as necessary for performance of this Contract.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.

  • Information Technology Accessibility Standards Any information technology related products or services purchased, used or maintained through this Grant must be compatible with the principles and goals contained in the Electronic and Information Technology Accessibility Standards adopted by the Architectural and Transportation Barriers Compliance Board under Section 508 of the federal Rehabilitation Act of 1973 (29 U.S.C. §794d), as amended. The federal Electronic and Information Technology Accessibility Standards can be found at: xxxx://xxx.xxxxxx-xxxxx.xxx/508.htm.

  • 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)

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