REQUIREMENT FOR SEPARATE PRICE AND TECHNICAL PROPOSALS Sample Clauses

REQUIREMENT FOR SEPARATE PRICE AND TECHNICAL PROPOSALS. Each offeror must submit both a Price Proposal and a Technical Proposal. The Price Proposal and Technical Proposal must be submitted as separate (CD-ROM) Discs. No hard paper copies will be accepted or evaluated. Both the Price Proposal and the Technical Proposal must be received by the closing date and time set for receipt of proposals. No dollar amounts from the Price Proposal are to be included in the Technical proposal. All information intended to be evaluated as part of the Technical Proposal must be submitted as part of the Technical Proposal. Do not cross-reference similar material in the Price Proposal, or vice versa. Do not include exceptions to the terms and conditions of the solicitation in either the technical or price proposal. Should the offer include any standard company terms and conditions that conflict with the terms and conditions of the solicitation, the offer may be determined “unacceptable” and thus ineligible for award. Should the offeror have any questions related to specific terms and conditions, these should be resolved prior to the submission of the offer. The technical data criteria specified for each factor identified herein and as described in Appendix B shall be submitted as part of the proposal. The contractor is responsible for including sufficient details in its proposal to permit a complete and accurate evaluation. Accordingly, the Contractor shall be clear and concise in its proposal. The Government will not make assumptions concerning the Contractor’s intent. Failure to submit all the data required by the RFP, this Appendix and Appendix B, may be cause for determining a proposal incomplete and, therefore, not considered for award.
Sample 1
AutoNDA by SimpleDocs

Related to REQUIREMENT FOR SEPARATE PRICE AND TECHNICAL PROPOSALS

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

  • PAYMENT FOR GOODS AND SERVICES a. DIR Customer shall comply with Chapter 2251, Texas Government Code, or applicable local law, in making payments to the Vendor. Payment under a DIR Contract shall not foreclose the right to recover wrongful payments.

  • Technical Proposal The technical proposal may be presented in free format. It shall not exceed ten pages, not counting the CVs. It shall respect the following page limit and structure: • Technical methodology (max. 7 pages) • Quality management (max. 1 page) • Project management (max. 1 page) • Resource management (proposal (max. 1 page) + CVs of experts)

  • Price Schedule, Payment Terms and Billing, and Price Adjustments (a) Price Schedule: Price Schedule under this Contract is set forth in Exhibit B.

  • Technical Proposals Technical proposal information will be streamlined, e.g., the Government anticipates written proposals consisting of thirty (30) pages or less stating compliance or exception to requirements, risks, assumptions and conflict of interest issues. Proposals shall not merely restate PWS/SOO requirements. Written technical proposals shall normally address: * Technical Approach and descriptive narrative of the contractor's understanding of the requested effort * PWS in response to a SOO * Integrated Master Plan (if applicable) * Integrated Master Schedule (if applicable) * Key Personnel Assigned * Quantities/Hours of Personnel by Labor Categories and narrative justification (if applicable) * Other Direct Costs (ODCs) (materials and supplies, travel, training, etc.(quantities and types only)) * Period of Performance * Government-Furnished Equipment (GFE)/Government-Furnished Information (GFI) * Security (including clearance level) * Teaming Arrangement (including subcontracting; identify new ACAs) * Small Business Plan (if a large business) * Other Pertinent Data, such as assumptions made.

  • Requirement for Project Planning No physical work will begin on the construction site until the receipt of a Proceed Order issued by the Owner. The Contract assumes that a Proceed Order will be issued in not more than sixty days from the Effective Date of the Contract. Failure of the Contractor to provide the necessary documentation for the issuance of a Proceed Order shall not entitle the Contractor to any extension of time. If a Proceed Order is not issued within sixty days from the award of the Contract and non-issuance is due to nonperformance by the Contractor, the Contractor may be in default.

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

  • OGS Centralized Contract: Terms and Conditions The terms and conditions set forth in this section are expressly incorporated in and applicable to the Contract. Captions are intended as descriptive and are not intended to limit or otherwise restrict the terms and conditions set forth herein. Appendix A Appendix A, Standard Clauses for New York State Contracts, dated January 2014, attached hereto, is hereby incorporated in, and expressly made a part of, this Contract. Appendix B Appendix B, Office of General Services General Specifications, dated January 2015 22772 Project Based Information Technology Consulting (Statewide), attached hereto, is hereby incorporated in, and expressly made a part of, this Contract.

  • Required Procurement Procedures for Obtaining Goods and Services The Grantee shall provide maximum open competition when procuring goods and services related to the grant-assisted project in accordance with Section 287.057, Florida Statutes.

  • Trunk Group Architecture and Traffic Routing The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows:

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