EGI Operations Architecture Clause Samples

EGI Operations Architecture. A technical description of all the operational services needed globally (▇▇▇.▇▇) and nationally (NGI/EIRO International Tasks). It also defines the operational interfaces that need to be supported by a technology for its integration into the EGI production infrastructure. [month 41]
View SourceView Similar (16)
EGI Operations Architecture. Infrastructure Platform and Collaboration Platform Integration, EGI-InSPIRE Deliverable D4.6, March 2012 (▇▇▇▇▇://▇▇▇▇▇▇▇▇▇.▇▇▇.▇▇/document/1309) The specific activities to be carried out in the framework of the collaboration are3: WP1 Participation to the ▇▇▇.▇▇ policy groups Parties Involved: ▇▇▇.▇▇ (Contact: EGI Chief Operations Officer); ASGC Description of work: APGI to be regularly represented in the Operations Management Board, to provide requirements necessary to drive the evolution of the operations architecture and generally to provide feedback through attendance to meetings, questionnaires and e-mail. APGI to regularly participate to the SPG meetings, with the status of voting member, contributing to the development of the security policies that ensure a secure distributed computing infrastructure. Expected outcome: Participation to OMB work. APGI Operations Manager and APGI Security Manager/Officer are already appointed and contributing to the OMB. Performance of all Operations Centres is assessed on an annual basis by ▇▇▇.▇▇. WP2 Global services Parties Involved: ▇▇▇.▇▇ (Contact: EGI Chief Operations Officer); ASGC Description of work: Identify a set of ▇▇▇.▇▇ Global services APGI is interested in using together with the respective guaranteed quality parameters that ▇▇▇.▇▇ commits to provide. Expected outcome: • A2.1 (09/2013) - ▇▇▇.▇▇ OLA defining the Global services offered is released and approved. The OLA should be periodically reviewed, at least yearly. (Leader ▇▇▇▇▇▇▇ ▇▇▇▇▇▇▇) • A2.2 (04/2014) - Annual report on used ▇▇▇.▇▇ Global services, including performance and utilization statistics. (Leader ▇▇▇▇▇▇▇ ▇▇▇▇▇▇▇) WP3 Reporting Parties Involved: ▇▇▇.▇▇ (Contact: EGI Chief Operations Officer); ASGC Description of work: As part of the EGI quality assurance procedures, performance of the services provided by APGI Resource Centres (site-level grid services) and performance of the core services provided by APGI (operations centre-level services) is reported on a monthly basis. Reports are produced by ▇▇▇.▇▇ and are accessible on the EGI wiki: ▇▇▇▇▇://▇▇▇▇.▇▇▇.▇▇/wiki/Performance APGI agrees to adhere to the minimum service level targets defined in the Resource Centre OLA4 and the Resource Infrastructure Provider OLA5. APGI installed capacity and utilization are also assessed yearly as part of the annual assessment of EGI. ▇▇▇.▇▇ is performing this assessment, which is publicly available on EGI document DB. Expected outcome: • A3.1 (every year...
View Source
EGI Operations Architecture. Infrastructure Platform and Collaboration Platform Integration, EGI-InSPIRE Deliverable D4.6, March 2012 (▇▇▇▇▇://▇▇▇▇▇▇▇▇▇.▇▇▇.▇▇/document/1309) 3 Party leading the activity is underlined. the operations architecture and generally to provide feedback through attendance to meetings, questionnaires and e-mail. IHEP to regularly participate to the SPG meetings, with the status of voting member, contributing to the development of the security policies that ensure a secure distributed computing infrastructure. Expected outcome: Participation to OMB work. China-ROC Operations Manager and China-ROC Security Manager/Officer are already appointed and contributing to the OMB. Performance of Operations Centre is assessed on an annual basis by ▇▇▇.▇▇.
View Source

Related to EGI Operations Architecture

  • Architecture The Private Improvements shall have architectural features, detailing, and design elements in accordance with the Project Schematic Drawings. All accessory screening walls or fences, if necessary, shall use similar primary material, color, and detailing as on the Private Improvements.

  • Configuration Management The Contractor shall maintain a configuration management program, which shall provide for the administrative and functional systems necessary for configuration identification, control, status accounting and reporting, to ensure configuration identity with the UCEU and associated cables produced by the Contractor. The Contractor shall maintain a Contractor approved Configuration Management Plan that complies with ANSI/EIA-649 2011. Notwithstanding ANSI/EIA-649 2011, the Contractor’s configuration management program shall comply with the VLS Configuration Management Plans, TL130-AD-PLN-010-VLS, and shall comply with the following:

  • 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.

  • Synchronization, Commissioning and Commercial Operation 5.1.1 The SPG shall give PGVCL at least thirty (30) days’ advanced preliminary written notice and at least fifteen (15) days’ advanced final written notice, of the date on which it intends to synchronize the Solar Power Project to the Grid System. 5.1.2 Subject to Article 5.1.1, the Power Project may be synchronized by the SPG to the Grid System when it meets all the connection conditions prescribed in applicable Grid Code then in effect and otherwise meets all other Indian legal requirements for synchronization to the Grid System. 5.1.3 The synchronization equipment and all necessary arrangements / equipment including 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 SPG at its generation facility of the Power Project at its own cost. The SPG shall synchronize its system with the Grid System only after the approval of synchronization scheme is granted by the head of the concerned substation/ and checking/verification is made by the concerned authorities of the PGVCL. 5.1.4 The SPG 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. In addition, the SPG will inject in-firm power to grid from time to time to carry out operational/ functional test prior to commercial operation. For avoidance of doubt, it is clarified that Synchronization / Connectivity of the Project with the grid shall not to be considered as Commissioning of the Project. 5.1.5 The SPG shall commission the Project within nine (9) Months from the Date of execution of this PPA. Declaration of COD shall be certified by the commissioning committee. 5.1.6 The Parties agree that for the purpose of commencement of the supply of electricity by SPG to PGVCL, liquidated damages for delay etc., the Scheduled Commissioning Date as defined in this Agreement shall be the relevant date.

  • Network Interconnection Architecture Each Party will plan, design, construct and maintain the facilities within their respective systems as are necessary and proper for the provision of traffic covered by this Agreement. These facilities include but are not limited to, a sufficient number of trunks to the point of interconnection with the tandem company, and sufficient interoffice and interexchange facilities and trunks between its own central offices to adequately handle traffic between all central offices within the service areas at a P.01 grade of service or better. The provisioning and engineering of such services and facilities will comply with generally accepted industry methods and practices, and will observe the rules and regulations of the lawfully established tariffs applicable to the services provided.