Scope of Charter School Operations. 1. Overview
Scope of Charter School Operations Sample Clauses
Related to Scope of Charter School Operations
Scope of Coverage 1. This Section shall apply to an investment dispute between a Member State and an investor of another Member State that has incurred loss or damage by reason of an alleged breach of any rights conferred by this Agreement with respect to the investment of that investor. 2. A natural person possessing the nationality or citizenship of a Member State shall not pursue a claim against that Member State under this Section. 3. This Section shall not apply to claims arising out of events which occurred, or claims which have been raised prior to the entry into force of this Agreement. 4. Nothing in this Section shall be construed so as to prevent a disputing investor from seeking administrative or judicial settlement available within the country of a disputing Member State.
CONTRACTOR NAME CHANGE An amendment is required to change the Contractor's name as listed on this Agreement. Upon receipt of legal documentation of the name change the State will process the amendment. Payment of invoices presented with a new name cannot be paid prior to approval of said amendment.
Minimum scope of coverage Commercial general coverage shall be at least as broad as Insurance Services Office Commercial General Liability occurrence form CG 0001 (ed. 11/88) or Insurance Services Office form number GL 0002 (ed. 1/73) covering comprehensive General Liability and Insurance Services Office form number GL 0404 covering Broad Form Comprehensive General Liability. Automobile coverage shall be at least as broad as Insurance Services Office Automobile Liability form CA 0001 (ed. 12/90) Code 1 (“any auto”). No endorsement shall be attached limiting the coverage.
Scope of Covenants Employer and Executive acknowledge that the time, scope, geographic area and other provisions of Sections 6 and 7 have been specifically negotiated by sophisticated commercial parties and agree that they consider the restrictions and covenants contained in such Sections to be reasonable and necessary for the protection of the interests of the Related Companies, but if any such restriction or covenant shall be held by any court of competent jurisdiction to be void but would be valid if deleted in part or reduced in application, such restriction or covenant shall apply with such deletion or modification as may be necessary to make it valid and enforceable. The restrictions and covenants contained in each provision of such Sections shall be construed as separate and individual restrictions and covenants and shall each be capable of being severed without prejudice to the other restrictions and covenants or to the remaining provisions of this Agreement.
Operations Fire An “Operations Fire” is a fire caused by Purchaser’s Operations other than a Neg- ligent Fire.
Synchronization, Commissioning and Commercial Operation 4.1.1 The Power Producer shall give at least fifteen (15) days written notice to the SLDC / ALDC / DISCOM as the case may be, of the date on which it intends to synchronize the Power Project to the Grid System. 4.1.2 Subject to Article 4.1.1, the Power Project may be synchronized by the Power Producer to the Grid System when it meets all the connection conditions prescribed in the Grid Code and otherwise meets all other Indian legal requirements for synchronization to the Grid System. 4.1.3 The synchronization equipment and all necessary arrangements / equipment including Remote Terminal Unit (RTU) for scheduling of power generated from the Project and transmission of data to the concerned authority as per applicable regulation shall be installed by the Power Producer at its generation facility of the Power Project at its own cost. The Power Producer shall synchronize its system with the Grid System only after the approval of GETCO / SLDC / ALDC and GEDA. 4.1.4 The Power Producer shall immediately after each synchronization / tripping of generator, inform the sub-station of the Grid System to which the Power Project is electrically connected in accordance with applicable Grid Code. 4.1.5 The Power Producer shall commission the Project within SCOD. 4.1.6 The Power Producer shall be required to obtain Developer and/ or Transfer Permission, Key Plan drawing etc, if required, from GEDA. In cases of conversion of land from Agricultural to Non-Agriculture, the commissioning shall be taken up by GEDA only upon submission of N.A. permission by the Power Producer. 4.1.7 The Power Producer shall be required to follow the Forecasting and Scheduling procedures as per the Regulations issued by Hon’ble GERC from time to time. It is to clarify that in terms of GERC (Forecasting, Scheduling, Deviation Settlement and Related Matters of Solar and Wind Generation Sources) Regulations, 2019 the procedures for Forecasting, Scheduling & Deviation Settlment are applicable to all solar generators having combined installed capacity above 1 MW connected to the State Grid / Substation including those connected via pooling stations.
Contractor Name Business License #: Address: City, State, Zip Code: Telephone: Facsimile: Email: * If you are an independent contractor you are required to obtain a business license with the City of Thousand Oaks. Contractor certifies under penalty of perjury that Contractor is a Sole Proprietor Corporation Limited Liability Company Partnership Nonprofit Corporation Other [describe: ]
Verizon Operations Support Systems Verizon systems for pre- ordering, ordering, provisioning, maintenance and repair, and billing.
SCOPE OF ARCHITECT’S BASIC SERVICES 3.1 The Architect’s Basic Services consist of those described in this Article 3 and include usual and customary structural, mechanical, and electrical engineering services. Services not set forth in this Article 3 are Supplemental or Additional Services. § 3.1.1 The Architect shall manage the Architect’s services, research applicable design criteria, attend Project meetings, communicate with members of the Project team, and report progress to the Owner. § 3.1.2 The Architect shall coordinate its services with those services provided by the Owner and the Owner’s consultants. The Architect shall be entitled to rely on, and shall not be responsible for, the accuracy, completeness, and timeliness of, services and information furnished by the Owner and the Owner’s consultants. The Architect shall provide prompt written notice to the Owner if the Architect becomes aware of any error, omission, or inconsistency in such services or information. § 3.1.3 As soon as practicable after the date of this Agreement, the Architect shall submit for the Owner’s approval a schedule for the performance of the Architect’s services. The schedule initially shall include anticipated dates for the commencement of construction and for Substantial Completion of the Work as set forth in the Initial Information. The schedule shall include allowances for periods of time required for the Owner’s review, for the performance of the Owner’s consultants, and for approval of submissions by authorities having jurisdiction over the Project. Once approved by the Owner, time limits established by the schedule shall not, except for reasonable cause, be exceeded by the Architect or Owner. With the Owner’s approval, the Architect shall adjust the schedule, if necessary, as the Project proceeds until the commencement of construction. § 3.1.4 The Architect shall not be responsible for an Owner’s directive or substitution, or for the Owner’s acceptance of non-conforming Work, made or given without the Architect’s written approval. § 3.1.5 The Architect shall contact governmental authorities required to approve the Construction Documents and entities providing utility services to the Project. The Architect shall respond to applicable design requirements imposed by those authorities and entities. § 3.1.6 The Architect shall assist the Owner in connection with the Owner’s responsibility for filing documents required for the approval of governmental authorities having jurisdiction over the Project.
Registry Interoperability and Continuity Registry Operator shall comply with the Registry Interoperability and Continuity Specifications as set forth in Specification 6 attached hereto (“Specification 6”).
