Verification Plans Sample Clauses

A Verification Plans clause outlines the procedures and requirements for confirming that products, services, or deliverables meet specified standards or contractual obligations. Typically, this clause details the methods, timing, and responsible parties for conducting inspections, tests, or reviews, and may require submission of documentation or reports as evidence of compliance. Its core function is to ensure that all parties have a clear, agreed-upon process for verifying quality and performance, thereby reducing the risk of disputes and ensuring that contractual expectations are met.
Verification Plans. As already explained in this scenario Metadata registry is tested by registering two IDS Connectors to the deployed metadata registry and finally transferring a JSON between 2 IDS connector. For this reason, we use 2 TRUE Connectors as IDS connector. One connector as producer and one as consumer. First the producer register itself to the metadata registry and then the consumer can search metadata registry for the provider and request a JSON content. Moreover, we test the Vocabulary Provider by testing the interaction between an IDS connector and Vocabulary Provider.
View Source
Verification Plans. (a) Promptly foLlowing execution of this Agreement, the University and the Company will work together to develop a proposed verification plan for the Analytical Testing Facility to inspect and test as comprehensively as reasonably possible, the instalLation and operation of all equipment installed as part of the Development Work and compliance of the Analytical Testing Facility with the FaciLity Requirements and the Approved Facility Design. (b) The Verification Plan shall include provision for the GLP Certification of the Analytical Testing Facility. (c) The Verification Plan must be approved by both the University and the Company, and may be amended by agreement of the parties from time to time. Upon approval, the Verification Plan shall be deemed to form integraL part of this Agreement as Schedule E - Verification Plan. 4 I 62714006080_6IR/\C 02/08/2018 2:26:41 PM
View Source
Verification Plans. For the Non-Edge scenario, historical data sources in CSV format should be converted to the semantified version via a semantic adaptor and served via a Federated Query Engine to the analytical tools. Finally, a visualizer component is used to present the results of the analytical tools. However, as in this case only one data source exists (already explained in Section 2.2.1), we decided to divide the data vertically into 2 parts. The result was 2 files with different columns in each as follows: CSV1: • Id • Date • Hour CSV2: • Id • Zone • Source • Connections By applying such a division, the Federated Query Engine can be tested to see if it can merge results from multiple data sources. To test the pipeline with bigger data, some synthetic data has been generated with different sizes. The procedure is explained in Section 39.
View Source
Verification Plans. As already explained in this scenario, data should come from a (mock) edge device. The data should be transformed and stored in a persistent database, and finally a visualization tool should be able to visualize the streaming data. As mentioned earlier, the container mocking the edge device should be on a different network than database and visualization tool.
View Source

Related to Verification Plans

  • Verification Procedure (1) The signature file of each processed file is validated. (2) If processed files are pieces of a bigger file, the latter is put together. (3) Each file obtained in the previous step is then decrypted and uncompressed. (4) Each data file contained in the previous step is then validated against the format defined in Part A, Section 9, reference 1 of this Specification. (5) If Part A, Section 9, reference 1 of this Specification includes a verification process, that will be applied at this step. If any discrepancy is found in any of the steps, the Deposit will be considered incomplete.

  • MEASUREMENT AND VERIFICATION The goal of this task is to report the benefits resulting from this project by performing M&V of GHG and energy consumption reduction. • Enter into agreement with M&V subcontractor per subtask 1.9 (if using outside vendor) • Coordinate demonstration site visits with the M&V subcontractor at the demonstration site • Develop M&V protocol for pre-installation measurements (and calculations): o Electric, natural gas and/or other fossil fuel consumption and GHG emissions (use appropriate emissions factor from Attachment 8, FPIP Calculator Tool of the grant solicitation) of the equipment/process/system(s)/sub-system(s) that are to be upgraded and/or replaced and/or modified. o Ensure installation of sub-metering equipment and data loggers for pre/post data analysis. • Prepare and provide a detailed M&V Plan for each project demonstration site to include but not be limited to: o A description of the monitoring equipment and instrumentation that will be used. o A description of the key input parameters and output metrics that will be measured. o A description of the M&V protocol and analysis methods to be employed. o A description of the independent, third-party M&V services to be employed, if applicable. • Perform three months (or shorter period as approved in writing by the CAM) of pre-installation measurements (and calculations) based on the M&V protocol for pre-installation. • Prepare and provide a Pre-Installation M&V Findings Report that includes M&V protocol, pre-install measurements (and calculations), analysis, and results performed in this task. • Develop M&V protocol for post-installation measurements (and calculations) of: o Electric, natural gas and/or other fossil fuel consumption and GHG emissions (use appropriate emissions factor from Attachment 8 of the grant solicitation) of the equipment/process/system(s)/sub-system(s) that will be upgraded and/or replaced and/or modified • Perform 12 months (or shorter period as approved in writing by the CAM) of post- installation measurements based on M&V protocol for post-installation. • Provide a summary of post-installation M&V progress in Progress Report(s) (see subtask 1.5) which shall include but not be limited to:

  • Employee Verification In accordance with Neb. Rev.

  • Verifications If Partner acquires Red Hat Products and/or Services directly from Red Hat, during the Term and for at least two (2) years thereafter, Partner will keep and maintain commercially reasonable written records regarding Partner’s use and distribution of the Red Hat Products and Services and business activities related to the Program(s) ("Records"). Red Hat may, at its own expense, verify the Records to determine Partner’s compliance with this Agreement. This verification may take the form of requests for information, documents or records (to which Partner will respond promptly), on-site visits (for which Partner shall grant Red Hat the requisite access), or both. The Parties will act reasonably and cooperate with each other in respect of such verifications. Any on-site visit will occur during regular business hours and will not interfere unreasonably with Partner’s business. For an on-site visit, Red Hat will give Partner at least thirty (30) day’s prior written notice.

  • Verification Bank may, from time to time, verify directly with the respective Account Debtors the validity, amount and other matters relating to the Accounts, either in the name of Borrower or Bank or such other name as Bank may choose.