The development contract Sample Clauses

The development contract. For works that are not yet completed, the fee shall fall due as follows: - 1 6 of the basic fee when the theatre requests that a manuscript be developed based on an idea or synopsis. - 1/6 as work progresses. - 1/6 upon delivery of the completed manuscript. - 3/6 upon acceptance.
AutoNDA by SimpleDocs

Related to The development contract

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

  • Employee Development The Employer may provide employees the opportunity to participate in appropriate seminars, workshops or short courses. When possible and appropriate the Employer will provide to all staff information on seminars, workshops or short courses by posting a notice on the Employer’s internal web site.

  • TRAINING AND EMPLOYEE DEVELOPMENT 9.1 The Employer and the Union recognize the value and benefit of education and training designed to enhance an employee’s ability to perform their job duties. Training and employee development opportunities will be provided to employees in accordance with Employer policies and available resources. 9.2 Attendance at employer-required training will be considered time worked. The Employer will make reasonable attempts to schedule employer-required training during an employee’s regular work shift. The Employer will pay the registration and associated travel costs in accordance with Article 23, Travel, for employer-required training.

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

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

  • Software Development Software designs, prototypes, and all documentation for the final designs developed under this agreement must be made fully transferable upon direction of NSF. NSF may make the software design, prototype, and documentation for the final design available to competitors for review during any anticipated re-competition of the project.

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

  • Sustainable Development 4.1 The Authority will review the Contractor’s Sustainable Development Policy Statement and Sustainable Development Plan submitted by the Contractor in accordance with the Schedule (Sustainable Development Requirements) and then at least annually thereafter. 4.2 Sustainable Procurement Risk Assessment Methodology (SPRAM) is a tool used by the Authority to identify and mitigate any potential risks to sustainability in contracts. The process requires that each Contract be assessed for its potential social, economic and environmental risks, throughout the various stages of its lifetime. Where risks are identified, appropriate mitigation action is required to reduce or eliminate the risk to sustainability. The Authority may at times require input from the Contractor in order to ensure that this process is given the required levels of consideration.

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

  • Direct Contracting Goods and works which the Association agrees meet the requirements for Direct Contracting may be procured in accordance with the provisions of said procurement method.

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