EPOS Scalability Problems Sample Clauses

EPOS Scalability Problems. For scalability, EPOS has two main challenges. First, it seeks integration of diverse data sets archived into different data centres using different technologies and schema. Second, it seeks federation of the same type of data across multiple data centres. The scalability issues are intimately related to the data services that will exploit the underlying data organization and accessibility. This includes, for example, the means for accessing, using, obtaining information, analyzing and displaying the data. With regard to the first challenge, the objective is very much alike that of EUDAT as whole but at a smaller scale ‒ it is sought the integration of diverse archives and creation of a common data infrastructure for the solid Earth sciences. A number of services will be implemented to “discover” and “mine” the data. We note that EPOS is now in the preparatory phase, PP, and it is now finishing to gather the information from all the working groups participating to EPOS (i.e., seismology, geodesy, geology, experimental laboratories, vulcanology, other geophysical data and satellite observations). The data types (digital objects) are very diverse (e.g., time series, images, movies) and differently organized (e.g., file systems, DBs). Thus in this first case, the scalability is to be meant as integration of diversity. To provide a few numbers resulting from the EPOS inventory, there are 19 countries with a total of 197 research infrastructures, from 136 institutions providing and acquiring data, in the solid earth sciences in Europe. We note also that the working group 7 of EPOS PP (WG7, ICT and e-RI Facilities) has proposed for this integration a multi-stack approach of the EPOS PP project. More specifically, WG7 of EPOS has envisaged the integrated services that EPOS will provide have the following main functionalities sub- divided into different levels of access and content – Discovery and Contextual and Detailed Levels. The second challenge consists of federating geographically distributed archives containing the same type and large (TBs) amounts of data (e.g., seismological data archived in specific data structures and formats). This is important since there are state-of-the-art analysis schemes that require access, for specific time windows, to data stored in several archives. The scalability issues derive from the difficulty of moving large quantities of data across the network. This all suggests prioritising the moving of the processes rather than the...

Related to EPOS Scalability Problems

  • Infrastructure Vulnerability Scanning Supplier will scan its internal environments (e.g., servers, network devices, etc.) related to Deliverables monthly and external environments related to Deliverables weekly. Supplier will have a defined process to address any findings but will ensure that any high-risk vulnerabilities are addressed within 30 days.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If ECI chooses to subtend a Verizon access Tandem, ECI’s NPA/NXX must be assigned by ECI to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG. 9.2.2 ECI shall establish Access Toll Connecting Trunks pursuant to applicable access Tariffs by which it will provide Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic to and from ECI’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office ECI utilizes to provide Telephone Exchange Service and Switched Exchange Access to its Customers in a given LATA to the access Tandem(s) Verizon utilizes to provide Exchange Access in such LATA. 9.2.4 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access to allow ECI’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.

  • Problem Solving Employees and supervisors are encouraged to attempt to resolve on an informal basis, at the earliest opportunity, a problem that could lead to a grievance. If the matter is not resolved by informal discussion, or a problem-solving meeting does not occur, it may be settled in accordance with the grievance procedure. Unless mutually agreed between the Employer and the Union problem-solving discussions shall not extend the deadlines for filing a grievance. The Union Xxxxxxx or in their absence, the Local Union President, or Area Xxxxxxx, or Chief Xxxxxxx, either with the employee or alone, shall present to the appropriate supervisor a written request for a meeting. If the supervisor agrees to a problem- solving meeting, this meeting shall be held within fourteen (14) calendar days of receipt of the request. The supervisor, employee, Union Xxxxxxx, and up to one (1) other management person shall attempt to resolve the problem through direct and forthright communication. If another member of management is present that person will not be hearing the grievance at Step Two, should it progress to that Step. The employee, the Union Xxxxxxx or in their absence, the Local Union President, or Area Xxxxxxx, or Chief Xxxxxxx, may participate in problem-solving activities on paid time, in accordance with Article 31, Union Rights, Section 1H.

  • Problems To endeavour to resolve in a fair and just manner any problems, grievances or difficulties which may be encountered while you volunteer with us;

  • Interoperability To the extent required by applicable law, Cisco shall provide You with the interface information needed to achieve interoperability between the Software and another independently created program. Cisco will provide this interface information at Your written request after you pay Cisco’s licensing fees (if any). You will keep this information in strict confidence and strictly follow any applicable terms and conditions upon which Cisco makes such information available.

  • Local Circuit Switching Capability, including Tandem Switching Capability 4.2.1 Local circuit switching capability is defined as: (A) line-side facilities, which include, but are not limited to, the connection between a loop termination at a main distribution frame and a switch line card; (B) trunk-side facilities, which include, but are not limited to, the connection between trunk termination at a trunk-side cross-connect panel and a switch trunk card; (C) switching provided by remote switching modules; and (D) all features, functions, and capabilities of the switch, which include, but are not limited to: (1) the basic switching function of connecting lines to lines, line to trunks, trunks to lines, and trunks to trunks, as well as the same basic capabilities made available to BellSouth’s customers, such as a telephone number, white page listings, and dial tone; and (2) all other features that the switch is capable of providing, including but not limited to customer calling, customer local area signaling service features, and Centrex, as well as any technically feasible customized routing functions provided by the switch. Any features that are not currently available but are technically feasible through the switch can be requested through the BFR/NBR process. 4.2.2 Notwithstanding BellSouth’s general duty to unbundle local circuit switching, BellSouth shall not be required to unbundle local circuit switching for Louisville Telephone when Louisville Telephone serves an end-user with four (4) or more voice-grade (DS-0) equivalents or lines served by BellSouth in one of the following MSAs: Atlanta, GA; Miami, FL; Orlando, FL; Ft. Lauderdale, FL; Charlotte-Gastonia-Rock Hill, NC; Greensboro-Winston Salem-High Point, NC; Nashville, TN; and New Orleans, LA, and BellSouth has provided non- discriminatory cost based access to the Enhanced Extended Link (EEL) throughout Density Zone 1 as determined by NECA Tariff No. 4 as in effect on January 1, 1999. 4.2.3 In the event that Louisville Telephone orders local circuit switching for an end user with four (4) or more DS0 equivalent lines within Density Zone 1 in an MSA listed above, BellSouth shall charge Louisville Telephone the market based rates in Exhibit B for use of the local circuit switching functionality for the affected facilities.

  • Required Procurement Procedures for Obtaining Goods and Services The Grantee shall provide maximum open competition when procuring goods and services related to the grant- assisted project in accordance with Section 287.057, Florida Statutes.

  • Equipment Procurement If responsibility for construction of the Connecting Transmission Owner’s Attachment Facilities or System Upgrade Facilities or System Deliverability Upgrades is to be borne by the Connecting Transmission Owner, then the Connecting Transmission Owner shall commence design of the Connecting Transmission Owner’s Attachment Facilities or System Upgrade Facilities or System Deliverability Upgrades and procure necessary equipment as soon as practicable after all of the following conditions are satisfied, unless the Developer and Connecting Transmission Owner otherwise agree in writing: 5.5.1 NYISO and Connecting Transmission Owner have completed the Interconnection Facilities Study pursuant to the Interconnection Facilities Study Agreement; 5.5.2 The NYISO has completed the required cost allocation analyses, and Developer has accepted his share of the costs for necessary System Upgrade Facilities and System Deliverability Upgrades in accordance with the provisions of Attachment S of the NYISO OATT; 5.5.3 The Connecting Transmission Owner has received written authorization to proceed with design and procurement from the Developer by the date specified in Appendix B hereto; and 5.5.4 The Developer has provided security to the Connecting Transmission Owner in accordance with Article 11.5 by the dates specified in Appendix B hereto.

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where Freedom has requested an Unbundled Loop and BellSouth uses IDLC systems to provide the local service to the End User and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to Freedom. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for Freedom (e.g. hairpinning): 1. Roll the circuit(s) from the IDLC to any spare copper that exists to the customer premises. 2. Roll the circuit(s) from the IDLC to an existing DLC that is not integrated. 3. If capacity exists, provide "side-door" porting through the switch. 4. If capacity exists, provide "Digital Access Cross Connect System (DACS)- door" porting (if the IDLC routes through a DACS prior to integration into the switch). 2.6.2 Arrangements 3 and 4 above require the use of a designed circuit. Therefore, non- designed Loops such as the SL1 voice grade and UCL-ND may not be ordered in these cases. 2.6.3 If no alternate facility is available, and upon request from Freedom, and if agreed to by both Parties, BellSouth may utilize its Special Construction (SC) process to determine the additional costs required to provision facilities. Freedom will then have the option of paying the one-time SC rates to place the Loop.

  • Service Level Expectations Without limiting any other requirements of the Agreement, the Service Provider shall meet or exceed the following standards, policies, and guidelines: