Where the Esri Mobile Sample Clauses

Where the Esri Mobile. Lab equipment is utilized at Licensee's domestic site, the following terms apply: ▪ Upon receipt, Licensee must immediately report any damage to the Mobile Lab equipment to the Training Event Assistant. ▪ Licensee must keep the Mobile Lab equipment in a secure, locked area between training event sessions. ▪ Licensee must ensure that only registered Students use the Mobile Lab equipment. ▪ Licensee is responsible for any and all loss of, damage to, or theft of the Mobile Lab equipment while in Licensee's possession. ▪ Licensee warrants that it maintains sufficient insurance coverage to enable it to meet its obligations created by this Addendum and by law. ▪ The Esri instructor will check all Mobile Lab equipment following the completion of training. Any damage to the Mobile Lab equipment due to Student use, excluding normal wear and tear, will be brought to the attention of Licensee by written notice. Licensee hereby agrees to be financially responsible for any repair or replacement of equipment resulting from such damage. ▪ Licensee shall make the Mobile Lab equipment available for freight pickup immediately upon conclusion of the Esri training event.
Sample 1
AutoNDA by SimpleDocs

Related to Where the Esri Mobile

  • Agreement with Respect to Leased Data Processing Equipment (a) The Receiver hereby grants to the Assuming Bank an exclusive option for the period of ninety (90) days commencing the day after Bank Closing to accept an assignment from the Receiver of any or all Data Processing Leases to the extent that such Data Processing Leases can be assigned. (b) The Assuming Bank shall (i) give written notice to the Receiver within the option period specified in Section 4.7(a) of its intent to accept or decline an assignment or sublease of any or all Data Processing Leases and promptly accept an assignment or sublease of such Data Processing Leases, and (ii) give written notice to the appropriate lessor(s) that it has accepted an assignment or sublease of any such Data Processing Leases. (c) The Receiver agrees to facilitate the assignment or sublease of Data Processing Leases or the negotiation of new leases or license agreements by the Assuming Bank; provided, that neither the Receiver nor the Corporation shall be obligated to engage in litigation or make payments to the Assuming Bank or to any third party in connection with facilitating any such assumption, assignment, sublease or negotiation. (d) The Assuming Bank agrees, during its period of use of any property subject to a Data Processing Lease, to pay to the Receiver or to appropriate third parties at the direction of the Receiver all operating costs with respect thereto and to comply with all relevant terms of the applicable Data Processing Leases entered into by the Failed Bank, including without limitation the timely payment of all rent, taxes, fees, charges, utilities, insurance and assessments. (e) The Assuming Bank shall, not later than fifty (50) days after giving the notice provided in Section 4.7(b), (i) relinquish and release to the Receiver all property subject to the relevant Data Processing Lease, in the same condition as at Bank Closing, normal wear and tear excepted, or (ii) accept an assignment or a sublease thereof or negotiate a new lease or license agreement under this Section 4.7.

  • Data Mining 4.1. Provider agrees not to use GLO Data for unrelated commercial purposes, advertising or advertising-related services, or for any other purpose not explicitly authorized by the GLO in this Contract or any document related thereto. 4.2. Provider agrees to take all reasonably feasible physical, technical, administrative, and procedural measures to ensure that no unauthorized use of GLO Data occurs.

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes. 11.2 We may (i) compile statistical and other information related to the performance, operation and use of the Services, and (ii) use data from the Services in aggregated form for security and operations management, to create statistical analyses, and for research and development purposes (clauses i and ii are collectively referred to as “Service Analyses”). We may make Service Analyses publicly available; however, Service Analyses will not incorporate Your Content, Personal Data or Confidential Information in a form that could serve to identify You or any individual. We retain all intellectual property rights in Service Analyses. 11.3 We may provide You with the ability to obtain certain Oracle Software (as defined below) for use with the Services. If we provide Oracle Software to You and do not specify separate terms for such software, then such Oracle Software is provided as part of the Services and You have the non-exclusive, worldwide, limited right to use such Oracle Software, subject to the terms of this Agreement and Your order (except for separately licensed elements of the Oracle Software, which separately licensed elements are governed by the applicable separate terms), solely to facilitate Your use of the Services. You may allow Your Users to use the Oracle Software for this purpose, and You are responsible for their compliance with the license terms. Your right to use any Oracle Software will terminate upon the earlier of our notice (by web posting or otherwise) or the end of the Services associated with the Oracle Software. Notwithstanding the foregoing, if Oracle Software is licensed to You under separate terms, then Your use of such software is governed by the separate terms. Your right to use any part of the Oracle Software that is licensed under the separate terms is not restricted in any way by this Agreement.

  • Data Management Contractor will not use State data, including production data, for testing or development purposes unless authorized in writing by the State Chief Information Security Officer or delegate. Contractor will implement and maintain procedures to physically and logically segregate State data, unless otherwise explicitly authorized by the State Chief Information Security Officer or delegate.

  • TOOL STORAGE 1. A company shall provide on all construction jobs in towns and cities, and elsewhere where reasonably necessary and practicable (or if requested buy the employee), a suitable and secure waterproof lock-up solely for the purpose of storing employees’ tools, and on multi-storey and major projects the company shall provide, where possible, a suitable lock-up for employees’ tools within a reasonable distance of the work area of large groups of employees. 2. Where an employee is absent from work because of illness or accident and has advised the company in accordance with Clause 33 – Personal Leave of the award, the company shall ensure that the employee’s tools are securely stored during his/her absence.

  • Purchased Services During the term of this Collective Agreement, no regular employee will be declared surplus in his/her position as a result of the use of purchased services to perform the work normally performed by that employee.

  • Zone File Access Agreement Registry Operator will enter into an agreement with any Internet user, which will allow such user to access an Internet host server or servers designated by Registry Operator and download zone file data. The agreement will be standardized, facilitated and administered by a Centralized Zone Data Access Provider, which may be ICANN or an ICANN designee (the “CZDA Provider”). Registry Operator (optionally through the CZDA Provider) will provide access to zone file data per Section 2.1.3 of this Specification and do so using the file format described in Section 2.1.4 of this Specification. Notwithstanding the foregoing, (a) the CZDA Provider may reject the request for access of any user that does not satisfy the credentialing requirements in Section 2.1.2 below; (b) Registry Operator may reject the request for access of any user that does not provide correct or legitimate credentials under Section 2.1.2 below or where Registry Operator reasonably believes will violate the terms of Section 2.1.5. below; and, (c) Registry Operator may revoke access of any user if Registry Operator has evidence to support that the user has violated the terms of Section 2.1.5 below.

  • PROHIBITION ON CERTAIN TELECOMMUNICATIONS AND VIDEO SURVEILLANCE SERVICES OR EQUIPMENT To the extent applicable, Supplier certifies that during the term of this Contract it will comply with applicable requirements of 2 C.F.R. § 200.216.

  • Two-Way Interconnection Trunks 2.4.1 Where the Parties have agreed to use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and PCS, PCS shall order from Verizon, and Verizon shall provide, the Two-Way Interconnection Trunks and the Entrance Facility, on which such Trunks will ride, and transport and multiplexing, in accordance with the rates, terms and conditions set forth in this Agreement and Verizon’s applicable Tariffs. 2.4.2 Prior to ordering any Two-Way Interconnection Trunks from Verizon, PCS shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Interconnection Trunks and the interface specifications at the Point of Interconnection (POI). Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.3 Two-Way Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. 2.4.4 On a semi-annual basis, PCS shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that PCS anticipates Verizon will need to provide during the ensuing two (2) year period to carry traffic from PCS to Verizon and from Verizon to PCS. PCS’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centium Call Second (Hundred Call Second) equal to five (5). 2.4.8 Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.01 during the average time consistent busy hour. Verizon and PCS shall engineer Two-Way Interconnection Trunks using BOC Notes on the LEC Networks SR-TSV-002275. 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three

  • Data Processing Agreement The Data Processing Agreement, including the Approved Data Transfer Mechanisms (as defined in the Data Processing Agreement) that apply to your use of the Services and transfer of Personal Data, is incorporated into this Agreement by this reference. Each party will comply with the terms of the Data Processing Agreement and will train its employees on DP Law.

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