DNS Service TLD Zone Contents 1.1. Apex SOA record 1.2. Apex NS records and in-‐bailiwick glue for the TLD’s DNS servers 1.3. NS records and in-‐bailiwick glue for DNS servers of registered names in the TLD
Continuous Service The Parties shall continue providing services to each other during the pendency of any dispute resolution procedure, and the Parties shall continue to perform their obligations (including making payments in accordance with Article IV, Section 4) in accordance with this Agreement.
Consultants’ Services All consultants’ services required for the Project and to be financed out of the proceeds of the Financing shall be procured in accordance with the requirements set forth or referred to in Sections I and IV of the Consultant Guidelines, and with the provisions of this Section.
DNS service availability Refers to the ability of the group of listed-‐as-‐authoritative name servers of a particular domain name (e.g., a TLD), to answer DNS queries from DNS probes. For the service to be considered available at a particular moment, at least, two of the delegated name servers registered in the DNS must have successful results from “DNS tests” to each of their public-‐DNS registered “IP addresses” to which the name server resolves. If 51% or more of the DNS testing probes see the service as unavailable during a given time, the DNS service will be considered unavailable.
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.
CLOUD SERVICE The Cloud Service offering, is described below and is specified in an Order Document for the selected entitled offerings. The Order Document will consist of the Quotation that is provided and the Proof of Entitlement (XxX) you will receive confirming the start date and term of the Cloud Services and when invoicing will commence.
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.
Employment Deemed Continuous The service of an employee who is absent from work in accordance with this article shall be considered continuous for the purpose of Articles 18 (Vacation Entitlement) and 25 (Health Care Plans). The Employer shall continue to make payments to Health and Welfare Plans, in the same manner as if the employee were not absent where the employee elects to pay his or her share of the cost of the plans.
Termination of Continuous Service Except as otherwise provided in this Section 3, the unvested portion of the award shall be forfeited as of the date (the “Termination Date”) that the Grantee actually ceases to provide services to the Company or any Affiliate in any capacity of Employee, Director or Consultant (irrespective of whether the Grantee continues to receive severance or any other continuation payments or benefits after such date) (such cessation of the provision of services by Grantee being referred to as “Service Termination”). A Service Termination shall not occur and Continuous Service shall not be considered interrupted in the case of (i) any approved leave of absence, (ii) transfers among the Company, any Subsidiary or Affiliate, or any successor, in any capacity of Employee, Director or Consultant, or (iii) any change in status as long as the individual remains in the service of the Company or a Subsidiary or Affiliate in any capacity of Employee, Director or Consultant.
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 xxxxx://xxx.xxxxxxxxx.xxx/about- us/compliance, and in the event of any change in our status, will comply with applicable notice requirements.