Technical Reviews Sample Clauses

Technical Reviews. Farmee shall, beginning in June of 1998, and in June and December of each calendar year thereafter during the term of this Contract, provide to the appropriate Amoco personnel, a review of Farmee's activities on the Lease Acreage in the Exploration Area. Information included in the review shall include, but shall not be limited to, details regarding proposed seismic acquisition programs, well status reports including location and results of xxxxx drilled and location and approximate drilling schedule of proposed xxxxx. Additionally, the review shall include. information regarding the handling of farmout requests received by Farmee including information detailing the response or proposed response Farmee made to each request. All information included in the review shall be held strictly confidential by Amoco.
AutoNDA by SimpleDocs
Technical Reviews. AGL may, if requested, hold technical reviews for Members at their request and at the Member’s site if the review has no impact on the Consortium’s Research Program. AGL travel and related expenses will be borne by the Member requesting the review.
Technical Reviews. 1. The Commission may initiate a technical review at any time during the implementation of the project and up to the date of the final payment. The aim of a technical review shall be to assess the work carried out under the project over a certain period, inter alia by evaluating the project reports and deliverables relevant to the period in question. Such reviews may cover scientific, technological and other aspects relating to the proper execution of the project and the grant agreement.
Technical Reviews. West shall periodically (but no less than once each year) coordinate and sponsor a joint technical review which will examine, without limitation, technical advances made by West that may directly or indirectly benefit BD.
Technical Reviews. All actions will in principle undergo one peer Review in each calendar year, according to the provisions established in Article II.29. As a general rule, no Review will be held in the first 10 months of implementation of the action. The first in-depth Review will take place around month 14, with no prejudice to the possibility of triggering earlier reviews when deemed appropriate by the EC. In particular the EC may decide to perform a pre-Review towards month 11 of the action, with the aim of preparing the first in- depth Review.
Technical Reviews. The CONSULTANT may review corridor and other multi-modal studies submitted to FDOT by outside consultants and/or agencies. Studies should be reviewed to ensure compliance with FDOT policies. When requested, the CONSULTANT shall attend meetings relating to these studies. Review of transportation studies may include verification of data collection efforts, data analysis, reports and/or plans. It may require research, meetings, and discussions with the appropriate transit companies, the report author(s) FDOT, and County agencies to determine their needs. The CONSULTANT may also be requested to review Developments of Regional Impact (DRI) and make recommendations on how to provide for multimodal options in the Development Order. The review shall be based on two (2) levels, the first being an evaluation of the assumptions and methodologies used in the study and second being a review of the accuracy of any qualitative analyses. Marked up plans, sketches and recommendations should be provided by the CONSULTANT to FDOT within ten (10) working days.
Technical Reviews. UH CENTER NAME may, if requested, hold technical reviews for Members at their request and at the Member’s site if the review has no impact on the Consortium’s Research Program. UH CENTER NAME travel expenses will be borne by the Member requesting the review.
AutoNDA by SimpleDocs
Technical Reviews. 4.6.6.1 Include appropriate technical reviews based on the work products associated with the task order. Appropriate technical reviews may include:  System Requirements Review (SSR)  System Functional Review (SFR)  Software Specification Review (SSR)  Preliminary Design Review (PDR)  Critical Design Review (CDR)  Test Readiness Review (TRR)  Government Acceptance Test (GAT)  Factory Acceptance Test (FAT)  System Verification Review (SVR)  Operational Readiness Review (XXX)
Technical Reviews. Technical reviews focus on the completeness, accuracy, consistency, traceability and overall technical integrity of the deliverables produced within the project. To ensure the highest quality of the deliverables the following Quality assurance procedure will be implemented:
Technical Reviews. 10 3.4.3 Requirements Analysis .............................................10 3.4.4 GIMDE 2K Design ...................................................11 3.4.5 Software Development - Functional Software ........................12 3.4.6
Time is Money Join Law Insider Premium to draft better contracts faster.