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.
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.
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 NYISO 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.
Format The data will be provided in the format specified in Specification 2 for Data Escrow (including encryption, signing, etc.) but including only the fields mentioned in the previous section, i.e., the file will only contain Domain and Registrar objects with the fields mentioned above. Registry Operator has the option to provide a full deposit file instead as specified in Specification 2.
EODUF Packing Specifications 7.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.
Escrow Format Specification 3.1. 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.
ODUF Packing Specifications 6.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.
Construction Documents Phase Services 3.4.1 Based on the Owner’s approval of the Design Development Documents, and on the Owner’s authorization of any adjustments in the Project requirements and the budget for the Cost of the Work, the Architect shall prepare Construction Documents for the Owner’s approval. The Construction Documents shall illustrate and describe the further development of the approved Design Development Documents and shall consist of Drawings and Specifications setting forth in detail the quality levels and performance criteria of materials and systems and other requirements for the construction of the Work. The Owner and Architect acknowledge that, in order to perform the Work, the Contractor will provide additional information, including Shop Drawings, Product Data, Samples and other similar submittals, which the Architect shall review in accordance with Section 3.6.4.
Alternative Schedules An employee may work an alternative work schedule with the written permission of the employee’s Department Manager. The alternative work schedule may be ended by the Department Manager and the employee’s schedule changed to a different alternative work schedule or the standard work schedule. The District may change the employees work period when an employee begins and/or ends working an alternative schedule. The alternative work schedules are listed in the table below.
Alternative Work Schedules Alternative work schedule means an approved schedule for an Employee that deviates from the work week described in Section 1, Section 2, or a schedule that deviates from a worksite’s normal schedule. Employees who work a “shift work schedule” as part of a rotating group of individuals who must continuously maintain a 24-hour operation or facility are not eligible for an alternative work schedule.
