Common use of Proposal Preparation Clause in Contracts

Proposal Preparation. a. An authorized representative of the offeror shall sign proposals. All information requested must be submitted. Failure to submit all information requested may result in the Purchasing Agency requiring prompt submission of missing information and/or giving a lowered evaluation of the proposal. The Purchasing Agency may reject proposals, which are substantially incomplete or lack key information. Mandatory requirements are those required by law or regulation or are such that they cannot be waived and are not subject to negotiation. b. It is the policy of the Commonwealth of Virginia to contribute to the establishment, preservation and strengthening of small businesses and businesses owned by women and minorities and to encourage their participation in State procurement activities. The Commonwealth encourages contractors to provide for the participation of small businesses and businesses owned by women and minorities through partnerships, joint ventures, subcontracts, or other contractual opportunities. Submission of a report of past efforts to utilize the goods and services of such businesses and plans for involvement on this contract are required. By submitting a proposal, offerors certify that all information provided in response to this RFP is true and accurate. Failure to provide information required by this RFP will ultimately result in rejection of the proposal. c. Proposals should be prepared simply and economically, providing a straightforward, concise description of capabilities to satisfy the requirements of the RFP. Emphasis should be on completeness and clarity of content. d. Proposals should be organized in the order in which the requirements are presented in the RFP. All pages of the proposal should be numbered. Each paragraph in the proposal should reference the paragraph number of the corresponding section of the RFP. It is also helpful to cite the paragraph number, sub-letter and repeat the text of the requirement as it appears in the RFP. If a response covers more than one page, the paragraph number and sub-letter should be repeated at the top of the next page. The proposal shall contain a table of contents, which cross-references the RFP requirements. Information, which the offeror desires to present, that does not fall within any of the requirements of the RFP should be inserted at an appropriate place or be attached at the end of the proposal and designated as additional material. Proposals that are not organized in this manner risk elimination from consideration if the evaluators are unable to find where the RFP requirements are specifically addressed. e. Each copy of the proposal shall be bound or contained in a single volume where practical. All documentation submitted with the proposal should be contained in that single volume. f. Ownership of all data, materials and documentation originated and prepared for the State pursuant to the RFP shall belong exclusively to the State and be subject to public inspection in accordance with the Virginia Freedom of Information Act. Trade secrets or proprietary information submitted by an offeror shall not be subject to public disclosure under the Virginia Freedom of Information Act; however, the offeror must invoke the protections of Section 2.2-4342F of the Code of Virginia, in writing, either before or at the time the data or other material is submitted. The written notice must specifically identify the data or materials to be protected and state the reasons why protection is necessary. The proprietary or trade secret materials must be identified by some distinct method such as highlighting or underlining and must indicate only the specific words, figures, or paragraphs that constitute trade secret or proprietary information. The classification of an entire proposal document, line item prices and/or total proposal prices as proprietary or trade secrets is not acceptable and will result in rejection of the proposal. g. All information requested by this RFP on the ownership, utilization and planned involvement of small businesses, women-owned businesses and minority-owned businesses must be submitted. If an offeror fails to submit all information requested, the purchasing agency may require prompt submission of missing information after the receipt of vendor proposals. h. All offerors who submit a proposal shall be financially responsible.

Appears in 1 contract

Samples: Standard Contract

AutoNDA by SimpleDocs

Proposal Preparation. a. An Proposals shall be signed by an authorized representative of the offeror shall sign proposalsofferor. All information requested must should be submitted. Failure to submit all information requested may result in the Purchasing Agency NCPS requiring prompt submission of missing information and/or giving a lowered evaluation of the proposal. The Purchasing Agency may reject proposals, Proposals which are substantially incomplete or lack key informationinformation may be rejected by NCPS. Mandatory requirements are those required by law or regulation or are such that they cannot be waived and are not subject to negotiation. b. It is the policy of the Commonwealth of Virginia to contribute to the establishment, preservation and strengthening of small businesses and businesses owned by women and minorities and to encourage their participation in State procurement activities. The Commonwealth encourages contractors to provide for the participation of small businesses and businesses owned by women and minorities through partnerships, joint ventures, subcontracts, or other contractual opportunities. Submission of a report of past efforts to utilize the goods and services of such businesses and plans for involvement on this contract are required. By submitting a proposal, offerors certify that all information provided in response to this RFP is true and accurate. Failure to provide information required by this RFP will ultimately result in rejection of the proposal. c. Proposals should be prepared simply and economically, providing a straightforward, concise description of capabilities to satisfy the requirements of the RFP. Emphasis should be placed on completeness and clarity of content. d. c. Proposals should be organized in the order in which the requirements are presented in the RFP. All pages of the proposal should be numbered. Each paragraph in the proposal should reference the paragraph number of the corresponding section of the RFP. It is also helpful to cite the paragraph number, sub-letter subletter, and repeat the text of the requirement as it appears in the RFP. If a response covers more than one page, the paragraph number and sub-letter subletter should be repeated at the top of the next page. The proposal shall should contain a table of contents, contents which cross-references the RFP requirements. Information, Information which the offeror desires to present, present that does not fall within any of the requirements of the RFP should be inserted at an appropriate place or be attached at the end of the proposal and designated as additional material. Proposals that are not organized in this manner risk elimination from consideration if the evaluators are unable to find where the RFP requirements are specifically addressed. d. As used in this RFP, the terms "must", "shall", "should" and “may” identify the criticality of requirements. "Must" and "shall" identify requirements whose absence will have a major negative impact on the suitability of the proposed solution. Items labeled as "should" or “may” are highly desirable, although their absence will not have a large impact and would be useful, but are not necessary. Depending on the overall response to the RFP, some individual "must" and "shall" items may not be fully satisfied, but it is the intent to satisfy most, if not all, "must" and "shall" requirements. The inability of an offeror to satisfy a "must" or "shall" requirement does not automatically remove that offeror from consideration; however, it may seriously affect the overall rating of the offerors’ proposal. e. Each copy of the proposal shall should be bound or contained in a single volume where practical. All documentation submitted with the proposal should be contained in that single volume. f. Ownership of all data, materials materials, and documentation originated and prepared for the State NCPS pursuant to the RFP shall belong exclusively to the State NCPS and be subject to public inspection in accordance with the Virginia Freedom of Information Act. Trade secrets or proprietary information submitted by an offeror shall not be subject to public disclosure under the Virginia Freedom of Information Act; however, the offeror must invoke the protections of Section Virginia Code § 2.2-4342F of the Code of Virginia4342(F), in writing, either before or at the time the data or other material is submitted. The written notice must specifically identify the data or materials to be protected and state the reasons why protection is necessary. The proprietary or trade secret materials material submitted must be identified by some distinct method such as highlighting or underlining and must indicate only the specific words, figures, or paragraphs that constitute trade secret or proprietary information. The classification of an entire proposal document, line item prices prices, and/or total proposal prices as proprietary or trade secrets is not acceptable and will result in rejection of the proposalacceptable. g. All information requested by this RFP on the ownership, utilization costs of proposal preparation and planned involvement of small businesses, women-owned businesses and minority-owned businesses must be submitted. If an offeror fails to submit all information requested, the purchasing agency may require prompt submission of missing information after the receipt of vendor proposals. h. All offerors who submit a proposal presentation shall be financially responsibleborne by each offeror. The County is not liable for any cost incurred by the offeror prior to issuance of a contract.

Appears in 1 contract

Samples: Solar Power Purchase Agreement Services

Proposal Preparation. a. An Proposals shall be signed by an authorized representative of the offeror shall sign offeror. b. Each Proposal must be and remain valid for a period of at least ninety (90) days from the date set by this RFP for receipt of proposals. . c. All information requested or required by this RFP must be submitted. Failure to submit all information requested may result in the Purchasing Agency requiring prompt submission of missing information and/or giving a lowered evaluation of the proposal. The Purchasing Agency may reject proposals, which are substantially incomplete or lack key information. Mandatory requirements are those required by law or regulation or are such that they cannot be waived and are not subject to negotiationan Offeror’s Proposal being rejected. b. It is the policy of the Commonwealth of Virginia to contribute to the establishment, preservation and strengthening of small businesses and businesses owned by women and minorities and to encourage their participation in State procurement activities. The Commonwealth encourages contractors to provide for the participation of small businesses and businesses owned by women and minorities through partnerships, joint ventures, subcontracts, or other contractual opportunities. Submission of a report of past efforts to utilize the goods and services of such businesses and plans for involvement on this contract are required. By submitting a proposal, offerors certify that all information provided in response to this RFP is true and accurate. Failure to provide information required by this RFP will ultimately result in rejection of the proposal. c. d. Proposals should be prepared simply and economicallysimply, providing a clear, straightforward, concise description of capabilities the Offeror’s qualifications and suitability to satisfy provide the required services, and of the Offeror’s capabilities, in all respects, to perform fully the requirements of this RFP, and the RFP. Emphasis should be on completeness Offeror’s integrity and clarity reliability that will assure good faith performance of contentthe Project requirements. d. e. Proposals should be organized in the order in which the requirements are presented in the RFP. All pages of the proposal should be numbered. Each paragraph in the proposal should reference the paragraph number of the corresponding section of the RFP. It is also helpful to cite the paragraph number, sub-letter paragraph, and repeat the text of the requirement as it appears in the RFP. If a response covers more than one page, the paragraph number and sub-letter paragraph number should be repeated at the top of the next page. The proposal shall should contain a table of contents, contents which cross-references the RFP requirements. Information, Information which the offeror Offeror desires to present, present that does not fall within any of the requirements of the RFP should be inserted at an appropriate place or be attached at the end of the proposal and designated as additional material. Proposals that are not organized in this manner risk elimination from consideration if the evaluators are unable to find where the RFP requirements are specifically addressed. e. f. As used in this RFP, the terms "must", “will” and "shall" identify mandatory requirements. Items labeled as "should" or “may” are highly desirable, and are preferred. Depending on the overall quality and completeness of a Proposal, inability of an Offeror to satisfy a "must", “will” or "shall" requirement may not automatically remove that Offeror from consideration; however, it may affect the overall rating of the Offerors’ proposal. g. Each copy of the proposal shall Proposal should be bound or contained in a single volume where practical. All documentation submitted with the proposal should be contained in that single volume. f. Ownership of all datah. All proceedings, materials records, contracts and documentation originated and prepared for the State pursuant other records relating to the RFP this procurement transaction shall belong exclusively to the State and be subject open to public inspection in accordance with the Virginia Freedom of Information Act. Trade secrets or proprietary information submitted by an offeror shall not be subject to public disclosure under the Virginia Freedom of Information Act; however, the offeror must invoke the protections of Section § 2.2-4342F of the Code of Virginia, in writing, either before or at the time the data or other material is submitted. The written notice must specifically identify the data or materials to be protected and state the reasons why protection is necessary. The proprietary or trade secret materials material submitted must be identified by some distinct method such as highlighting or underlining and must indicate only the specific words, figures, or paragraphs that constitute trade secret or proprietary information. The classification of an entire proposal document, line item prices prices, and/or total proposal prices as proprietary or trade secrets is not acceptable acceptable. Offerors, upon request, shall be afforded the opportunity to inspect proposal records within a reasonable time after the evaluation and will result negotiations of proposals are completed, but prior to award, except in rejection the event that the City decides not to accept any of the proposalproposals and to reopen the contract. Otherwise, proposal records shall be open to public inspection only after award of a contract by the City. g. i. All information requested by this RFP on the ownership, utilization costs of proposal preparation and planned involvement of small businesses, women-owned businesses and minority-owned businesses must be submitted. If an offeror fails to submit all information requested, the purchasing agency may require prompt submission of missing information after the receipt of vendor proposals. h. All offerors who submit a proposal presentation shall be financially responsibleborne by each offeror. The City is not liable for any cost incurred by the offeror prior to issuance of a contract.

Appears in 1 contract

Samples: Amendment to Agreement No. 23 Pol R 653

Proposal Preparation. a. An Proposals shall be signed by an authorized representative of the offeror shall sign proposalsofferor. All information requested must should be submitted. Failure to submit all information requested may result in the Purchasing Agency County of Northampton requiring prompt submission of missing information and/or giving a lowered evaluation of the proposal. The Purchasing Agency may reject proposals, Proposals which are substantially incomplete or lack key informationinformation may be rejected by the County. Mandatory requirements are those required by law or regulation or are such that they cannot be waived and are not subject to negotiation. b. It is the policy of the Commonwealth of Virginia to contribute to the establishment, preservation and strengthening of small businesses and businesses owned by women and minorities and to encourage their participation in State procurement activities. The Commonwealth encourages contractors to provide for the participation of small businesses and businesses owned by women and minorities through partnerships, joint ventures, subcontracts, or other contractual opportunities. Submission of a report of past efforts to utilize the goods and services of such businesses and plans for involvement on this contract are required. By submitting a proposal, offerors certify that all information provided in response to this RFP is true and accurate. Failure to provide information required by this RFP will ultimately result in rejection of the proposal. c. Proposals should be prepared simply and economically, providing a straightforward, concise description of capabilities to satisfy the requirements of the RFP. Emphasis should be placed on completeness and clarity of content. d. c. Proposals should be organized in the order in which the requirements are presented in the RFP. All pages of the proposal should be numbered. Each paragraph in the proposal should reference the paragraph number of the corresponding section of the RFP. It is also helpful to cite the paragraph number, sub-letter sub letter, and repeat the text of the requirement as it appears in the RFP. If a response covers more than one page, the paragraph number and sub-sub letter should be repeated at the top of the next page. The proposal shall should contain a table of contents, contents which cross-references the RFP requirements. Information, Information which the offeror desires to present, present that does not fall within any of the requirements of the RFP should be inserted at an appropriate place or be attached at the end of the proposal and designated as additional material. Proposals that are not organized in this manner risk elimination from consideration if the evaluators are unable to find where the RFP requirements are specifically addressed. d. As used in this RFP, the terms "must", "shall", "should" and “may” identify the criticality of requirements. "Must" and "shall" identify requirements whose absence will have a major negative impact on the suitability of the proposed solution. Items labeled as "should" or “may” are highly desirable, although their absence will not have a large impact and would be useful, but are not necessary. Depending on the overall response to the RFP, some individual "must" and "shall" items may not be fully satisfied, but it is the intent to satisfy most, if not all, "must" and "shall" requirements. The inability of an offeror to satisfy a "must" or "shall" requirement does not automatically remove that offeror from consideration; however, it may seriously affect the overall rating of the offeror’s proposal. e. Each copy of the proposal shall should be bound or contained in a single volume where practical. All documentation submitted with the proposal should be contained in that single volume. f. Ownership of all data, materials materials, and documentation originated and prepared for the State County pursuant to the RFP shall belong exclusively to the State County and be subject to public inspection in accordance with the Virginia Freedom of Information Act. Trade secrets or proprietary information submitted by an offeror shall not be subject to public disclosure under the Virginia Freedom of Information Act; however, the offeror must invoke the protections of Section § 2.2-4342F of the Code of Virginia, in writing, either before or at the time the data or other material is submitted. The written notice must specifically identify the data or materials to be protected and state the reasons why protection is necessary. The proprietary or trade secret materials material submitted must be identified by some distinct method such as highlighting or underlining and must indicate only the specific words, figures, or paragraphs that constitute trade secret or proprietary information. The classification of an entire proposal document, line item prices prices, and/or total proposal prices as proprietary or trade secrets is not acceptable and will result in rejection of the proposal. g. All information requested by this RFP on the ownership, utilization and planned involvement of small businesses, women-owned businesses and minority-owned businesses must be submitted. If an offeror fails to submit all information requested, the purchasing agency may require prompt submission of missing information after the receipt of vendor proposals. h. All offerors who submit a proposal shall be financially responsible.

Appears in 1 contract

Samples: Maintenance and Support Agreement

AutoNDA by SimpleDocs

Proposal Preparation. a. An Proposals shall be signed by an authorized representative of the offeror shall sign proposalsofferor. All information requested must should be submitted. Failure to submit all information requested may result in the Purchasing Agency CCPS requiring prompt submission of missing information and/or giving a lowered evaluation of the proposal. The Purchasing Agency may reject proposals, Proposals which are substantially incomplete or lack key informationinformation may be rejected by CCPS. Mandatory requirements are those required by law or regulation or are such that they cannot be waived and are not subject to negotiation. b. It is the policy of the Commonwealth of Virginia to contribute to the establishment, preservation and strengthening of small businesses and businesses owned by women and minorities and to encourage their participation in State procurement activities. The Commonwealth encourages contractors to provide for the participation of small businesses and businesses owned by women and minorities through partnerships, joint ventures, subcontracts, or other contractual opportunities. Submission of a report of past efforts to utilize the goods and services of such businesses and plans for involvement on this contract are required. By submitting a proposal, offerors certify that all information provided in response to this RFP is true and accurate. Failure to provide information required by this RFP will ultimately result in rejection of the proposal. c. Proposals should be prepared simply and economically, providing a straightforward, concise description of capabilities to satisfy the requirements of the RFP. Emphasis should be placed on completeness and clarity of contentofcontent. d. c. Proposals should be organized in the order in which the requirements are presented in the RFP. All pages of the proposal should be numbered. Each paragraph in the proposal should reference the paragraph number of the corresponding section of the RFP. It is also helpful to cite the paragraph number, sub-letter sub letter, and repeat the text of the requirement as it appears in the RFP. If a response covers more than one page, the paragraph number and sub-sub letter should be repeated at the top of the next page. The proposal shall should contain a table of contents, contents which cross-references the RFP requirements. Information, Information which the offeror desires to present, present that does not fall within any of the requirements of the RFP should be inserted at an appropriate place or be attached at the end of the proposal and designated as additional material. Proposals that are not organized in this manner risk elimination from consideration if the evaluators are unable to find where the RFP requirements are specifically addressed. d. As used in this RFP, the terms "must", "shall", "should" and “may” identify the criticality of requirements. "Must" and "shall" identify requirements whose absence will have a major negative impact on the suitability of the proposed solution. Items labeled as "should" or “may” are highly desirable, although their absence will not have a large impact, and would be useful, but are not necessary. Depending on the overall response to the RFP, some individual "must" and "shall" items may not be fully satisfied, but it is the intent to satisfy most, if not all, “must” and “shall" requirements. The inability of an offeror to satisfy a "must" or "shall" requirement does not automatically remove that offeror from consideration; however, it may seriously affect the overall rating of the offeror’s proposal. e. Each copy of the proposal shall should be bound or contained in a single volume where practical. All documentation submitted with the proposal should be contained in that single volume. f. Ownership of all data, materials materials, and documentation originated and prepared for the State CCPS pursuant to the RFP shall belong exclusively to the State CCPS and be subject to public inspection in accordance with the Virginia Freedom of Information Act. Trade secrets or proprietary information submitted by an offeror shall may not be subject to public disclosure under the Virginia Freedom of Information Act; however, the offeror must invoke the protections of Section Virginia Code § 2.2-4342F of the Code of Virginia4342(F), in writing, either before or at the time the data or other material is submitted. The To be considered, the written notice must specifically identify the data or materials to be protected and state the reasons why protection is necessary. The proprietary or trade secret materials material submitted must be identified by some distinct method such as highlighting or underlining and must indicate only the specific words, figures, or paragraphs that constitute trade secret or proprietary information. The classification of an entire proposal document, line item prices prices, and/or total proposal prices as proprietary or trade secrets is not acceptable and will result in rejection of the proposalacceptable. g. All information requested by this RFP on the ownership, utilization costs of proposal preparation and planned involvement of small businesses, women-owned businesses and minority-owned businesses must be submitted. If an offeror fails to submit all information requested, the purchasing agency may require prompt submission of missing information after the receipt of vendor proposals. h. All offerors who submit a proposal presentation shall be financially responsibleborne by each offeror. CCPS is not liable for any cost incurred by the offeror prior to issuance of a contract.

Appears in 1 contract

Samples: Solar Power Purchase Agreement Services

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