Faculty Development Coordinator Workload Assignment Sample Clauses

Faculty Development Coordinator Workload Assignment. 12.4.1 The Faculty Development Coordinator is accountable to the Executive Director, Centre for the Advancement of Faculty Excellence (CAFÉ), for the development, administration, and delivery of the faculty development program consistent with the directions and policies of the University Faculty Development Committee and the University.
AutoNDA by SimpleDocs

Related to Faculty Development Coordinator Workload Assignment

  • Project Coordinator 3. Within 14 days of the effective date of this Consent Agreement, DTSC and Respondent shall each designate a Project Coordinator and shall notify each other in writing of the Project Coordinator selected. Each Project Coordinator shall be responsible for overseeing the implementation of this Consent Agreement and for designating a person to act in his/her absence. All communications between Respondent and DTSC, and all documents, report approvals, and other correspondence concerning the activities performed pursuant to this Consent Agreement shall be directed through the Project Coordinators. Each party may change its Project Coordinator with at least seven days prior written notice. WORK TO BE PERFORMED

  • Project Manager The term “Project Manager” refers to the employee of the State who has been assigned responsibility for overseeing and managing the proper and timely implementation of the project.

  • Program Development NWESD agrees that priority in the development of new applications services by XXXXX shall be in accordance with the expressed direction of the XXXXX Board of Directors operating under their bylaws.

  • Project Management Plan 1 3.4.1 Developer is responsible for all quality assurance and quality control 2 activities necessary to manage the Work, including the Utility Adjustment Work.

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

  • Coordinator 6.4.1 The Coordinator shall be the intermediary between the Parties and the Funding Authority and shall perform all tasks assigned to it as described in the Grant Agreement and in this Consortium Agreement.

  • Joint Development If joint development is involved, the Recipient agrees to follow the latest edition of FTA Circular 7050.1, “Federal Transit Administration Guidance on Joint Development.”

  • Development Agreement As soon as reasonably practicable following the ISO’s selection of a transmission Generator Deactivation Solution, the ISO shall tender to the Developer that proposed the selected transmission Generator Deactivation Solution a draft Development Agreement, with draft appendices completed by the ISO to the extent practicable, for review and completion by the Developer. The draft Development Agreement shall be in the form of the ISO’s Commission-approved Development Agreement for its reliability planning process, which is in Appendix C in Section 31.7 of Attachment Y of the ISO OATT, as amended by the ISO to reflect the Generator Deactivation Process. The ISO and the Developer shall finalize the Development Agreement and appendices as soon as reasonably practicable after the ISO’s tendering of the draft Development Agreement. For purposes of finalizing the Development Agreement, the ISO and Developer shall develop the description and dates for the milestones necessary to develop and construct the selected project by the required in-service date identified in the Generator Deactivation Assessment, including the milestones for obtaining all necessary authorizations. Any milestone that requires action by a Connecting Transmission Owner or Affected System Operator identified pursuant to Attachment P of the ISO OATT to complete must be included as an Advisory Milestone, as that term is defined in the Development Agreement. If the ISO or the Developer determines that negotiations are at an impasse, the ISO may file the Development Agreement in unexecuted form with the Commission on its own, or following the Developer’s request in writing that the agreement be filed unexecuted. If the Development Agreement is executed by both parties, the ISO shall file the agreement with the Commission for its acceptance within ten (10) Business Days after the execution of the Development Agreement by both parties. If the Developer requests that the Development Agreement be filed unexecuted, the ISO shall file the agreement at the Commission within ten (10) Business Days of receipt of the request from the Developer. The ISO will draft, to the extent practicable, the portions of the Development Agreement and appendices that are in dispute and will provide an explanation to the Commission of any matters as to which the parties disagree. The Developer will provide in a separate filing any comments that it has on the unexecuted agreement, including any alternative positions it may have with respect to the disputed provisions. Upon the ISO’s and the Developer’s execution of the Development Agreement or the ISO’s filing of an unexecuted Development Agreement with the Commission, the ISO and the Developer shall perform their respective obligations in accordance with the terms of the Development Agreement that are not in dispute, subject to modification by the Commission. The Connecting Transmission Owner(s) and Affected System Operator(s) that are identified in Attachment P of the ISO OATT in connection with the selected transmission Generator Deactivation Solution shall act in good faith in timely performing their obligations that are required for the Developer to satisfy its obligations under the Development Agreement.

  • County’s Project Manager Note: The written approval of substituted A-E Key Personnel is for departmental use only and shall not be used for auditing purposes outside OC Public Works or other County department.

  • Information Systems Acquisition Development and Maintenance Security of System Files. To protect City Information Processing Systems and system files containing information, Service Provider will ensure that access to source code is restricted to authorized users whose specific job function necessitates such access.

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