Subfactor 3 Transition Task Order Sample Clauses

Subfactor 3 Transition Task Order 
AutoNDA by SimpleDocs

Related to Subfactor 3 Transition Task Order

  • Detailed Description of Services / Statement of Work Describe fully the services that Contractor will provide, or add and attach Exhibit B to this Agreement.

  • PRICING for Markup of Non-Prepriced Items in RS Means Unit Price Book What is your proposed Markup Percentage on materials not found in the RS Means Price Book? If any materials being utilized for a project cannot be found in the RS Means Price Book, this question is what is the markup percentage on those materials? When answering this question please insert the number that represents your percentage of proposed markup. Example: if you are proposing a 30 percent markup, please insert the number "30". Remember that this is a ceiling markup. You may markup a lesser percentage to the TIPS Member customer when pricing the project, but not a greater percentage. EXAMPLE: You need special materials that are not in the RS Means Unit Price Book for a project. You would buy the materials and mark them up to the TIPS Member customer by the percentage you propose in this question. If the materials cost you, the contractor, $100 and you proposed a markup on this question for the material of 30 percent, then you would charge the TIPS Member customer $130 for the materials.

  • DISTRIBUTION OF CONTRACTOR PRICE LIST AND CONTRACT APPENDICES Contractor shall provide Authorized Users with electronic copies of the Contract, including price lists and Appendices, upon request. OGS CENTRALIZED CONTRACT MODIFICATIONS Contract Updates will be handled as provided in Appendix C – Contract Modification Procedures.

  • Task Order X19.5 The Contractor submits a Task Order programme to the Service Manager within 2 days of receiving the Task Order Z The additional conditions of contract are Z1 to Z11 always apply. Z1 Cession delegation and assignment

  • Selection Criteria for Awarding Task Order The Government will award to the offeror whose proposal is deemed most advantageous to the Government based upon an integrated assessment using the evaluation criteria. The Government will evaluate proposals against established selection criteria specified in the task order RFP. Generally, the Government's award decision will be based on selection criteria which addresses past performance, technical acceptability, proposal risk and cost. Among other sources, evaluation of past performance may be based on past performance assessments provided by TO Program Managers on individual task orders performed throughout the life of the contract. The order of importance for the factors will be identified in the RFP for the specified task order.

  • Contract Task Order A-E shall be assigned work via a task order by COUNTY which shall subsequently be referred to as the “Contract Task Order” (hereinafter “CTO”). A CTO for each project shall be developed by A-E in conjunction with COUNTY Project Management staff. The COUNTY Project Manager shall manage all A-E’s work including monitoring the CTO work schedule, quality of deliverables, review of invoiced amounts, adherence to set budget, and internal review of submittal packages. A-E shall follow all requirements as outlined in the CTO; this general Scope of Work, the project specific Scope Statement, and the Architect-Engineer Guide (Rev July 2018). The CTO shall include a detailed Scope Statement, describing tasks to be performed with a specific list of deliverables for each task, schedule of work and cost to complete the work. The schedule of work shall allow enough time for meetings with COUNTY Management staff to review the work progress, provide technical and policy direction, resolve problems and ensure adherence to the work completion schedule. The CTO shall include a cover sheet provided by COUNTY Project Management staff with the appropriate signature blocks and contract information. Once both Parties agree, and all Parties have signed the CTO, COUNTY Management staff shall provide A-E with a Notice to Proceed (NTP) to begin work. A-E shall submit all plans, reports and other documents produced under the CTO to the assigned COUNTY Project Manager within the timeframe indicated in the CTO or as directed by COUNTY Project Management staff.

  • MSAA Indicator Technical Specification Document This Agreement shall be interpreted with reference to the MSAA Indicator Technical Specifications document.

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

  • Transition Plan In the event of termination by the LHIN pursuant to this section, the LHIN and the HSP will develop a Transition Plan. The HSP agrees that it will take all actions, and provide all information, required by the LHIN to facilitate the transition of the HSP’s clients.

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