Development Schedules Sample Clauses

Development Schedules. Licensor shall provide TWC throughout the Term, on a no-less-than monthly basis, with detailed schedules of properties in development or which have been acquired by Licensor and which are intended to be or which may become an Eligible Picture hereunder. Such schedules shall include all information relevant to TWC as distributor regarding each such property including, without limitation, tentative title and underlying rights (including without limitation drafts of treatments and/or screenplays), key creative attachments, and development or production status (including without limitation greenlight date, actual or scheduled commencement of principal photography date, and scheduled Initial Theatrical Release date).
Sample 1Sample 2
AutoNDA by SimpleDocs
Development Schedules. FOREWORD The products and services provided in this Statement of Work (SOW) support the ISS Program, the Constellation Program (CxP) or any related technology development activitie s, and any commercial provider of visiting vehicles. The contractor shall maintain flexibility and responsiveness to changing requirements. The contractor shall perform the activities in the most cost-effective and efficient manner while supporting the Government’s priorities for safety, mission success, and customer satisfaction. The ISS requires support consisting of analytical and physical processing activities to support pressurized cargo requirements for visiting vehicle flights to and from the ISS. The ISS Program process for ground processing will be utilized by the CxP for both ISS Program and CxP provided Flight Crew Equipment (FCE). This support includes: • Cargo Mission Planning • Cargo Coordination • Stowage Integration • Cargo Physical Processing • International Shipping • Decals, Placards and Graphics Production • The capability to build hardware to support pressurized and unpressurized cargo transportation, as needed. The contractor shall perform Flight Crew Equipment processing related activities necessary to provide and maintain flight and training hardware and services in support of the ISS and Constellation Programs. All hardware shall be provided on an as needed basis and meet design and operational requirements. FCE includes: • Crew Clothing and Personal Hygiene Items • Housekeeping Items • Audio/Video Equipment and Associated Cabling • Laptop Computers and Support Equipment • Batteries • Crew Survival Equipment (Constellation unique requirement)
Sample 1
Development Schedules. The contractor shall prepare and deliver schedules for all hardware development projects to provide the Government with insight into overall project status in accordance with DRD C-PC- 05, Cargo Mission Contract Program Schedules.
Sample 1
Development Schedules. SDID shall update schedules and coordinate progress with CT monthly. SDID and CT shall mutually work schedule issues to support program success. The responsibility of each party is defined in the [*] (Attachment 2). Should either party become aware of facts or circumstances which could reasonably be expected to adversely affect the anticipated schedules, it shall be that party's responsibility to inform the other party to the Agreement of the anticipated change in the schedules and the reason for such change and the parties to the Agreement shall cooperate with each other in any efforts which may be made to correct the situation giving rise to the change in facts or circumstances.
Sample 1
Development Schedules. Both companies will publish to each other, Gxxxx charts showing the activities and end dates needed to produce the deliverables described in the work plan
Sample 1
Development Schedules. By April 1, 2005, Tris shall deliver to the PMC and Interpharm the Development Schedule for each Product for their review and for Interpharm's approval. In the event that Interpharm shall not approve the Development Schedule for a Product, Tris and Interpharm shall meet and in good faith discuss the reasons for the failure to approve and a method to resolve the basis for non-approval. In the event that the Parties are unable to agree on a method to resolve the basis for non-approval, Interpharm shall provide to Tris a written explanation of the reasons for disagreement. Thereafter, each Party shall have the right to retain a Third Party Expert to assist in the evaluation of the issue in dispute. In such event, the Third Party Experts shall provide to each Party's representative on the PMC their recommendation and analysis on such disputed issue in writing, including a reasonably detailed explanation for such decision. Interpharm mayconsider the recommendations of the Third Party Experts but shall have the right to make the final decision with respect to such issue in its sole and absolute discretion. The parties shall make a good faith effort to resolve the issue in dispute within thirty (30) days (from the point that the dispute arose).
Sample 1
Development Schedules. Not less than 45 days following the date of this Agreement, each Member shall deliver to the other, for approval, a detailed schedule, including the estimated delivery dates and a description of components, for the development by such Member of components to be sold to the Company.
Sample 1
AutoNDA by SimpleDocs

Related to Development Schedules

  • Development Schedule The Project shall substantially comply with the specific timetables and triggers for action set forth in Article 5 of this Agreement. The parties acknowledge that, as provided in G.S. 160A-400.25(b), the failure to meet a commencement or completion date shall not, in and of itself, constitute a material breach of this Agreement pursuant to G.S. 160A-400.27 but must be judged based upon the totality of the circumstances.

  • Development Plan document specifying the work program, schedule, and relevant investments required for the Development and the Production of a Discovery or set of Discoveries of Oil and Gas in the Contract Area, including its abandonment.

  • Project Plan Development of Project Plan Upon the Authorized User’s request, the Contractor must develop a Project Plan. This Project Plan may include Implementation personnel, installation timeframes, escalation procedures and an acceptance plan as appropriate for the Services requested. Specific requirements of the plan will be defined in the RFQ. In response to the RFQ, the Contractor must agree to furnish all labor and supervision necessary to successfully perform Services procured from this Lot. Project Plan Document The Contractor will provide to the Authorized User, a Project Plan that may contain the following items: • Name of the Project Manager, Contact Phone Numbers and E-Mail Address; • Names of the Project Team Members, Contact Phone Numbers and E-Mail Address; • A list of Implementation milestones based on the Authorized User’s desired installation date; • A list of responsibilities of the Authorized User during system Implementation; • A list of designated Contractor Authorized Personnel; • Escalation procedures including management personnel contact numbers; • Full and complete documentation of all Implementation work; • Samples of knowledge transfer documentation; and • When applicable, a list of all materials and supplies required to complete the Implementation described in the RFQ. Materials and Supplies Required to Complete Implementation In the event that there are items required to complete an Implementation, the Contractor may request the items be added to its Contract if the items meet the scope of the Contract. Negotiation of Final Project Plan If the Authorized User chooses to require a full Project Plan, the State further reserves the right for Authorized Users to negotiate the final Project Plan with the apparent RFQ awardee. Such negotiation must not substantively change the scope of the RFQ plan, but can alter timeframes or other incidental factors of the final Project Plan. The Authorized User will provide the Contractor a minimum of five (5) business days’ notice of the final negotiation date. The Authorized User reserves the right to move to the next responsible and responsive bidder if Contractor negotiations are unsuccessful.

  • Work Schedules Workweeks and work shifts of different numbers of hours may be established by the Employer in order to meet business and customer service needs, as long as the work schedules meet federal and state laws.

  • Alternative Work Schedules Employees may request alternative work schedules such as a nine (9) day - 80 hour two week schedule or a four (4) day - 40 hour week schedule. Management will respond to an employee's request within 15 calendar days. Any changes from existing work schedules will be based on the needs of the service as determined by Management. Employees covered by the Fair Labor Standards Act will not be placed on alternate work schedules that mandate the payment of overtime under the Act.

  • Development Plans 4.3.1 For each Licensed Indication and corresponding Licensed Product in the Field, Licensee will prepare and deliver to Licensor a development plan and budget (each a “Development Plan”). The initial Development Plans for each Licensed Indication will be delivered within […***…] after the Grant Date for such Licensed Indication.

  • Project Schedule Construction must begin within 30 days of the date set forth in Appendix A, Page 2, for the start of construction, or this Agreement may become null and void, at the sole discretion of the Director. However, the Recipient may apply to the Director in writing for an extension of the date to initiate construction. The Recipient shall specify the reasons for the delay in the start of construction and provide the Director with a new start of construction date. The Director will review such requests for extensions and may extend the start date, providing that the Project can be completed within a reasonable time frame.

  • Research Plan The Parties recognize that the Research Plan describes the collaborative research and development activities they will undertake and that interim research goals set forth in the Research Plan are good faith guidelines. Should events occur that require modification of these goals, then by mutual agreement the Parties can modify them through an amendment, according to Paragraph 13.6.

  • Project Plans The Contractor: must carry out the Contractor's Activities in accordance with, and otherwise implement, the Project Plans; and for the purposes of subparagraph (i), must: prepare Project Plans based, where applicable, on the draft Project Plans lodged by the Contractor in its tender for the Contractor's Activities, and otherwise in accordance with the requirements of the Contract and submit them to the Contract Administrator so as to ensure that there is no delay or disruption to the Contractor's Activities and in any event no later than the number of days specified in the Contract Particulars after the Award Date for each Project Plan; not commence any of the Contractor's Activities to which any Project Plan applies, unless the Contract Administrator has had the number of days specified in the Contract Particulars for each Project Plan to review the Project Plan and has not rejected the Project Plan; if any Project Plan is rejected, submit an amended Project Plan to the Contract Administrator; in any event, finalise each Project Plan so as to ensure that there is no delay or disruption to the Contractor's Activities and in any event in accordance with the requirements of the Contract to the satisfaction of the Contract Administrator; after each Project Plan has been finalised: regularly review, update and amend each Project Plan in accordance with the process set out in each Project Plan (and otherwise at least on each anniversary of the Award Date); update or amend a Project Plan on request of the Contract Administrator; and continue to correct any defects in or omissions from a Project Plan (whether identified by the Contract Administrator or the Contractor), and submit an updated or amended Project Plan to the Contract Administrator, after which: the Contractor must continue to comply with the requirements of the then current Project Plan until the process in subparagraph (ii) has been completed in respect of the updated or amended Project Plan; and subsubparagraphs B - E will apply (to the extent applicable); and document and maintain detailed records of all: reviews, updates, amendments and submissions of each Project Plan; audits or other monitoring of each Project Plan; and training and awareness programs and communications provided to Contractor and subcontractor personnel in respect of each Project Plan (including each updated or amended Project Plan). The Contractor will not be relieved from compliance with any of its obligations under the Contract or otherwise at law or in equity as a result of: the implementation of, and compliance with, the requirements of any Project Plan; any direction by the Contract Administrator concerning a Project Plan or the Contractor's compliance or non-compliance with a Project Plan; any audit or other monitoring by the Contract Administrator or anyone else acting on behalf of the Commonwealth of the Contractor's compliance with a Project Plan; or any failure by the Contract Administrator, or anyone else acting on behalf of the Commonwealth, to detect any defect in or omission from a Project Plan including where any such failure arises from any negligence on the part of the Contract Administrator or other person.

  • Development Budget Attached hereto as Exhibit "B" and incorporated herein by this reference is the Development Budget in an amount equal to $_____________. Owner acknowledges and represents that the attached Development Budget includes the total costs and expenses to acquire, develop, renovate and construct the Real Property and the Apartment Housing.

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