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.
Implementation Schedule TIME IS OF THE ESSENCE with regard to all dates and time periods set forth and/or incorporated herein. Any material modification or deviation from an approved schedule described in this Agreement shall occur only upon approval of the City and RDA, with any such approvals required to be in writing as an amendment to this Agreement, and which approvals shall not be unreasonably withheld. City shall cooperate and act promptly with respect to any and all permits or approvals necessary for completion of the Project. Notwithstanding the above, this Agreement shall not limit the discretion of the City, or any of its duly appointed and authorized governing bodies, boards or entities, in approving or rejecting any aspect of the Project or improvements contemplated on or about the Property.
Escrow Format Specification 3.1. Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.
Supplemental JBoss Software Conditions Software Access and Software Maintenance for Supplemental JBoss Software is intended and available for Development Purposes only and for up to 25 users for each 16 Core Band Subscription of Red Hat JBoss Middleware Software that you purchased. If you deploy or use the Supplemental JBoss Software for Production Purposes or for more than 25 users, you agree to purchase the appropriate Software Subscriptions for each Unit that you deploy or use. Red Hat’s Open Source Assurance Program applies only to the Red Hat JBoss Middleware Software Subscription that you purchased (such as Red Hat JBoss Enterprise Application Platform in the example above) and does not apply to Supplemental JBoss Software. JBoss xPaaS Subscriptions (defined below) are not considered Supplemental JBoss Software. Each installation and use of JBoss xPaaS Subscriptions Software for either Development Purposes or Production Purposes is a Unit and requires a paid Software Subscription.
Implementation Specifications 1. The accounting shall contain the date, nature, and purpose of such disclosures, and the name and address of the person or agency to whom the disclosure is made.
Effect of Addenda, Bulletins, and Change Orders No special implication, interpretation, construction, connotation, denotation, import, or meaning shall be assigned to any provision of the Contract Documents because of changes created by the issuance of any (1) Addendum, (2) Bulletin, or (3) Change Order other than the precise meaning that the Contract Documents would have had if the provision thus created had read originally as it reads subsequent to the (1) Addendum, (2) Bulletin, or (3) Change Order by which it was created.
Specification and Service Levels The Specification sets out the Services that the Contractor has undertaken to provide. The Specification includes Service Levels setting out particular levels of service that the Contractor has undertaken to meet.
Change Order Formats Formats for Lump Sum Change Orders and for Change Orders based upon either a force account or upon unit pricing with an indeterminate number of units are in Section 7, Forms.
Penalties for Non-compliance to Service Level Agreement Where the Supplier/Service Provider fails to deliver the Goods/Services within the agreed and accepted milestone timelines and provided that the cause of the delay was not due to a fault of Transnet, penalties shall be imposed at …………………………………………………… .
Attachment A, Scope of Services The scope of services is amended as follows:
