Evolution of the Market-to-Market Coordination Process Sample Clauses

Evolution of the Market-to-Market Coordination Process. Nothing in this Agreement will preclude the Parties from further evolving their market coordination process in conjunction with input from their respective market monitors.
AutoNDA by SimpleDocs

Related to Evolution of the Market-to-Market Coordination Process

  • Project Coordination The Engineer shall coordinate all subconsultant activity to include quality and consistency of deliverables and administration of the invoices and monthly progress reports. The Engineer shall coordinate with necessary local entities.

  • Cooperation of the Parties Each Party agrees to cooperate fully in the preparation, filing, and prosecution of any Patent Rights under this Agreement. Such cooperation includes, but is not limited to:

  • Application Services Under an “Application Services” engagement, we will assist you with defining, developing and deploying end-to-end enterprise or departmental applications; tasks may include determining the optimal technology approach and caching strategy to deliver effective, high-performance applications; leveraging a best practice approach for building new applications which includes conducting user workshops, building wireframes, iterating, testing, documenting and mentoring to increase adoption; and enhancing, optimizing or redesigning existing applications for improved user experience, faster performance or extended functionality.

  • Development Services During the term of this Agreement, the Provider agrees to provide to or on behalf of the Port the professional services and related items described in Exhibit A (collectively, the “Development Services”) in accordance with the terms and conditions of this Agreement. The Provider specifically agrees to include at least one Port representative in any economic development negotiations or discussions in which the Provider is involved concerning (i) a port-related business prospect or (ii) a business transaction which will ultimately require Port involvement, financial or otherwise.

  • Innovative Scheduling Schedules which are inconsistent with the Collective Agreement provisions may be developed in order to improve quality of working life, support continuity of resident care, ensure adequate staffing resources, and support cost-efficiency. The parties agree that such innovative schedules may be determined locally by the Home and the Union subject to the following principles:

  • Information Services Traffic 5.1 For purposes of this Section 5, Voice Information Services and Voice Information Services Traffic refer to switched voice traffic, delivered to information service providers who offer recorded voice announcement information or open vocal discussion programs to the general public. Voice Information Services Traffic does not include any form of Internet Traffic. Voice Information Services Traffic also does not include 555 traffic or similar traffic with AIN service interfaces, which traffic shall be subject to separate arrangements between the Parties. Voice Information services Traffic is not subject to Reciprocal Compensation as Local Traffic under the Interconnection Attachment.

  • DEVELOPMENT OR ASSISTANCE IN DEVELOPMENT OF SPECIFICATIONS REQUIREMENTS/ STATEMENTS OF WORK Firms and/or individuals that assisted in the development or drafting of the specifications, requirements, statements of work, or solicitation documents contained herein are excluded from competing for this solicitation. This shall not be applicable to firms and/or individuals providing responses to a publicly posted Request for Information (RFI) associated with a solicitation.

  • Academic Policies and Student Support Services X. Xxxx College courses offered as dual credit, regardless of where they are taught, follow the same syllabus, course outline, textbook, grading method, and other academic policies and procedures as the courses outlined in the Hill College policy manual, catalog, and student handbook. [TAC 19, Part 1, Chapter 4, Subchapter D, 4.85(g)(1)]

  • Research Use Reporting To assure adherence to NIH GDS Policy, the PI agrees to provide annual Progress Updates as part of the annual Project Renewal or Project Close-out processes, prior to the expiration of the one (1) year data access period. The PI who is seeking Renewal or Close-out of a project agree to complete the appropriate online forms and provide specific information such as how the data have been used, including publications or presentations that resulted from the use of the requested dataset(s), a summary of any plans for future research use (if the PI is seeking renewal), any violations of the terms of access described within this Agreement and the implemented remediation, and information on any downstream intellectual property generated from the data. The PI also may include general comments regarding suggestions for improving the data access process in general. Information provided in the progress updates helps NIH evaluate program activities and may be considered by the NIH GDS governance committees as part of NIH’s effort to provide ongoing stewardship of data sharing activities subject to the NIH GDS Policy.

  • Utility Coordination Identify all potential utility conflicts and provide preliminary office check plans showing the problem locations, posted to the City’s FTP site. Plans will clearly identify specific utility company facilities by color and by name (i.e. not just “gas” or “fiber optic”). ENGINEER shall include a conflict list for each utility, also posted to the FTP site. ENGINEER shall meet with utility company representatives to review plans and utility verification forms (Attachment No. 3 to Exhibit “A”) at each milestone date and as directed by the CITY and as determined necessary by the ENGINEER. This in- formation will be compiled into a summary report (Attachment No. 4 to Exhibit “A” also available on the City’s FTP site) maintained and updated by ENGINEER as necessary to present a cohesive and reflective status of utilities, and provided to the City as necessary. ENGINEER shall maintain involvement with utility companies until all conflicts have been resolved (not just identified). When appropriate, the City Engineer will approve the identification on plans of conflicts to be resolved during construction. ENGINEER shall meet with involved utility company/ies and project contractor to resolve any conflicts with utilities that occur during construction.

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