Electronic Course Development Agreement Sample Clauses

Electronic Course Development Agreement. If authorized to proceed with development of the Electronic Course materials, the College and the faculty member will enter into a written Electronic Course Development Agreement which details the scope of the Electronic Course materials to be developed, a schedule for completion, and the terms and conditions of ownership of any intellectual property rights in the materials developed. This Agreement shall also identify the compensation for course development, based on the following criteria: a. If 80 to 100 percent of the Electronic Course is original material developed by the faculty member, the compensation is the course contact units multiplied by three (3), up to a maximum compensation of five thousand dollars ($5,000). b. If 25 to 79 percent of the Electronic Course is original material developed by the faculty member, the compensation is the course contact units multiplied by two (2). c. If less than 25 percent of the Electronic Course is original material developed by the faculty member, the compensation is equal to the course contact units. d. Compensation may be units paid at the overload rate or units assigned as release time. e. If the compensation is payment at the overload rate, half of the compensation will be paid following the semester when the course is first offered.
Sample 1Sample 2Sample 3See All (22)
AutoNDA by SimpleDocs

Related to Electronic Course Development Agreement

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

  • Collaboration Agreement The Collaboration Agreement shall not have been terminated in accordance with its terms and shall be in full force and effect.

  • Information Systems Acquisition Development and Maintenance a. Client Data – Client Data will only be used by State Street for the purposes specified in this Agreement.

  • DEVELOPMENT OR ASSISTANCE IN DEVELOPMENT OF SPECIFICATIONS REQUIREMENTS/ STATEMENTS OF WORK

  • Project Management Plan 3.2.1 Developer is responsible for all quality assurance and quality control activities necessary to manage the Work, including the Utility Adjustment Work. Developer shall undertake all aspects of quality assurance and quality control for the Project and Work in accordance with the approved Project Management Plan, Good Industry Practice and applicable Law. 3.2.2 Developer shall develop the Project Management Plan and its component parts, plans and other documentation in accordance with the requirements set forth in Section 1.5.2.5

  • Project Development a. Collaborate with COUNTY and project clients to identify requirements and develop a project Scope Statement. a. Develop a Work Breakdown Structure (WBS) for each project. b. Evaluate Scope Statement to develop a preliminary cost estimate and determinate whether project be vendor bid or be executed under a Job Order Contract (JOC).

  • Design Development Documents See Section 2, Part 1, Article 2.1.5.

  • WASHINGTON’S ELECTRONIC BUSINESS SOLUTION (WEBS). Contractor represents and warrants that it is registered in Washington’s Electronic Business Solution (WEBS), Washington’s contract registration system and that, all of its information therein is current and accurate and that throughout the term of this Master Contract, Contractor shall maintain an accurate profile in WEBS.

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

  • Completion of Concrete Pours and Emergency Work (a) Except as provided in this sub-clause an Employee shall nor work or be required to work in the rain. (b) Employees shall not be required to start a concrete pour in Inclement Weather. (c) Where a concrete pour has been commenced prior to the commencement of a period of Inclement Weather Employees may be required to complete such concrete pour to a practical stage and for such work shall be paid at the rate of double time calculated to the next hour, and in the case of wet weather shall be provided with adequate wet weather gear. (d) If an Employee’s clothes become wet as a result of working in the rain during a concrete pour the Employee shall, unless the Employee has a change of dry working clothes available, be allowed to go home without loss of pay. (e) The provisions of clauses 32.7(c) and 32.7(d) hereof shall also apply in the case of emergency work where the Employees concerned and their delegates agree that the work is of an emergency nature and can start and/or proceed.

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