Installation Plan and Timeline Support Sample Clauses

Installation Plan and Timeline Support. The Contractor shall deliver an initial report detailing a plan for infrastructure installation, and any issues with implementation of their solution along with recommended mitigations. Included in this Plan is addressing what parts need to be compliant in order to achieve the Authority to Operate (ATO) milestone. A final version of the report shall be delivered. While developing the report, the Contractor will meet with and formally present any discovered risks to the Contracting Officer’s Representative (COR) and immediately work with the COR to rapidly resolve any known risks to a successful physical implementation for the DoD facility. Having been informed of all identified issues, the COR may choose to accept some risks and proceed with the installation. Installation of at least one site shall be completed no later than prescribed by the task order after contract award and a second site or more no later than prescribed by the task order after contract award.
AutoNDA by SimpleDocs

Related to Installation Plan and Timeline Support

  • Technical Specification As enumerated in Special Conditions of Contract/Scope of Work/attached Drawing/ Details/Schedule of Rates.

  • Technical Specifications The Technical Specifications furnished on the CD are intended to establish the standards for quality, performance and technical requirements for all labor, workmanship, material, methods and equipment necessary to complete the Work. When specifications and drawings are provided or referenced by the County, these are to be considered part of the Scope of Work, and to be specifically documented in the Detailed Scope of Work. For convenience, the County supplied specifications, if any, and the Technical Specifications furnished on the CD.

  • Technical Specifications and Drawings a) The Goods and Related Services supplied under this Contract shall conform to the technical specifications and standards mentioned in Section VI, Schedule of Requirements and, when no applicable standard is mentioned, the standard shall be equivalent or superior to the official standards whose application is appropriate to the Goods' country of origin.

  • TECHNICAL TASKS Products that require a draft version are indicated by marking “(draft and final)” after the product name in the “Products” section of the task/subtask. If “(draft and final)” does not appear after the product name, only a final version of the product is required. Subtask 1.1 (Products) describes the procedure for submitting products to the CAM.

  • Installation Services 3.1 The Bitstream 2a Service includes a Standard Install as set out below (in each case to the extent that the relevant provisioning works are not already complete for the relevant Service Order).1

  • All new supplies equipment and services shall include manufacturer's minimum standard warranty unless otherwise agreed to in writing. Vendor shall be legally permitted to sell all products offered for sale to TIPS Members. All goods proposed and sold shall be new unless clearly stated in writing. Customer Support The Vendor shall provide timely and accurate customer support for orders to TIPS Members as agreed by the Parties. Vendors shall respond to such requests within a commercially reasonable time after receipt of the request. If support andƒor training is a line item sold or packaged with a sale, support shall be as agreed with the TIPS Member. Agreements Agreements for purchase will normally be put into effect by means of a purchase order(s) executed by authorized agents of the TIPS Member participating government entities, but other means of placing an order may be used at the Member’s discretion. Tax exempt status Most TIPS Members are tax exempt and the related laws andƒor regulations of the controlling jurisdiction(s) of the TIPS Member shall apply. Assignments of Agreements No assignment of Agreement may be made without the prior notification of TIPS. Written approval of TIPS shall not be unreasonably withheld. Payment for delivered goods and services can only be made to the awarded Vendor, Vendor designated reseller or vendor assigned company.

  • 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.

  • 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.

  • Statement of Work The Contractor shall provide the services and staff, and otherwise do all things necessary for or incidental to the performance of work, as set forth below:

  • 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.

Time is Money Join Law Insider Premium to draft better contracts faster.