EGI Operations Architecture Sample Clauses

EGI Operations Architecture. A technical description of all the operational services needed globally (XXX.xx) 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 17]
Sample 1Sample 2Sample 3See All (17)
AutoNDA by SimpleDocs
EGI Operations Architecture. Infrastructure Platform and Collaboration Platform Integration, EGI-InSPIRE Deliverable D4.6, March 2012 (xxxxx://xxxxxxxxx.xxx.xx/document/1309) The specific activities to be carried out in the framework of the collaboration are3: WP1 Participation to the XXX.xx policy groups Parties Involved: XXX.xx (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 XXX.xx. WP2 Global services Parties Involved: XXX.xx (Contact: EGI Chief Operations Officer); ASGC Description of work: Identify a set of XXX.xx Global services APGI is interested in using together with the respective guaranteed quality parameters that XXX.xx commits to provide. Expected outcome: • A2.1 (09/2013) - XXX.xx OLA defining the Global services offered is released and approved. The OLA should be periodically reviewed, at least yearly. (Leader Xxxxxxx Xxxxxxx) • A2.2 (04/2014) - Annual report on used XXX.xx Global services, including performance and utilization statistics. (Leader Xxxxxxx Xxxxxxx) WP3 Reporting Parties Involved: XXX.xx (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 XXX.xx and are accessible on the EGI wiki: xxxxx://xxxx.xxx.xx/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. XXX.xx is performing this assessment, which is publicly available on EGI document DB. Expected outcome: • A3.1 (every year...
Sample 1
EGI Operations Architecture. Infrastructure Platform and Collaboration Platform Integration, EGI-InSPIRE Deliverable D4.6, March 2012 (xxxxx://xxxxxxxxx.xxx.xx/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 XXX.xx.
Sample 1

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:

  • Design Development Phase Services 3.3.1 Based on the Owner’s approval of the Schematic Design 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 Design Development Documents for the Owner’s approval. The Design Development Documents shall illustrate and describe the development of the approved Schematic Design Documents and shall consist of drawings and other documents including plans, sections, elevations, typical construction details, and diagrammatic layouts of building systems to fix and describe the size and character of the Project as to architectural, structural, mechanical and electrical systems, and other appropriate elements. The Design Development Documents shall also include outline specifications that identify major materials and systems and establish, in general, their quality levels.

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

  • Synchronization, Commissioning and Commercial Operation 4.1.1 The Power Producer shall give at least thirty (30) days written notice to the SLDC and GUVNL, of the date on which it intends to synchronize the Power Project to the Grid System.

  • Physical Architecture 59.2.1 CenturyLink's network architecture in any given local exchange area and/or LATA can vary markedly from another local exchange area/LATA. Using one or more of the NIMs herein, the Parties will agree to a physical architecture plan for a specific LATA, or if appropriate based on other requirements in Section 59, Local Calling Area. The physical architecture plan, as described in the Local Interconnection POI Profile, will be discussed during joint implementation planning. CLEC and CenturyLink agree to Interconnect their networks through existing and/or new Interconnection Facilities between CLEC switch(es) and CenturyLink's End Office Switch(es) and/or Tandem Switch(es). The physical architecture plan will be in accordance with Forecasting and Planning requirements in Article IV.

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

  • Schematic Design Phase Services § 3.2.1 The Architect shall review the program and other information furnished by the Owner, and shall review laws, codes, and regulations applicable to the Architect’s services.

  • Synchronisation Commissioning and Commercial Operation 8.1 The Developer shall provide at least forty (40) days advanced preliminary written notice and at least twenty (20) days advanced final written notice to ESCOM of the date on which it intends to synchronize the Power Project to the Grid System.

  • INTERNET PLANNING, ENGINEERING AND OPERATIONS ‌ Job Title: Internet/Web Engineer Job#: 2620 General Characteristics Integrally involved in the development and support of all Internet/Intranet/Extranet sites and supporting systems. Works closely with other IT groups and customers to define the system design and user interface based on customer needs and objectives. Participates in all phases of the development and implementation process, and may act as a project manager on special projects. Ensures the integration of the Web servers and all other supporting systems. Responsible for system tuning, optimization of information/data processing, maintenance and support of the production environment.

Time is Money Join Law Insider Premium to draft better contracts faster.