Voltage Schedules Once the Developer has synchronized the Large Generating Facility with the New York State Transmission System, NYISO shall require Developer to operate the Large Generating Facility to produce or absorb reactive power within the design capability of the Large Generating Facility set forth in Article 9.5.1 (Power Factor Design Criteria). NYISO’s voltage schedules shall treat all sources of reactive power in the New York Control Area in an equitable and not unduly discriminatory manner. NYISO shall exercise Reasonable Efforts to provide Developer with such schedules in accordance with NYISO procedures, and may make changes to such schedules as necessary to maintain the reliability of the New York State Transmission System. Developer shall operate the Large Generating Facility to maintain the specified output voltage or power factor at the Point of Interconnection within the design capability of the Large Generating Facility set forth in Article 9.5.1 (Power Factor Design Criteria) as directed by the Connecting Transmission Owner’s System Operator or the NYISO. If Developer is unable to maintain the specified voltage or power factor, it shall promptly notify NYISO.
Outage Schedules The Connecting Transmission Owner shall post scheduled outages of its transmission facilities on the NYISO OASIS. Developer shall submit its planned maintenance schedules for the Large Generating Facility to Connecting Transmission Owner and NYISO for a minimum of a rolling thirty-six month period. Developer shall update its planned maintenance schedules as necessary. NYISO may direct, or the Connecting Transmission Owner may request, Developer to reschedule its maintenance as necessary to maintain the reliability of the New York State Transmission System. Compensation to Developer for any additional direct costs that the Developer incurs as a result of rescheduling maintenance, including any additional overtime, breaking of maintenance contracts or other costs above and beyond the cost the Developer would have incurred absent the request to reschedule maintenance, shall be in accordance with the ISO OATT. Developer will not be eligible to receive compensation, if during the twelve (12) months prior to the date of the scheduled maintenance, the Developer had modified its schedule of maintenance activities other than at the direction of the NYISO or request of the Connecting Transmission Owner.
Contract Schedule The information set forth in the Contract Schedule is true and correct.
Delivery Schedule The Goods specified in the List of Goods are required to be delivered within the acceptable time range (after the earliest and before the final date, both dates inclusive) specified in Section V, Schedule of Requirements. No credit will be given to deliveries before the earliest date, and Tenders offering delivery after the final date shall be treated as non-responsive. Within this acceptable period, an adjustment of [insert the adjustment factor], will be added, for evaluation purposes only, to the Tender price of Tenders offering deliveries later than the “Earliest Delivery Date” specified in Section V, Schedule of Requirements.
DELIVERY SCHEDULES In accordance with the "Non-State Agencies Participation in Centralized Contracts” and “Extension of Use” clauses herein, this Contract is extended to local governments, political subdivisions and others authorized by law as well as State agencies. The Delivery Schedules (based on Requirement Letter RL182) are available as a guide to indicate proposed delivery points and estimated annual requirements. Delivery Schedules may be revised or clarified as necessary. Any specific questions regarding the site conditions should be directed to the end-user at the telephone number shown on the Delivery Schedule. The Delivery Schedules are available upon request. Contractors shall be obligated to deliver under the Contract to any State agency which places a purchase order under the Contract, whether or not such delivery location is identified in the Delivery Schedules. Any political subdivision or other non-State entity which has not filed a requirement with OGS as of the date of the bid opening shall be eligible to receive deliveries at Contractor's option only, upon placement of a valid purchase order to the Contractor's address as indicated in the award. Contracts created by OGS in response to receipt of Filed Requirements are considered to be binding. At Contractor's request, Contractor will be advised in writing regarding political subdivisions or other Non-State entities which have filed on a timely basis but do not appear on the Delivery Schedule. Where “Standby” is indicated in the Delivery Schedule, this reflects those facilities which normally use a fuel supply (i.e. natural gas) other than fuel oil and will only use fuel oil when alternate fuel is unavailable.
Escrow Format Specification Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.
MSAA Indicator Technical Specification Document This Agreement shall be interpreted with reference to the MSAA Indicator Technical Specifications document.
Wage Schedules The Parties shall, upon completing a wage adjustment calculation, forthwith prepare, publish, post and distribute a wage schedule resulting therefrom. The final determination of the wage schedules shall be issued no later than the 7th day of March or September, for the May and November adjustments, respectively.
Price Schedule 35.1. All prices under this agreement are set forth in the attachments designated Table One and Table Two of this Agreement are hereby incorporated into, and made a part of, this Agreement. 35.2. Subject to the provisions of Part B, Section 4 of this Agreement, all rates provided under this Agreement shall remain in effect for the term of this Agreement.
Contract Task Order A- E shall be assigned work via a task order by COUNTY which shall subsequently be referred to as the “Contract Task Order” (hereinafter “CTO”). A CTO for each project shall be developed by A-E in conjunction with COUNTY Project Management staff. The County Project Manager shall manage all A-E’s work including monitoring the CTO work schedule, quality of deliverables, review of invoiced amounts, adherence to set budget, and internal review of submittal packages. A-E shall follow all requirements as outlined in the CTO; this general Scope of Work, the project specific Scope Statement, and the Architect-Engineer Guide (Rev July 2018). The CTO shall include a detailed Scope Statement, describing tasks to be performed with a specific list of deliverables for each task, schedule of work and cost to complete the work. The schedule of work shall allow enough time for meetings with County Management staff to review the work progress, provide technical and policy direction, resolve problems and ensure adherence to the work completion schedule. The CTO shall include a cover sheet provided by County Project Management staff with the appropriate signature blocks and contract information. Once both Parties agree, and all Parties have signed the CTO, County Management staff shall provide A-E with a Notice to Proceed (NTP) to begin work. A-E shall submit all plans, reports and other documents produced under the CTO to the assigned County Project Manager within the timeframe indicated in the CTO or as directed by County Project Management staff.