System Maintenance The Trust understands that USBFS will perform periodic maintenance to the System(s), which may cause temporary service interruptions. To the extent possible, USBFS shall notify the Trust of all planned outages and will perform any necessary maintenance during non-business hours.
Road Maintenance Purchaser shall maintain roads, commensurate with Purchaser’s use, in accor- dance with Road Maintenance Requirements in C5.31 and the Road Maintenance Specifications. Performance of road maintenance work by Purchaser may be required prior to, during, or after each period of use. The timing of work accomplishment shall be based on Purchaser’s Op- erating Schedule under B6.31.
Bulk Registration Data Access to Icann Periodic Access to Thin Registration Data. In order to verify and ensure the operational stability of Registry Services as well as to facilitate compliance checks on accredited registrars, Registry Operator will provide ICANN on a weekly basis (the day to be designated by ICANN) with up-to-date Registration Data as specified below. Data will include data committed as of 00:00:00 UTC on the day previous to the one designated for retrieval by ICANN.
Operation and Maintenance 17.1 O&M obligations of the Concessionaire
17.1.1 During the Operation Period, the Concessionaire shall operate and maintain the Bus Terminal in accordance with this Agreement either by itself, or through the O&M Contractor and if required, modify, repair or otherwise make improvements to the Bus Terminal to comply with the provisions of this Agreement, Applicable Laws and Applicable Permits, and conform to Specifications and Standards and Good Industry Practice. The obligations of the Concessionaire hereunder shall include:
(a) permitting safe, smooth and uninterrupted flow of traffic on the Bus Terminal during normal operating conditions. Buses of other state road transport corporations shall be parked inside the Bus Terminal for which no charges shall be payable to the Concessionaire and if any charges are applicable for such parking then it shall be realized by Authority only;
(b) minimising incidents affecting the safety and use of the Bus Terminal by providing a rapid and effective response and maintaining liaison with emergency services of the State;
(c) carrying out periodic preventive maintenance of the Bus Terminal;
(d) undertaking routine maintenance including prompt repairs of ticket counters, Workshops, Authority's Office and other infrastructure as mentioned in the Operation and Maintenance Schedule;
(e) undertaking major maintenance such as per the Maintenance Schedule of the major infrastructure in the Bus Terminal;
(f) preventing, with the assistance of the concerned law enforcement agencies, any encroachments on the Bus Terminal;
(g) protection of the environment and provision of equipment and materials therefor;
(h) operation and maintenance of all communication, control and administrative systems necessary for the efficient operation of the Bus Terminal;
(i) maintaining a public relations unit to interface with and attend to suggestions from the Users, passengers, government agencies, media and other agencies;
(j) complying with Safety Requirements in accordance with Article 18;
(k) operation and maintenance of all Project Assets diligently and efficiently and in accordance with Good Industry Practice;
(l) maintaining punctuality and reliability in operating the Bus Terminal; and
(m) maintaining a high standard of cleanliness and hygiene in the Bus Terminal.
17.1.2 The Concessionaire shall remove promptly from the Bus Terminal all surplus construction machinery and materials, waste materials (including hazardous materials and waste water), rubbish and other debris (including, without limitation, accident debris) and keep the Bus Terminal in a clean, tidy and orderly condition,
Registration Data Directory Services Until ICANN requires a different protocol, Registry Operator will operate a WHOIS service available via port 43 in accordance with XXX 0000, and a web-‐based Directory Service at <whois.nic.TLD> providing free public query-‐based access to at least the following elements in the following format. ICANN reserves the right to specify alternative formats and protocols, and upon such specification, the Registry Operator will implement such alternative specification as soon as reasonably practicable. Registry Operator shall implement a new standard supporting access to domain name registration data (SAC 051) no later than one hundred thirty-‐five (135) days after it is requested by ICANN if: 1) the IETF produces a standard (i.e., it is published, at least, as a Proposed Standard RFC as specified in RFC 2026); and 2) its implementation is commercially reasonable in the context of the overall operation of the registry.
1.1. The format of responses shall follow a semi-‐free text format outline below, followed by a blank line and a legal disclaimer specifying the rights of Registry Operator, and of the user querying the database.
1.2. Each data object shall be represented as a set of key/value pairs, with lines beginning with keys, followed by a colon and a space as delimiters, followed by the value.
1.3. For fields where more than one value exists, multiple key/value pairs with the same key shall be allowed (for example to list multiple name servers). The first key/value pair after a blank line should be considered the start of a new record, and should be considered as identifying that record, and is used to group data, such as hostnames and IP addresses, or a domain name and registrant information, together.
1.4. The fields specified below set forth the minimum output requirements. Registry Operator may output data fields in addition to those specified below, subject to approval by ICANN, which approval shall not be unreasonably withheld.
Maintenance and Support Services If this Agreement is for IT goods or services, this section applies: Unless otherwise specified in this Agreement: The Contractor shall promptly provide the Court with all Upgrades, including without limitation: (i) all Upgrades generally made available by Contractor to its other customers; (ii) Upgrades as necessary so that the Work complies with the Specifications and Applicable Law (including changes in Applicable Law); (iii) Upgrades as necessary so that the Work operates under new versions or releases of the Court’s operating system or database platform; and (iv) all on-site services necessary for installation of Upgrades. Without limiting any other obligation of Contractor under this Agreement, Contractor represents and warrants that it will maintain services, equipment, software or any other part of the Work so that they operate in accordance with their Specifications and Documentation; and The Contractor shall respond to the Court within four (4) hours after the Court reports a Technical Support Incident (such hours all occurring during Standard M&S Hours) to Contractor. DELIVERY, ACCEPTANCE, AND PAYMENT Delivery. Contractor shall deliver to the Court the Deliverables in accordance with this Agreement, including the Statement of Work. Unless otherwise specified by this Agreement, Contractor will deliver all goods purchased by the Court “Free on Board Destination Freight Prepaid” to the Court at the address and location specified by the Court. Title to all goods purchased by the Court vests in the Court upon payment of the applicable purchase price. Contractor will bear the risk of loss for any Work being delivered until received by the Court at the proper location. All shipments by Contractor or its Subcontractors must include packing sheets identifying: this Agreement number, the Court’s purchase order number, item number, quantity and unit of measure, part number and description of the goods shipped, and appropriate evidence of inspection, if required. Goods for different Agreements shall be listed on separate packing sheets.
Information Systems Acquisition Development and Maintenance a. Client Data – Client Data will only be used by State Street for the purposes specified in this Agreement.
Periodic Access to Thin Registration Data In order to verify and ensure the operational stability of Registry Services as well as to facilitate compliance checks on accredited registrars, Registry Operator will provide ICANN on a weekly basis (the day to be designated by ICANN) with up-‐to-‐date Registration Data as specified below. Data will include data committed as of 00:00:00 UTC on the day previous to the one designated for retrieval by ICANN.
Record Maintenance and Retention A. Grantee shall keep and maintain under GAAP or GASB, as applicable, full, true, and complete records necessary to fully disclose to the System Agency, the Texas State Auditor’s Office, the United States Government, and their authorized representatives sufficient information to determine compliance with the terms and conditions of this Grant Agreement and all state and federal rules, regulations, and statutes.
B. Grantee shall maintain and retain legible copies of this Grant Agreement and all records relating to the performance of the Grant Agreement, including supporting fiscal documents adequate to ensure that claims for grant funds are in accordance with applicable State of Texas requirements. These records shall be maintained and retained by the Grantee for a minimum of seven (7) years after the Grant Agreement expiration date or seven (7) years after all audits, claims, litigation or disputes involving the Grant Agreement are resolved, whichever is later.
Covenant to Provide Financial Information and Maintain Sufficient Capital The Administrator shall obtain and maintain the necessary capital to fulfill its obligations under this Agreement and shall remain solvent. The Administrator will report to the Issuer on a semi-annual basis its current and total assets, current and total liabilities, and total equity and the Company intends to include such amounts in its SEC reports.
