AVEVA’s Server Sample Clauses

AVEVA’s Server. Software and data are stored and accessed by Customer via AVEVA’s servers. The Type B license does not cover the installation of the Software and/or data on Customer’s servers or any desktop or laptop computer, or Customer’s use of the Software via an intranet hosted service. Customer will be allowed to access and use the Software and Documentation on AVEVA’s servers via the internet.

Related to AVEVA’s Server

  • SaaS Services 6.1 Our SaaS Services are audited at least yearly in accordance with the AICPA’s Statement on Standards for Attestation Engagements (“SSAE”) No. 18. We have attained, and will maintain, SOC 1 and SOC 2 compliance, or its equivalent, for so long as you are timely paying for SaaS Services. Upon execution of a mutually agreeable Non-Disclosure Agreement (“NDA”), we will provide you with a summary of our compliance report(s) or its equivalent. Every year thereafter, for so long as the NDA is in effect and in which you make a written request, we will provide that same information. 6.2 You will be hosted on shared hardware in a Tyler data center or in a third-party data center. In either event, databases containing your Data will be dedicated to you and inaccessible to our other customers. 6.3 Our Tyler data centers have fully-redundant telecommunications access, electrical power, and the required hardware to provide access to the Tyler Software in the event of a disaster or component failure. In the event any of your Data has been lost or damaged due to an act or omission of Tyler or its subcontractors or due to a defect in Tyler’s software, we will use best commercial efforts to restore all the Data on servers in accordance with the architectural design’s capabilities and with the goal of minimizing any Data loss as greatly as possible. In no case shall the recovery point objective (“RPO”) exceed a maximum of twenty-four (24) hours from declaration of disaster. For purposes of this subsection, RPO represents the maximum tolerable period during which your Data may be lost, measured in relation to a disaster we declare, said declaration will not be unreasonably withheld. 6.4 In the event we declare a disaster, our Recovery Time Objective (“RTO”) is twenty-four (24) hours. For purposes of this subsection, RTO represents the amount of time, after we declare a disaster, within which your access to the Tyler Software must be restored. 6.5 We conduct annual penetration testing of either the production network and/or web application to be performed. We will maintain industry standard intrusion detection and prevention systems to monitor malicious activity in the network and to log and block any such activity. We will provide you with a written or electronic record of the actions taken by us in the event that any unauthorized access to your database(s) is detected as a result of our security protocols. We will undertake an additional security audit, on terms and timing to be mutually agreed to by the parties, at your written request. You may not attempt to bypass or subvert security restrictions in the SaaS Services or environments related to the Tyler Software. Unauthorized attempts to access files, passwords or other confidential information, and unauthorized vulnerability and penetration test scanning of our network and systems (hosted or otherwise) is prohibited without the prior written approval of our IT Security Officer. 6.6 We test our disaster recovery plan on an annual basis. Our standard test is not client-specific. Should you request a client-specific disaster recovery test, we will work with you to schedule and execute such a test on a mutually agreeable schedule. At your written request, we will provide test results to you within a commercially reasonable timeframe after receipt of the request. 6.7 We will be responsible for importing back-up and verifying that you can log-in. You will be responsible for running reports and testing critical processes to verify the returned Data. 6.8 We provide secure Data transmission paths between each of your workstations and our servers. 6.9 Tyler data centers are accessible only by authorized personnel with a unique key entry. All other visitors to Tyler data centers must be signed in and accompanied by authorized personnel. Entry attempts to the data center are regularly audited by internal staff and external auditors to ensure no unauthorized access. 6.10 Where applicable with respect to our applications that take or process card payment data, we are responsible for the security of cardholder data that we possess, including functions relating to storing, processing, and transmitting of the cardholder data and affirm that, as of the Effective Date, we comply with applicable requirements to be considered PCI DSS compliant and have performed the necessary steps to validate compliance with the PCI DSS. We agree to supply the current status of our PCI DSS compliance program in the form of an official Attestation of Compliance, which can be found at ▇▇▇▇▇://▇▇▇.▇▇▇▇▇▇▇▇▇.▇▇▇/about- us/compliance, and in the event of any change in our status, will comply with applicable notice requirements.

  • Mobile Gas Service Corp 350 U.S. 332 (1956) and Federal Power Commission v. Sierra Pacific Power Co., 350 U.S. 348 (1956) , and clarified by ▇▇▇▇▇▇ ▇▇▇▇▇▇▇ Capital Group, Inc. v.

  • Verizon OSS Services 8.2.1 Upon request by PNG, Verizon shall provide to PNG Verizon OSS Services. Such Verizon OSS Services will be provided in accordance with, but only to the extent required by, Applicable Law. 8.2.2 Subject to the requirements of Applicable Law, Verizon Operations Support Systems, Verizon Operations Support Systems functions, Verizon OSS Facilities, Verizon OSS Information, and the Verizon OSS Services that will be offered by Verizon, shall be as determined by Verizon. Subject to the requirements of Applicable Law, Verizon shall have the right to change Verizon Operations Support Systems, Verizon Operations Support Systems functions, Verizon OSS Facilities, Verizon OSS Information, and the Verizon OSS Services, from time-to-time, without the consent of PNG. 8.2.3 To the extent required by Applicable Law, in providing Verizon OSS Services to PNG, Verizon will comply with Verizon’s applicable OSS Change Management Guidelines, as such Guidelines are modified from time-to-time, including, but not limited to, the provisions of the Guidelines related to furnishing notice of changes in Verizon OSS Services. Verizon’s OSS Change Management Guidelines will be set out on a Verizon website.

  • Unbundled Network Terminating Wire (UNTW) 2.8.3.1 UNTW is unshielded twisted copper wiring that is used to extend circuits from an intra-building network cable terminal or from a building entrance terminal to an individual End User’s point of demarcation. It is the final portion of the Loop that in multi-subscriber configurations represents the point at which the network branches out to serve individual subscribers. 2.8.3.2 This element will be provided in MDUs and/or Multi-Tenants Units (MTUs) where either Party owns wiring all the way to the End User’s premises. Neither Party will provide this element in locations where the property owner provides its own wiring to the End User’s premises, where a third party owns the wiring to the End User’s premises.

  • ADS Services Up to U.S. $5.00 per 100 ADSs (or fraction thereof) held on the applicable record date(s) established by the Depositary. Person holding ADSs on the applicable record date(s) established by the Depositary.