Shared Systems Sample Clauses

Shared Systems. The Shared Systems include the following systems and all related equipment as follows: – USP Purified Water Generation and Distribution System – Compressed Air Generation and Distribution System – Plant Steam Boilers (2) and Distribution Piping – Hot Water Boilers (2) – Heat Exchanger #1 and Pump (heat exchange for HVAC reheat coils) – Heat Exchanger #2 and Pump (heat exchange for eyewash stations) – Emergency Power Generator – Building Management System – Waste Neutralization System – Air Handler #1 (services portion of second floor for both GTC and PPM, 3rd floor GTC) – Air Handler #5 (services machine room and waste neutralization, 1st floor) – Exhaust Fan #8 (services second floor offices GTC-PPM, and 3rd floor offices GTC) – Exhaust Fan #9 (services second floor labs GTC-PPM) – Exhaust Fan #12 (services machine room and waste neutralization, 1st floor) PPM shall be responsible for the repair, maintenance and replacement of the Shared Systems, which may include, without limitation, (all in PPM’s sole discretion), the following actions: maintaining preventative maintenance programs and contracts,
Sample 1Sample 2
AutoNDA by SimpleDocs
Shared Systems. In partial consideration of the payments made pursuant to Section 6.1 and to assist Exa in its utilization of the Framework Code and PowerVIZ Software, beginning on the Effective Date and for one (1) year thereafter, s+c agrees to provide Exa’s PowerVIZ Software development team at no additional charge with access to and use of the software and hardware systems it utilizes in connection with the Framework Code and PowerVIZ Software, including but not limited to (a) the FTP servers utilized by s+c in connection with the Framework Code and PowerVIZ Software; (b) s+c’s file servers on which the Framework Code and PowerVIZ Software Source Code is maintained and built; and (c) the RT system used by s+c to detect, track and fix bugs in the Framework Code and PowerVIZ Software; and (d) such other of s+c’s hardware or software necessary for the development and maintenance of the Framework Code and PowerVIZ Software by Exa. s+c shall work in good faith with Exa to set up secure network access for Exa’s PowerVIZ Software development team to Exa’s networked systems.
Sample 1
Shared Systems. Landlord and Tenant understand that certain components of the mechanical infrastructure serving the Premises, such as portions of the HVAC system and compressed air system, are shared with the currently unoccupied Suite 100. As part of any lease negotiation for Xxxxx 000, Xxxxxxxx will make commercially reasonable efforts to make sure that the mechanical needs of any potential tenant for Suite 100 will not interfere with Tenant’s pro rata share of the existing mechanical system capacities, and will expand such systems at no cost to Tenant if required by any such outsized requirements of the Suite 100 tenant, as part of any lease agreement for the Suite 100 space.
Sample 1
Shared Systems. The water supply and wastewater treatment systems (“Water Systems”) serving the Park, including the Premises, are currently provided by the Maryland Environmental Service (“MES”). Tenant shall, throughout the Term of this Lease, receive all of Tenant’s Water Systems services, including operations and maintenance, from MES (or from such Water Systems provider that DNR or the State shall elect to replace MES at any time in the future), and Landlord and Tenant shall share the cost of operation and maintenance of such Water Systems on a pro rata basis, provided that MES (or such other Water Systems provider) can provide an adequate supply of water to the Premises. In the event that Tenant ever determines that the water supply is not adequate, Tenant shall be required to substantiate such determination to the satisfaction of Landlord.
Sample 1
Shared Systems. Any computer, accounting, administrative, -------------- telephone or other communications systems used by Seller (collectively, "Shared Systems"), or assets relating to the maintenance, operation or support of any Shared Systems, irrespective of whether such systems are physically located, in whole or in part, on any GBB Real Property; provided, however, that Seller shall allow Purchaser to use certain Shared Systems and shall provide certain transition support as set forth in the Transition Services Agreement (as defined in Section 5.9); or
Sample 1

Related to Shared Systems

  • Shared Services CUPE agrees to adopt a shared services model that will allow other Trusts to join the shared services model. The shared services office of the Trust is responsible for the services to support the administration of benefits for the members, and to assist in the delivery of benefits on a sustainable, efficient and cost effective basis recognizing the value of benefits to the members.

  • Shared roles The Parties will meet the requirements of Schedule E, Clause 26 of the IGA FFR, by ensuring that prior agreement is reached on the nature and content of any events, announcements, promotional material or publicity relating to activities under this Agreement, and that the roles of both Parties will be acknowledged and recognised appropriately.

  • Shared Facilities The Parties acknowledge and agree that certain of the Shared Facilities and Interconnection Facilities, and Seller’s rights and obligations under the Interconnection Agreement, may be subject to certain shared facilities and/or co-tenancy agreements to be entered into among Seller, the Transmission Provider, Seller’s Affiliates, and/or third parties pursuant to which certain Interconnection Facilities may be subject to joint ownership and shared maintenance and operation arrangements; provided, such agreements (i) shall permit Seller to perform or satisfy, and shall not purport to limit, its obligations hereunder, and (ii) provide for separate metering of the Facility.

  • Shared Transport The Shared Transport Network Element (“Shared Transport”) provides the collective interoffice transmission facilities shared by various Carriers (including Qwest) between end-office switches and between end-office switches and local tandem switches within the Local Calling Area. Shared Transport uses the existing routing tables resident in Qwest switches to carry the End User Customer’s originating and terminating local/extended area service interoffice Local traffic on the Qwest interoffice message trunk network. CLEC traffic will be carried on the same transmission facilities between end- office switches, between end-office switches and tandem switches and between tandem switches on the same network facilities that Qwest uses for its own traffic. Shared Transport does not include use of tandem switches or transport between tandem switches and end-office switches for Local Calls that originate from end users served by non- Qwest Telecommunications Carriers (“Carrier(s)”) which terminate to QLSP End Users.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CSTC chooses to subtend a Verizon access Tandem, CSTC’s NPA/NXX must be assigned by CSTC 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 CSTC 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 CSTC’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office CSTC 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 CSTC’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.

  • NETWORK INTERCONNECTION METHODS 3.1 The Interconnection provided herein may not be used solely for the purpose of originating a Party’s own interexchange traffic.

  • Infrastructure Infrastructure serves as the foundation and building blocks of an integrated IT solution. It is the hardware which supports Application Services (C.3.2) and IT Management Services (C.3.3); the software and services which enable that hardware to function; and the hardware, software, and services which allow for secure communication and interoperability between all business and application service components. Infrastructure services facilitate the development and maintenance of critical IT infrastructures required to support Federal government business operations. This section includes the technical framework components that make up integrated IT solutions. One or any combination of these components may be used to deliver IT solutions intended to perform a wide array of functions which allow agencies to deliver services to their customers (or users), whether internal or external, in an efficient and effective manner. Infrastructure includes hardware, software, licensing, technical support, and warranty services from third party sources, as well as technological refreshment and enhancements for that hardware and software. This section is aligned with the FEA/DoDEA Technical Reference Model (TRM) which describes these components using a vocabulary that is common throughout the entire Federal government. A detailed review of the TRM is provided in Section J, Attachment 5. Infrastructure includes complete life cycle support for all hardware, software, and services represented above, including planning, analysis, research and development, design, development, integration and testing, implementation, operations and maintenance, information assurance, and final disposition of these components. The services also include administration and help desk functions necessary to support the IT infrastructure (e.g., desktop support, network administration). Infrastructure components of an integrated IT solution can be categorized as follows:

  • Data shared with Subcontractors If DSHS Data provided under this Contract is to be shared with a subcontractor, the Contract with the subcontractor must include all of the data security provisions within this Contract and within any amendments, attachments, or exhibits within this Contract. If the Contractor cannot protect the Data as articulated within this Contract, then the contract with the sub- Contractor must be submitted to the DSHS Contact specified for this contract for review and approval.

  • Computer Equipment Recycling Program If this Contract is for the purchase or lease of computer equipment, then Contractor certifies that it is in compliance with Subchapter Y, Chapter 361 of the Texas Health and Safety Code related to the Computer Equipment Recycling Program and the Texas Commission on Environmental Quality rules in 30 TAC Chapter 328.

  • Verizon OSS Facilities Any gateways, interfaces, databases, facilities, equipment, software, or systems, used by Verizon to provide Verizon OSS Services to ICG.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!