Development Work The Support Standards do not include development work either (i) on software not licensed from CentralSquare or (ii) development work for enhancements or features that are outside the documented functionality of the Solutions, except such work as may be specifically purchased and outlined in Exhibit 1. CentralSquare retains all Intellectual Property Rights in development work performed and Customer may request consulting and development work from CentralSquare as a separate billable service.
Project Completion Part 1 – Material Completion
Development Rights The Employee agrees and declares that all proprietary information including but not limited to trade secrets, know-how, patents and other rights in connection therewith developed by or with the contribution of Employee's efforts during his employment with the Company shall be the sole property of the Company. Upon the Company's request (whenever made), Employee shall execute and assign to the Company all the rights in the proprietary information.
Purchase Order A Customer may use purchase orders to buy commodities or contractual services pursuant to the Contract and, if applicable, the Contractor must provide commodities or contractual services pursuant to purchase orders. Purchase orders issued pursuant to the Contract must be received by the Contractor no later than the close of business on the last day of the Contract’s term. The Contractor is required to accept timely purchase orders specifying delivery schedules that extend beyond the Contract term even when such extended delivery will occur after expiration of the Contract. Purchase orders shall be valid through their specified term and performance by the Contractor, and all terms and conditions of the Contract shall survive the termination or expiration of the Contract and apply to the Contractor’s performance. The duration of purchase orders for recurring deliverables shall not exceed the expiration of the Contract by more than twelve months. Any purchase order terms and conditions conflicting with these Special Contract Conditions shall not become a part of the Contract.
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.
Development Program A. Development activities to be undertaken (Please break activities into subunits with the date of completion of major milestones)
Forecasts and Purchase Orders On or before the twelfth (12th) day of each month, beginning on January 12, 2022, Indivior shall furnish to Curia a written twelve (12) month rolling forecast of the quantities of Product that Indivior intends to order from Curia during such period ("Rolling Forecast"). The first six (6) months of such Rolling Forecast shall constitute a firm and binding commitment to order quantities of Product specified therein ("Firm Period Forecast"), and the following six (6) months of the Rolling Forecast shall be non-binding, good faith estimates. Each month of the Rolling Forecast shall begin on the twelfth (12th) of the calendar month in which such Rolling Forecast is submitted and end on the eleventh (11th) day of the following calendar month. With exception to the Firm Period Forecast, Curia reserves the right to reject any Rolling Forecast that does not align with the physical Processing capabilities of the Facility(ies) and the parties shall work in good faith to adjust the Rolling Forecast based on available resources, Facility capacity and other relevant factors. Indivior shall have the right to request an increase of the Firm Period Forecast to include additional units of Product. Curia may, in its sole discretion, supply such additional quantities, subject to Curia's other supply commitments and manufacturing capacity. In the event Curia agrees to supply such additional quantities, Indivior shall submit a Purchase Order for such additional quantities, with the required lead times as specified below. In no event shall Curia's inability to fulfill Purchase Orders for quantities in excess of the Firm Period Forecast be deemed a breach of this Agreement, nor relieve Indivior of its obligations under this Agreement. Indivior shall submit with each Rolling Forecast, a non-cancelable Purchase Order for the Firm Period Forecast (or such portion of the Firm Period Forecast not covered by previously submitted Purchase Orders). Indivior may alternatively submit Purchase Orders for certain portions of the Firm Period Forecast subsequent to the submission of the Rolling Forecast, provided the Purchase Orders provide the required lead time for Processing as set forth below. Curia shall notify Indivior of acceptance of the Rolling Forecast and any Purchase Order within seven (7) business days of receipt. Curia shall be deemed to have accepted Purchase Orders which it does not acknowledge within seven (7) business days of receipt. Curia shall have the right to reject Rolling Forecasts and Purchase Orders that are inconsistent with this Agreement. Each Purchase Order shall specify the quantity of Product being ordered, and the desired delivery date. Upon mutual agreement in writing for additional quantities of Product beyond the Firm Period Forecast, including projected delivery date(s), Indivior shall issue the applicable Purchase Order to be accepted by Curia as described above. Once placed, all Purchase Orders for Product shall be non-cancelable. No different or additional terms or conditions set forth in any Purchase Order shall modify in any way the terms and conditions of this Agreement, and in the event of a conflict between terms in any Purchase Order and this Agreement, the terms of this Agreement shall control. All Purchase Orders submitted in accordance with the terms of this Agreement shall be effective and binding on the parties upon acceptance by Curia. Except as otherwise provided herein, neither party shall have the right or power to refuse, reduce, or otherwise modify their obligations under any Purchase Order; however, Purchase Orders may be amended (i) upon written mutual agreement regarding such modification that is signed by both parties; or (ii) as otherwise provided in this Section 4.3 or Section 4.4.
Deliverables Upon satisfactory completion of the work authorization, the Engineer shall submit the deliverables as specified in the executed work authorization to the State for review and acceptance.
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.
Production Work The Company may use Outside Entities to perform production work outside the plant and its environs provided the Company demonstrates that it is utilizing plant equipment to the maximum extent consistent with equipment capability and customer requirements and the Company is making necessary capital investments to remain competitive in the steel business and is in compliance with Article Eleven, Section B (Investment Commitment).
