DR System Validation Options Sample Clauses

DR System Validation Options. Validation testing will be performed to insure the 2 readiness and soundness of the standby environment. The monthly recurring fees will include the 3 number and type of activation tests per year, as defined in the Monthly Recurring Fees section of this 4 CONTRACTOR System Schedule. If additional Level 1 or 2 Activation Tests are required, there will be 5 an additional fee. 6 1) DR Solution Graceful switch over Activation - This test will use a graceful 7 switchover from COUNTY production environment to the DR system at the CTC and can be used to 8 validate the core components of the DR solution and the activation process. The graceful switchover 10 when the database is shutdown. Performing a graceful shutdown of the production database allows all 11 data to be completely written to the database. The environment at the CTC is activated, made available 12 to COUNTY, and tested. In this scenario, both databases are identical and no data is lost. To ensure 13 continued availability of the DR solution, a separate copy of the DR database will be created at CTC and 14 used for the test activation. End users will not be moved over to the DR environment for this test. When 15 all data has been transferred to CTC and the database can be opened, the source production environment 16 can be brought back up for end user access. 17 2) DR solution Activation - This test will be performed to validate the core 18 components of the DR solution and the activation process. These core components are the database and 19 the code warehouse for the back-end as well as the front-end systems. To ensure continued availability 20 of the DR solution, a separate copy of the DR database will be created at CTC and used for the test 21 activation. This level of activation testing does not require a down-time for the source production 22 environment and will not affect end users in any way. In the event COUNTY and CONTRACTOR 23 identify issues during the test activation that warrant a re-test, COUNTY and CONTRACTOR will work 24 together to reschedule an additional test activation. If the cause of the testing failure is the fault of 25 CONTRACTOR, the subsequent retesting event will be performed at no additional fees. If the cause of 26 the testing failure is not due to the fault of CONTRACTOR, COUNTY can request a subsequent 27 retesting event for $3,000.
Sample 1
AutoNDA by SimpleDocs

Related to DR System Validation Options

  • License Types (a) A Team License shall mean a subscription license that provides a limited number of licenses to a set amount of developers for a named Customer. Customer must procure enough active licenses for each individual who has Programmatic Access. A Team License only grants rights to a named Customer and does not extend any right, in any form, to any parent or subsidiary company of Customer. A Team License cannot be used as a floating license. (b) A Project License shall mean a subscription license which covers one named Customer application. The license fees are based on the total number of developers working on a named project, regardless of whether such developers are directly using the Licensed Product. For the purposes of pricing and license administration, a “Project Group” is deemed to be a distinct Customer software team within a Customer’s business unit that works towards a distinct business purpose for the benefit of a single application. Customer is required to identify the name of each such Project Group to Syncfusion; such name must be unambiguous in nature. It is acknowledged and agreed by Customer that each identified Project Group shall exist for a valid business purpose and not just as a means for consolidating software licenses to minimize license fees that are otherwise due. If, in the sole opinion of Syncfusion, multiple Customer teams would each individually meet the above definition of a Project Group, such multiple teams shall not be combined for the purpose of consolidating licenses under a single Project Group. Customer is responsible for providing information about each such Project Group to Syncfusion. By entering into this Agreement, Customer represents that after the effective date, it will not withhold information that Syncfusion requires to properly license each such Project Group, and further agrees that any misrepresentation in this regard constitutes a material breach of this Agreement. (c) A Division License shall mean a subscription license which will cover one named Division and allow for development work on more than one project within such Division. A Division shall mean a business unit within Customer’s organization that works towards a distinct business purpose. Customer is required to identify the name of such Division to Syncfusion; such name must be unambiguous in nature. License fee determinations will be at the sole discretion of Syncfusion and be based on such factors including, but not limited to, Customer’s Division size, developer count, and the scope of the Division’s business purpose. By entering into this Agreement, Customer acknowledges that it is responsible for providing information about the named Customer Division to Syncfusion sufficient for Syncfusion to price the Division License, and Customer represents that it will not withhold information that Syncfusion requires to properly license each such named Customer division, and further agrees that any misrepresentation in this regard constitutes a material breach of this Agreement. (d) A Global License shall mean a subscription license for all development for a named Customer, where the license fees are based on the overall size of a named Customer. A Global License only grants rights to a named Customer and does not extend any right, in any form, to any parent or subsidiary company of Customer. (e) A Retail License shall mean a single named user, non-transferable license to use the Licensed Product. Retail Licenses will only made available to Customers in Syncfusion’s sole discretion and only when the number of such End-Users is finite and readily ascertainable. Accordingly, Syncfusion will make a determination as to whether or not the provision of Retail Licenses is appropriate under the circumstances applicable to any given Customer, and Syncfusion reserves the right, in its sole discretion, to refuse to make available Retail Licenses to a Customer and instead require a given Customer to procure a Project License, Division License, or Global License as circumstances dictate. A Retail License only grants rights to a named Customer and does not extend any right, in any form, to any parent or subsidiary company of Customer.

  • System Upgrade Facilities and System Deliverability Upgrades Connecting Transmission Owner shall design, procure, construct, install, and own the System Upgrade Facilities and System Deliverability Upgrades described in Appendix A hereto. The responsibility of the Developer for costs related to System Upgrade Facilities and System Deliverability Upgrades shall be determined in accordance with the provisions of Attachment S to the NYISO OATT.

  • Commencement and Completion of Work The professional services to be performed pursuant to this Agreement shall commence within five (5) days from the Effective Date of this Agreement. Failure to commence work in a timely manner and/or diligently pursue work to completion may be grounds for termination of this Agreement.

  • Stop Work Orders A. The JBE may, at any time, by Notice to Contractor, require Contractor to stop all or any part of the Services for a period up to ninety (90) days after the Notice is delivered to Contractor, and for any further period to which the parties may agree (“Stop Work Order”). The Stop Work Order shall be specifically identified as such and shall indicate it is issued under this provision. Upon receipt of the Stop Work Order, Contractor shall immediately comply with its terms and take all reasonable steps to minimize the incurrence of costs allocable to the Services covered by the Stop Work Order during the period of stoppage. Within ninety (90) days after a Stop Work Order is delivered to Contractor, or within any extension of that period to which the parties shall have agreed, the JBE shall either (i) cancel the Stop Work Order; or (ii) terminate the Services covered by the Stop Work Order as provided for in this Agreement. B. If a Stop Work Order issued under this provision is canceled or the period of the Stop Work Order or any extension thereof expires, Contractor shall resume the performance of Services. The JBE shall make an equitable adjustment in the delivery schedule, the Contract Amount, or both, and the Agreement shall be modified, in writing, accordingly, if: i. The Stop Work Order results in an increase in the time required for, or in Contractor’s cost properly allocable to the performance of any part of this Agreement; and ii. Contractor requests an equitable adjustment within thirty (30) days after the end of the period of stoppage; however, if the JBE decides the facts justify the action, the JBE may receive and act upon a proposal submitted at any time before final payment under this Agreement. C. The JBE shall not be liable to Contractor for loss of profits because of a Stop Work Order issued under this provision.

  • COMMENCEMENT OF WORK UNDER A SOW AGREEMENT Commencement of work as a result of the SOW-RFP process shall be initiated only upon issuance of a fully executed SOW Agreement and Purchase Order.

  • Commencement of Work Engineer shall not commence any field work under this Contract until he/she/it has obtained all required insurance and such insurance has been approved by County. As further set out below, Engineer shall not allow any subcontractor/subconsultant(s) to commence work to be performed in connection with this Contract until all required insurance has been obtained and approved and such approval shall not be unreasonably withheld. Approval of the insurance by County shall not relieve or decrease the liability of Engineer hereunder.

  • License Terms This license is for one full Semester. It cannot be cancelled or terminated except under the conditions cited in this license.

  • Service Terms Each Service Order will provide for a service term. At the end of the service term of any Service Order, unless either party gives written notice to the other party of its intention not to renew at least ninety (90) days before the end of a service term, the term of such Service Order will automatically renew for successive twelve (12) month periods. Termination of one Service Order will not affect the term of any other Service Order.

  • License Type Your license to a Product will be under a Named User or CPU license type, as specified on an order. Each Named User license to a Product entitles a Named User to access and use that Product in one production environment and up to two non-production environments. Each CPU license to a Product entitles you to assign the Product to a single CPU in one production environment and up to two non-production environments, for use in support of an unspecified number of Named Users.

  • Selection of Subcontractors, Procurement of Materials and Leasing of Equipment The contractor shall not discriminate on the grounds of race, color, religion, sex, national origin, age or disability in the selection and retention of subcontractors, including procurement of materials and leases of equipment. The contractor shall take all necessary and reasonable steps to ensure nondiscrimination in the administration of this contract. a. The contractor shall notify all potential subcontractors and suppliers and lessors of their EEO obligations under this contract. b. The contractor will use good faith efforts to ensure subcontractor compliance with their EEO obligations.

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