Technical Integration Changes and Outages
Technical Integration Changes and Outages Sample Clauses
Related to Technical Integration Changes and Outages
SYSTEM CHANGES AND MAINTENANCE/SUPPORT The Contractor shall give a minimum of 5 business days advance Written notice to the designated Authorized User contact of any upgrades, system changes and Maintenance/support actions that may potentially impact services described in the Authorized User Agreement. Upgrades, system changes, and Maintenance/support actions which are required by system vulnerabilities or emergency situations shall be carried out by the Contractor to protect the system. Authorized Users shall be notified by the Contractor as soon as possible after the change has taken place. Contractor shall provide documentation of upgrades, system changes and Maintenance/support actions upon request from an Authorized User. EXPIRATION, TERMINATION OR SUSPENSION OF SERVICES Return of Data The Contractor shall return Data in a format agreed upon within the Authorized User Agreement or as agreed to with the Authorized User. This can, if specified within the Authorized User Agreement, be carried out by providing application programmable interface or other such efficient electronic tools. The Contractor must certify all Data has been removed from its system and removed from backups within timeframes established in the Authorized User Agreement or as agreed to with the Authorized User. Suspension of Services During any period of suspension of service, the Authorized User shall have full access to all Data at no charge. This can, if specified within the Authorized User Agreement, be carried out by providing an application programmable interface or other such efficient electronic tools. The Contractor shall not take any action to erase and/or withhold any Authorized User Data, except as directed by the Authorized User. Expiration or Termination of Services Upon expiration or termination of an Authorized User Agreement, the Authorized User shall have full access to all Data for a period of 60 calendar days. Unless noted in the original Authorized User Agreement, this period will be covered at no charge. This can, if specified within the Authorized User Agreement, be carried out by providing application programmable interface or other such efficient electronic tools. During this period, the Contractor shall not take any action to erase and/or withhold any Data, except as directed by the Authorized User. An Authorized User shall have the right to specify a period in excess of 60 calendar days in its RFQ. SECURE DATA DISPOSAL When requested by the Authorized User, the Contractor shall destroy Data in all of its forms, including all back-ups. Data shall be permanently deleted and shall not be recoverable, according ITS Policy S13-003 Sanitization/Secure Disposal or successor and S14-003 Information Security Controls or successor. Certificates of destruction, in a form acceptable to the Authorized User, shall be provided by the Contractor to the Authorized User.
Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.
CHANGES TO PRODUCT OR SERVICE OFFERINGS a. Product or Service Discontinuance Where Contractor is the Product Manufacturer/Developer, and Contractor publicly announces to all U.S. customers (“date of notice”) that a Product is being withdrawn from the U.S. market or that maintenance service or technical support provided by Contractor (“withdrawn support”) is no longer going to be offered, Contractor shall be required to: (i) notify the Commissioner, each Licensee and each Authorized User then under contract for maintenance or technical support in writing of the intended discontinuance; and (ii) continue to offer Product or withdrawn support upon the Contract terms previously offered for the greater of: a) the best terms offered by Contractor to any other customer, or b) not less than twelve (12) months from the date of notice; and (iii) at Authorized User’s option, provided that the Authorized User is under contract for maintenance on the date of notice, either: provide the Authorized User with a Product replacement or migration path with at least equivalent functionality at no additional charge to enable Authorized User to continue use and maintenance of the Product. In the event that the Contractor is not the Product Manufacturer, Contractor shall be required to: (i) provide the notice required under the paragraph above, to the entities described within five (5) business days of Contractor receiving notice from the Product Manufacturer, and (ii) include in such notice the period of time from the date of notice that the Product Manufacturer will continue to provide Product or withdraw support. The provisions of this subdivision (a) shall not apply or eliminate Contractor’s obligations where withdrawn support is being provided by an independent Subcontractor. In the event that such Subcontractor ceases to provide service, Contractor shall be responsible for subcontracting such service, subject to state approval, to an alternate Subcontractor.
Changes to Scope of Work The City of Nashua may, at any time, by written order, make changes to the general scope, character, or cost of this contract and in the services or work to be performed, either increasing or decreasing the scope, character, or cost of Independent Contractor's performance under the contract. Independent Contractor shall provide to the City of Nashua within 10 calendar days, a written proposal for accomplishing the change. The proposal for a change shall provide enough detail, including personnel hours for each sub-task and cost breakdowns of tasks, for the City of Nashua to be able to adequately analyze the proposal. The City of Nashua will then determine in writing if Independent Contractor should proceed with any or all of the proposed change. If the change causes an increase or a decrease in Independent Contractor's cost or time required for performance of the contract as a whole, an equitable adjustment shall be made and the contract accordingly modified in writing. Any claim of Independent Contractor for adjustment under this clause shall be asserted in writing within 30 days of the date the City of Nashua notified Independent Contractor of the change. When Independent Contractor seeks changes, Independent Contractor shall, before any work commences, estimate their effect on the cost of the contract and on its schedule and notify the City of Nashua in writing of the estimate. The proposal for a change shall provide enough detail, including personnel hours for each sub-task and cost breakdowns of tasks, for the City of Nashua to be able to adequately analyze the proposal. The City of Nashua will then determine in writing if Independent Contractor should proceed with any or all of the proposed change. Except as provided in this paragraph, Independent Contractor shall implement no change unless the City of Nashua in writing approves the change. Unless otherwise agreed to in writing, the provisions of this contract shall apply to all changes. The City of Nashua may provide verbal approval of a change when the City of Nashua, in its sole discretion, determines that time is critical or public health and safety are of concern. Any verbal approval shall be confirmed in writing as soon as practicable. Any change undertaken without prior City of Nashua approval shall not be compensated and is, at the City of Nashua's election, sufficient reason for contract termination.
Notifications of Outages and Maintenance In the event that a Registry Operator plans maintenance, it will provide notice to the ICANN emergency operations department, at least, twenty-‐four (24) hours ahead of that maintenance. ICANN’s emergency operations department will note planned maintenance times, and suspend Emergency Escalation services for the monitored services during the expected maintenance outage period. If Registry Operator declares an outage, as per its contractual obligations with ICANN, on services under a service level agreement and performance requirements, it will notify the ICANN emergency operations department. During that declared outage, ICANN’s emergency operations department will note and suspend emergency escalation services for the monitored services involved.
Technical Standards Applicable to a Wind Generating Plant i. Low Voltage Ride-Through (LVRT) Capability A wind generating plant shall be able to remain online during voltage disturbances up to the time periods and associated voltage levels set forth in the standard below. The LVRT standard provides for a transition period standard and a post-transition period standard.
Purchase Order Flip via Ariba Network (AN) The online process allows suppliers to submit invoices via the AN for catalog and non- catalog goods and services. Contractors have the ability to create an invoice directly from their Inbox in their AN account by simply “flipping” the purchase order into an invoice. This option does not require any special software or technical capabilities. For the purposes of this section, the Contractor warrants and represents that it is authorized and empowered to and hereby grants the State and the third-party provider of MFMP the right and license to use, reproduce, transmit, distribute, and publicly display within the system the information outlined above. In addition, the Contractor warrants and represents that it is authorized and empowered to and hereby grants the State and the third-party provider the right and license to reproduce and display within the system the Contractor’s trademarks, system marks, logos, trade dress, or other branding designation that identifies the products made available by the Contractor under the Contract.
TECHNICAL SUPPORT AND MAINTENANCE If technical support and maintenance is a part of the Goods that Contractor provides under the Contract, Contractor will use commercially reasonable efforts to respond to the Department in a reasonable time when the Department makes technical support or maintenance requests regarding the Goods.
Technical Feasibility of String While ICANN has encouraged and will continue to encourage universal acceptance of all top-‐level domain strings across the Internet, certain top-‐level domain strings may encounter difficulty in acceptance by ISPs and webhosters and/or validation by web applications. Registry Operator shall be responsible for ensuring to its satisfaction the technical feasibility of the TLD string prior to entering into this Agreement.
Commingling of Resold Services with Unbundled Network Elements and Combinations of Unbundled Network Elements 6.7.1 To the extent it is Technically Feasible and pursuant to the terms of Section 9.1, CLEC may Commingle Telecommunications Services purchased on a resale basis with an Unbundled Network Element or combination of Unbundled Network Elements.
